Slide 2
Last lecture: agile models, and your exit tickets
Kanban
Lean
DSDM
Agile Modeling
AUP
Visual flow, WIP limits
Remove waste
Fix time and cost, vary features
Model just enough
Serial in the large, iterative in the small
Weak: "Kanban, because it is easy."
Better: "Kanban, because canteen requests arrive in small, unplanned pieces, and WIP limits stop us starting too much."
Today: we step back from HOW teams work and look at WHAT they build: the nature of software, its kinds, and the four layers software engineering stands on.
SE Lecture 7
Recap
Sheet 02 of 19
Slide 3
Learning outcomes
SLO 7.1
Explain what software is and its characteristics, using the failure curves
→ CLO1 · C2 Understand
SLO 7.2
Classify software into seven domains; explain components and legacy software
→ CLO1 · C2 Understand
SLO 7.3
Explain SE as a layered technology and apply the layers to a project
→ CLO1 · C3 Apply
CLO1: Explain application of software engineering processes and techniques to various types of software.
SE Lecture 7
Outcomes
Sheet 03 of 19
Slide 4
Today's plan: 50 minutes
0-5 min
Recap and exit tickets
This week
5-8 min
Outcomes and plan
- Lecture 08: the generic process model
- Quiz 1 at the start of Lecture 08
- Practicals 07-08: write your project's SRS
8-19 min
What software is; how it fails
19-30 min
Components, domains, legacy software
30-35 min
SE as a layered technology
35-43 min
Activity: your project's nature and layers
43-48 min
Common mistakes and recap quiz
48-50 min
Homework and exit ticket
SE Lecture 7
Plan
Sheet 04 of 19
Slide 5
What software is: three parts, two roles
Instructions
Dual role
Programs that give the features and performance we want
- A product
- Turns data into useful information for the user. The JazzCash app turns your taps into a transfer and a receipt.
Data structures
Let programs store and work with information
Documentation
- A vehicle for delivering products
- Android runs the app; network software carries its data; a compiler built it.
Explains how the programs work and how to use them
Same idea as Lecture 1: programs + data + documentation.
Word help
dual = two at the same time vehicle = something that carries
Software delivers the most important product of our time: information.
SE Lecture 7
What is software
Sheet 05 of 19
Slide 6
Characteristic 1: developed, not manufactured
Textile mill
Billing app
- Every metre of cloth needs cotton, power and labour
- 1,000 metres ≈ 1,000 × the cost of one metre
- Quality problems can come from the factory process
- Months of developers' time to design and build
- The 1,000th copy costs almost nothing
- Quality comes from the engineering work
So: software projects cannot be managed like factory production. Cost and quality depend on the engineering (people's work), not on making copies.
SE Lecture 7
Characteristics
Sheet 06 of 19
Slide 7
Characteristic 2: software does not wear out
Hardware: the bathtub curve
Software: idealized vs actual
infant mortality
wear out
each spike = a change
Failure rate ↑ Time → (shapes only, not real data)
Software deteriorates: every change can add new errors, so the failure rate jumps, and its lowest point slowly rises.
SE Lecture 7
Characteristics
Sheet 07 of 19
Slide 8
No spare parts for software
Result: software maintenance is usually more complex than hardware maintenance.
Word help
spare part = a new copy of a part, kept to replace a broken one side effect = an unplanned result of a change
SE Lecture 7
Characteristics
Sheet 08 of 19
Slide 9
Software components: build with reusable parts
Component = a reusable, self-contained piece of software with a clear interface. Built once, used in many systems.
Code library
Python datetime; a PDF library for fee vouchers
UI widget
A ready-made date picker or login form
Much software is still custom built, but the industry is moving toward component-based building, like phones built from ready-made chips.
Online service (API)
JazzCash payment; Google Maps; Google sign-in
Word help
interface = the agreed way other code uses a component
Framework
Django or Laravel for a web app
Benefits: faster, cheaper, already tested by many users.
Risks: you depend on someone else (price, closure, bugs). Re-check assumptions: Ariane 5!
SE Lecture 7
Components
Sheet 09 of 19
Slide 10
Seven software application domains
System software
Application software
Windows, Android, drivers
Mill payroll; FESCO billing
Engineering / scientific
Embedded software
Weather models; AutoCAD
Washing machine; electricity meter
Product-line software
Web / mobile apps
MS Excel; a school product sold to many
Daraz, foodpanda, Careem
Artificial intelligence
Many systems span domains: a smart meter = embedded + web app.
Crop-disease detection from photos
Word help
domain = an area of use embedded = built inside another product product-line = reused by many customers
SE Lecture 7
Domains
Sheet 10 of 19
Slide 11
Quick check: which domain?
A
Android
System
B
Program inside a washing machine
Embedded
C
FESCO billing system
Application
D
Weather forecasting model
Engineering / scientific
E
MS Excel
Product-line
F
App that finds crop disease from a leaf photo
AI (and mobile)
Say the domain before your teacher reveals it.
SE Lecture 7
Domains
Sheet 11 of 19
Slide 12
Legacy software: old, ugly, essential
Legacy software = older software, built years or decades ago, still in use, changed again and again. Often business-critical.
It must evolve when it has to be ...
Adapted to new technology or environments
Enhanced for new business needs
Extended to work with newer systems
- Typical problems
- Designs that are hard to extend
- Confusing code
- Little or no documentation
- No saved test cases or change history
Re-architected for new computing environments (cloud)
Real-world example: Raast
Banks did not throw away their old core systems. They extended them to connect to the State Bank's Raast.
SE Lecture 7
Legacy
Sheet 12 of 19
Slide 13
Software engineering: a layered technology
Tools
Automated support for process and methods (CASE when integrated)
Methods
Technical how-to's: requirements, design, construction, testing
Process
The foundation and glue: framework, work products, milestones, change control
A quality focus
The bedrock: commitment to quality and continuous improvement
↑ build from the bottom
Word help
bedrock = solid rock everything stands on CASE = computer-aided software engineering
SE Lecture 7
Layers
Sheet 13 of 19
Slide 14
The layers in practice
Remember: great tools with no process and no commitment to quality still produce poor software.
SE Lecture 7
Layers
Sheet 14 of 19
Slide 15
Activity: your project's nature and layers
In your project teams:
Name your project's application domain(s).
Name one reusable component you will use, and one risk.
Fill in the four layers for your project.
minutes
Describe one way your software could deteriorate after release.
- 6 min in teams
- 2 min to share
SE Lecture 7
Activity
Sheet 15 of 19
Slide 16
Common mistakes
"Software wears out like hardware."
✗
It deteriorates because of changes
"Software is just the code."
✗
Programs + data structures + documentation
"Legacy software is bad: throw it away."
✗
Often business-critical; evolve it for a reason
"Tools are the most important layer."
✗
Quality focus is the bedrock; tools are on top
"With components, no engineering is needed."
✗
Choose, integrate, test and watch them
SE Lecture 7
Mistakes
Sheet 16 of 19
Slide 17
Recap quiz: hands up
Which layer of SE is the bedrock?
What is the hardware failure curve called?
Why does the actual software failure curve jump?
A washing machine's control program belongs to which domain?
Give one reason legacy software must evolve.
SE Lecture 7
Recap quiz
Sheet 17 of 19
Slide 18
Before the next lecture
Read
Quiz 1: next lecture
Pressman Ch. 1 and section 2.1. Skim Pressman 2.2 and Ch. 3 for Lecture 08.
- First 10 minutes of Lecture 08
- 10 MCQs, 1 mark each, closed book
- Covers Lectures 1-6: SE basics, process models, agile, XP, Scrum, other agile models
- Revise the comparison tables and the self-check questions in your notes
Practicals 07-08
Bring your Practical 2 user stories. You will turn them into an SRS.
SE Lecture 7
Homework
Sheet 18 of 19
Slide 19
Exit ticket
On a small piece of paper, with your name and roll number:
Write the four layers of SE from the bottom up, with one example of each from your project.
One question you still have.
Questions?
SE Lecture 7
Exit ticket
Sheet 19 of 19