Slide 2
Last lecture in one minute
Specification
Development
Validation
Evolution
Decide what the software must do
Design and build it
Check it is what users need
Change it over time
Today: every team does these four activities. A process model is a plan that tells the team in what order to do them, and how many times to repeat them.
SE Lecture 2
Recap
Sheet 02 of 19
Slide 3
By the end of today, you will be able to
Explain what a software process and a process model are
Compare plan-driven and agile ways of working
Describe four models: Waterfall, Incremental, Integration and configuration, and Spiral
Say what each model is good at, and where it fails
Explain why change is the main problem every model must handle
Choose a model for a real project and give reasons
SE Lecture 2
Objectives
Sheet 03 of 19
Slide 4
Today's plan: 60 minutes
0-5 min
Welcome, recap, your questions
5-12 min
What a process model is; plan-driven vs agile
12-22 min
The Waterfall model and the V-model
22-30 min
Incremental development
30-35 min
Integration and configuration (reuse)
35-42 min
The Spiral model, and dealing with change
42-52 min
Group activity: choose the model
52-60 min
Comparison, key points, homework, exit ticket
SE Lecture 2
Plan
Sheet 04 of 19
Slide 5
Process and process model
Software process
Real-world example: biryani
The steps a team actually follows to build one software system.
- A biryani recipe is like a process model: the general steps everyone knows.
- What your mother actually does in her kitchen today is the process. Every home changes the recipe a little, but it is still biryani.
Process model
A general plan for how to build software. Teams change it to fit their project. It is a guide, not strict rules.
Word help
model = a simple picture or plan of something real framework = a basic structure you build on
SE Lecture 2
Concepts
Sheet 05 of 19
Slide 6
Plan-driven or agile? A range, not two teams
Plan-driven
Agile
Waterfall
V-model
Spiral
Incremental
Scrum, XP
Plan-driven
Agile
Plan everything first, then follow the plan. Progress = how much of the plan is done.
Plan a little, build a little, learn, and change the plan often.
Example: building a motorway. The route, bridges and budget are fixed before work starts.
Example: a food delivery app. The team adds and changes features every few weeks based on what customers do.
Word help
agile = quick and able to change direction easily
SE Lecture 2
Concepts
Sheet 06 of 19
Slide 7
The Waterfall model: one step after another
- Requirements
- What must the system do?
Real-world example: building a house
- Design
- How will it be built?
- First the map, then the foundation, then walls, then the roof.
- If you want a basement after the roof is built, it is very costly. Waterfall software works the same way.
- Coding and unit testing
- Write and test each part
- Integration and system testing
- Join parts, test the whole
- Operation and maintenance
- Use it, fix it, improve it
Word help
sign off = formally approve a step before moving on maintenance = fixing and improving software after it is in use
SE Lecture 2
Waterfall
Sheet 07 of 19
Slide 8
When Waterfall works, and when it hurts
Use it when
Watch out for
- Requirements are clear and will not change much
- The system is safety-critical and needs full checks and documents
- Software is part of a hardware project with a fixed schedule
- A fixed contract needs an approved specification first
- Big decisions are made early, when we know the least
- Working software appears only near the end
- Customers see the product too late to change it cheaply
- Problems are pushed to later and patched afterwards
Real-world example: a final year project where the proposal is approved in semester 7 and shown only at the end of semester 8. Often the team discovers too late that they built the wrong thing.
SE Lecture 2
Waterfall
Sheet 08 of 19
Slide 9
The V-model: plan the tests while you plan the system
Requirements
Acceptance testing
Real-world example: car airbag
System design
System testing
- Requirement: "open within a fraction of a second after a crash."
- The test for it is planned on day one, not after coding. Car companies use the V-model for this reason.
Detailed design
Unit and integration testing
Coding
Each step on the left is checked by the matching test on the right (dashed lines).
Word help
verify = check that something is correct acceptance testing = the customer checks if the system is acceptable
SE Lecture 2
Waterfall
Sheet 09 of 19
Slide 10
Incremental development: build in small pieces
Done together, again and again
Specification
Version 1
- Word help
- increment = a small part that is added each time
- version = one release of the software
Outline description
Development
Versions 2, 3, 4...
Validation
Final version
Real-world example: WhatsApp grew one piece at a time
- 2009
- Status updates
- Then
- Messaging
- Later
- Groups, voice notes
- Later
- Voice and video calls
- Recently
- Channels, payments
SE Lecture 2
Incremental
Sheet 10 of 19
Slide 11
Incremental development: good and bad
Benefits
Problems
- Changes cost less, because less work must be redone
- Users try real software, not long documents
- Useful software reaches users early
- Managers find it harder to see progress
- The code gets messy as pieces are added, unless the team cleans it up (refactoring)
- Hard for very large systems where many teams need a fixed structure early
Real-world example: a house where a new room is added every few years without a plan. Each room is useful, but soon the stairs are in strange places and the wiring is a mess. Code becomes like this without refactoring.
SE Lecture 2
Incremental
Sheet 11 of 19
Slide 12
Integration and configuration: build less, reuse more
1. Requirements
2. Search
3. Adjust needs
4. Set up and connect
Write the basic needs
Find existing software that fits
Change needs to match what exists
Configure, join parts, add new code
Ready-made systems
Code libraries
Online services (APIs)
Real-world example
e.g. Moodle set up for a university
e.g. packages from PyPI or npm
e.g. JazzCash payments, Google Maps
Buying ready-made furniture and arranging it in your room, instead of making every chair yourself. Faster and cheaper, but you get the sizes the shop has.
Word help
configure = set up the settings to fit your needs integrate = join separate parts so they work together
SE Lecture 2
Reuse
Sheet 12 of 19
Slide 13
The Spiral model: deal with the biggest risk first
1. Set goals
2. Find and reduce risks
- Each loop of the spiral is one round of work, and it passes through four steps.
- Before each round, the team asks: what could go most wrong right now?
- They deal with that risk first, often by building a small test version.
Real-world example: crop disease app
The biggest risk: can AI find diseases from cheap phone photos? Loop 1 tests only this on 200 photos. If it fails, the team stops early and loses little.
4. Plan the next loop
3. Build and test
Word help
risk = something that might go wrong prototype = a quick early sample version
SE Lecture 2
Spiral
Sheet 13 of 19
Slide 14
Every model is really an answer to change
Plan for change early
Make change cheap
Build a prototype so users can react before the real work starts.
Deliver in small pieces, so a change only affects the pieces not built yet.
Example: Like a tailor's trial fitting: he checks the sizes with you before final stitching.
Example: Like changing the menu of a new restaurant week by week, instead of printing 10,000 fixed menus on day one.
Throwaway prototype = thrown away after learning. Evolutionary prototype = grows into the real product.
This is what Incremental development does.
Why change is costly: one new requirement can mean new design, new code and new tests.
SE Lecture 2
Change
Sheet 14 of 19
Slide 15
Activity: choose the model
Each group gets one project. Choose a model, give two reasons, and name one risk your model handles badly.
A. Spraying drone
B. Farmer marketplace
Software that flies a crop-spraying drone. Strict safety rules. Hardware is ready in 12 months.
A startup app that connects Punjab farmers to buyers. The founders are not sure what farmers will use.
minutes
C. University library
D. National tax system
UAF wants an online library catalogue and book loans. Good free library systems already exist.
Replace a national tax system. Huge budget, new technology, big risk if it fails.
- 6 min in groups of 4-5
- 4 min to share answers
SE Lecture 2
Activity
Sheet 15 of 19
Slide 16
The four models side by side
Real projects often mix models. There is no best model, only the best fit for a project.
SE Lecture 2
Comparison
Sheet 16 of 19
Slide 17
Key points to remember
A process model is a general plan that teams change to fit their project.
Plan-driven and agile are two ends of a range. Most teams mix them.
Waterfall: good for stable, safety-critical work, but change is costly.
Incremental: change is cheap and users get software early, but code needs regular cleanup.
Integration and configuration: reuse existing parts to save time, but you lose some control.
Spiral: deal with the biggest risk first.
SE Lecture 2
Wrap-up
Sheet 17 of 19
Slide 18
Before the next lecture
Read
Assignment 2: process memo (team)
Sommerville, Software Engineering, 10th ed., Chapter 2, sections 2.1 to 2.3.
One page about your semester project:
- What problem it solves, and for whom
- Which process model you will follow
- Two reasons it fits your project
- One risk your model handles badly, and what you will do about it
Look ahead
Read the Agile Manifesto at agilemanifesto.org (one page). Next lecture: Agile development and Scrum.
SE Lecture 2
Homework
Sheet 18 of 19
Slide 19
Exit ticket
On a small piece of paper, with your name and roll number:
Name one project where Waterfall is the right choice, and say why in one sentence.
One question you still have after today.
Questions?
SE Lecture 2
Exit ticket
Sheet 19 of 19