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.

The main standard to follow for requirements engineering is IEEE 29148 "Systems and software engineering - Life cycle processes - Requirements Engineering" that replaced the old standard IEEE830. We see how the standard is structured and how it can be applied to software projects.

Lecture

• Software Requirements types & Business Requirements
• IEEE Std 29148-2011 - [annotated version] 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! Still, could contain useful information)