System Use Case Diagrams and Their Role in Enterprise Architecture Modeling

System use case diagrams illustrate the relationships between participants (users) and providers of application services, showing how and when services are used, thereby providing richer content for describing application functionality.

The purpose of system use case diagrams is to help describe and validate interactions between participants, their roles, and the application; as architecture evolves, use cases can evolve from purely functional information to include technical implementation details and can be reused in more detailed system design work.

System use case diagrams use UML use cases, with TOGAF roles and participants substituting UML actors, and a "component implementation" link that indicates which application components implement which use cases.

UML/BPMN EAP Profile

External participant: participants outside the enterprise.

Internal participant: participants belonging to the enterprise.

Use case

Communication link: represents communication between participants and the use cases they are involved in.

Component implementation link: the relationship between application components and the business elements they implement.

Archimate

Use cases are enriched by the representation of the application components that implement them.

The article includes a reference link to the original source and invites readers to join various communities (WeChat groups, QQ groups, video channels, etc.) for deeper discussion on enterprise architecture, cloud computing, big data, AI, and related technologies.