GoConqr has a new look! Let us know what you think.

Requirements Engineering

34 resources created by 34 users

This Requirements Engineering page on GoConqr gathers community-made mind maps, flashcards, quizzes and a note, covering elicitation, validation and establishing requirements. University students and school students can use them to practice identifying and checking requirements, while teachers can find material to share. The page has over 30 resources across university and school levels, including more than 20 mind maps and a few quizzes and flashcard decks. Pick a resource and start exploring.

Requirements Engineering

Top Requirements Engineering resources

Quizzes

Mind maps

Flashcards

Notes

More Software Requirements and Design topics

About Requirements Engineering

GoConqr Original

Start with establishing requirements

Begin with the mind map “Establishing Requirements.” It asks what a project is trying to achieve, how it can achieve it and why it matters. It also looks at understanding users and producing a set of rules to start designing.

Next, open “Identifying need and establishing requirements.” This map considers understanding users, their work and their context. Use the two maps to compare how they describe the work of establishing requirements.

Explore elicitation

The “Requirement Elicitation” mind map introduces functional and non-functional requirements. It describes functional requirements in terms of how a system should react or behave, and non-functional requirements as constraints on services.

Continue with “Requirements Elicitation” to see types of requirements, including business, stakeholder and transition requirements. The “Requirements” flashcards offer questions about why elicitation is difficult and about the cyclical elicitation and analysis process. Read a map first, then use the cards to recall the ideas without looking back.

Check requirements with validation maps

The “Requirements Validation” mind map focuses on checking a requirements document. Its branches include completeness and consistency, conflicts, technical errors and ambiguity. It also introduces validation methods and requirement reviews.

Compare it with “Requirement Validation,” which includes raw requirements, validation and a final draft. As you study, look for the checks that appear in both maps and note where their coverage differs.

Use the page within the unit

Requirements Engineering is a section of the Software Requirements and Design unit in Computing and ICT (programming, computer science, digital skills, educational technology). The maps and flashcards offer starting points within this section, alongside the listed quizzes and note.

After working through a map, try the “Software Engineering” quiz and use its questions to guide another look at the resources. Choose a map or quiz and work through it at your own pace.

Frequently asked questions

Which resource should I start with?

The “Establishing Requirements” mind map is a useful starting point. It asks what a project is trying to achieve, how it can achieve it and why it matters. From there, the “Requirement Elicitation” map introduces functional and non-functional requirements, and “Requirements Validation” focuses on checking a requirements document.

What do the mind maps cover?

The maps cover establishing requirements, elicitation and validation. For example, “Requirements Elicitation” includes business, stakeholder, functional, non-functional and transition requirements. “Requirements Validation” covers checks for completeness, consistency, conflicts, technical errors and ambiguity, as well as validation methods and requirement reviews.

Are the resources free to use?

Yes. Every resource listed on this page is free to open, study and take without an account. The resources were made by GoConqr users. A free account can also save your quiz scores and let you make your own quizzes, mind maps, flashcards and notes.

Feedback

What is it about?

What do you think of the new look?

How do you like it?