What's is the best diagram to show technologies used to develop a solution?
When a fairly complex application is developed, it'll involved a number of different components.
E.g.: An multi-tier application with;
- A data store
- A processing server (implemented on an application server)
- A web application
- An android app
We can show there components clearly in component diagrams or deployment diagrams.
But, all above components will be implemented with different technologies such as MySQL, Tomcat, Java, JSP, Angular etc...
Is there a standard diagram that we can show the technologies used for the overall solution (in UML/ Archimate etc...)? Such a diagram can help to plan a software development project as well as to build the technology landscape of an organization.
It is a bit beyond what I typically do but I would say the deployment and component diagrams are all you need.
The deployment diagram allows you to show the components of the system on the deployment level, indicating specific artifacts and environments on which those are deployed. It doesn't have a direct indicator of technology used, but you could easily use e.g. stereotypes for that. If you want a visual representation, combine it with profiles.
Note that environment can be any executable environment so for example a FE component deployed on TomCat run under Solaris server will have the Solaris as environment with TomCat deployed on it also as environment and eventually the component itself shown as component with artifact representing actual implementation (and language). The diagram below, taken from uml-diagrams.org may be a bit simplified view (for instance doesn't show specific technologies) but overall shows how detailed the listing of elements can be. Just add stereotypes and you have what you need.
The component diagram obviously doesn't show deployment level so no environments are there. But again, using stereotypes (and with profiles - those can again be represented in a visual way) you can show the technology (programming language and frameworks) used to create specific components. It is more system logic architecture level.
The choice of diagrams will depend on what specifically you want to show.
- Do you know any alternative to NDepend for architects?
- Xcode 12 Apple M1 arm64 - Designable error: "wrong architecture"
- Building a minimal plugin architecture in Python
- Cross module communication in modular monolith
- Software design for simultaneously running python programs
- Proper design for th Keycloak auth with APIs and UI
- "Aggregator microservice" or just gateway api?
- Macro definition to determine big endian or little endian machine?
- Angular Service Injection in reusable components
- What is the real difference between an API and an microservice?
- Offset pagination vs Cursor pagination
- With the MESI protocol, a write hit also stalls the processor, right?
- Architecture design for divide the subsystems
- Solution/Architecture: queues or something else?
- How functional approach of web app architecture looks like?
- Prevent duplicate messages
- The better way to read a formated data from .TXT file strings in Python
- Building app and Anti pattern (distributed monolith...)
- Effective Backend for Real Estate Application
- In which place is it better to create kafka topics programmatically?
- What's the relationship between assembly language and machine language?
- Logging out: GET or POST?
- Architectural question - how to avoid multiple events tobe processed at the same time
- Layered architecture, Request and Response DTO, or View Models
- Interfaces and errors in go
- How to Implement Queue Based Workflow System?
- "Microservices Using Database Per Service" pattern in practice
- Handling Multiple Actors in a Use Case in Clean Architecture and DDD
- Should services always return DTOs, or can they also return domain models?
- When do I call my class controller, manager or service?