Add Your Heading Text Here
The requirements management glossary.
Clear, practical definitions of the requirements, compliance, and Azure DevOps terms used across the Modern Requirements platform.
A
Acceptance criteria
Acceptance criteria are the specific, testable conditions a user story or requirement must meet to be considered complete.
WeiterlesenAzure DevOps work item
A work item in Azure DevOps is a record used to track a single piece of work, such as a user story, bug, task, feature, or epic.
WeiterlesenC
E
EARS notation
EARS, short for Easy Approach to Requirements Syntax, is a set of simple sentence templates for writing clear, testable requirements.
WeiterlesenEpisch
In Azure DevOps, an epic is the highest level of work item, representing a large body of work that spans multiple features and often several months.
WeiterlesenF
Funktion
In Azure DevOps, a feature is a mid-level work item that represents a distinct capability a product delivers, sitting below an epic and above user stories.
WeiterlesenFunctional requirements
A functional requirement describes something a product must do: a specific behavior, feature, or response to a given input.
WeiterlesenN
P
R
Anforderungsanalyse
Requirements analysis is the work of examining gathered requirements to make sure they are clear, complete, consistent, and feasible, then prioritizing and refining them into something a team can build.
WeiterlesenRequirements baseline
A requirements baseline is a reviewed and approved set of requirements, frozen at a point in time to serve as the agreed reference for the work ahead.
WeiterlesenRequirements elicitation
Requirements elicitation is the work of drawing out what stakeholders actually need, using techniques like interviews, workshops, observation, and prototyping.
WeiterlesenRequirements engineering
Requirements engineering is the discipline of discovering, analyzing, documenting, validating, and managing the requirements for a system across its lifecycle.
WeiterlesenRequirements gathering
Requirements gathering is the process of collecting the needs and expectations for a product from stakeholders, users, and other sources at the start of a project.
WeiterlesenRequirements management
Requirements management is the process of documenting, organizing, and tracking a product's requirements across its lifecycle, so that stakeholder needs are captured, agreed on, and traceable from first idea…
WeiterlesenRequirements management in Azure DevOps
Requirements management in Azure DevOps is the practice of capturing, organizing, and tracing requirements directly inside Azure DevOps, using work items like epics, features, and user stories rather than…
WeiterlesenRequirements management plan
A requirements management plan is a document that sets out how requirements will be handled on a project: how they are captured, tracked, changed, and traced, and who is responsible for each part.
WeiterlesenAnforderungsüberprüfung
A requirements review is a structured check of requirements by stakeholders to confirm they are clear, complete, correct, and agreed before development starts.
WeiterlesenRückverfolgbarkeit der Anforderungen
Requirements traceability is the practice of linking each requirement to its source and to everything downstream that fulfills or verifies it, such as designs, code, and test cases.
WeiterlesenRequirements traceability matrix (RTM)
A requirements traceability matrix, or RTM, is a table that maps each requirement to the items that satisfy and verify it, such as design elements, test cases, and results.
WeiterlesenRequirements versioning
Requirements versioning is the practice of tracking changes to requirements over time, keeping a record of what changed, when, and by whom.
WeiterlesenS
T
Test case management in Azure DevOps
Test case management in Azure DevOps is the practice of creating, organizing, and running test cases within Azure Test Plans, and linking them to the requirements and user stories they verify.
WeiterlesenTraceability in Azure DevOps
Traceability in Azure DevOps means linking work items to each other and to code, builds, and tests, so a team can follow a requirement through to the work that delivers and verifies it.
WeiterlesenU
Anwendungsfall
A use case describes how a user, or another system, interacts with a system to achieve a specific goal, laid out as a sequence of steps including the main path and the things that can go wrong.
WeiterlesenUser story
A user story is a short, plain-language description of a feature told from the point of view of the person who wants it, usually in the form 'as a [user], I want [goal], so that [benefit]'.
WeiterlesenV
W
Put these terms to work in Azure DevOps
See how Modern Requirements turns definitions into a single source of truth for requirements, traceability, and compliance.
