tipsoreo.blogg.se - Application architectural diagrams

APPLICATION ARCHITECTURAL DIAGRAMS HOW TO
APPLICATION ARCHITECTURAL DIAGRAMS CODE

Even then, a generated diagram many not be at the correct logical solution level nor apply the proper lens to the diagram for the solution architect's specific need. Magic diagram creation seems like a no brainer: why not just press a button to get a diagram? However, this would only work in the same scenarios as #2. There are also tools for some platforms that generate platform-specific architecture diagrams based on the configured operating environment. In this case a "comes with" diagram can be very fit-for-purpose. This is a special case of #1 because these diagrams are usually created at the building block level.

APPLICATION ARCHITECTURAL DIAGRAMS CODE

In low-code and other graphical configuration-over-code environments, icon-based workflows often serve as both code and visual documentation (aka.

Even then, this will not provide the greatest design agility moving forward if the organization decides to take advantage of future innovations outside the current stack.

In organization's where the entire technology stack is standardized on a single platform (or platform vendor), a platform-specific architecture diagram approach that is well suited for the organization's architecture design needs may be suitable.

Often times a fit-for-purpose design product, including a specific diagramming approach, is best suited to communicate that level of design to the developers and/or implementation team. While solution architects assemble a solution using the technology building blocks of the enterprise, those building blocks often require design as well.

Platform-specific diagrams can be appropriate at the more detailed levels of the architecture where the application and component architecture are designed.

There are situations where platform-specific architecture diagrams make sense. If UML is not your preference for Solution Architecture diagrams, then select the notation of your choice, but make sure it is platform-agnostic! I would also recommend against too many icons, but I will save that for another article! When to use Platform-Specific Architecture Diagrams So not only can UML be your diagramming solution, but it can also be the foundation of a hybrid solution.

In a pinch, you can add icons to the components - UML allows that - to satisfy your trendy, flavor of the day, icon-architecture audience, thus making UML your rosetta stone across icon architecture boundaries.With them you can seamlessly diagram your way across all architecture paradigms and components, including ones you need a time machine to purchase. The icon-free shapes are a boring but timeless, and can represent any architecture component you throw at them.Our recommendation is the tried and true UML. Not surprisingly, we recommend you adopt a platform-agnostic standard notation for solution architecture diagrams. The impact can range from making your diagram look dated to obsoleting the meaning of the icons you used. Plus, any time someone new gets hired in the marketing department, new and improved icons are released. Those icons spread the brand all over the place they are as much a marketing tool as an architecture tool. The last thing you want is for them to have to figure out your icons and notation before they can start understanding your architecture.

APPLICATION ARCHITECTURAL DIAGRAMS HOW TO

The most optimized approach is to teach your audience how to read a single, simple diagram approach, then let them enjoy that forever. The goal of architecture diagrams is to communicate architecture designs clearly. For example, a single architecture can include AWS and Azure cloud components alongside on-premises mainframe and distributed components.Īrchitecture is already Confusing Enough. This diversification of technologies results in architectures with an expansive sprawl across platforms and paradigms. In any enterprise of moderate complexity, those building blocks are a variety of technologies and some are, er, more mature than others. Solution architects assembly solutions from the technology building blocks of the enterprise. At that point, the notation should get as much thought as the keyboard does when you are writing a document.Īrchitecture is Heterogeneous. Solution architects should burn a diagram notation into muscle memory until they can use it to fluently communicate architecture. I want the time I spent learning Novell icons back.) A solution architect needs to keep pace with new architecture paradigms, but learning new platform-specific architecture diagrams and icons to communicate them is not a valuable use of time. I don't want to sound like a curmudgeon, but today's architecture trend is tomorrow's legacy system.