Knowra Requirements analysis Requirements analysis Requirements analysis identifies, examines, and documents stakeholder needs and constraints to define what a system must do and the conditions it must satisfy.
Stakeholder analysis : The identification and assessment of people or organizations that affect or are affected by a project. It identifies whose needs and influence must shape the analysis.
Functional requirement : A statement of a function or behavior that a system must provide. It captures what the system is required to do.
Requirements engineering : The systematic discipline of eliciting, analyzing, specifying, validating, and managing requirements. Requirements analysis is one activity within this broader discipline.
Design specification : A description of how a system or component will be structured and implemented. Analysis defines what is needed; design specifies how to meet those needs.
Requirements elicitation : The process of discovering requirements through activities such as interviews, observation, and workshops. It supplies the needs and constraints that analysis examines.
Non-functional requirement : A requirement specifying a system quality, constraint, or operating condition rather than a particular function. It expresses constraints such as performance, security, or usability.
Software development life cycle : A structured process for planning, building, testing, deploying, and maintaining software. Analysis informs system decisions throughout the development process.
Feasibility study : An assessment of whether a proposed project or solution is practical and worthwhile. Feasibility constrains which stakeholder needs can realistically become requirements.
Requirements classification : The organization of requirements into categories such as functional, nonfunctional, and domain requirements. Classification makes different kinds of stakeholder needs easier to examine.
Business requirement : A statement of an organization’s goals, outcomes, or needs that motivate a project. It connects system requirements to the outcomes stakeholders seek.
Show all 22