requirements - Concepts

Explore concepts tagged with "requirements"

Total concepts: 13

Concepts

Requirements Engineering - The systematic process of defining, documenting, validating, and managing software requirements throughout a project lifecycle.
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.
Software Analysis - The process of studying a software system to understand its requirements, structure, behavior, and constraints before design and implementation.
Acceptance Criteria - Specific conditions that must be met for a user story or feature to be considered complete and acceptable.
Business Analysis - The practice of identifying business needs, analyzing problems, and determining solutions that deliver value to stakeholders.
Product Requirements Document - A document that defines the purpose, features, functionality, and behavior of a product to be built.
Software Requirements Specification - A comprehensive document that describes what a software system should do, including functional and non-functional requirements.
Requirements Elicitation - The process of gathering and discovering requirements from stakeholders through interviews, workshops, observation, and other techniques.
Backlog - A prioritized list of all desired work items for a product or project.
Use Cases - Descriptions of interactions between actors and a system to achieve specific goals, capturing functional requirements in a scenario-based format.
Non-Functional Requirements - Requirements that specify quality attributes of a system such as performance, security, reliability, and usability.
Functional Requirements - Requirements that specify what a system should do, including its features, capabilities, and behaviors.
User Stories - Short descriptions of features from the user's perspective used to capture requirements.

← Back to all concepts