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
- All Software Requirements and Design resources
- Software Development Methodologies9
- Software Requirements Types and Specification30
- User Interface Design and Prototyping17
- Software Design Principles19
- Design Patterns47
- Software Architecture36
- Software Architecture Views and Description15
- Architectural Styles and Patterns55
- Service-Oriented Architecture30
- Microservices Architecture10
- UML Diagrams44
Top Requirements Engineering resources
-
87 questionsSoftware Engineering What is a requirement?
-
89 cardsRequirements Engineering What are requirements?
-
49 nodesRequirements Elicitation Types of Requirements · Techniques · Inputs · Outputs
-
137 nodesChapter 4: Requirements Engineering (3705) Functional and non-fu... · Requirements engineer... · Requirements elicitation · Requirements specific... · Requirements validation · Requirements change
-
69 nodesIdentifying need and establishing requirements May aim to replace, u... · 2 Main Aims · The activity of under... · Task Description: Are... · Task Analysis: Use to...
-
41 nodesRequirements Engineering Type of Requirements · Requirements Engineer... · Requirements Elicitation · Requirements Specific... · Requirements Validation
-
14 cardsRequirements Requirements elicitation is difficult due to (4 reasons)...
-
105 nodesRequirements Engineering Framework Requirements Document... · Requirements Management · Requirements Elicitation · Requirements Analysis · Requirements Validation
Quizzes
Mind maps
-
49 nodesRequirements Elicitation Types of Requirements · Techniques · Inputs · Outputs
-
137 nodesChapter 4: Requirements Engineering (3705) Functional and non-fu... · Requirements engineer... · Requirements elicitation · Requirements specific... · Requirements validation · Requirements change
-
69 nodesIdentifying need and establishing requirements May aim to replace, u... · 2 Main Aims · The activity of under... · Task Description: Are... · Task Analysis: Use to...
-
41 nodesRequirements Engineering Type of Requirements · Requirements Engineer... · Requirements Elicitation · Requirements Specific... · Requirements Validation
-
105 nodesRequirements Engineering Framework Requirements Document... · Requirements Management · Requirements Elicitation · Requirements Analysis · Requirements Validation
-
24 nodesRequirement Elicitation Functional Requirements · Non-Functional Requir... · Steps in requirement ... · Different ways to rep...
-
66 nodesRequirement Validation Objective · Analysis · Validation · Requirements Reviews · Problem actions · Preview Checking
-
63 nodesREQUIREMENTS VALIDATION Certifies requirement... · Analysis & Validation · Validation Inputs · Validation Outputs · Review · Problem Actions
Flashcards
Notes
More Software Requirements and Design topics
About Requirements Engineering
GoConqr OriginalStart 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.