UML aggregation of user access to multiple components
Got the following diagram of a building block view level 1 (no technical unit allowed here). Each component shown has an interaction with users. The UML port (baz) at the top should visualize the user access. Do I really need to draw a dependency from the UML port "baz" to each component, or can I aggregate user access to all components in some way?
I've tried drawing dependency lines from each component to the top UML port - but this looks messy.
Yes, you need to draw dependency lines to each component. If that looks messy, maybe your design is messy. Or maybe, it's just necessary. Remember, if your design is complicated, the diagram will - and should - reflect it. By visualizing the complicated structure, it is at least easier to reason about it.
Now the question is, whether the interface is really the same for all components? If not, you need to have separate ports anyway. And then it is important to know which component talks to which port.
- Self-Contained Systems vs Monolithic
- Handling Multiple Actors in a Use Case in Clean Architecture and DDD
- iOS: error when running project on real device
- How to avoid using global variables and how to split code across dart files in flutter
- What's the difference between REST & RESTful
- Service layer in java swing application
- ExtJS Architecture for Multi Page Application
- How to design an efficient Pub/Sub pull subscriber for both maximum throughput and fault-tolerance?
- Facebook - Twitter authentication - information merge
- Service oriented architecture vs Microservices
- Event sourcing, CQRS with Axon Server / Framework - Event Sourcing the entire application a good idea?
- ExtJS 7 application architecture
- Is decision-logic inside Android Composable functions a bad idea?
- WPf, MEF Architecture design
- Comparison (pros/cons) of various .NET dependency injection frameworks
- Identifying the CPU architecture type using C#
- Google mock dependency injection in fixture gives 'invalid new-expression of abstract class type' error
- Multi-platform social networking application development architecture
- Hexagonal Architecture on a front end React app
- Why do Examples of the Repository Pattern never deal with Database Connection Exceptions?
- Error: Could not find EOCD, after adding "splits" in Android
- Which architectural style and pattern(s) would be suitable for this system?
- Xcode 12 Apple M1 arm64 - Designable error: "wrong architecture"
- Backend solution for fetching and transforming data from various third-party APIs
- Why do stacks typically grow downwards?
- Cross module communication in modular monolith
- Transfer data between web sites
- What is a good API architecture to handle long running tasks?
- How to extend a class stored in the database without big consequences for the whole system?
- Instructions for RISC-V(.word)