How to use these notes: section numbers (§1.1, §1.2 ...) match the question bank. "Slide L01-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 1.1 | Explain what software is, and why it is more than a program. | CLO1 | C2 Understand | L01-S05, S06 |
SLO 1.2 | Define software engineering and the problem it was created to solve. | CLO1 | C2 Understand | L01-S07, S09-S11 |
SLO 1.3 | Distinguish programming from software engineering. | CLO1 | C2 Understand | L01-S04, S08 |
SLO 1.4 | Describe the four essential attributes of good software. | CLO1 | C2 Understand | L01-S12 |
SLO 1.5 | Name the four fundamental activities of every software process. | CLO1 | C1 Remember | L01-S13, S14 |
SLO 1.6 | Recognise the professional and ethical duties of a software engineer. | CLO1 | C2 Understand | L01-S15, S16 |
Until now you have learned to write programs. This course is about how professionals build software that real people depend on, often for many years. These notes follow the slides of Lecture 1 in the same order.
§1 From programs to software systems
Slides L01-S04
§1.1 Your assignment vs a mobile wallet
Slide L01-S04
Think about your OOP assignment and a mobile wallet like JazzCash or Easypaisa. Both are made by writing code. But they are very different problems.
Your OOP assignment | A mobile wallet (JazzCash / Easypaisa) | |
|---|---|---|
Who builds it | One developer: you | Large teams across many departments |
Who uses it | One user: your teacher | Millions of users, most of them non-technical |
How long it runs | Once, at the demo | 24 hours a day, 7 days a week, especially on Eid and payday |
Size | A few hundred lines | A huge codebase with many connected systems |
Future | Nobody touches it again | Changed and maintained for years |
If your assignment crashes, you lose a few marks. If a mobile wallet crashes the night before Eid, millions of people cannot pay, shopkeepers lose sales and the company loses money and trust. Same skill (writing code), completely different problem. Software engineering is about the second column.
§2 What is software?
Slides L01-S05 to L01-S06
§2.1 Software is more than a program
Slide L01-S05
Software = programs + documentation + data + configuration. It is the programs plus everything needed to install, run, understand and change them.
- Programs: the source code and the executable files.
- Documentation: user manuals, design documents, help pages, comments.
- Data: the database, files and records the programs use.
- Configuration: settings files that make the software work on a particular machine or for a particular customer.
Test yourself: if someone gives you an .exe file with no instructions, no data and nobody who knows how it works, is it useful software? Most people say no. That is the point of the definition.
§2.2 Generic and customised (bespoke) products
Slide L01-S05
Type | Who decides what it does | Examples |
|---|---|---|
Generic product | The developer. It is built for an open market and sold or given to anyone. | WhatsApp, MS Word, Android, Photoshop |
Customised (bespoke) product | The customer. It is built for one specific customer and their needs. | UAF student portal, a hospital records system, a bank's core banking system |
The key difference is who owns the specification (the description of what the software must do). For WhatsApp, Meta decides. For a university portal, the university decides, and the developers must find out exactly what it needs. That is why requirements engineering (Lectures 12-15) matters so much for bespoke systems.
The line is blurring: many products are generic platforms set up for one customer, for example an ERP system like SAP, or Moodle configured for a university.
Word help bespoke = made for one particular customer, like a suit stitched by a tailor for you specification = a written description of what the software must do |
§2.3 Why building software is hard
Slide L01-S06
In 1986 Fred Brooks wrote a famous essay called "No Silver Bullet". He said some difficulties are built into the nature of software itself, so no single tool or trick will make software development dramatically easier.
Difficulty | Meaning | Example |
|---|---|---|
Complexity | No two parts are alike, and the number of possible states explodes as the system grows. | A program with 20 true/false flags has over a million combinations to test (2^20 = 1,048,576). |
Conformity | Software must fit laws, organisations, other systems and hardware that it cannot change. | When FBR changes tax rules in the budget, every payroll system must change. |
Changeability | Because software seems easy to change, everyone keeps asking it to change. | Nobody asks a civil engineer to add three floors to a finished building, but clients ask for "small changes" to software all the time. |
Invisibility | You cannot see or hold software; it has no natural physical shape. | This is why we will learn UML diagrams: to make software visible. |
Software does not wear out, but it does deteriorate A car's parts wear out with use. Software does not wear out: the same code runs the same way on day 1 and day 1,000. But software deteriorates (gets worse) as changes pile up. Each quick fix adds a little mess. After years, the code becomes hard to change. This is called software decay or technical debt. |
Word help deteriorate = slowly become worse technical debt = the extra future work caused by choosing a quick, messy fix now |
§3 What is software engineering?
Slides L01-S07 to L01-S08
§3.1 The IEEE definition
Slide L01-S07
Software engineering is "the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software." (IEEE Standard 610.12-1990)
Keyword | Simple meaning |
|---|---|
Systematic | A defined method is followed, not trial and error. |
Disciplined | The method is followed even under deadline pressure. |
Quantifiable | Cost, time and quality are measured with numbers. |
Whole lifecycle | It covers development, operation and maintenance, not only writing the first version. |
Sommerville gives a simpler version: software engineering is an engineering discipline concerned with all aspects of software production, from early specification to maintaining the system after it is in use.
Students often think the job ends when the code works. For most long-lived systems, most of the total cost is spent after the first release, on maintenance and evolution.
Quick check: copying code from the internet until it works breaks which keywords? Systematic and disciplined.
Word help quantifiable = can be measured and given a number lifecycle = all the stages of a product's life, from idea to retirement |
§3.2 Programming vs software engineering
Slide L01-S08
Programming | Software engineering | |
|---|---|---|
Goal | Code that works | A system that keeps working, for real users, within budget |
Scale | One person | Teams, often across organisations |
Lifetime | Days or weeks | Years or decades |
Concerns | Correctness | Correctness, cost, schedule, security, usability, maintainability |
Output | Source code | Requirements, design, code, tests, documentation, deployment |
Users | You and your teacher | People who neither know nor care how it works |
David Parnas described software engineering as "the multi-person construction of multi-version software." Multi-person means communication becomes the hard problem. Multi-version means the software keeps changing.
Real-world example: bricklayer and civil engineer Programming is to software engineering as laying bricks is to civil engineering. A bricklayer is skilled and essential. A civil engineer must also think about the soil, the load, the budget, the regulations, safety, and the building's next 50 years. Programming is not less important; it is PART of software engineering. Good software engineers are almost always good programmers too. |
§4 Why the discipline exists
Slides L01-S09 to L01-S11
§4.1 The software crisis (1968)
Slide L01-S09
In the 1960s, computers like the IBM System/360 made big systems possible. Organisations started huge projects: operating systems, airline reservations, defence systems. Many failed badly. This was called the software crisis.
Symptoms of the crisis (and they still appear today):
- Projects late and over budget
- Software unreliable and full of defects
- Systems that did not do what users needed
- Code too tangled to maintain
- Projects cancelled after years of work
In 1968 a NATO conference in Garmisch, Germany used the term software engineering on purpose. It argued that software should be built with the same rigour as bridges and aircraft.
Word help crisis = a time of serious difficulty rigour = being very careful and exact |
§4.2 When engineering is missing, people pay
Slide L01-S10
Case | What happened | Lesson |
|---|---|---|
Therac-25 (1985-87) | A radiation therapy machine gave massive overdoses to patients; several died. Earlier models had hardware safety locks; this one trusted software alone. A race condition, triggered when operators edited settings quickly, let the machine fire a high-power beam wrongly. | Safety-critical systems need independent safeguards and rigorous testing. |
Ariane 5 (1996) | A European rocket destroyed itself about 40 seconds after launch. Code reused from Ariane 4 converted a 64-bit number into a 16-bit integer. Ariane 5 flew faster, so the value overflowed and both guidance computers (running the same code) shut down. | Reuse is powerful, but the old code's assumptions must be checked again for the new system. |
Boeing 737 MAX (2018-19) | Two crashes killed 346 people. A flight control system (MCAS) pushed the nose down based on data from a single sensor that could fail. | Software engineering is also systems engineering: hardware, software, people and training together. |
In each case, the code often did exactly what it was written to do. The real failures were in requirements, design, testing and process, not just programming.
Word help race condition = a bug where the result depends on which of two things happens first overflow = a number becomes too big to fit in the space given for it safety-critical = a failure could injure or kill people |
§4.3 When engineering is done well, a country runs on it
Slide L01-S11
System | What it does |
|---|---|
NADRA | The national identity database behind CNICs, used daily to verify citizens for SIMs, banking and services. |
Raast | The State Bank of Pakistan's instant payment system (launched 2021), moving money between banks in seconds. |
Mobile wallets | JazzCash, Easypaisa and digital banks serve millions of people, many without a traditional bank account. |
IT exports | Pakistan's software and IT services exports exceed US$3 billion a year, built by people sitting where you are. |
These systems work because teams used requirements, architecture, testing, security and operations, not just coding. Every time Raast or a mobile wallet worked for you this month, that was software engineering.
§5 Good software and the software process
Slides L01-S12 to L01-S13
§5.1 The four essential attributes of good software
Slide L01-S12
Attribute | Meaning | Student-friendly example |
|---|---|---|
Maintainability | It can evolve as needs change. Change is certain, so this matters most over time. | Open your first-semester code. Can you change it easily? Probably not. |
Dependability and security | Reliable, safe and secure. A failure should not cause physical or economic harm, and attackers should not be able to break it. | A result portal that crashes on result day is not dependable, however good it looks. |
Efficiency | It does not waste memory, processor time or battery. | An app that drains a phone battery in two hours gets uninstalled. |
Acceptability | Its intended users find it understandable, usable and compatible with their other systems. | A system for farmers that only works in English and needs fast internet will not be used in rural areas. |
Notice what is not on the list: "it has lots of features".
Attributes trade off More security can mean less usability (more passwords, more steps). Engineering means choosing the right balance for the context. |
Word help attribute = a quality or feature of something dependability = how much you can trust something to work when you need it |
§5.2 The four activities of every software process
Slide L01-S13
Activity | What happens | Example: a student result portal |
|---|---|---|
1. Specification | Customers and engineers define what the software must do, and its constraints. | What results do students see? Who can enter marks? What about privacy? |
2. Development | The software is designed and programmed. | Database design, screens, code. |
3. Validation | The software is checked to make sure it is what the customer needs. | Testing with real data; checking GPA calculation against official rules. |
4. Evolution | The software is changed to meet new customer and market needs. | Next year the grading policy changes, so the portal must change. |
Evolution feeds back into specification, so the cycle repeats for the life of the system. Every process model this semester (Waterfall, Incremental, Spiral, Agile/Scrum) contains these same four activities. The models differ in how they order and repeat them.
Honest question: in your assignments, which activities do you skip? Usually specification and validation. This course will fix that habit.
Word help validation = checking that the software is what the customer really needs constraint = a limit you must work within, such as budget, time or law |
§6 Worked activity: engineer the UAF cafeteria app
Slides L01-S14
§6.1 The task
Slide L01-S14
The university wants an app so students can pre-order food from the cafeteria and pick it up between classes. In groups of 4-5 (7 minutes): (1) list every stakeholder, (2) write five one-sentence requirements, (3) choose the quality attribute that matters most and say why, (4) describe one way it could fail on its first day.
§6.2 A model answer
Slide L01-S14
Part | Model answer |
|---|---|
Stakeholders | Students; faculty and staff who eat there; cafeteria owner; cashier; kitchen staff; university administration; IT department; payment provider (JazzCash / Easypaisa / bank); food safety authority. |
Requirements | (1) A student can view the daily menu with prices. (2) A student can place and pay for an order. (3) The app notifies the student when the order is ready. (4) A student can cancel an order before preparation starts. (5) The owner can update the menu and mark items as sold out. |
Most important attribute | Dependability or efficiency, because of the 1 pm lunch rush when hundreds order at once. Acceptability is also strong: it must be simple and fast. |
Day-one failures | Server overload at lunch; double payment charges; orders sent to the kitchen without payment; internet down in the cafeteria; sold-out items still orderable. |
In ten minutes you did specification and thought about validation without writing a single line of code. That is software engineering.
Word help stakeholder = any person or group affected by the system, or who can affect it |
§7 Professional and ethical responsibility
Slides L01-S15
§7.1 The ACM/IEEE-CS Software Engineering Code of Ethics
Slide L01-S15
The code has eight principles. A software engineer acts in the interest of:
Principle | Meaning |
|---|---|
1. Public | The wider public interest comes first. |
2. Client and employer | Their best interest, consistent with the public interest. |
3. Product | The highest professional standards possible. |
4. Judgment | Integrity and independence in professional judgment. |
5. Management | Ethical management of software projects. |
6. Profession | Its integrity and reputation. |
7. Colleagues | Fair and supportive treatment. |
8. Self | Lifelong learning. |
Notice that Public comes before Client and Employer. That order is the heart of professional ethics.
Everyday responsibilities (Sommerville): confidentiality (keep client data and business secrets private), competence (do not accept work beyond your ability), intellectual property (respect licences and copyright; no copied code without permission) and computer misuse (never use your skills to access systems you should not).
§7.2 Scenario: the phone-number leak
Slide L01-S15
Your manager asks you to release a feature tomorrow. You know it exposes users' phone numbers to anyone who looks. What do you do?
- Good answers: raise it clearly with the manager in writing; explain the risk and possible legal consequences (for example under the Prevention of Electronic Crimes Act, PECA 2016); propose a fix or a short delay; escalate if you are ignored.
- Bad answers: ship it silently, or leak the problem publicly first.
Word help integrity = being honest and doing the right thing even when nobody is watching escalate = take a problem to a higher level of management |
§8 Careers and the semester ahead
Slides L01-S16 to L01-S17
§8.1 Software engineering is a team sport
Slide L01-S16
Process activity | Roles |
|---|---|
Specification | Business / requirements analyst; product manager |
Development | Software architect; software developer; UX designer |
Validation | QA and test engineer; security engineer |
Evolution and operation | DevOps / cloud engineer; project manager / Scrum master |
Only one of these roles is mainly about writing code. Most software houses hire for all of them. This course gives you a working view of every role so you can choose where you fit.
§8.2 This semester
Slide L01-S17
We will cover process models, agile and Scrum, requirements engineering, UML system modelling, design and architecture, testing and quality, evolution, project management and configuration management. Your team will take one real project from idea to models: process memo, SRS, UML design and a final demo.
Main textbooks: Pressman & Maxim, *Software Engineering: A Practitioner's Approach*; Sommerville, *Software Engineering* (10th ed.).
Summary
- Software is programs plus documentation, data and configuration.
- Software engineering applies a systematic, disciplined, quantifiable approach across the whole lifecycle.
- Programming is one part of software engineering, not the whole of it.
- Good software is maintainable, dependable and secure, efficient, and acceptable to its users.
- Every process contains specification, development, validation and evolution.
- Engineers are responsible to the public first.
- Before Lecture 2: read Sommerville Ch. 1 (sections 1.1-1.2); write Assignment 1 (one-page failure case study); form your project team of 4-5.
Word bank
Word | Simple meaning | Example |
|---|---|---|
software | programs plus the documents, data and settings needed to use and change them | WhatsApp is the app, its servers' data, its help pages and its settings |
software engineering | a careful, planned and measured way of building and looking after software | how NADRA's system is built and kept running |
bespoke / customised | made for one customer | UAF's student portal |
generic product | made for anyone in the market | MS Word |
specification | a description of what the software must do | "A student can see her GPA after login" |
deteriorate | slowly get worse | code becomes messy after many quick fixes |
lifecycle | all stages of a product's life | idea, build, use, change, retire |
quantifiable | can be measured with a number | "the page loads in under 2 seconds" |
crisis | a time of serious difficulty | projects late, over budget and full of bugs in the 1960s |
race condition | a bug that depends on which event happens first | Therac-25's fast-typing operators |
overflow | a number too big for its storage | Ariane 5's 16-bit value |
safety-critical | failure could injure or kill people | aircraft controls, medical machines |
maintainability | how easily software can be changed | adding a new grading rule in one place only |
dependability | how much you can trust it to work | a payment app that never double-charges |
stakeholder | anyone affected by the system | cafeteria owner, students, payment provider |
validation | checking it is what users really need | testing GPA results against official rules |
ethics | rules about what is right and wrong | not shipping a feature that leaks phone numbers |
confidentiality | keeping private information private | not sharing a client's customer list |
Self-check questions
Try each question without looking. Then check your answer in the section shown.
# | Question | See |
|---|---|---|
1 | Name the four parts of software, according to the definition used in this course. | §2.1 |
2 | What is the difference between a generic product and a bespoke product? Give one example of each. | §2.2 |
3 | Explain Brooks' difficulty called "changeability" with an example. | §2.3 |
4 | "Software does not wear out, but it deteriorates." What does this mean? | §2.3 |
5 | Write the IEEE definition of software engineering and explain the word "disciplined". | §3.1 |
6 | Give four differences between programming and software engineering. | §3.2 |
7 | What was the software crisis, and what did the 1968 NATO conference do about it? | §4.1 |
8 | What was the root cause of the Ariane 5 failure, and what lesson does it teach? | §4.2 |
9 | List the four essential attributes of good software and give an example of each. | §5.1 |
10 | Name the four process activities and apply them to a cafeteria pre-order app. | §5.2, §6 |
11 | Which principle comes first in the ACM/IEEE-CS Code of Ethics, and why does that matter? | §7.1 |
12 | Name three roles in a software team other than developer. | §8.1 |
Further reading
- Sommerville, *Software Engineering*, 10th ed., Chapter 1, sections 1.1-1.2.
- Pressman & Maxim, *Software Engineering: A Practitioner's Approach*, 8th ed., Chapter 1 (The Nature of Software).