Models
|
This is the list of TOGAF artefacts as defined in the TOGAF book. Examples of models are provided for each diagram. Click on the artefact (diagram) you want to see. Togaf-Modeling intents to also provide examples for matrixes and catalogs in future iterations.
|
|||||||||||||
|
|||||||||||||
|
|||||||||||||
|
«StartPrev123NextEnd» |
|||||||||||||
| Page 1 of 3 | |||||||||||||
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.
The processing diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. A deployment unit represents grouping of business function, service, or application components. The processing diagram addresses the following questions:
The purpose of the process/system realization diagram is to clearly depict the sequence of events when multiple applications are involved in the execution of a business process. It enhances the application communication diagram by augmenting it with any sequencing constraints, and hand-off points between batch and real-time processing. It would identify complex sequences that could be simplified, and identify possible rationalization points in the architecture in order to provide more timely...
An organization decomposition diagram describes the links between actors, roles and locations within an organization tree. An organization map should provide a chain of command of owners and decision-makers in the organization. Although it is not the intent of the organization decomposition diagram to link goal to organization, it should be possible to intuitively link the goals to the stakeholders from the organization decomposition diagram.
Starting with the transformation to client-server systems from mainframes and later with the advent of e-Business and J2EE, large enterprises moved predominantly into a highly network-based distributed network computing environment, with firewalls and demilitarized zones. Currently, most applications have a web front-end, and looking at the deployment architecture of these applications, it is very common to find three distinct layers in the network landscape: a web presentation layer, a...
Login
Sign in to use the forum and be informed of the latest news.
Forum activity
-
-
- Re: Business Footprint Diagram
- In Diagrams
- at 12:25 on May 14, 2013 (CEST)
-
-
-
- Business Footprint Diagram
- In Diagrams
- at 18:38 on May 03, 2013 (CEST)
-
-
-
- Re: Solution Concept Diagram
- In Diagrams
- at 13:56 on Mar 26, 2013 (CET)
-
-
-
- Re: EAP Profil
- In Welcome
- at 09:23 on Mar 11, 2013 (CET)
-
-
-
- Re: EAP Profil
- In Welcome
- at 15:52 on Mar 10, 2013 (CET)
-
Latest comments
Business footprint diagrams
@nicesmile It is common practice to layer an SOA b...
Business footprint diagrams
I have another question: what is the difference be...- Business footprint diagrams
I'm trying to build an architecture and as for the... 
Data dissemination diagrams
Typically done with Data Flow Diagrams. TOGAF is f...
Enterprise manageability diagrams
I think that the above diagram intends to show on...