Table of Contents
High level architecture diagram
6.1 Conceptual View
[Description: This section should contain description of general solution concept; this view is single and simple picture for all involved stakeholders.
Synonym view name: marchitecture view.
Section purpose: View should explain what solution general purpose is, how it will be used by key roles and how it will be integrated with existing infrastructure and 3rd party solutions/systems.
Section target audience: Customer business and engineers, EPAM development Team, etc.
Section content: business-oriented conceptual diagram(s), text description.
Section Type: Mandatory if legacy solution should be re-designed and re-implemented]
[Example: Conceptual diagram. See more examples and source files here: https://kb.epam.com/display/CTOOCC/Solution+Architecture+Diagrams+Best+Practices
]
6.2 Logical View
[Description: This section should contain description of solution structure. This is not 4+1 architectural view model view, though you can use 4+1 notation in this part if it fits for your purpose.
Synonym view name: solution structure view.
Section purpose: View should explain what components the solution consists of (including technical details about each component like technology stack, etc).
Section target audience: Customer engineers, EPAM development Team, etc.
Section content: logical diagram(s) and text description that describes:
- Solution structure.
- Set of solution components.
- High-level architectural styles to be used in the solution architecture and motivation for them.
Include the following items:
- High-level solution structure diagram (highly recommended).
- List of architecturally significant components and descriptions of their technology stack and integration with each other.
- High-level description of the solution’s behavior (in terms of sequences, state-machine, data flow and execution diagrams) – if this makes sense.
- Recommendations about architectural styles/patterns to be used.
Section Type: Mandatory if legacy solution should be re-designed and re-implemented]
[Examples: Logical diagram. See more examples and source files here: https://kb.epam.com/display/CTOOCC/Solution+Architecture+Diagrams+Best+Practices
Example 1:
Example 2:
Example 3:
]
6.3 Integration View
[Description: This section should contain description of aspects of solution integration with other products/solutions/systems.
Section purpose: View should explain how exactly solution will be integrated using what interfaces, tools, technologies, etc).
Section target audience: Customer engineers, EPAM development Team, etc.
Section content: diagram(s), text description.
Section Type: Mandatory if legacy solution should be re-designed and re-implemented]
6.4 Data View
[Description: This section should contain description of aspects of solution data architecture.
Section purpose: View should describe data model and explain how exactly solution data will be collected/streamed, processed, stored, etc.
Section target audience: Customer engineers, EPAM development Team, etc.
Section content: diagram(s), text description.
Section Type: Mandatory if legacy solution should be re-designed and re-implemented]
6.5 Infrastructure / Deployment View
[Description: This section should contain description of solution deployment and infrastructure (for all key environments, like development, staging, production, etc.).
Synonym view name: physical view.
Section purpose: View should explain how exactly particular components the solution will be deployed (including technical details about network, network security, performance and availability aspects, technology stack that will be used for deployment, etc).
Section target audience: Customer engineers, EPAM development Team, etc.
Section content: deployment diagram(s), text description.
Section Type: Mandatory if legacy solution should be re-designed and re-implemented]
6.6 [Any other views to be placed here]
[Description: Feel free to add any other views that you need to describe baseline solution architecture from any other points of views.
...
Deployment diagrams
Rancher community
