Software Requirements Types and Specification

Start with requirements types

The mind map Types of Requirements is a useful starting point. It introduces requirements as behavior or qualities a new system is required to have. It also distinguishes functional requirements, which describe what a system must do, from non-functional requirements, which describe qualities.

A related note presents the content from the mind map in text form. Read it alongside the map if you want to follow the ideas in a different format. Another note outlines business, user, functional and system requirements.

Explore stakeholders and qualities

The Requirements mind map introduces the intended purpose of a system and the people involved, including clients, users and developers. It also points to qualities of requirements, such as being necessary, traceable and unambiguous.

Next, look at Non-functional requirements for an example of a quality: the look and feel of a product. The flashcard deck on requirements concepts asks about the difference between functional and non-functional requirements and includes questions on usability.

Move on to documentation

The Documenting the requirements mind map introduces the software requirements specification and labeling requirements. A separate mind map, Software Requirements Specification, is also listed. These resources connect the types and qualities you have studied with the way requirements are documented.

This topic is one section of the Software Requirements and Design unit in Computing and ICT. Use the resources on this page to follow requirements from their types and stakeholders through to documentation.

Check your understanding

The page has no listed quizzes, but its flashcards offer questions to work through. With a free account, you can also make your own quiz from the ideas in a mind map, answer it, and return to the map to check what you missed.

Choose a mind map and build a quiz around the concepts you want to practice.