Slide 2
Quiz 1: Lectures 1-6
10 MCQs, 1 mark each
8 minutes of writing
Closed book: no notes, no phones
minutes in all
Name and roll number first
- 1 min hand out
- 8 min write
- 1 min collect
Paper A and Paper B in alternate rows
SE Lecture 8
Quiz 1
Sheet 02 of 18
Slide 3
Last lecture: the four layers
Tools Trello, draw.io, GitHub
- Exit-ticket fix
- "Tools: Scrum" is wrong.
- Scrum = process
- Trello = tool
- User stories = method
Methods User stories, UML, testing
Process TODAY: what is inside this layer?
A quality focus Definition of Done
Today: the parts every process model is built from: framework activities, umbrella activities, process flows, task sets and process patterns.
SE Lecture 8
Recap
Sheet 03 of 18
Slide 4
Learning outcomes
SLO 8.1
Describe the five framework activities and the eight umbrella activities
→ CLO1 · C2 Understand
SLO 8.2
Compare the four process flows and link them to process models
→ CLO1 · C2 Understand
SLO 8.3
Write a task set for a framework activity and explain process patterns
→ CLO1 · C3 Apply
CLO1: Explain application of software engineering processes and techniques to various types of software.
SE Lecture 8
Outcomes
Sheet 04 of 18
Slide 5
Today's plan: 50 minutes
0-10 min
Quiz 1
Coming up
10-14 min
Recap, outcomes, plan
- Practicals 07-08: your SRS
- Lecture 09: specialized process models and the Unified Process
14-24 min
Framework and umbrella activities
24-30 min
Process flows
30-37 min
Task sets and process patterns
37-44 min
Activity: design part of your process
44-48 min
Common mistakes and recap quiz
48-50 min
Homework and exit ticket
SE Lecture 8
Plan
Sheet 05 of 18
Slide 6
Five framework activities
Communication
Planning
Modeling
Construction
Deployment
Understand stakeholders' goals; gather requirements
Project plan: tasks, risks, resources, work products, schedule
Models of requirements and design
Code generation AND testing
Deliver; customer evaluates and gives feedback
Meet the canteen manager and students
Two-week sprints; payment risk
User stories, screens, class diagram
Order screen + its unit tests
Version 1 in the canteen
Used again and again: every Scrum sprint contains all five, for one increment.
SE Lecture 8
Framework
Sheet 06 of 18
Slide 7
Eight umbrella activities: across the whole project
- Project tracking and control
- Burndown, sprint review
- Risk management
- "API may be late": plan B
Real-world example: a wedding
- Software quality assurance
- Definition of Done, test plan
- Technical reviews
- Teammate reviews a diagram
- Main events in order: mehndi, barat, walima.
- Across all of them: budget tracking, food-quality checks, guest-list changes, photos. Those are the 'umbrella'.
- Measurement
- Velocity, defects per sprint
- Configuration management
- Git branches and tags
- Reusability management
- Reuse a login component
- Work product preparation
- SRS, manual, release notes
Word help
umbrella activity = work that runs across the whole project metric = a measurement
Many are taught later: SQA (L27), project management (L31), SCM (L32).
SE Lecture 8
Umbrella
Sheet 07 of 18
Slide 8
Activities, actions and task sets
- Framework activity
- Modeling
Sommerville (Lecture 1) → Pressman
- SE actions
- Requirements modeling · Design modeling
- Task set (for each action)
- Work tasks · work products · quality checkpoints · milestones
Milestone = an important point, e.g. "design approved". A task set lists the tasks, what they produce, how quality is checked and which milestones they reach.
SE Lecture 8
Framework
Sheet 08 of 18
Slide 9
Four process flows
Linear each activity once, in order (Waterfall)
Iterative repeat an activity before moving on
Com
→
Plan
→
Model
→
Constr
→
Deploy
Com
→
Plan
→
Model
→
Constr
→
Deploy
one pass from start to finish
↺ e.g. communication and modeling repeated
Evolutionary loops; each loop = a better version
Parallel activities at the same time
Com
Deploy
Plan
Incremental, Spiral, Scrum, XP: a new increment every loop
Model
design one screen while coding another
Constr
Constr
Model
Deploy
SE Lecture 8
Process flows
Sheet 09 of 18
Slide 10
Quick check: name the flow
A
All requirements, then all design, then all code, then one deployment.
Linear
B
Three meetings to refine requirements before design starts.
Iterative
C
A better version of the app every two weeks.
Evolutionary
D
The UI designer sketches the payment screen while developers code the menu.
Parallel
Say the flow before your teacher reveals it.
SE Lecture 8
Process flows
Sheet 10 of 18
Slide 11
One activity, two task sets: communication
Choose the task set that fits the project's size, risk and team. Too heavy wastes weeks; too light misses requirements. (Large set in detail: Lectures 12-15.)
SE Lecture 8
Task sets
Sheet 11 of 18
Slide 12
Process patterns: proven solutions to recurring problems
Pattern name
Forces
Type
Three types
- Stage: a problem in one framework activity
- e.g. EstablishingCommunication
Initial context
Problem
Solution
- Task: a problem in one action or task
- e.g. RequirementsGathering
Resulting context
Related patterns
Known uses
- Phase: the order of framework activities
- e.g. Prototyping, SpiralModel
Ambler's template
Word help
pattern = a proven solution to a problem that happens again and again context = the situation around something
Why: teams reuse solutions that worked before, instead of inventing a new one every time.
SE Lecture 8
Patterns
Sheet 12 of 18
Slide 13
Example pattern: RequirementsUnclear
Type
Phase pattern
Initial context
Stakeholders known; main problem known; scope roughly understood
Problem
Requirements are hazy or missing, but everyone agrees there is a problem
Solution
Build a PROTOTYPE; stakeholders try it; improve it in short loops
Resulting context
A prototype showing the basic requirements, approved by stakeholders
Known uses
A first app for farmers who have never used one
Based on Pressman's example. Related patterns: CustomerCommunication, IterativeDesign, IterativeDevelopment.
SE Lecture 8
Patterns
Sheet 13 of 18
Slide 14
Activity: design part of your process
In your project teams:
Write a task set (4-6 tasks) for the DEPLOYMENT activity of one sprint.
Choose your process flow and give one reason.
Name one umbrella activity you will do every sprint, and how.
minutes
- 5 min in teams
- 2 min to share
Tip: deployment must include customer feedback.
SE Lecture 8
Activity
Sheet 14 of 18
Slide 15
Common mistakes
"Umbrella activities are a sixth step at the end."
✗
They run across the whole project
"Construction means coding only."
✗
Construction = code + testing
"Deployment ends the project."
✗
It brings feedback that starts the next cycle
"Every project needs the same task set."
✗
Fit the task set to size, risk and team
"Iterative = evolutionary."
✗
Iterative repeats a step; evolutionary grows versions
SE Lecture 8
Mistakes
Sheet 15 of 18
Slide 16
Recap quiz: hands up
Name the five framework activities in order.
Risk management and SQA are examples of what kind of activity?
Scrum releasing a better version every sprint is which process flow?
Construction includes which two things?
Name the three types of process patterns.
SE Lecture 8
Recap quiz
Sheet 16 of 18
Slide 17
Before the next lecture
Read
Team task: your SRS
Pressman 2.2 and 3.1-3.4. Skim 4.2-4.4 for Lecture 09.
- Finish the SRS sections started in Practicals 07-08
- Every functional requirement traced to a user story
- Fix the issues from the peer review
- Upload the SRS to the LMS before Practical 09
Next lecture
Lecture 09: specialized process models and the Unified Process.
SE Lecture 8
Homework
Sheet 17 of 18
Slide 18
Exit ticket
On a small piece of paper, with your name and roll number:
Name ONE umbrella activity your team will do every sprint, and HOW you will do it.
One question you still have.
Questions?
SE Lecture 8
Exit ticket
Sheet 18 of 18