What you should be able to do
- State scope, assumptions and quality criteria.
- Separate a feature from the requirement it serves.
01 / PROCESS MODELS AND AGILE SOFTWARE DEVELOPMENT / L02
Software Engineering Basics
A useful system has a purpose, defined users, observable behaviour and constraints that can be checked.
What has to be true before a software solution can be trusted?
Terms to use precisely
Common mistakes
- Calling a technology choice a requirement without a reason.
Decide before you code.
Use a small case to separate requirements, design choices, verification and validation.
A lecturer asks for an attendance app. What should happen first?
Choose the action or concept that best fits.
CHECKED LEARNING LINKS
Watch the part that solves the gap.
Each link is matched to this lesson. Start with a quick video when available. Open the full lecture when you need the academic explanation.