How to use these notes: section numbers (§1.1, §1.2 ...) match the question bank. "Slide L08-S07" means slide 7 of this lecture. Difficult words are explained in "Word help" boxes and in the word bank at the end.
Learning outcomes
By the end of this lecture you should be able to:
SLO | Learning outcome | CLO | Bloom | Slides |
|---|---|---|---|---|
SLO 8.1 | Describe the five framework activities and the eight umbrella activities of the generic process model. | CLO1 | C2 Understand | L08-S06 to S08 |
SLO 8.2 | Compare the four process flows (linear, iterative, evolutionary, parallel) and link them to process models. | CLO1 | C2 Understand | L08-S09, S10 |
SLO 8.3 | Write a task set for a framework activity and explain process patterns. | CLO1 | C3 Apply | L08-S11 to S14 |
In Lecture 07 we saw that process is the foundation layer of software engineering. Today we open that layer and look inside. Every process model you have studied (Waterfall, Spiral, Scrum, XP, Kanban) is built from the same parts: framework activities, umbrella activities, a process flow, task sets and process patterns. Once you know the parts, you can understand, compare or design any process.
§1 Recap: software and its layers
Slides L08-S03
§1.1 From Lecture 07
Slide L08-S03
Software is developed, not manufactured; it does not wear out but deteriorates with change; and SE rests on four layers: quality focus → process → methods → tools. Today: the process layer.
Exit-ticket check: "Tools: Scrum" is wrong. Scrum is a process; Trello is a tool; user stories are a method.
§2 The process framework
Slides L08-S06 to L08-S08
§2.1 Five framework activities
Slide L08-S06
A process framework is the basic structure of every software process. Pressman's generic framework has five framework activities, used in almost every project, small or large:
Framework activity | Purpose | UAF cafeteria pre-order app |
|---|---|---|
1. Communication | Talk with the customer and other stakeholders to understand their goals and gather requirements. | Meet the canteen manager and some students; list what they need. |
2. Planning | Make a map (the project plan): technical tasks, risks, resources, work products and a schedule. | Plan two-week sprints, who does what, and the risk of payment API delays. |
3. Modeling | Create models (sketches) of the requirements and the design to understand them better. | User stories, a use case diagram, screen sketches, a class diagram. |
4. Construction | Generate the code and test it to find errors. | Write the order screen and its unit tests. |
5. Deployment | Deliver the software (a complete product or an increment) to the customer, who evaluates it and gives feedback. | Release version 1 in the canteen; collect feedback after a week. |
These five activities are used again and again: in a Scrum project, each sprint contains communication, planning, modeling, construction and deployment of an increment.
Word help framework = a basic structure that you fill in for each project deployment = delivering the software to its users |
§2.2 Eight umbrella activities
Slide L08-S07
Umbrella activities run across the whole project, from start to finish, like an umbrella over all five framework activities. They help the team manage progress, quality, change and risk:
Umbrella activity | What it does | Example |
|---|---|---|
Software project tracking and control | Compare progress with the plan; act to keep to the schedule. | Burndown chart; sprint review |
Risk management | Find risks that could hurt the project or quality, and plan for them. | "The payment API may be late" → plan cash at the counter |
Software quality assurance (SQA) | Define and carry out activities that ensure quality. | Definition of Done; test plan |
Technical reviews | Check work products to find and remove errors before they move on. | A teammate reviews the class diagram |
Measurement | Collect process, project and product measures (metrics). | Velocity, defects found per sprint |
Software configuration management (SCM) | Manage the effects of change across the whole process. | Git branches and version tags |
Reusability management | Set rules for reusing work products and components. | Reuse a login component in two apps |
Work product preparation and production | Create documents, models, logs, forms and lists. | SRS, user manual, release notes |
Real-world example: a Pakistani wedding The main events happen in order: mehndi, barat, walima (like framework activities). Some work runs over the whole wedding: tracking the budget, checking the food quality, managing guest-list changes, photography (like umbrella activities). |
Word help umbrella activity = work that runs across the whole project, not in one step only metric = a measurement, such as defects per week |
§2.3 Activities, actions and task sets
Slide L08-S08
Pressman builds the process in three levels:
1. Framework activity (e.g. modeling).
2. Software engineering actions inside it (e.g. requirements modeling, design modeling).
3. Task set for each action: the work tasks, the work products, the quality checkpoints and the milestones.
Link to Lecture 1: Sommerville's four activities map onto Pressman's five.
Sommerville (Lecture 1) | Pressman framework activities |
|---|---|
Specification | Communication (+ requirements modeling) |
Development | Planning, modeling (design) and construction (code) |
Validation | Construction (testing); customer evaluation in deployment |
Evolution | Deployment feedback that starts the next cycle |
Word help action = a set of tasks that produces a major work product, e.g. design modeling milestone = an important point in the project, e.g. 'design approved' |
§3 Process flows
Slides L08-S09 to L08-S10
§3.1 Four ways to organise the activities
Slide L08-S09
Process flow describes how the framework activities (and the actions and tasks inside them) are organised in sequence and time:
Process flow | How it works | Seen in |
|---|---|---|
Linear | Each of the five activities is done once, one after another, from communication to deployment. | Waterfall |
Iterative | One or more activities are repeated before moving to the next. | Repeating communication and modeling until the requirements are clear |
Evolutionary | The activities run in a circle; each circuit produces a more complete version of the software. | Incremental, Spiral, Scrum, XP |
Parallel | One or more activities run at the same time as others. | Modeling one part while constructing another |
Real-world example: making a family dinner Linear: cook rice, then curry, then salad, one after the other. Iterative: taste and adjust the curry several times before serving. Evolutionary: serve a simple dinner today, improve the recipe each week. Parallel: one person cooks rice while another makes the salad. |
Word help linear = in a straight line, one step after another parallel = happening at the same time |
§3.2 Worked quick check: name the flow
Slide L08-S10
Situation | Flow |
|---|---|
A government project finishes all requirements, then all design, then all code, then deploys once. | Linear |
The team meets the client three times to refine requirements before starting design. | Iterative |
Every two weeks the team releases a better version of the app. | Evolutionary |
The UI designer sketches the payment screen while developers code the menu screen. | Parallel |
§4 Task sets and process patterns
Slides L08-S11 to L08-S13
§4.1 Defining a framework activity with a task set
Slide L08-S11
The same framework activity needs different task sets for different projects. The task set must fit the project's size, risk and the team. Example: the communication activity.
Small, simple project (cafeteria app) | Large, complex project (national tax system) |
|---|---|
1. List the stakeholders. | 1. Inception: identify stakeholders, business need and scope. |
2. Invite them to one informal meeting. | 2. Elicitation: structured meetings and interviews with many groups. |
3. Ask each to list the features they need. | 3. Elaboration: build detailed requirements models. |
4. Discuss and agree a final list. | 4. Negotiation: resolve conflicts between groups. |
5. Prioritise the list. | 5. Specification: write a formal requirements document. |
6. Note areas that are still unclear. | 6. Validation: formal reviews of the requirements. |
A small team that uses the large task set wastes weeks. A large project that uses the small task set misses important requirements. Choose the task set that fits. (We study the large set in detail in Lectures 12-15.)
Word help task set = the actual work tasks, work products and checkpoints for one action stakeholder = anyone who affects or is affected by the system |
§4.2 Process patterns
Slide L08-S12
A process pattern describes a process-related problem that teams meet again and again, the environment in which it happens, and a proven solution. Patterns let teams reuse good solutions instead of inventing them each time. Ambler's template:
Part | Meaning |
|---|---|
Pattern name | A short, meaningful name, e.g. RequirementsUnclear. |
Forces | The issues that make the problem hard and shape the solution. |
Type | Stage pattern (a problem in one framework activity), task pattern (a problem in one action or task) or phase pattern (the order of framework activities). |
Initial context | What must already be true before the pattern is used. |
Problem | The specific problem the pattern solves. |
Solution | How to solve it. |
Resulting context | What is true after the pattern is used successfully. |
Related patterns | Other patterns used with this one. |
Known uses and examples | Where the pattern has worked. |
Word help pattern = a proven solution to a problem that happens again and again context = the situation around something |
§4.3 Example pattern: RequirementsUnclear
Slide L08-S13
Part | RequirementsUnclear (based on Pressman's example) |
|---|---|
Type | Phase pattern |
Initial context | Stakeholders are identified; communication is set up; the main problem is known; scope is roughly understood. |
Problem | Requirements are hazy or missing, yet everyone agrees there is a problem to solve. |
Solution | Build a prototype, let stakeholders try it, and improve it in short loops until the requirements are clear. |
Resulting context | A prototype that shows the basic requirements, approved by stakeholders. |
Related patterns | CustomerCommunication, IterativeDesign, IterativeDevelopment. |
Known uses | Recommended whenever requirements are uncertain, e.g. a new app for farmers who have never used one. |
§5 Worked activity: design part of your process
Slides L08-S14
§5.1 The task and a model answer
Slide L08-S14
In project teams (7 minutes), for your own project: (1) write a task set of 4-6 tasks for the deployment activity of one sprint; (2) choose your process flow and give one reason; (3) name one umbrella activity you will do every sprint and how.
Part | Model answer (cafeteria app) |
|---|---|
Deployment task set | 1. Run all tests and check the Definition of Done. 2. Upload the build to the test phone / web host. 3. Show it to the canteen manager in the sprint review. 4. Record feedback as new backlog items. 5. Write short release notes. 6. Tag the version in Git. |
Process flow | Evolutionary: we deliver a better version every two weeks, because requirements are still changing. |
Umbrella activity | Technical reviews: every pull request is reviewed by one teammate before merging. (Also good: SCM with Git tags; risk management in each planning meeting.) |
Accept other sensible answers. Check that deployment tasks include customer feedback, and that the umbrella activity really runs every sprint.
§6 Common mistakes
Slides L08-S15
§6.1 Five mistakes
Slide L08-S15
Mistake | Correct idea |
|---|---|
"Umbrella activities are a sixth step at the end." | They run across the whole project, alongside all five activities. |
"Construction means coding only." | Construction is code generation AND testing. |
"Deployment ends the project." | Deployment includes customer evaluation and feedback that starts the next cycle. |
"Every project needs the same task set." | The task set must fit the project's size, risk and team. |
"Evolutionary and iterative flows are the same." | Iterative repeats activities before moving on; evolutionary loops through all activities to grow versions. |
Summary
- Generic process framework: five framework activities: communication, planning, modeling, construction, deployment.
- Eight umbrella activities run across the whole project: tracking and control, risk management, SQA, technical reviews, measurement, SCM, reusability management, work product preparation.
- Levels: framework activity → software engineering actions → task sets (tasks, work products, quality checkpoints, milestones).
- Four process flows: linear, iterative, evolutionary, parallel.
- The task set must fit the project: small projects need light task sets; large ones need formal ones.
- Process patterns record proven solutions to recurring process problems; types: stage, task, phase.
- Before Lecture 09: read Pressman 2.2 and 3.1-3.4; skim 4.2-4.4 (specialized models, Unified Process). Finish your SRS from Practicals 07-08.
Word bank
Word | Simple meaning | Example |
|---|---|---|
process framework | the basic structure of every software process | the five framework activities |
framework activity | one of the five main kinds of work | modeling |
umbrella activity | work that runs across the whole project | risk management |
SQA | software quality assurance: activities that ensure quality | Definition of Done, test plan |
SCM | software configuration management: controlling change | Git branches and tags |
technical review | checking a work product to remove errors | a teammate reviews a diagram |
SE action | a set of tasks that makes a major work product | design modeling |
task set | tasks, work products, checkpoints and milestones for an action | six tasks for communication |
milestone | an important point in a project | design approved |
linear flow | activities once, in sequence | Waterfall |
iterative flow | repeat an activity before moving on | refine requirements three times |
evolutionary flow | loop through all activities, each loop a better version | Scrum sprints |
parallel flow | activities at the same time | design one screen while coding another |
process pattern | a proven solution to a recurring process problem | RequirementsUnclear → prototyping |
Self-check questions
Try each question without looking. Then check your answer in the section shown.
# | Question | See |
|---|---|---|
1 | List the five framework activities and say what each produces. | §2.1 |
2 | What is the difference between a framework activity and an umbrella activity? | §2.1, §2.2 |
3 | Name any six umbrella activities with an example of each. | §2.2 |
4 | Explain the levels framework activity → action → task set with an example. | §2.3 |
5 | Map Sommerville's four activities onto Pressman's five. | §2.3 |
6 | Describe the four process flows and name a model that uses each. | §3.1 |
7 | "The UI designer sketches one screen while developers code another." Which flow? | §3.2 |
8 | Write a communication task set for a small project and for a large project. | §4.1 |
9 | List the parts of Ambler's process pattern template. | §4.2 |
10 | Name the three types of process patterns with an example of each. | §4.2 |
11 | Describe the RequirementsUnclear pattern. | §4.3 |
Further reading
- Pressman & Maxim, 8th ed., section 2.2 (the process framework) and Chapter 3, sections 3.1-3.4.
- Look ahead: Pressman 4.2-4.4 (specialized process models and the Unified Process) for Lecture 09.