requirements - Concepts

Explore concepts tagged with "requirements"

Total concepts: 18

Concepts

Software Analysis - The process of studying a software system to understand its requirements, structure, behavior, and constraints before design and implementation.
Given-When-Then - A structured format for writing acceptance criteria and test scenarios that specifies context, action, and expected outcome in plain language.
Functional Requirements - Requirements that specify what a system should do, including its features, capabilities, and behaviors.
User Acceptance Testing - The final phase of testing where actual users or stakeholders verify that a system meets their requirements and is ready for deployment.
User Stories - Short descriptions of features from the user's perspective used to capture requirements.
Non-Functional Requirements - Requirements that specify quality attributes of a system such as performance, security, reliability, and usability.
Job Story - A requirements format from JTBD that focuses on the situation and motivation rather than the user persona, using 'When... I want to... So I can...' structure.
Specification by Example - A collaborative approach to defining software requirements using concrete examples that serve as both living documentation and automated tests.
Product Requirements Document - A document that defines the purpose, features, functionality, and behavior of a product to be built.
INVEST Criteria - A set of six qualities that make a good user story: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
Three Amigos - A collaborative practice where a product owner, developer, and tester discuss a user story together to build shared understanding before development begins.
Requirements Elicitation - The process of gathering and discovering requirements from stakeholders through interviews, workshops, observation, and other techniques.
Requirements Engineering - The systematic process of defining, documenting, validating, and managing software requirements throughout a project lifecycle.
Use Cases - Descriptions of interactions between actors and a system to achieve specific goals, capturing functional requirements in a scenario-based format.
Business Analysis - The practice of identifying business needs, analyzing problems, and determining solutions that deliver value to stakeholders.
Backlog - A prioritized list of all desired work items for a product or project.
Software Requirements Specification - A comprehensive document that describes what a software system should do, including functional and non-functional requirements.
Acceptance Criteria - Specific conditions that must be met for a user story or feature to be considered complete and acceptable.

← Back to all concepts