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 customer objectives can become a practical ML project before detailed delivery work begins.
- How deep it goes
- Defines requirement categories and a clarification process, then develops validation stories while deferring detailed stories until funding and resources are available.
- Examples
- Uses book recommendations from a user profile, budget, and date, constrained by per-request cost and response time.
- What you can do after
- Practice/perform pre-project validation by specifying constraints, checking viability, and drafting stories that expose harms and corner cases.
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 →
Related concepts
- database designpart of · Database design is the process of defining a database’s structures, relationships, constraints, and organization to meet data requirements.
- waterfall methodologypart of · Waterfall methodology is a software development approach that organizes work into predominantly linear, sequential phases, with limited iteration between them.
- behavior-driven developmentused by · Behavior-driven development is a collaborative software practice that specifies and validates expected behavior through human-readable examples meaningful to technical and nontechnical stakeholders.
- 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.
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.