How to use these notes: section numbers (§1.1, §1.2 ...) match the question bank. "Slide L07-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 7.1 | Explain what software is and its main characteristics, using the hardware and software failure curves. | CLO1 | C2 Understand | L07-S05 to S08 |
SLO 7.2 | Classify software into Pressman's seven application domains, and explain software components and legacy software. | CLO1 | C2 Understand | L07-S09 to S12 |
SLO 7.3 | Explain software engineering as a layered technology and apply the four layers to a project. | CLO1 | C3 Apply | L07-S13 to S15 |
For three weeks we studied how teams work: process models and agile methods. Today we step back and look closely at the product itself: what makes software different from a car, a building or a chair, what kinds of software exist, and why so much old software is still running. Then we see how software engineering is built in four layers, from quality at the bottom to tools at the top.
§1 What software is
Slides L07-S02, L07-S05
§1.1 Recap: agile models and your exit tickets
Slide L07-S02
Lecture 06 covered Kanban (visual flow, WIP limits), Lean (remove waste), DSDM (fix time and cost, vary features), Agile Modeling (model just enough) and the Agile Unified Process (serial in the large, iterative in the small).
Exit-ticket check: "Kanban, because it is easy" is not a reason. A good answer links the model to the project: "Kanban, because our work arrives as small, unpredictable requests from the canteen, and WIP limits stop us starting too many things at once."
§1.2 Software: three parts and two roles
Slide L07-S05
Pressman describes software as three things together:
1. Instructions (computer programs) that, when run, give the features, function and performance we want.
2. Data structures that let the programs store and work with information.
3. Descriptive information (documents, in print or online) that explains how the programs work and how to use them.
This matches Lecture 1: software = programs + data + documentation (+ configuration).
Software also plays a dual role (two roles at the same time):
Role | Meaning | Example |
|---|---|---|
A product | It gives computing power to the user. It produces, manages, changes and shows information. | The JazzCash app turns your taps into a money transfer and a receipt. |
A vehicle for delivering a product | It controls the computer, connects computers, or helps build other software. | Android runs the JazzCash app; the 4G network software carries its data; the compiler built it. |
Pressman calls software the most important product of our time because it delivers the most important thing of our time: information.
Word help dual = having two parts or two roles vehicle = something that carries or delivers something else |
§2 Characteristics of software
Slides L07-S06 to L07-S08
§2.1 Software is developed, not manufactured
Slide L07-S06
Hardware and software both need good design. But in manufacturing hardware, quality problems can come from the factory process, and every copy has a cost in material and labour. Software is developed (engineered): the cost is in the people who design and build it. Making a copy costs almost nothing.
Real-world example: a textile mill and a billing app A mill in Faisalabad spends money on cotton, power and labour for every metre of cloth. 1,000 metres cost roughly 1,000 times one metre. A billing app costs months of developers' time to build. Installing it on the 1,000th phone costs almost nothing extra. So software projects cannot be managed like factory production. Cost and quality depend on the engineering work, not on the copying. |
Word help manufacture = make many copies of a product in a factory engineer (verb) = design and build something using a careful, planned method |
§2.2 Software does not wear out, but it deteriorates
Slide L07-S07
The hardware failure curve is called the bathtub curve because of its shape. Failures are high early in the product's life (infant mortality: design and manufacturing defects), then low and steady for a long time, then rise again as parts wear out (dust, heat, vibration, age).
Software is not affected by dust or heat, so in theory its curve should follow the idealized curve: high failures at first (undiscovered defects), then a flat, low line once those defects are fixed.
In real life software is changed many times: new features, fixes, new rules. Each change can bring new errors, so the actual curve jumps up after every change. Before it settles back, the next change arrives. Slowly the minimum failure rate rises: the software is deteriorating because of change.
Figure 7.1 Hardware bathtub curve and software idealized vs actual curves (illustrative shapes).
Real-world example: the result portal after five years of quick fixes Year 1: the portal works well. Each semester a new grading rule, a new fee or a new report is added in a hurry. Every quick change adds a small risk of a new bug. By year 5, simple changes break other screens: the floor of the curve has risen. |
Word help wear out = become weak or broken through use and age deteriorate = slowly become worse infant mortality = failures that happen very early in a product's life |
§2.3 No spare parts
Slide L07-S08
When a hardware part wears out, it is replaced with a spare part. There are no spare parts for software. Every software failure shows an error in the design or in turning the design into code. So software maintenance (fixing and changing it) is usually more complex than hardware maintenance.
Hardware (a motorcycle) | Software (a mobile app) | |
|---|---|---|
Why it fails | Parts wear out with use | A design or coding error, often added during a change |
How it is fixed | Replace the worn part with an identical new one | Find the error, change the design or code, test again |
Effect of the fix | Back to the original condition | Can add new errors (side effects) |
Word help spare part = a new copy of a part, kept to replace a broken one side effect = an unplanned result of a change, such as a new bug in another screen |
§3 Software components and reuse
Slides L07-S09
§3.1 From custom-built to component-built
Slide L07-S09
In hardware engineering, engineers build with standard components: a mobile phone uses ready-made chips, screens and batteries. In software, the industry is moving the same way, but much software is still custom built for a particular customer.
A software component is a reusable, self-contained piece of software with a clear interface (the way other code uses it). It is built once and used in many systems.
Kind of component | Example |
|---|---|
Code library | Python's datetime library for dates; a PDF library to print fee vouchers |
User-interface widget | A ready-made date picker or a login form |
Online service (API) | JazzCash or Easypaisa payment API; Google Maps for a delivery app; Google sign-in |
Framework | Django or Laravel, which give the skeleton of a web app |
Benefits: faster development, lower cost, and the component is already tested by many users. Risks: you depend on someone else's code (price changes, the service closes, a security bug), and the component may not fit your needs exactly. Remember Ariane 5 (Lecture 1): reused code failed because nobody re-checked its assumptions.
Word help component = a reusable, self-contained piece of software interface = the agreed way other code talks to a component |
§4 Software application domains
Slides L07-S10 to L07-S11
§4.1 Seven domains
Slide L07-S10
Pressman groups software into seven broad application domains (areas of use):
Domain | What it is | Local example |
|---|---|---|
System software | Programs that serve other programs: operating systems, compilers, drivers, networking software. | Windows, Android, a printer driver |
Application software | Stand-alone programs that solve a specific business or technical need. | Payroll system of a textile mill; FESCO billing system |
Engineering / scientific software | Number-crunching programs for science and engineering. | Weather forecasting models at the Met Office; AutoCAD; crop-yield simulation |
Embedded software | Lives inside a product or system and controls its features. | Washing machine controller; car fuel injection; prepaid electricity meter |
Product-line software | Built to be reused by many different customers, often sold as a product. | MS Excel; an accounting product sold to many shops; a school management product |
Web / mobile applications | Network-centric software used in browsers and on phones. | Daraz, foodpanda, Careem, the JazzCash app |
Artificial intelligence software | Uses non-numerical methods (learning, reasoning) to solve complex problems. | Leaf-photo crop-disease detection; speech-to-text; chatbots |
Many real systems belong to more than one domain. A smart electricity meter has embedded software in the meter, and a web app where customers see their usage.
Word help domain = an area or field of use embedded = built inside another product |
§4.2 Worked quick check: classify
Slide L07-S11
Software | Domain | Why |
|---|---|---|
Android | System software | It serves other programs (apps run on it). |
Program inside a washing machine | Embedded | It lives inside the product and controls it. |
FESCO billing system | Application software | It meets one specific business need. |
Weather forecasting model | Engineering / scientific | Heavy number-crunching for science. |
MS Excel | Product-line | One product sold to millions of different customers. |
App that finds crop disease from a leaf photo | Artificial intelligence (also mobile) | It learns patterns from images. |
§5 Legacy software
Slides L07-S12
§5.1 Old software that is still running
Slide L07-S12
Legacy software is older software, often built decades ago, that is still in use and has been changed again and again. Many banks, airlines, utilities and government departments depend on legacy systems every day.
Legacy systems often have poor quality by today's standards: designs that are hard to extend, confusing code, little or no documentation, no saved test cases, and a poorly recorded history of changes. But they are often business-critical: the business cannot run without them.
What should we do with legacy software? If it meets users' needs and runs reliably, it is not broken: do not fix it. It must evolve (change) when it must be: (1) adapted to new technology or environments; (2) enhanced for new business needs; (3) extended to work with newer systems or databases; (4) re-architected for new computing environments (for example the cloud). |
Real-world example: a bank's core system A bank's core accounts system may be decades old. Rewriting it is risky and expensive; it handles every account in the country every day. When the State Bank launched Raast, banks did not throw away their cores. They extended them to connect to Raast. That is reason (3). |
Word help legacy = something old that is handed down and still used business-critical = the business cannot work without it |
§6 Software engineering: a layered technology
Slides L07-S13 to L07-S14
§6.1 The four layers
Slide L07-S13
Pressman shows software engineering as four layers. Each layer rests on the one below it:
Layer (bottom to top) | Meaning |
|---|---|
1. A quality focus (the bedrock) | Every engineering approach must rest on a commitment to quality. Ideas such as Total Quality Management and Six Sigma build a culture of continuous improvement. |
2. Process (the foundation) | The glue that holds the technology layers together. It defines a framework for the work: what is done, when, by whom, what is produced (work products), milestones, quality checks and change control. |
3. Methods | The technical how-to's: communication, requirements analysis, design modelling, program construction, testing and support. |
4. Tools | Automated or semi-automated support for the process and the methods. When tools are integrated so one tool's output feeds another, this is called CASE (computer-aided software engineering). |
Exam tip Draw the layers from the bottom: Quality focus → Process → Methods → Tools. A common mistake is to put tools at the bottom. |
Word help bedrock = the solid rock under the ground on which everything stands CASE = computer-aided software engineering: tools that support SE work |
§6.2 The layers in practice
Slide L07-S14
Layer | UAF cafeteria pre-order app | Building a house in Faisalabad |
|---|---|---|
Quality focus | The team agrees: no story is Done until it is tested and reviewed (Definition of Done). | A commitment to building codes and safe materials |
Process | Scrum: two-week sprints, planning, daily scrum, review, retrospective. | The construction stages: foundation, walls, roof, finishing |
Methods | User stories, UML diagrams, test-first unit testing. | How to lay bricks, mix concrete, wire a room |
Tools | Trello, draw.io, GitHub, pytest. | Cement mixer, spirit level, drill |
Without the lower layers, the upper ones do not help: a team with excellent tools but no process and no commitment to quality will still produce poor software.
§7 Worked activity: your project's nature and layers
Slides L07-S15
§7.1 The task and a model answer
Slide L07-S15
In project teams (8 minutes): (1) name your project's application domain(s); (2) name one reusable component you will use and one risk of using it; (3) fill in the four layers for your project; (4) describe one way your software could deteriorate after release.
Part | Model answer (cafeteria pre-order app) |
|---|---|
Domain | Web / mobile application (and application software for the canteen's sales records). |
Component and risk | JazzCash/Easypaisa payment API. Risk: the provider changes its API or fees, or the service is down at lunch time. |
Layers | Quality: Definition of Done with tests. Process: Scrum, 2-week sprints. Methods: user stories, UML, test-first. Tools: Trello, draw.io, GitHub, pytest. |
Deterioration | Each new menu rule or discount is added in a hurry without tests; after a year, changing the price list breaks the order screen. |
Accept other answers with good reasons. Check that the layers are named in the right order and that the component is really reusable (not "our own login code").
§8 Common mistakes
Slides L07-S16
§8.1 Five mistakes
Slide L07-S16
Mistake | Correct idea |
|---|---|
"Software wears out like hardware." | Software does not wear out; it deteriorates because of changes. |
"Software is just the code." | Software = programs + data structures + documentation. |
"Legacy software is bad; throw it away." | It is often business-critical. Evolve it only when there is a real need. |
"Tools are the most important layer." | Quality focus is the bedrock; tools only support process and methods. |
"With components, no engineering is needed." | Components must still be chosen, integrated, tested and watched for changes. |
Summary
- Software = instructions + data structures + documentation. It is both a product and a vehicle for delivering products.
- Software is developed, not manufactured: the cost is in the engineering, not in copying.
- Hardware follows the bathtub curve and wears out. Software does not wear out but deteriorates because each change can add errors. There are no spare parts.
- Components (libraries, widgets, APIs, frameworks) speed up development, but bring dependency risks.
- Seven application domains: system, application, engineering/scientific, embedded, product-line, web/mobile, AI.
- Legacy software is old but often business-critical; it evolves when it must adapt, be enhanced, be extended or be re-architected.
- SE is a layered technology: quality focus → process → methods → tools.
- Before Lecture 08: read Pressman Ch. 1 and 2.1; revise Lectures 1-6 for Quiz 1 (first 10 minutes of Lecture 08); bring your Practical 2 user stories to Practical 07.
Word bank
Word | Simple meaning | Example |
|---|---|---|
software | instructions + data structures + documentation | the JazzCash app with its data and help pages |
dual role | two roles at once: product and vehicle | an app (product) running on Android (vehicle) |
manufacture | make many copies in a factory | cloth in a textile mill |
bathtub curve | hardware failure curve: high, low, then high again | a motorcycle: early faults, good years, then worn parts |
deteriorate | slowly become worse | a portal that breaks more after each quick fix |
side effect | an unplanned result of a change | a new discount rule breaks the receipt screen |
component | reusable, self-contained piece of software | a payment API |
interface | the agreed way to use a component | the functions a payment API offers |
application domain | an area of use of software | embedded software in a washing machine |
embedded software | software inside a product | car fuel-injection control |
product-line software | software reused by many customers | MS Excel |
legacy software | old software still in use | a bank's decades-old core system |
business-critical | the business cannot work without it | airline booking system |
layered technology | SE built in four layers, each resting on the one below | quality → process → methods → tools |
CASE | computer-aided software engineering tools | draw.io, GitHub, pytest |
Self-check questions
Try each question without looking. Then check your answer in the section shown.
# | Question | See |
|---|---|---|
1 | Give Pressman's three-part description of software. | §1.2 |
2 | Explain the dual role of software with one example of each role. | §1.2 |
3 | Why is software 'developed, not manufactured'? Give an example. | §2.1 |
4 | Draw the bathtub curve and label infant mortality and wear out. | §2.2 |
5 | Why does the actual software failure curve rise after each change? | §2.2 |
6 | What does 'no spare parts' mean for software maintenance? | §2.3 |
7 | What is a software component? Give two benefits and one risk. | §3.1 |
8 | List the seven application domains with one example each. | §4.1 |
9 | Classify: Android, a washing machine controller, MS Excel, a crop-disease app. | §4.2 |
10 | What is legacy software? Give two reasons it must evolve. | §5.1 |
11 | Draw the four layers of SE in the correct order and explain each. | §6.1 |
12 | Fill in the four layers for your team project. | §6.2 |
Further reading
- Pressman & Maxim, 8th ed., Chapter 1 (The Nature of Software) and section 2.1 (Defining the discipline: the layered technology).
- Look ahead: Pressman 2.2 and Chapter 3 (the generic process model) for Lecture 08.