Requirements analysis
Requirements analysis is the systematic process of eliciting, clarifying, assessing, and documenting the needs and constraints a system or product must satisfy.
Delivering Machine Learning Projects: From design to deployment
Requirements analysis is the systematic process of eliciting, clarifying, assessing, and specifying what a system must provide and under what constraints.
- How it is used
- Tests whether proposed ML systems can meet business objectives within practical delivery constraints.
- How deep it goes
- Sets out requirement categories and an iterative validation process, deferring detailed story development until the project has funding and resources.
- Examples
- Uses a book recommendation task with input, output, cost, and latency requirements.
- What you can do after
- Evaluate and understand proposed solutions by identifying requirements, assessing viability, and drafting stakeholder stories.
Everyday Data Visualization
Requirements gathering is the process of documenting what a project should build, why it should build it, and whether stakeholders confirm those requirements.
- How it is used
- Structures project discovery by turning stakeholder and user conversations into approved scope for a dashboard or visualization.
- How deep it goes
- Details interviews, data checks, scope documentation, approval, and change effects, but does not describe implementation procedures.
- Examples
- Uses dashboard planning, a team productivity report, and mismatched team-name formats across systems as concrete cases.
- What you can do after
- Apply requirements analysis to define scope, document needs, secure approval, and communicate the consequences of later changes.
Read how Everyday Data Visualization explains requirements analysis →
Functional Design and Architecture: Examples in Haskell
Requirement analysis is the process of eliciting, examining, and specifying the capabilities and constraints a software system must satisfy.
- How it is used
- Guides domain understanding before architecture and implementation by collecting problems, facts, and notions to determine what to create.
- How deep it goes
- Moves from documentation and conversations to focused mind maps, then stops before architecture design and code implementation.
- Examples
- Uses a Minecraft brainstorming exercise expanded into level-one, level-two, and level-three mind maps.
- What you can do after
- Evaluate/understand a domain by collecting its problems, facts, notions, and important terms before constructing architecture.
Read how Functional Design and Architecture: Examples in Haskell explains requirements analysis →
Also covered in
- Grokking Relational Database Design
- Object-Oriented Software Design in C++
- Software Design for Python Programmers
- Decision EngineeringIn early access (MEAP)
- Architecture Modernization: Socio-technical alignment of software, strategy, and structure
What to know first
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
- meanThe mean is a measure of central location equal to the arithmetic average of numerical observations, or the probability-weighted average of a random variable’s possible values.
- throughputThroughput is the rate at which a system processes or completes work, data, or requests over a specified period.
- cachingCaching is the temporary storage of data or computed results for reuse, reducing the work or delay of retrieving or computing them again.
Related concepts
- software engineeringpart of · Software engineering is the disciplined application of engineering principles, methods, and tools to the specification, development, operation, and maintenance of software.
- behavior-driven developmentused by · Behavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
- database designpart of · Database design is the process of defining a database’s structures, relationships, constraints, and organization to meet data requirements.
- interviewhas part · An interview is a structured or semi-structured conversation in which questions elicit information about a participant’s experiences, views, needs, qualifications, or requirements.
- waterfall modelpart of · The waterfall model is a development and project-management approach that organizes work into largely sequential phases, with limited iteration between them.
Questions about requirements analysis
What is requirements analysis?
Requirements analysis is the systematic process of eliciting, clarifying, assessing, and documenting the needs and constraints a system or product must satisfy.
Which Manning books explain requirements analysis?
Delivering Machine Learning Projects: From design to deployment, Everyday Data Visualization and Functional Design and Architecture: Examples in Haskell.
What should I know before learning requirements analysis?
Manning books that teach requirements analysis usually introduce stakeholder, mean, throughput and caching first.
What is requirements analysis part of?
Requirements analysis is part of software engineering. Software engineering is the disciplined application of engineering principles, methods, and tools to the specification, development, operation, and maintenance of software.
What are the parts of requirements analysis?
Requirements analysis includes interview.
What is requirements analysis also called?
Requirements analysis is also called requirements gathering.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.


