Jump to content

User:Mdd/ArchiMate

From Wikipedia, the free encyclopedia
Insurance claim process depicted in ArchiMate. Archimate enables modelling in different layers.

ArchiMate (/ˈ[invalid input: 'ar'].kɪmeɪt/ AR-ki-mayt) is an open and independent enterprise architecture modeling language to support the description, analysis and visualization of architecture within and across business domains[1] in an unambiguous way.

ArchiMate is a technical standard from The Open Group and is based on the concepts of the IEEE 1471 standard. It is supported by various tool vendors and consulting firms. ArchiMate is also a registered trademark of The Open Group. The Open Group has introduced a certification program [2] for ArchiMate 2.0.

ArchiMate distinguishes itself from other languages such as Unified Modeling Language (UML) and Business Process Modeling Notation (BPMN) by its enterprise modelling scope.[3]

Overview[edit]

Just like an architectural drawing in classical building architecture describes the various aspects of the construction and use of a building, ArchiMate offers a common language for describing the construction and operation of business processes, organizational structures, information flows, IT systems, and technical infrastructure. This insight helps the different stakeholders to design, assess, and communicate the consequences of decisions and changes within and between these business domains.

An architecture framework is used to structure the concepts and relationships of the ArchiMate language. It divides the enterprise architecture into a business, application and technology layer. In each layer, three aspects are considered: active elements that exhibit behavior (e.g. Process and Function), an internal structure and elements that define use or communicate information.

One of the objectives of the ArchiMate language is to define the relationships between concepts in different architecture domains. The concepts of this language therefore hold the middle between the detailed concepts, that are used for modeling individual domains, for example, the UML for modeling software products.,[4] and BPMN which is used for business process modeling.

History[edit]

ArchiMate is partly based on the IEEE 1471 standard. It was developed in the Netherlands by a project team from the Telematica Instituut in cooperation with several Dutch partners from government, industry and academia. Among the partners were Ordina, Radboud Universiteit Nijmegen, the Leiden Institute for Advanced Computer Science (LIACS) and the Centrum Wiskunde & Informatica (CWI). Later, tests were performed in organizations such as ABN AMRO, the Dutch Tax and Customs Administration and the ABP.[5]

The development process lasted from July 2002 to December 2004, and took about 35 man years and approximately 4 million euros. The development was funded by the Dutch government (Dutch Tax and Customs Administration), and business partners, including ABN AMRO and the ABP Pension Fund.[6] There were different stages of this development process:

  • At first the state of the art of architecture concepts and description [7], and of the architecture support[8] has been investigated.
  • Next requirements have been developed for the modeling language that enables coherent enterprise architecture descriptions [9], and concepts for architectural modelling have been formulated.[10]
  • Resulting in the construction and validation of the ArchiMate Language and final presentation in the "ArchiMate Language Primer."[11]

In 2008 the ownership and stewardship of ArchiMate was transferred to the Open Group. It is now managed by the ArchiMate Forum [12] within The Open Group. In February 2009 The Open Group published the ArchiMate® 1.0 standard[13] as a formal technical standard. In January 2012 the ArchiMate® 2.0 standard [14] was released.

ArchiMate topics[edit]

ArchiMate is an integrated architectural approach that describes and visualises the different business domains and their relations. Using these integrated architectures aids stakeholders in assessing the impact of design choices and changes.

Architecture[edit]

Organisations need to adapt increasingly fast and anticipate changing customer requirements and business goals. This need influences the entire chain of activities of a business, from the organisational structure to the network infrastructure. How can you control the impact of these changes? Architecture may be the answer.

Architecture is a consistent whole of principles, methods and models that are used in the design and realisation of organisational structure, business processes, information systems, and infrastructure. However, these domains are not approached in an integrated way, which makes it difficult to judge the effects of proposed changes. Every domain speaks its own language, draws its own models, and uses its own techniques and tools. Communication and decision making across domains is seriously impaired.

ArchiMate provides this integration. ArchiMate is an architecture language and visualisation techniques that picture these domains and their relations. ArchiMate will provide the architect with instruments that support and improve the architecture process.

Layers[edit]

View model of ArchiMate Architectural Framework.

ArchiMate has layered and service-oriented look on architectural models. The higher layers make use of services that are provided by the lower layers. Although, at an abstract level, the concepts that are used within each layer are similar, we define more concrete concepts that are specific for a certain layer. In this context, we distinguish three main layers:[1][6]

  • The Business layer about business processes, services, functions and events of business units. This layer "offers products and services to external customers, which are realized in the organization by business processes performed by business actors and roles".
  • The Application layer about software applications that "support the components in the business with application services".
  • The Technology layer deals "with the hardware and communication infrastructure to support the Application Layer. This layer offers infrastructural services needed to run applications, realized by computer and communication hardware and system software".

