Solution Blueprint¶
The solution blueprint collects the solution components that together deliver a business solution.
A project may have multiple solution blueprints, each showing a particular aspect, or level of detail. The aim is to model only the detail that is important for the team members to discuss, agree on and share with stakeholders. As such, a blueprint does not contain many of the details, such as data types and cardinality, typically found on more technical models such as UML, or E-R diagrams. Their purpose is to support the telling of a story.
The diagram below shows the mermaid diagram produced by Egeria for a solution blueprint that describes how the Open Metadata Archives are created and loaded.
---
title: Components and Roles for Solution Blueprint - Open Metadata Archive Solution Blueprint [a5a780a1-6f54-4f3c-bdc5-970c371ffb4e]
---
flowchart TD
%%{init: {"flowchart": {"htmlLabels": false}} }%%
subgraph 1 [Components and Actors]
2@{ shape: lin-cyl, label: "*Solution Component*
**Open Metadata Archive**"}
3@{ shape: lin-cyl, label: "*Solution Component*
**Open Metadata Repository**"}
4@{ shape: subproc, label: "*Solution Component*
**Egeria Gradle Build**"}
5@{ shape: rect, label: "*Solution Component*
**Load Archive**"}
6@{ shape: trap-t, label: "*Solution Actor Role*
**Egeria Open Source Community**"}
6==>|"develops content,
[Solution Component Actor]"|2
4==>|"constructs,
[Solution Linking Wire]"|2
5==>|"reads,
[Solution Linking Wire]"|2
5==>|"load,
[Solution Linking Wire]"|3
7@{ shape: trap-t, label: "*Solution Actor Role*
**Open Metadata User**"}
7==>|"calls,
[Solution Component Actor]"|5
end
style 1 color:#FFFFFF, fill:#3079ab, stroke:#000000
style 2 color:#000000, fill:#dda0dd, stroke:#000000
style 3 color:#000000, fill:#dda0dd, stroke:#000000
style 4 color:#000000, fill:#dda0dd, stroke:#000000
style 5 color:#000000, fill:#dda0dd, stroke:#000000
style 6 color:#000000, fill:#FFE599, stroke:#000000
style 7 color:#000000, fill:#FFE599, stroke:#000000The inverted trapeziums shown in yellow are the solution actor roles involved in the solution. They are typically teams, roles, or individuals that are part of the solution. However, they may be automated processes from outside the solution that are interacting with one or more of the solution components.
The solution components are shown in pink. Their shapes indicate the type of component (based on the solutionComponentType attribute).
A solution blueprint is defined as a specialized collection of solution components. The visualization of the blueprint includes just these components, any solution actors linked to these components and the solution linking wires that collect them together. Each solution linking wire includes the label from the relationship as well as its type.
The operations for working with solution blueprints are found in the Solution Architect services and the open metadata types are found in model 0740 Solution Blueprints.
Raise an issue or comment below