Project context diagrams

A project context diagram shows the scope of a work package to be implemented as a part of a broader transformation roadmap. The project context diagram links a work package to the organizations, functions, services, processes, applications, data and technology that will be added, removed or impacted by the project. The project context diagram is also a valuable tool for project portfolio management and project mobilization.

project-context-diagram
In this diagram, the context is centered on the "DiscountTravelOrderingSite"

external-actor-32External actor: An actor that is external to the enterprise.

internal-actor-32Internal actor: An actor that belongs to the enterprise.

requirementRequirements: In this context, these are business requirements.

interaction-application-componentInteraction application component: Represents the top level components that manage the interaction with elements outside the IS. In most cases, it is a GUI component, such as here a web interface.

functionFunction: Describes one function of the organization.

database-application-componentDatabase application component: Represents a repository. In pure SOA architecture, these elements should not appear. However, for legacy analysis or technology architecture, modeling repositories or repository deployment can be useful.

ApplicationApplication: This application component corresponds to legacy applications, off the shelf products, or can be an assembly of application components.

system-federationSystem federation: A system federation is the coarser-grained application component. It assembles systems to federate them, such as in the example of cooperation between different information systems between different companies.

use-caseUse case: Represents an interaction between an actor and the system, in order to fulfill a business need. A use case is further described by a set of scenarios that express the interactions between the system and the actors.

business-service-32Business service: Represents a service provided by the business, which may then be realized by one or more IS services.

togaf-process-32Business process: As presented in process maps (event diagrams). The business process is detailed in flow diagrams.

information-flowInformation flow: dDefines the flow of any kind of information (business entity, event, product, informal, etc) between active entities of the enterprise.

consumes-linkConsumes link: Expresses that participant (e.g. an actor) consumes an element of the IS (service, operation, application component).

realizes-linkRealizes link: Component realization. An application component realizes the designated element, for example a business process.

satisfy-linkSatisfy link: Expresses that an element of the IS satisfies a requirement.

Login

Sign in to use the forum and be informed of the latest news.

Latest comments