The Solution Sketch and Process/ Application Design templates come preset under the Solution Architecture Design phase. The Solution Sketch puts the proposed solution on paper to find the right mix of reused and new components. The Process and Application Design views show how business processes and applications work after the change.
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 details on what permissions each role has.
The object definitions for the design type you are creating are available in your repository (listed per design type below).
Open a View
From the Basic workflow preset:
Create a project with the Basic workflow. See Create a New Project for the steps.
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.
Solution Sketch
The sketch brings together the solution components, found on the Service Blueprint, High-Level Design, and other Solution Specific Requirements. Uses the following object definitions:
Capability
Business Service
Business Object
Application Service
Technology Service
Business Process
Data Object
Application
Node
Open the Solution Sketch template.
Click the pencil
icon in the right corner to activate edit mode.Drag and drop the relevant objects from the repository onto the view, bringing in their relationships where relevant.
Create any component that does not exist in the architecture yet as a new object, marked as Future state. For detailed instructions, refer to Add Objects to Architecture Views
Add annotations, graphics, and icons to record assessments and decisions.
The sketch now documents the solution direction and the reuse-versus-new decisions behind it.
TIP: Use the draw-related-objects tool on an object to bring more potentially relevant objects onto the view. If the sketch grows too big, split it into multiple sketches.
Process and Application Design
All seven design types below share one view template, split into a Current State and a Target State section. You document how processes and applications work today in the current state, and how they work after the change in the target state, so the two can be compared side by side.
Which design types you need depends on the scope of the change. For example, a change to a way of working with no technological enhancements may need the Process Flow Design.
Process Flow Design
Shows how a business service is realized by its underlying processes, for the current and target state. Uses: Business Service, Business Process, Business Process (L2), Business Process (L3), Business Object.
Click the pencil
icon in the right corner to activate edit mode.Place the current business process on the left side
Connect the missing business processes, then the relevant inputs and outputs.
Copy the current state to the target state, and add the processes, inputs, and outputs the service needs.
NOTE: Detailed work processes can be mapped in BPMN and connected through the navigation structure.
Application Component Design
Shows how an application fits into the solution, with business processes or application services above it and technology underneath. Uses:
Business Process
Application Service
Application
Application Parts
Data Objects
Nodes
Technology Services
Connect each application to the business processes that use it
Connect the Data Objects each application holds that those services and processes depend on. Duplicated or unshared data between applications now shows on the view.
Design the integrations between the applications in the Application Flow Design.
Fit the supporting technology under the application.
Annotate findings and open decisions directly on the view, for example, an overlap between two applications or a phase-out still to be decided.
TIP: Create this view only for applications central to the solution or functionally complex; fitting every application into the solution does not require its own view.