The High-Level Design and Solution Requirements templates come preset under the Requirements Refinement phase. The High-Level Design explains the solution so non-technical stakeholders can understand it. The Solution Requirements view visualizes the most important requirements and their relationships with Business Services.
For an overview of all templates and phases, see Solution Design Templates.
Prerequisites
You have access to the project as a Project Owner or Project Contributor. Refer to Roles and Permissions for Solution Design for what each role can do.
For the Solution Requirements template: the Business Service and Requirement object definitions are available in your repository.
Open a View
From the Basic workflow preset:
Create a project with the Basic workflow. See Create a New Project.
On the right side of a deliverable in the Requirements Refinement phase, click
to create or connect a View.Click Create view
For detailed instructions on connecting a view, refer to Connect a View to a Deliverable.
High-Level Design Template
The High-Level Design tells the story of the solution with icons, text, pictures, and shapes. It is also known as a charcoal sketch, napkin sketch, or bird's-eye view.
Open the High-Level Design template.
Take the Gain Creators and Pain Relievers from the Value Proposition Canvas as the outcomes your story must reach, and the services, processes, and systems from the Service Blueprint as the medium that delivers them.
Craft the story connecting customer, outcomes, and medium with FreeShapes, supplemented by your own custom images.
Reuse existing objects from the repository where applicable, for example, an application or a data object. Structured data is not needed yet.
The design now communicates the solution in a form that non-technical stakeholders can follow.
Solution Requirements Template
The Solution Requirements visualizes requirements, their relationships with Business Services, and properties such as MoSCoW, using objects and conditional layouts. MoSCoW is a prioritization method that ranks each requirement as must-have, should-have, could-have, or won't-have.
Open the Solution Requirements template.
Place the Business Service and its sub-services in the top section: the services the change creates or improves.
Place the applicable Requirements and sub-requirements in the bottom section: these are the conditions those services must satisfy. Use the first level of requirements as the category, for example, regulatory or security requirements.
In each Requirement's questionnaire, fill in the properties, such as MoSCoW priority and owner, and relate the Requirement to the Business Service it supports. Refer to Object Questionnaires for how to open and fill in a questionnaire.
The view now shows which requirements support which Business Services.
TIP: Manage requirements in an Excel sheet first, as they evolve through many rounds of stakeholder input (columns such as ID, short name, description, MoSCoW, owner, parent ID). Use the exact MoSCoW values from the questionnaire dropdown so requirements display correctly in the view.