This week we start look at requirements elicitation phase, that is the collection of requirements for a specific project. We look initially about all the different types of requirements there can be in a project.
We look in particular at the importance of business requirements as they are at the top of the hierarchy of all requirements: how these can be modelled (by means of context diagram, eco-system map, feature tree or events list). Independently for the methodology of development, business requirements should always be specified at the beginning of a software project.

Lecture

• Software Requirements types & Business Requirements
• The three beasts in Software development: uncertainty, irreversibility, complexity (note this was not covered during the lecture, so it will not be part of the exam)