Software Requirements and Design

What the resources cover

The unit splits into two halves: working out what a system must do, and deciding how to build it. On the requirements side, the mind maps include Introduction to RE, Requirements Engineering Processes, Types of Requirements, Requirement Elicitation and Non-functional requirements. There are also several maps on requirements validation. The map on Standard IEEE830-1998 walks through the overall description, user characteristics, constraints, assumptions and dependencies.

On the design side, you will find UML, design patterns, SOLID principles, service-oriented architecture and microservices.

Where to start

1. Open Introduction to RE, then Types of Requirements, to get the vocabulary.
2. Move to Requirements Engineering Processes and the validation maps.
3. Read the UML maps, including the one on structural, behavioural, grouping and annotational things.
4. Finish with design patterns and architecture.

Using quizzes and maps together

Read a map first, then test yourself. The UML arrows quiz asks which edge shows interface implementation and how aggregation is drawn. The Design Patterns quiz asks you to say what Adapter, Observer, Factory method, Abstract Factory, Decorator and Command are, and when to use them. The Software Architecture quiz covers module and service structures. Go back to the map for anything you miss.

Flashcards for recall

The Design Patterns flashcard deck gives examples of SOLID principles and DRY. The GoF Design Patterns and Non-GoF Design Patterns decks are good for quick recall. The State Machine Diagrams deck helps with behaviour modelling.

Where it fits

This unit sits in the Software and Systems Development strand of Computing and ICT. Some resources mention SQA Higher and National 5 Computing Science, so school students may find a few useful items too.

Choose one map, take one quiz, and then make your own flashcards from what you missed.