Specification
The specification, also known as “Functional Requirement Specification”, is a document used to describe a solution's intended capabilities, appearance, and interactions with users.
Last updated
The specification, also known as “Functional Requirement Specification”, is a document used to describe a solution's intended capabilities, appearance, and interactions with users.
Last updated
Specification is the first of three phases in the Uniscale Method.
Before describing your specification, check our article for an overview of the elements and functionalities: Solution basics
Now start with: High-level specification
Lastly, proceed to: Detailed specification
| High level - Abstract | Detailed - Concrete | |
|---|---|---|
What
High-level overview and introduction of your product:
Abstract specification
Purpose and motivation
High-level requirements
High-level end-user behaviour
Overview of actors
Structure breakdown
Moving from abstract to concrete thinking:
Decide the overall approach to your solution.
Concrete user interface.
UX requirements.
UI requirements.
Why
Align all stakeholders on what you are building and the purpose while serving as a reference point for your solution.
The detailed specification guides all UI and UX design aspects, forming the user experience foundation.
Who
Product Owner or someone with a deep understanding of the product.
UX/UI Designer
Outcome
A clear understanding of the requirements and desired outcome.
An overview of the structure of your product.
A specification ready to be handed over to your product designer for continuing on the detailed specification.
Deciding on the look and feel of your product.
A fully specified solution that can be handed to your technical team to start the service linking.
How
