| Typ | Begrepp |
|---|
| Business Actor | Aktör C-073 |
| Business Role | Roll C-074, Informationsägare C-167, Processägare C-206 (osäker) |
| Business Collaboration | Verksamhetssamverkan C-141 |
| Business Interface | Verksamhetsgränssnitt C-138 |
| Business Process | Verksamhetsprocess C-130, Handläggning C-160, Verksamhetsaktivitet C-175 (osäker) |
| Business Function | Verksamhetsfunktion C-158 |
| Business Interaction | Mappas inte: interaktion (C-083) is a plain concept with no types: the behaviour a collaboration performs together is described as a process, or for an application or a technical resource as a function |
| Business Event | Verksamhetshändelse C-135 |
| Business Service | Verksamhetstjänst C-127 |
| Business Object | Verksamhetsobjekt C-159 |
| Contract | Överenskommelse C-084 |
| Representation | Representation C-085 |
| Product | Produkt C-014 |
| Application Component | Applikation C-071 |
| Application Collaboration | Applikationssamverkan C-142 |
| Application Interface | Applikationsgränssnitt C-139 |
| Application Function | Applikationsfunktion C-133 |
| Application Interaction | Mappas inte: interaktion (C-083) is a plain concept with no types: the behaviour a collaboration performs together is described as a process, or for an application or a technical resource as a function |
| Application Process | Applikationsprocess C-131, Applikationsaktivitet C-176 (osäker) |
| Application Event | Applikationshändelse C-136 |
| Application Service | Applikationstjänst C-128 |
| Data Object | Informationsobjekt C-060 |
| Node | Nod C-079, Plattform C-072 (osäker) |
| Device | Enhet C-080 |
| System Software | Systemprogramvara C-087 |
| Technology Collaboration | Tekniksamverkan C-143 |
| Technology Interface | Teknikgränssnitt C-140 |
| Path | Sökväg C-089 |
| Communication Network | Kommunikationsnätverk C-088 |
| Technology Function | Teknikfunktion C-134 |
| Technology Process | Teknikprocess C-132, Teknikaktivitet C-177 (osäker) |
| Technology Interaction | Mappas inte: interaktion (C-083) is a plain concept with no types: the behaviour a collaboration performs together is described as a process, or for an application or a technical resource as a function |
| Technology Event | Teknikhändelse C-137 |
| Technology Service | Tekniktjänst C-129 |
| Artifact | Artefakt C-081 |
| Equipment | Utrustning C-090 |
| Facility | Anläggning C-091 |
| Distribution Network | Distributionsnätverk C-092 |
| Material | Material C-093 |
| Principle | Princip C-018, Arkitekturprincip C-040 (osäker) |
| Goal | Mål C-017 |
| Outcome | Mål C-017 (osäker) |
| Requirement | Krav C-021 (osäker) |
| Driver | Påverkan C-184 |
| Assessment | Bedömning C-185 |
| Begrepp | Skäl |
|---|
| Tillstånd C-182 | tillstånd (ADR 0024) is the state a verksamhetsobjekt is in, drawn in a state view; ArchiMate has no state element, the state goes into a Business Object's name or a Business Event |
| Beslutslogik C-178 | beslutslogik (ADR 0022) is DMN's Decision, the reusable rule by which an outcome is determined from inputs; ArchiMate has no element for decision logic, and the logic is drawn in DMN, not exported |
| Lagringsyta C-165 | a lagringsyta is the place an application keeps representations; ArchiMate has no element for a storage place, Artifact and Node sit in the technology layer |
| Verksamhet C-007 | the store's own architecture-object type for the enterprise as a whole (ISO 42010 scoping); ArchiMate's core has no element for architecture-object scope |
| Verksamhetsdomän C-008 | the store's own architecture-object type for a domain (ISO 42010 scoping); ArchiMate's core has no element for architecture-object scope |
| Utvecklingsdomän C-009 | the store's own architecture-object type for a development domain (ISO 42010 scoping); ArchiMate's core has no element for architecture-object scope |
| Produktionsdomän C-010 | the store's own architecture-object type for a production domain (ISO 42010 scoping); ArchiMate's core has no element for architecture-object scope |
| Lösning C-055 | the store's own architecture-object type for a solution (ISO 42010 scoping); ArchiMate's core has no element for architecture-object scope |
| Verksamhetsförmåga C-069 | capability sits in ArchiMate's Strategy layer, outside the 3.2 core this table covers |
| Initiativ C-012 | an initiativ is ArchiMate's Work Package, which sits in the Implementation and Migration layer, outside the 3.2 core this table covers |
| Portfölj C-011 | a portfölj is a set of initiatives and products prioritised and funded together; ArchiMate has no portfolio element, Grouping comes nearest and is a composite, not a type (ADR 0019) |
| Bärare C-016 | a document or artefact that carries styrmedel or ändamål; ArchiMate's motivation elements have no element for the carrier of a motivation, and as a data carrier it is an Artifact (C-081), which the table already maps |
| Styrbeslut C-019 | the alternative chosen in a single matter; ArchiMate has no decision element in its core or its motivation elements |
| Regel C-020 | a binary statement of what is to be done or not done; ArchiMate's Constraint restricts how a system may be realised and is not the same thing, and ArchiMate has no element that tests an action against a rule |
| Ändamål C-022 | the purpose the business is to serve, given with the uppdrag and outliving the management; it is not a Goal, which is a state the management chose for the styrobjekt to reach or hold (C-017), and not a Driver, which is the påverkan (C-184) the purpose is read out of (ADR 0025) |
| härleds ur C-064 | provenance relation for governance objects (a decision derived from a principle); no ArchiMate core relationship names this |
| beskriver C-065 | a description referencing the object it describes; no ArchiMate core relationship names this |
| förfinar C-103 | refinement between governance objects at different levels of generality (a rule refining a principle); no ArchiMate core relationship maps to it precisely enough without guessing |
| ersätter C-104 | the store's own relation type for one architecture element taking another's place (a replacement in a target or transition); no ArchiMate core relationship names this |
| Gapanalys C-105 | the store's own comparison of two architecture descriptions; a gap analysis is a document, not an ArchiMate core element or relationship |
| Diagram C-106 | a drawing made in a tool that shows parts of architecture views; ArchiMate's core has no element for a drawing of a model |
| Kartläggning C-107 | an investigation that establishes the current architecture; a survey is work done, not an ArchiMate core element or relationship |
| Målgrupp C-145 | ArchiMate's core has no element for a group of people the organisation exists for; the nearest, Stakeholder, sits in the Motivation layer outside the 3.2 core this table covers, and stands for someone with a concern, not a group with a need |
| Behov C-146 | ArchiMate's core has no element for what people are trying to achieve; Driver has no row in this table, because no governance type maps to it, and Goal is mapped to C-017; both name the organisation's own aims, not the people's |
| Resa C-147 | ArchiMate's core has no element for a course of events in people's lives that runs across organisations; a Business Process is what an organisation does, which a journey is not |
| Värdeerbjudande C-148 | ArchiMate's Value sits in the Motivation layer outside the 3.2 core this table covers, and stands for what a stakeholder gains, not for a promise aimed at one target group or actor; mapping it would blur the two |
| har behov C-151 | no ArchiMate core relationship says that a group of people has a need; Association is already held by C-099 and says nothing about direction or meaning |
| riktas till C-152 | no ArchiMate core relationship says that a value proposition is aimed at a target group or actor; Association is already held by C-099 |
| möter C-153 | no ArchiMate core relationship says that a value proposition meets a need; Association is already held by C-099 and Realization (C-094) says that something is made real, not that it helps |
| levereras till C-154 | no ArchiMate core relationship says that a product is delivered to an actor; Serving (C-095) runs between behaviour and what it serves, not from a product to its receiver, and Association is already held by C-099 |
| är leverantör till C-155 | no ArchiMate core relationship says that an actor supplies something an architecture object needs; Association is already held by C-099 and Assignment (C-096) says who performs, not who supplies |
| Forum C-156 | a forum is the store's own specialisation of verksamhetssamverkan (C-141); Business Collaboration imports as C-141, and a forum is typed by hand |
| fastställs av C-183 | fastställs av (ADR 0023) says who decided or adopted a bärare or a styrmedel, SBVR's business jurisdiction; no ArchiMate core or motivation relationship says who decided a motivation element, and Association is already held by C-099 |
| ansvarar för C-208 | ansvarar för (ADR 0035) says which roll owns an informationsobjekt or a verksamhetsbeteende; Assignment (C-096) says who performs and may not run from a role to a passive object, and Association is already held by C-099 |
| Värdeström C-190 | värdeström (ADR 0027) is the set of stages that build up the value a värdeerbjudande promises, BACM's ValueStream; ArchiMate's Value Stream lies in the strategy layer outside the core this table covers |
| Värde C-195 | värde (ADR 0028) is the measurable benefit a product's delivery gives its recipient, part of the värdeerbjudande and realised by a värdeström's stages, VDML's ValueDefinition, ValuePropositionComponent and ValueAdd; ArchiMate's Value lies in the motivation layer outside the core this table covers and gets its row when the table is reviewed |