Copyright © 2012-2019 The Open Group
Preface
The Open Group
The Open Group is a global consortium that enables the achievement of business objectives through technology standards. Our diverse membership of more than 700 organizations includes customers, systems and solutions suppliers, tools vendors, integrators, academics, and consultants across multiple industries.
The mission of The Open Group is to drive the creation of Boundaryless Information Flow™ achieved by:
·Working with customers to capture, understand, and address current and emerging requirements, establish policies, and share best practices
·Working with suppliers, consortia, and standards bodies to develop consensus and facilitate interoperability, to evolve and integrate specifications and open source technologies
·Offering a comprehensive set of services to enhance the operational efficiency of consortia
UML Class Diagram Notation. When it comes to system construction, a class diagram is the most widely used diagram. UML Class Diagrams is a type of static structure diagram that is used for general conceptual modeling of the systematics of the application. UML Class Diagram Cheat Sheet (Class Diagram Element Overview) Class A class is an extensible template for creating objects, it is a common form for all instances of the same type (e.g. Concept, thing, person).
·Developing and operating the industry’s premier certification service and encouraging procurement of certified products
Further information on The Open Group is available at www.opengroup.org.
I found this UML cheat sheet on the internet for class diagrams a few months ago. It's pretty handy. I ended up printing it out and putting it up in my workspace. Reading select chapters from Uncle Bob's 'Clean Architecture' is one of first items on the training. If you're in need of a refresher on your UML, this cheatsheet should come in handy. The Unified Modeling Language (UML) can help you model systems in various ways. One of the more popular types in UML is the class diagram. Popular among software engineers to document software architecture, class diagrams are a type of structure diagram because they describe what must be present in the system being modeled.
The Open Group publishes a wide range of technical documentation, most of which is focused on development of Open Group Standards and Guides, but which also includes white papers, technical studies, certification and testing documentation, and business titles. Full details and a catalog are available at www.opengroup.org/library.
This Document
This document is the ArchiMate® 3.1 Specification, a standard of The Open Group. It has been developed and approved by The Open Group.
This edition of the standard includes a number of corrections, clarifications, and improvements to the previous edition, as well as several additions.
Intended Audience
The intended audience of this standard is threefold:
•All those working to shape and implement complex organization change
Typical job titles include Enterprise Architecture practitioners, Business Architects, IT architects, application architects, data architects, information architects, process architects, infrastructure architects, software architects, systems architects, solutions architects, product/service managers, senior and operational management, project leaders, and anyone working within the reference framework defined by an Enterprise Architecture.
•Those who intend to implement the ArchiMate language in a software tool
They will find a complete and detailed description of the language in this document.
•The academic community, on which we rely for amending and improving the language based on state-of-the-art research in the architecture field
Structure
The structure of this standard is as follows:
•Chapter 1, Introduction, provides the introduction to this standard, including the objectives, a brief overview, conformance requirements, and terminology
•Chapter 2, Definitions, defines the general terms used in this standard
•Chapter 3, Language Structure, describes the structure of the ArchiMate modeling language, including the top-level structure, layering, the ArchiMate Core Framework, and the ArchiMate Full Framework
•Chapter 4, Generic Metamodel, describes the structure and elements of the ArchiMate generic metamodel
•Chapter 5, Relationships, describes the relationships in the language
•Chapter 6, Motivation Elements, describes the concepts for expressing the motivation for an architecture, together with examples
•Chapter 7, Strategy Elements, provides elements for modeling the enterprise at a strategic level, together with examples
•Chapter 8, Business Layer, covers the definition and usage of the Business Layer elements, together with examples
•Chapter 9, Application Layer, covers the definition and usage of the Application Layer elements, together with examples
•Chapter 10, Technology Layer, covers the definition and usage of the Technology Layer elements, together with examples
•Chapter 11, Physical Elements, describes the language elements for modeling the physical world, together with examples
•Chapter 12, Relationships Between Core Layers, covers the relationships between different layers of the language
•Chapter 13, Implementation and Migration Elements, describes the language elements for expressing the implementation and migration aspects of an architecture (e.g., projects, programs, plateaus, and gaps)
•Chapter 14, Stakeholders, Architecture Views, and Viewpoints, describes the ArchiMate viewpoint mechanism
•Chapter 15, Language Customization Mechanisms, describes how to customize the ArchiMate language for specialized or domain-specific purposes
•Appendix A, Summary of Language Notation, is an informative appendix
•Appendix B, Relationships, is a normative appendix detailing the required relationships between elements of the language and the rules to derive these
•Appendix C, Example Viewpoints, presents a set of architecture viewpoints, developed in ArchiMate notation based on practical experience
All viewpoints are described in detail. The appendix specifies the elements, relationships, usage guidelines, goals, and target groups for each viewpoint.
•Appendix D, Relationship to Other Standards, Specifications, and Guidance Documents, describes the relationships of the ArchiMate language to other standards and specifications, including the TOGAF® framework, the BIZBOK® Guide, BPMN™, UML®, and BMM™
•Appendix E, Changes from Version 2.1 to Version 3.1, is an informative appendix outlining the changes in the standard between Version 2.1 and Version 3.1
Trademarks
ArchiMate®, DirecNet®, Making Standards Work®, Open O® logo, Open O and Check® Certification logo, OpenPegasus®, Platform 3.0®, The Open Group®, TOGAF®, UNIX®, UNIXWARE®, and the Open Brand X® logo are registered trademarks and Agile Architecture Framework™, Boundaryless Information Flow™, Build with Integrity Buy with Confidence™, Dependability Through Assuredness™, Digital Practitioner Body of Knowledge™, DPBoK™, EMMM™, FACE™, the FACE™ logo, IT4IT™, the IT4IT™ logo, O-AAF™, O-DEF™, O-HERA™, O-PAS™, Open FAIR™, Open Platform 3.0™, Open Process Automation™, Open Subsurface Data Universe™, Open Trusted Technology Provider™, O-SDU™, Sensor Integration Simplified™, SOSA™, and the SOSA™ logo are trademarks of The Open Group.
A Guide to the Business Architecture Body of Knowledge® and BIZBOK® are registered trademarks of the Business Architecture Guild.
Java® is a registered trademark of Oracle and/or its affiliates.
UML® and Unified Modeling Language® are registered trademarks and BMM™, BPMN™, Business Motivation Model™, and Business Process Modeling Notation™ are trademarks of the Object Management Group.
All other brands, company, and product names are used for identification purposes only and may be trademarks that are the sole property of their respective owners.
Acknowledgements
The Open Group gratefully acknowledges The Open Group ArchiMate Forum for developing this standard.
The Open Group gratefully acknowledges the contribution of the following people in the development of this and earlier versions of this standard:
•Iver Band, EA Principals & Cambia Health Solutions
•Thorbjørn Ellefsen, Capgemini
•William Estrem, Metaplexity Associates
•Maria-Eugenia Iacob, University of Twente
•Henk Jonkers, BiZZdesign
•Marc M. Lankhorst, BiZZdesign
•Dag Nilsen, Biner
•Carlo Poli, Macaw
•Erik (H.A.) Proper, Luxembourg Institute for Science and Technology & Radboud University Nijmegen
•Dick A.C. Quartel, BiZZdesign
•G. Edward Roberts, Elparazim
•Jean-Baptiste Sarrodie, Accenture
•Serge Thorn, Metaplexity Fellow
The Open Group and ArchiMate project team would like to thank in particular the following individuals for their support and review of this and earlier versions of this standard:
•Adina Aldea
•Mary Beijleveld
•Alexander Bielowski
•Remco de Boer
•Adrian Campbell
•John Coleshaw
•Jörgen Dahlberg
•Garry Doherty
•Ingvar Elmér
•Wilco Engelsman
•Roland Ettema
•Henry M. Franken
•Mats Gejnevall
•Sonia González
•Kirk Hansen
•Jos van Hillegersberg
•Andrew Josey
•Ryan Kennedy
•Louw Labuschagne
•Antoine Lonjon
•Veer Muchandi
•Michelle Nieuwoudt
•Erwin Oord
•Antonio Plais, Centus
•Daniel Simon
•Gerben Wierda
•Egon Willemsz
The first version of this standard was largely produced by the ArchiMate project. The Open Group gratefully acknowledges the contribution of the many people – former members of the project team – who have contributed to it.
The ArchiMate project comprised the following organizations:
•ABN AMRO
•Centrum voor Wiskunde en Informatica
•Dutch Tax and Customs Administration
•Leiden Institute of Advanced Computer Science
•Novay
•Ordina
•Radboud Universiteit Nijmegen
•Stichting Pensioenfonds ABP
Referenced Documents
The following documents are referenced in this standard. These references are informative.
(Please note that the links below are good at the time of writing but cannot be guaranteed for the future.)
[1] Enterprise Architecture at Work: Modeling, Communication, and Analysis, Third Edition, M.M. Lankhorst et al., Springer, 2013.
[2] The Anatomy of the ArchiMate® Language, M.M. Lankhorst, H.A. Proper, H. Jonkers, International Journal of Information Systems Modeling and Design (IJISMD), 1(1):1-32, January-March 2010.
[3] Extending Enterprise Architecture Modeling with Business Goals and Requirements, W. Engelsman, D.A.C. Quartel, H. Jonkers, M.J. van Sinderen, Enterprise Information Systems, 5(1):9-36, 2011.
[4] TOGAF® Version 9.2, The Open Group Standard (C182), April 2018, published by The Open Group; refer to: www.opengroup.org/library/c182.
[5] Extending and Formalizing the Framework for Information Systems Architecture, J.F. Sowa, J.A. Zachman, IBM Systems Journal, Volume 31, No. 3, pp.590-616, 1992.
[6] TOGAF® Framework and ArchiMate® Modeling Language Harmonization: A Practitioner’s Guide to Using the TOGAF® Framework and the ArchiMate® Language, White Paper (W14C), December 2014, published by The Open Group; refer to: www.opengroup.org/library/w14c.
[7] Unified Modeling Language®: Superstructure, Version 2.0 (formal/05-07-04), Object Management Group, August 2005.
[8] Unified Modeling Language®: Infrastructure, Version 2.4.1 (formal/201-08-05), Object Management Group, August 2011.
[9] A Business Process Design Language, H. Eertink, W. Janssen, P. Oude Luttighuis, W. Teeuw, C. Vissers, in Proceedings of the First World Congress on Formal Methods, Toulouse, France, September 1999.
[10] Enterprise Business Architecture: The Formal Link Between Strategy and Results, R. Whittle, C.B. Myrick, CRC Press, 2004.
[11] Composition of Relations in Enterprise Architecture, R. van Buuren, H. Jonkers, M.E. Iacob, P. Strating, in Proceedings of the Second International Conference on Graph Transformation, pp.39-53, edited by H. Ehrig et al., Rome, Italy, 2004.
[12] Business Process Modeling Notation™ (BPMN™), Version 2.0 (formal/2011-01-03), Object Management Group, 2011.
[13] Performance and Cost Analysis of Service-Oriented Enterprise Architectures, H. Jonkers, M.E. Iacob, in Global Implications of Modern Enterprise Information Systems: Technologies and Applications, edited by A. Gunasekaran, IGI Global, 2009.
[14] ISO/IEC 42010:2011, Systems and Software Engineering – Recommended Practice for Architectural Description of Software-Intensive Systems, Edition 1.
[15] Business Motivation Model™ (BMM™), Version 1.1 (formal/2010-05-01), Object Management Group, 2010.
[16] Using the ArchiMate® Language with UML®, White Paper (W134), September 2013, published by The Open Group; refer to: www.opengroup.org/library/w134.
[17] TOGAF® Series Guide: Value Streams (G178), October 2017, published by The Open Group: refer to: www.opengroup.org/library/g178.
[18] Business Architecture Guild. A Guide to the Business Architecture Body of Knowledge® (BIZBOK® Guide), Version 7.0, 2018; refer to: www.businessarchitectureguild.org.
[19] TOGAF® Series Guide: The TOGAF® Technical Reference Model (TRM) (G175), September 2017, published by The Open Group: refer to: www.opengroup.org/library/g175.
[20] ArchiMate® Model Exchange File Format for the ArchiMate Modeling Language, Version 3.0, The Open Group Standard (C174), May 2017, published by The Open Group; refer to: www.opengroup.org/library/c174.
Uml Notation Cheat Sheet
return to top of page
Downloads
Downloads of the ArchiMate documentation are available under license from the Download link within the ArchiMate information web site. The license is free to anyorganization wishing to use ArchiMate documentation entirely for internal purposes.A book is also available from The Open Group Library as document C197.
ArchiMate is a registered trademark of The Open Group.
Uml Notation Cheat Sheet Free
| < Previous | ▲ Home | Next > |
A UML diagram is a partial graphical representation (view) of a model of a system under design, implementation, or already in existence. UML diagram contains graphical elements (symbols) - UML nodes connected with edges (also known as paths or flows) - that represent elements in the UML model of the designed system. The UML model of the system might also contain other documentation such as use cases written as templated texts.
The kind of the diagram is defined by the primary graphical symbols shown on the diagram. For example, a diagram where the primary symbols in the contents area are classes is class diagram. A diagram which shows use cases and actors is use case diagram. A sequence diagram shows sequence of message exchanges between lifelines.
UML specification does not preclude mixing of different kinds of diagrams, e.g. to combine structural and behavioral elements to show a state machine nested inside a use case. Consequently, the boundaries between the various kinds of diagrams are not strictly enforced. At the same time, some UML Tools do restrict set of available graphical elements which could be used when working on specific type of diagram.
Classification of UML 2.5 Diagrams
Uml Notation Cheat Sheet
UML specification defines two major kinds of UML diagram: structure diagrams and behavior diagrams.
Structure diagrams show the static structure of the system and its parts on different abstraction and implementation levels and how they are related to each other. The elements in a structure diagram represent the meaningful concepts of a system, and may include abstract, real world and implementation concepts.
Behavior diagrams show the dynamic behavior of the objects in a system, which can be described as a series of changes to the system over time.
UML 2.5 diagrams could be categorized hierarchically as shown below. Note, items shown in blue are not part of official UML 2.5 taxonomy of diagrams.
UML 2.5 Diagrams Overview.
Note, items in blue are not part of official taxonomy of UML 2.5 diagrams.
UML 2.5 Structure Diagrams
Structure diagrams show static structure of the system and its parts on different abstraction and implementation levels and how those parts are related to each other. The elements in a structure diagram represent the meaningful concepts of a system, and may include abstract, real world and implementation concepts.
Structure diagrams are not utilizing time related concepts, do not show the details of dynamic behavior. However, they may show relationships to the behaviors of the classifiers exhibited in the structure diagrams.
| Diagram | Purpose | Elements |
|---|---|---|
| Class diagram | Shows structure of the designed system, subsystem or component as related classes and interfaces, with their features, constraints and relationships - associations, generalizations, dependencies, etc. | class, interface, feature, constraint, association, generalization, dependency. |
| Object diagram | Instance level class diagram which shows instance specifications of classes and interfaces (objects), slots with value specifications, and links (instances of association). Object diagram was defined in now obsolete UML 1.4.2 Specification as 'a graph of instances, including objects and data values. A static object diagram is an instance of a class diagram; it shows a snapshot of the detailed state of a system at a point in time.' It also stated that object diagram is 'a class diagram with objects and no classes.' UML 2.5 specification simply provides no definition of object diagram. | instance specification, object, slot, link. |
| Package diagram | Shows packages and relationships between the packages. | package, packageable element, dependency, element import, package import, package merge. |
| Model diagram | UML auxiliary structure diagram which shows some abstraction or specific view of a system, to describe architectural, logical or behavioral aspects of the system. It could show, for example, architecture of a multi-layered (aka multi-tiered) application - see multi-layered application model. | model, package, packageable element, dependency. |
| Composite structure diagram | Diagram could be used to show: | |
| Internal structure diagram | Shows internal structure of a classifier - a decomposition of the classifier into its properties, parts and relationships. | structured class, part, port, connector, usage. |
| Collaboration use diagram | Shows objects in a system cooperating with each other to produce some behavior of the system. | collaboration, connector, part, dependency. |
| Component diagram | Shows components and dependencies between them. This type of diagrams is used for Component-Based Development (CBD), to describe systems with Service-Oriented Architecture (SOA). | component, interface, provided interface, required interface, class, port, connector, artifact, component realization, usage. |
| Manifestation diagram | While component diagrams show components and relationships between components and classifiers, and deployment diagrams - deployments of artifacts to deployment targets, some missing intermediate diagram is manifestation diagram to be used to show manifestation (implementation) of components by artifacts and internal structure of artifacts. Because manifestation diagrams are not defined by UML 2.5 specification, manifestation of components by artifacts could be shown using either component diagrams or deployment diagrams. | manifestation, component, artifact. |
| Deployment diagram | Shows architecture of the system as deployment (distribution) of software artifacts to deployment targets. Note, that components were directly deployed to nodes in UML 1.x deployment diagrams. In UML 2.x artifacts are deployed to nodes, and artifacts could manifest (implement) components. Components are deployed to nodes indirectly through artifacts. Specification level deployment diagram (also called type level) shows some overview of deployment of artifacts to deployment targets, without referencing specific instances of artifacts or nodes. Instance level deployment diagram shows deployment of instances of artifacts to specific instances of deployment targets. It could be used for example to show differences in deployments to development, staging or production environments with the names/ids of specific build or deployment servers or devices. | deployment, artifact, deployment target, node, device, execution environment, communication path, deployment specification, |
| Network architecture diagram | Deployment diagrams could be used to show logical or physical network architecture of the system. This kind of deployment diagrams - not formally defined in UML 2.5 - could be called network architecture diagrams. | node, switch, router, load balancer, firewall, communication path, network segment, backbone. |
| Profile diagram | Auxiliary UML diagram which allows to define custom stereotypes, tagged values, and constraints as a lightweight extension mechanism to the UML standard. Profiles allow to adapt the UML metamodel for different
| profile, metaclass, stereotype, extension, reference, profile application. |
Uml Syntax Cheatsheet
UML 2.5 Behavior Diagrams
Behavior diagrams show the dynamic behavior of the objects in a system, which can be described as a series of changes to the system over time.
| Diagram | Purpose | Elements |
|---|---|---|
| Use case diagram | Describes a set of actions (use cases) that some system or systems (subject) should or can perform in collaboration with one or more external users of the system (actors) to provide some observable and valuable results to the actors or other stakeholders of the system(s). Note, that UML 2.4.1 specification (see '16.4 Diagrams') stated that Use Case Diagrams are a specialization of Class Diagrams such that the classifiers shown are restricted to being either Actors or Use Cases.Class diagrams are structure diagrams. | use case, actor, subject, extend, include, association. |
| Information flow diagram | Shows exchange of information between system entities at some high levels of abstraction. Information flows may be useful to describe circulation of information through a system by representing aspects of models not yet fully specified or with less details. | information flow, information item, actor, class. |
| Activity diagram | Shows sequence and conditions for coordinating lower-level behaviors, rather than which classifiers own those behaviors. These are commonly called control flow and object flow models. | activity, partition, action, object, control, activity edge. |
| State machine diagram | Used for modeling discrete behavior through finite state transitions. In addition to expressing the behavior of a part of the system, state machines can also be used to express the usage protocol of part of a system. These two kinds of state machines are referred to as behavioral state machines and protocol state machines. | |
| Behavioral state machine diagram | Shows discrete behavior of a part of designed system through finite state transitions. | behavioral state, behavioral transition, pseudostate. |
| Protocol state machine diagram | Shows usage protocol or a lifecycle of some classifier, e.g. which operations of the classifier may be called in each state of the classifier, under which specific conditions, and satisfying some optional postconditions after the classifier transitions to a target state. | protocol state, protocol transition, pseudostate. |
| Interaction diagram | Interaction diagrams include several different types of diagrams:
| |
| Sequence diagram | Most common kind of interaction diagrams which focuses on the message interchange between lifelines (objects). | lifeline, execution specification, message, combined fragment, interaction use, state invariant, destruction occurrence. |
| Communication diagram (a.k.a. Collaboration diagram in UML 1.x) | Focuses on the interaction between lifelines where the architecture of the internal structure and how this corresponds with the message passing is central. The sequencing of messages is given through a sequence numbering scheme. | lifeline, message. |
| Timing diagram | Shows interactions when a primary purpose of the diagram is to reason about time. Timing diagrams focus on conditions changing within and among lifelines along a linear time axis. | lifeline, state or condition timeline, destruction event, duration constraint, time constraint. |
| Interaction overview diagram | Defines interactions through a variant of activity diagrams in a way that promotes overview of the control flow. Interaction overview diagrams focus on the overview of the flow of control where the nodes are interactions or interaction uses. The lifelines and the messages do not appear at this overview level. | initial node, flow final node, activity final node, decision node, merge node, fork node, join node, interaction, interaction use, duration constraint, time constraint. |