[[
wikihub
]]
Search
⌘K
Explore
People
For Agents
Sign in
Explore
People
For Agents
Sign in
@jemoka / Jemoka Knowledge Base / wiki/concepts/requirements_analysis.md
Suggest edit
Cancel
Submit suggestion
Title
Name
Note
--- title: "Requirements Analysis" type: concept related: [User Interviews, Requirements Analysis, Customer Journey Map] source: https://www.jemoka.com/posts/kbhrequirements_analysis/ confidence: high status: active --- Requirements Analysis is how to satisfy your persnickety users while keeping your fucking app simple. Goal The broad goal of Requirements Analysis is to come up with a spec that is: Documented Actionable Measurable Testable Traceable Defined with details Satisfies business goals Timing Requirements Analysis should be performed when Calculating costs Setting priorities Creating breakdowns Including specialists Steps Gather requirements by doing User Interviews Analyze the requirements for clarity, completeness, consistency, and lack of conflicts Write them down and implement them Tools Gap Analysis Analyze the difference between where the business is at and its stated goals; figure out how the goals can be closed. Business Motivation Model (BMM) Does it matter? https://www.omg.org/spec/BMM/1.3/PDF Someone decided to throw XML to running a company. Why. Customer Journey Modeling See Customer Journey Map