Fundamentals 5 min read

Project Context Diagram and UML/BPMN EAP Profile Overview with Archimate Example

The article explains how a project context diagram maps work packages to organizational elements and describes UML/BPMN EAP profile elements and an Archimate model centered on a DiscountTravelOrderingSite, while also providing contact information for further discussion.

Architects Research Society
Architects Research Society
Architects Research Society
Project Context Diagram and UML/BPMN EAP Profile Overview with Archimate Example

The project context diagram illustrates the scope of work packages as part of a broader transformation roadmap, linking work packages with organizations, functions, services, processes, applications, data, and technology that will be added, removed, or affected.

UML/BPMN EAP Profile

External participant: participants outside the enterprise.

Internal participant: participants belonging to the enterprise.

Requirement: business requirements in this context.

Interaction application component: top‑level component that manages interaction with external IS elements, usually a GUI such as a web interface.

Database application component: a repository; in pure SOA it would not appear, but useful for legacy analysis or technical architecture.

Application: may correspond to a legacy application, off‑the‑shelf product, or an assembly of application components.

System federation: coarse‑grained application component that assembles systems for joint operation, e.g., cross‑company collaboration.

Use case: represents interaction between participants and the system to satisfy a business requirement, further described by scenarios.

Business service: a service offered by the business, which can be realized by one or more IS services.

Business process: detailed in flowcharts (event diagrams) and described in the process diagram.

Information flow: defines any type of information flow between enterprise activity entities (business entities, events, products, informal information, etc.).

Consume link: indicates a participant consumes an IS element (service, operation, application component).

Implementation link: component implementation; an application component implements a specified element such as a business process.

Satisfy link: indicates an IS element satisfies a requirement.

Archimate

The central element of this diagram is “DiscountTravelOrderingSite”.

For further discussion, the author provides links to a website, WeChat, QQ group, and other social media channels.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

BPMNUMLenterprise architectureproject context diagram
Architects Research Society
Written by

Architects Research Society

A daily treasure trove for architects, expanding your view and depth. We share enterprise, business, application, data, technology, and security architecture, discuss frameworks, planning, governance, standards, and implementation, and explore emerging styles such as microservices, event‑driven, micro‑frontend, big data, data warehousing, IoT, and AI architecture.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.