This week we will look at the main problems in software development and requirements engineering - and how typically these are addressed by different development methodologies. We see how to start modelling system requirements and the typical indications given by standards such as IEEE 29148 (that replaced IEEE830) and how this differs in the agile context.

Lecture

• The three beasts in Software development: uncertainty, irreversibility, complexity [not at the exam]
• The top-10 Requirements Traps [annotated version] [not at the exam]
• The main IEEE standard for requirements: IEEE29148 [annotated version]

Additional Material

The following are the more recent IEEE standard about requirements engineering (IEEE29148-2011) and the old standard IEEE830-1998 (replaced by the new one, but still useful).

• IEEE Std 29148-2011 - Systems and software engineering - Life cycle processes - Requirements engineering
• IEEE Std 830-1998 - IEEE Recommended Practice for Software Requirements Specifications (this is the old one and superseded by 29148!)