![]() ![]() Most engineers only think of the last 3 layers - what they build and maintain. We like to see 4 layers - from top to bottom: Yet, it may be a new concept for technical stakeholders. This technique is common among Engineers. Let's look at examples of each of these techniques. Use different shades of 1 color to show relative differences.Use red/yellow/green colors to show health or risk.If you need acronyms, use a legend or reference key.Avoid technical terms as much as possible.Consider a hierarchical numbering scheme to tie the drawing to other artifacts.Consider printing on a large format printer - at least 11" x 17".Use animation with more than a dozen objects on the diagram.Only use arrows or connecting lines to show data flow.Organize left to right to show processes or journeys.Group in layers such as users, user interfaces, business logic, and data persistence.To create an effective diagram for non-technical stakeholders, we use several techniques. As such, diagrams need to be artistic enough to tell the right story. In Transformations, another goal is to show the current state and one or more future states. The goal of these diagrams is to bridge the communication gap between 'The Business' and technology. ![]() Technology Diagrams for Business Stakeholders or non-Engineers are designed for the rest of the organization. Most Technology Diagrams are designed by Engineers for Engineers. What is a Technology Diagram for Business Stakeholders? Explaining to Executives how different components interact and where technical debt exists.Splitting a monolith to understand what component/services belong to specific business domains.Mergers and acquisitions where digital products/services have overlapping or similar features.In our previous blogpost The Big Picture - Connecting Strategy to Architecture, we identified Technology Diagrams as an important artifact during Transformations.Ī technology diagram is helpful in the following digital transformation scenarios: ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |