Processes and roles
Describe participants, data they use and the expected outcome of each workflow.
Preparing your experience…
Before implementation, everyone needs a shared understanding of what a solution must do and how it will be validated. An SRS makes business needs explicit and reduces ambiguity.
An SRS covers functional needs, business rules, exceptions, integrations, non-functional requirements and acceptance criteria. The detail depends on project risk.
Describe participants, data they use and the expected outcome of each workflow.
Specify behaviours, constraints, integrations and acceptance conditions.
Connect business needs, requirements, priorities and tests.
Collect input from business, users and technical stakeholders.
Map processes, rules, scenarios and key data.
Document functional and non-functional requirements.
Review agreements and priorities with stakeholders.
Talk to us before building or procuring your next solution.