Each of these main layers can be further divided in sub-layers. For example, in the Business layer, the primary business processes realising the products of a company may make use of a layer of secondary (supporting) business processes; in the Application layer, the end-user applications may make use of generic services offered by supporting applications. On top of the Business layer, a separate Environment layer may be added, modelling the external customers that make use of the services of the organisation (although these may also be considered part of the Business layer).

In line with service orientation, the most important relation between layers is formed by use relations, which show how the higher layers make use of the services of lower layers. However, a second type of link is formed by realisation relations: elements in lower layers may realise comparable elements in higher layers; e.g., a ‘data object’ (Application layer) may realise a ‘business object’ (Business layer); or an ‘artifact’ (Technology layer) may realise either a ‘data object’ or an ‘application component’ (Application layer).

General structure of models within the different layers[edit]

Core concepts of the ArchiMate language (Lankhorst, 2013).

The general structure of models within the different layers is similar. The same types of concepts and relations are used, although their exact nature and granularity differ.

First, we distinguish the structural or static aspect and the behavioural or dynamic aspect. Behavioural concepts are assigned to structural concepts, to show who or what displays the behaviour. In the example, role, interface and collaboration are assigned to business process, organisational service and business interaction, respectively.

Second, we make a distinction between an external view and an internal view on systems. When looking at the behavioural aspect, these views reflect the principles of service orientation as introduced in the previous section. The service concept represents a unit of essential functionality that a system exposes to its environment. For the external users, only this external functionality, together with non-functional aspects such as the quality of service, costs etc., are relevant. If required, these can be specified in a contract or service level agreement. Services are accessible through interfaces, which constitute the external view on the structural aspect.

Although for the external users only the external view is relevant, the design of organisations or systems and their internal operations and management also requires knowledge about the internal realisation of the services and interfaces. For this realisation, we make a distinction between behaviour that is performed by an individual structural element (e.g., actor, role component, etc.), or collective behaviour (interaction) that is performed by a collaboration of multiple structural elements.

In addition to active structural elements (the business actors, application components and devices that display actual behaviour, i.e., the ‘subjects’ of activity), we also recognise passive structural elements, i.e., the objects on which behaviour is performed. In the domain of information-intensive organisations, which is the main focus of our language, these are usually information objects in the business layer and data objects in the application layer, but they may also be used to represent physical objects.

References[edit]

  1. ^ a b What is ArchiMate? at archimate.org. Accessed 18 jan 2009
  2. ^ ArchiMate 2.0 Certification
  3. ^ Pallab Saha (2008) Advances in Government Enterprise Architecture. p.39.
  4. ^ Zoran Stojanović et al. (2007). Service-oriented Software System Engineering. p.145-146.
  5. ^ Telematica Instituut (2006) Annual Report 2005. p.7. Accessed 18 jan 2009.
  6. ^ a b ArchiMate : Its Time Has Come? Enterprise Architecture Demystified. Posted by snair007 on August 3, 2008
  7. ^ Henk Jonkers et al. State of the Art in Architecture Concepts and Description. Enschede: Telematica Instituut, 2002
  8. ^ Iacob, M., Huijsen, W., Leeuwen, D. V., Doest, H. T., Bosma, H., Vos, M., & Scholten, J. G. (2002). State of the Art in Architecture Support.
  9. ^ Jonkers, Henk, et al. "Towards a language for coherent enterprise architecture descriptions." Enterprise Distributed Object Computing Conference, 2003. Proceedings. Seventh IEEE International. IEEE, 2003.
  10. ^ Jonkers, H., Lankhorst, M., Van Buuren, R., Hoppenbrouwers, S., Bonsangue, M., & Van Der Torre, L. (2004). Concepts for modeling enterprise architectures. International Journal of Cooperative Information Systems, 13(03), 257-287.
  11. ^ Lankhorst, Marc. "ArchiMate Language Primer–Introduction to the ArchiMate Modelling Language for Enterprise Architecture. Version 1.0." ArchiMate Language Primer (2004): 27.
  12. ^ The ArchiMate Forum
  13. ^ ArchiMate 1.0 Specification
  14. ^ ArchiMate 2.0 Specification

Further reading[edit]

  • The Open Group (2009), ArchiMate 1.0 Specification. ISBN 978-90-8753-502-5.
  • The Open Group (2009), ArchiMate 1.0 Specification - online.
  • The Open Group (2012), ArchiMate 2.1 Specification - online.
  • Marc Lankhorst et al. (2005). Enterprise Architecture at Work - Modelling, Communication and Analysis. Berlin: Springer-Verlag.
  • Marc Lankhorst and Hans van Drunen (2007). Enterprise Architecture: Development and Modelling Combining TOGAF and ArchiMate
  • Marc Lankhorst (ed.) and the ArchiMate team (2004) ArchiMate Language Primer. Enschede: Novay.

External links[edit]

Wikimedia Commons has media related to Mdd/ArchiMate.
Retrieved from "https://en.wikipedia.org/w/index.php?title=User:Mdd/ArchiMate&oldid=791852447"