HPE Enterprise Maps Data Model, ArchiMate, TOGAF HPE Software, Cloud and Automation
Data Model Enterprise Maps
ArchiMate Overview Modeling language for EA 2002-2004 - NL university + government + industry project Since 2008 managed by The OpenGroup, version 1.0 in 2009 Latest version is 2.1 (2012), 3.0 in progress Focused on the way of how to create EA diagrams Defines set of relationships (7+3+2=12 +0+1=13) and elements (16+7+9 = 32 +7+4 = 41) Clear semantical background classification of elements, definition of elements direct relationships between elements derived relationships Layers CORE: Business, Application, Technology OPTIONAL: Motivation, Implementation and Migration Viewpoints Huge set of viewpoint point types for several stakeholders of EA 16 7 9 4 7
EM Data Model Relationships
ArchiMate Relationships Overview Structural Composition: B is composed of one more A, A can be in at most 1 B Aggregation: B aggregates one more A, A can in more Bs Assignment: Links active elements with units of behavior that are performed by them (business role B performs business function A) Realization: links a logical entity with a more concrete entity that realizes it (business process A realizes business service B) Used By: models the use of services and access to interfaces (service A is used by function B); beware: A uses B = A B Access: access behavioral elements to data/business objects (business service creates contract, application service writes data) Association: any other Dynamic Triggering: causal/temporal relationship (business event triggers process) Flow: non-causal/temporal exchange of information between Other: Specialization, Influence, Grouping Some elements might be represented as relationships (Network, Communication Path) and some elements are relationships in ArchiMate (Grouping, Junction)
ArchiMate Business Layer offering relative worth form of object rights and obligations exposed behavior point of access something happens Relevant to business process - workflow function any criteria 1:1 responsibility organizational entity where? http://pubs.opengroup.org/architecture/archimate2-doc/chap03.html#_toc371945176
ArchiMate Application Layer exposed behavior point of access passive data used in automated processing automated behavior 1:1 deployable software http://pubs.opengroup.org/architecture/archimate2-doc/chap04.html#_toc371945189
ArchiMate Technology Layer exposed behavior point of access physical data behaviour computational resource data exchange software environment hardware communication medium http://pubs.opengroup.org/architecture/archimate2-doc/chap05.html#_toc371945204
ArchiMate Cross Layer Dependencies, Derived Relationships Business Services use Infrastructure services, Nodes Application Components realize Business Services Business Actors creates Business Contracts Application Interfaces are used by Business Services Business Services use Infrastructure Services Files realize Contracts
ArchiMate Motivation Extension/Layer Stakeholder is the role of an individual, team, or organization (or classes thereof) that represents their interests in, or concerns relative to, the outcome of the architecture. Board, CEO, Customer Driver is something that creates, motivates, and fuels the change in an organization. Profit, Sales, Cost, Shareholder/Customer Satisfaction Assessment is the outcome of some analysis of some driver. High Service Time, Complaining Customers Goal is an end state that a stakeholder intends to achieve. Reduce workload/maintenance cost, Facilitate self-service Principle is a normative property of all systems in a given context, or the way in which they are realized. Systems should be customer facing, Store data only once Requirement is a statement of need that must be realized by a system. Assign personal assistant, provide online portfolio service Constraint is a restriction on the way in which a system is realized. Application should be in Java, Budget 500k$ http://pubs.opengroup.org/architecture/archimate2-doc/chap10.html
ArchiMate Implementation and Migration Extension/Layer Plateau is a relatively stable state of the architecture that exists during a limited period of time. Base line (AS-IS), transition and target state (TO-BE) Gap is an outcome of a gap analysis between two plateaus. Difference between 2 plateaus with described relationship to elements, descriptions indicate the change Deliverable is a precisely-defined outcome of a work package. Integrated Back-office System, Financial Application, Analysis of ABC, Upgrade to XYZ, Hardware for XYZ Work package is a series of actions designed to accomplish a unique goal within a specified time. Project: Back-office system integration, Program: Application portfolio rationalization http://pubs.opengroup.org/architecture/archimate2-doc/chap11.html
ArchiMate Key facts An Open Group Standard; Open and independent modelling language for enterprise architecture Provides a uniform representation for diagrams that describe enterprise architectures 3 main core types of elements - active structure, behavior, passive structure (objects) service-orientation paradigm incorporated EM is compliant with the ArchiMate 2.0 and 2.1, it is certified ArchiMate element types are artifact types in EM EM helps you learn ArchiMate on the fly element types and relationships are explained Links http://www.opengroup.org/subjectareas/enterprise/archimate http://masteringarchimate.com/mastering-archimate-edition-ii/
EM Data Model Key Facts Data model of EM repository is called System Data Model = SDM The types in the data model are called artifact types inheritance is supported, the core type is named artifactbase The instances of the artifact types are called artifacts Artifacts have named properties of various kinds (string, number, category ) even with multiple cardinalities properties can be grouped to property groups, so they are easier to define on artifacts every artifact has system properties, such as name and description Relationship to another artifact is an also artifact property, relationships have primitive attributes All artifacts have revisions, artifact history is kept upon every change Category property is defined by a taxonomy that usually specifies hierarchical organization of possible values
TOGAF Key Facts An Open Group Standard; enterprise architecture methodology and framework https://www.opengroup.org/togaf/ HP EM is designed according to principles and recommendations defined in TOGAF ArchiMate correspondence with TOGAF Includes Architecture Development Method
HPE Enterprise Maps hp.com/go/em Copyright 2015 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.