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 about Software Requirements Specifications)

 Videos

Video about ending the discussion about business requirements (sorry, in this video I was still experimenting after fixing some issues with the mic, the source was set to windowed instead of full screen so you do not see the slides, but the discussion starts from slide nr.11, where we stopped the lecture)

Video about IEEE Standard 29148-2011 which represents all that has to be in a requirements specification: distinguishing between Stakeholders Specifications, System Requirements Specification, and Software Requirements Specifications.