Software Engineering, unit: Requirements Engineering. Core concepts, terminology, and worked-example cues a college student meets for this unit, building on prior units without repeating them. Front: a term, concept, or short problem cue. Back: the definition, explanation, or answer.
16 cards · basic cards · AI-written, checked twice. Edit anything.
- What is requirements engineering?
- The process of gathering, analyzing, documenting, and managing software requirements
- What is a functional requirement?
- A requirement describing what a system should do, such as a specific feature
- What is a non-functional requirement?
- A requirement describing how a system should perform, such as speed, security, or usability
- What is a stakeholder, in requirements engineering?
- Any person or group with an interest in or influence over a software project
- What is requirements elicitation?
- The process of gathering requirements from stakeholders through interviews, surveys, or observation
- What is requirements analysis?
- Examining gathered requirements for completeness, consistency, and feasibility
- What is requirements specification?
- Formally documenting requirements in a clear, unambiguous, and structured format
- What is requirements validation?
- Confirming that documented requirements accurately reflect stakeholder needs
- What is a use case?
- A description of how a user interacts with a system to achieve a specific goal
- What is a user story, in Agile requirements engineering?
- A short, informal description of a feature from the perspective of an end user
- What is requirements traceability?
- The ability to track a requirement through design, implementation, and testing
- What is scope creep?
- The uncontrolled expansion of a project's requirements beyond its original scope
- What is ambiguity, as a risk in requirements documentation?
- Vague or unclear wording that can be interpreted in multiple ways
- What is a requirements review used for?
- Verifying requirements are correct, complete, and agreed upon before development begins
- What is prioritization, in requirements management?
- Ranking requirements by importance or urgency to guide development order