Slide 2
By the end of today, you will be able to
Explain what software is, and why it is more than a program
Define software engineering and the problem it was created to solve
Distinguish programming from software engineering
Describe the four essential attributes of good software
Name the four fundamental activities of every software process
Recognise the professional and ethical duties of a software engineer
SE Lecture 1
Objectives
Sheet 02 of 20
Slide 3
Today's plan: 60 minutes
0-5 min
Welcome and a question to start
5-17 min
What software is, and what software engineering means
17-27 min
Why the discipline exists: the crisis and the failures
27-35 min
Good software and the software process
35-45 min
Group activity: engineer a real app
45-52 min
Ethics, careers, and the semester ahead
52-60 min
Takeaways, homework, exit ticket
SE Lecture 1
Plan
Sheet 03 of 20
Slide 4
You have written programs. Have you ever built software?
Your OOP assignment
A mobile wallet like JazzCash or Easypaisa
- One developer: you
- One user: your teacher
- Runs once, at the demo
- A few hundred lines
- Nobody touches it again
- Large teams across many departments
- Millions of users, most non-technical
- Must run 24/7, especially on Eid and payday
- Huge codebase, many connected systems
- Maintained and changed for years
SE Lecture 1
Hook
Sheet 04 of 20
Slide 5
What is software?
Programs
+
Documentation
+
Data
+
Configuration
Software is programs plus everything needed to install, run, understand and change them.
Generic products
Customised (bespoke) products
Built for an open market. The developer decides what it does.
Built for one specific customer. The customer decides what it must do.
e.g. WhatsApp, MS Word, Android, Photoshop
e.g. a university's student portal, a hospital records system, a bank's core system
SE Lecture 1
What is software
Sheet 05 of 20
Slide 6
Why is building software hard?
Fred Brooks (1986, "No Silver Bullet"): some difficulties are built into the nature of software itself.
Complexity
Conformity
No two parts are alike, and the number of possible states explodes as systems grow.
Software must fit laws, organisations, other systems and hardware that it cannot change.
Changeability
Invisibility
Because it seems easy to change, everyone keeps asking it to change.
You cannot see or hold software; it has no natural physical shape to inspect.
Unlike hardware, software does not wear out, but it does deteriorate as changes pile up.
SE Lecture 1
What is software
Sheet 06 of 20
Slide 7
What is software engineering?
“
The application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software.
IEEE Standard Glossary of Software Engineering Terminology (IEEE 610.12-1990)
Systematic
Disciplined
Quantifiable
Whole lifecycle
A defined method, not trial and error
Followed even under deadline pressure
Cost, time and quality are measured
Development, operation and maintenance
SE Lecture 1
Definition
Sheet 07 of 20
Slide 8
Programming vs software engineering
David Parnas described it as the multi-person construction of multi-version software.
SE Lecture 1
Definition
Sheet 08 of 20
Slide 9
The software crisis
1968
Symptoms, then and now
NATO conference, Garmisch, Germany
- 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
- Hardware was growing powerful fast, and software projects were growing faster than anyone knew how to manage.
- The conference used the term software engineering on purpose: to argue that software needed the discipline of real engineering.
SE Lecture 1
Why SE
Sheet 09 of 20
Slide 10
When engineering is missing, people pay
1985-87
1996
2018-19
Therac-25
Ariane 5
Boeing 737 MAX
A radiation therapy machine gave massive overdoses to patients; several died. A race condition triggered by fast operator input was the cause.
A European rocket self-destructed about 40 seconds after launch. Reused code converted a 64-bit number to a 16-bit integer, and it overflowed.
Two crashes killed 346 people. A flight control system (MCAS) acted on data from a single sensor that could fail.
Lesson: hardware safety locks were removed and the software was trusted without proper testing.
Lesson: code was reused without checking that its assumptions still held.
Lesson: a system-level design and safety failure, worsened by poor communication to pilots.
SE Lecture 1
Why SE
Sheet 10 of 20
Slide 11
When engineering is done well, a country runs on it
NADRA
Raast
Mobile wallets
IT exports
The national identity database behind CNICs, used daily to verify citizens for SIMs, banking and services.
The State Bank's instant payment system, launched in 2021, moving money between banks in seconds.
JazzCash, Easypaisa and digital banks serve millions, many without a traditional bank account.
Pakistan's software and IT services exports exceed US$3 billion a year, built by people sitting where you are.
SE Lecture 1
Why SE
Sheet 11 of 20
Slide 12
What makes software good?
Maintainability
Dependability and security
It can evolve as needs change. Change is inevitable, so this matters most over time.
Reliable, safe and secure. A failure should not cause physical or economic harm, and attackers should not be able to break it.
Efficiency
Acceptability
It does not waste memory, processor time or battery: responsive and resource-aware.
Its intended users find it understandable, usable and compatible with the other systems they use.
Notice what is missing from the list: "it has lots of features".
SE Lecture 1
Good software
Sheet 12 of 20
Slide 13
Every software process has four activities
Specification
Development
Validation
Evolution
Customers and engineers define what the software must do, and its constraints.
The software is designed and programmed.
The software is checked to make sure it is what the customer needs.
The software is changed to meet new customer and market needs.
Evolution feeds back into specification. The cycle repeats for the life of the system.
SE Lecture 1
Process
Sheet 13 of 20
Slide 14
Activity: engineer the UAF cafeteria app
The university wants an app so students can pre-order food from the cafeteria and pick it up between classes.
List every stakeholder affected by this app.
Write five requirements, each one sentence.
Choose the one quality attribute that matters most here, and say why.
minutes
- 7 min in groups of 4-5
- 3 min for two groups to share
Describe one way it could fail on its first day.
SE Lecture 1
Activity
Sheet 14 of 20
Slide 15
Professional and ethical responsibility
The ACM/IEEE-CS Software Engineering Code of Ethics sets eight principles. A software engineer acts in the interest of:
Public
Client and employer
Product
Judgment
The wider public interest comes first
Their best interest, consistent with the public
The highest professional standards possible
Integrity and independence
Management
Profession
Colleagues
Self
Ethical management of projects
Its integrity and reputation
Fair and supportive treatment
Lifelong learning
Think about it: your manager asks you to release a feature tomorrow. You know it exposes users' phone numbers to anyone who looks. What do you do?
SE Lecture 1
Ethics
Sheet 15 of 20
Slide 16
Software engineering is a team sport
Specification
Development
Validation
Evolution and operation
Business / requirements analyst
Software architect
QA and test engineer
DevOps / cloud engineer
Product manager
Software developer
Security engineer
Project manager / Scrum master
UX designer
Each role owns part of the lifecycle. This course gives you a working view of all of them, so you can choose where you fit.
SE Lecture 1
Careers
Sheet 16 of 20
Slide 17
The semester ahead
Introduction to software engineering
Architectural design
Software process models
Design and implementation
Agile development and Scrum
Software testing
Requirements engineering
Software evolution and maintenance
System modelling with UML
Project management and quality
Throughout the semester, your team takes one project from idea to tested system.
SE Lecture 1
Roadmap
Sheet 17 of 20
Slide 18
Key takeaways
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.
SE Lecture 1
Wrap-up
Sheet 18 of 20
Slide 19
Before the next lecture
Read
Assignment 1: failure case study
Sommerville, Software Engineering, 10th ed., Chapter 1 (Introduction), sections 1.1 to 1.2.
One page on a real software failure not covered today. Answer:
- What happened, and who was affected?
- What was the root cause?
- Which quality attribute failed?
- Which engineering practice could have prevented it?
Form teams
Groups of 4-5 for the semester project. Submit names at the start of next class.
SE Lecture 1
Homework
Sheet 19 of 20
Slide 20
Exit ticket
On a slip of paper, with your name and roll number:
In one sentence, what is the difference between programming and software engineering?
One question you still have after today.
Questions?
SE Lecture 1
Exit ticket
Sheet 20 of 20