Transcription

1a TOGAF artefacts with ArchiMate illustrationsand the meta model derived from those artefactsLast updated 02/01/2018 18:40TOGAF and ArchiMate are registered trademarks of The Open Group.This document updates and extends research done by Avancier Ltd for the British Computer Societyinto harmonisation of different enterprise architecture standards and sources.Avancier Ltd hereby gives permission for members of The Open Group’s Architecture Forum toreproduce text from this document in any document that is the copyright of The Open Group.Reproduction of text from this document in documents that are not the copyright of Avancier Ltd orThe Open Group requires the permission of The Open Group but not the permission of Avancier Ltd.Copyright Avancier Ltd 2009-2018

11. To support TOGAF‘s artefacts and principles (more comprehensive,coherent and consistent than some realise)2. To simplify and clarify definitions of TOGAF‘s architecture artefacts3. To distinguish EA artefacts from SA artefacts4. To illustrate EA artefacts using ArchiMate where possible5. To illustrate SA artefacts using ArchiMate where possible6. To raise awareness of a few points7. To generate a TOGAF meta model that is more demonstrably consistentwith its artefactsCopyright Avancier Ltd 2009-2018

TOGAF Principlesservice-oriented implementation-independent specification of business systemsMotivationsand constraintsPassive structuresBehaviorsThings that are actedin or onThings happening overtime that access orchange the state ofbusiness s (SIB)Design Patterns (RM)ManagementTimeBudgetResourcesLogical activestructuresPhysical activestructuresSpecificationsof things that actThings that sData EntityProcessRoleLogicalData EntityApp/ISServiceLogical *AppComponentPhysicalAppComponentLogical DataComponentTechnologyServiceLogical orSeparation of logical ABBs from physical SBBsPhysical things in EA are still “considerably abstracted from implementation“Avancier Limited 2009-2018

21. To support TOGAF‘s artefacts and principles (more comprehensive,coherent and consistent than some realise)2. To simplify and clarify definitions of TOGAF‘s architecture artefacts3. To distinguish EA artefacts from SA artefacts4. To illustrate EA artefacts using ArchiMate where possible5. To illustrate SA artefacts using ArchiMate where possible6. To raise awareness of a few points7. To generate a TOGAF meta model that is more demonstrably consistentwith its artefactsCopyright Avancier Ltd 2009-2018

For exampleTurgid textWhat it saysRole CatalogRole CatalogProvides a listing of all authorization levels or zonesLists roles by authorization level and/or zone.within an enterprise. Frequently, application securityHelps to prevent difficulties when different localor behavior is defined against locally understoodsecurity standards are combined, ensuring both aconcepts of authorization that create complex andmore seamless user experience and more secureunexpected consequences when combined on theapplications.user desktop. If roles are defined, understood, andA key input to change impact analysis for rolealigned across organizations and applications, thisdefinition and user training.allows for a more seamless user experience andgenerally more secure applications, as administratorsdo not need to resort to workarounds in order toenable users to carry out their jobs. In addition tosupporting security definition for the enterprise, theRole Catalog also forms a key input to identifyingorganizational change management impacts,defining job functions, and executing end-usertraining. As each role implies access to a number ofbusiness functions, if any of these business functionsare impacted, then change management will berequired, organizational responsibilities may need tobe redefined, and retraining may be needed.Copyright Avancier Ltd 2009-2018

31. To support TOGAF‘s artefacts and principles (more comprehensive,coherent and consistent than some realise)2. To simplify and clarify definitions of TOGAF‘s architecture artefacts3. To distinguish EA artefacts from SA artefacts4. To illustrate EA artefacts using ArchiMate where possible5. To illustrate SA artefacts using ArchiMate where possible6. To raise awareness of a few points7. To generate a TOGAF meta model that is more demonstrably consistentwith its artefactsCopyright Avancier Ltd 2009-2018

The ADM (KLP 2.4-1) “Architecture Development Method––––The core of TOGAF.A step-by-step approach todevelop and usean Enterprise Architecture.”Copyright Avancier Ltd 2009-2018

The different levels of architecture that exist in an organization (KLP 20-1) “Strategic Architecture– an organizing framework for change anddirection setting at an executive level. “Segment Architecture– an organizing framework for change anddirection setting and the development ofeffective architecture roadmaps at aprogram or portfolio level. “Capability [increment?] Architecture– an organizing framework for change,and the development of effectivearchitecture roadmaps realizingcapability increments”Copyright Avancier Ltd 2009-2018

A picture that can mislead Because the artefacts and activities at topand bottom levels are so differentCopyright Avancier Ltd 2009-2018

Problem: TOGAF 9 decoupled the ADM from the architecture levelCopyright Avancier Ltd 2009-2018

Solution: distinguish Enterprise Architecture from Solution Architecture artefacts for Analysis and direction setting atan executive level and portfoliolevelEA Differ from artefacts for Architecture developmentduring an ADM cycle at thecapability or solution levelSACopyright Avancier Ltd 2009-2018

c40 TOGAF artefacts (more comprehensive, coherent and consistent than some realise)MotivationEnterprise / Strategy / Portfolio level artefactsSolution or Capability Increment level artefactsDriver Goal/Objective CatalogOrganization Decomposition DiagramGoal/Objective/Service DiagramNode Connectivity Diagram (physical or logical)Functional Decomposition DiagramBusinessFunction/Org MatrixProcess Flow DiagramBusiness ScenarioActor/Role MatrixRole CatalogBusiness Function/Service CatalogOrganization/Actor DiagramProcess/Event/Control/Product CatalogProcess Application Realization DiagramApplication Portfolio CatalogApplicationsApplication Use Case DiagramApplication/Function MatrixApplication User Location DiagramRole/Application MatrixApplication Communications DiagramDataConceptual Data DiagramSoftware Distribution DiagramBusiness Service/Info DiagramData Entity/Function MatrixLogical Data DiagramApplication/Data MatrixData Security DiagramData Entity/Data Component CatalogData Lifecycle DiagramData Dissemination DiagramData Migration DiagramEnvironments and Locations DiagramTechnology Standards CatalogTechnologySoftware Engineering DiagramProcessing DiagramTechnology Portfolio CatalogTechnology Services Catalog (TRM)Technology/Application MatrixNetworked Computing/Hardware DiagramCommunications Engineering DiagramPlatform Decomposition DiagramCopyright Avancier Ltd 2009-2018

41. To support TOGAF‘s artefacts and principles (more comprehensive,coherent and consistent than some realise)2. To simplify and clarify definitions of TOGAF‘s architecture artefacts3. To distinguish EA artefacts from SA artefacts4. To illustrate EA artefacts using ArchiMate where possible5. To illustrate SA artefacts using ArchiMate where possible6. To raise awareness of a few points7. To generate a TOGAF meta model that is more demonstrably consistentwith its artefactsThe ArchiSurance examples are the widelypublished ones created by Marc Lankhorst.Copyright Avancier Ltd 2009-2018

1st the EA / Strategic / Portfolio level TOGAF features c20 Catalogs andMatrices that enable portfolio level––––Gap analysisCluster analysisImpact analysisTraceability analysisEAEACopyright Avancier Ltd 2009-2018

STRATEGIC BUSINESS ARCHITECTUREEnterprise Strategy and Portfolio levelMotivationDriver Goal/Objective CatalogPHYSICAL STRUCTUREOrganization Decomposition DiagramNode Connectivity Diagram (physical)LOGICAL STRUCTUREFunctional Decomposition DiagramBusinessNode Connectivity Diagram (logical)Function/Org MatrixRole CatalogBEHAVIORBusiness Function/Service CatalogProcess/Event/Control/Product CatalogApplicationsDataTechnologyCopyright Avancier Ltd 2009-2018Solution or Capability Increment level

TOGAF artefact: Driver/Goal/Objective CatalogGoal/ObjectiveDriverOrganization Unit Driver/Goal/Objective Catalog– provides a cross-organizational view of how an organization responds todrivers through the setting of goals, objectives, and any measure associatedwith them.– Helps to identify synergies (e.g. organizations with similar or related objectives)allowing stakeholders to be identified and change initiatives to be aligned orconsolidated.Organization UnitDriverGoalCopyright Avancier Ltd 2009-2018Objective

TOGAF artefact: Organization Decomposition DiagramOrganization Unit Organization Decomposition Diagram––––––The base artefact for physical / strategic-level business architectureprovides the foundation for other artefactsrelates actors and/or roles to organization units in an organization tree.may indicate locationsindicates owners, decision-makers and a chain of commandhelps to identify which stakeholders are concerned with which businessdrivers, goals and objectives.Copyright Avancier Ltd 2009-2018

ArchiMateOrganization UnitActor Org Unit An organization viewCopyright Avancier Ltd 2009-2018

TOGAF artefact: Node Connectivity DiagramOrganization Unit The Node Connectivity Diagram (physical)––––(aka goods and services flow diagram)A node: an organizational unit, actor, location or facility.A needline: shows the need of one node for information from another.An arrow: shows information flow directionA flow can be named and annotated to describe the data carried contenttransport mechanism/mediasecurity or other classification level,timelinessinteroperability requirements.Copyright Avancier Ltd 2009-2018

Node connectivity Diagram: SCOR techniqueOrganization Unit Identify your customers Identify your suppliersCopyright Avancier Ltd 2009-2018

Node connectivity Diagram: SCOR techniqueOrganization Unit1.2.3.4.Identify your customersIdentify your suppliersIdentify the key nodes (entities in the supply chain)Link nodes by flows.InformationflowA subsystem orcomponentMaterial andInformation flowCopyright Avancier Ltd 2009-2018

ArchiMateOrganization Unit An Organization View - Nodes are physical ActorsCopyright Avancier Ltd 2009-2018Surelycommunication pathrather than interface?

Reverse engineering principles (1) Reverse engineer from– physical structure to logical structureOrganizationUnitFunctionCopyright Avancier Ltd 2009-2018

TOGAF artefact: Functional Decomposition DiagramFunction Functional Decomposition Diagram– The base artefact for logical / strategic-level business architecture– provides the foundation for other artefacts– shows on a single page the organization capabilities relevant to thearchitecture to be defined and governed.– helps to quickly model the organization’s capabilities without being draggedinto debate on how the organization does it.– given a basic diagram, it is possible to layer heat-maps on top of it to showscope and decisions. For example, the capabilities to be implemented indifferent phases of a change program.can be composed or decomposed - from wide/top to narrow/bottom.“the level and rigor of decomposition varies” (TOGAF)Copyright Avancier Ltd 2009-2018

ArchiMateA strict (non-redundant) hierarchy.Strategic management functionsFiscal andaccountingStrategyRisk andCompliancePerformanceOperational functionsSalesMarketingProductsCustomer ormanceBankingAccountsContractslife oryCash flowMoneymarketContractadmin.Claim admin.Support functionsOrganizationHRProcessOfficeCopyright Avancier Ltd 2009-2018FacilityITSM

TOGAF artefact: Node Connectivity DiagramFunction Node Connectivity Diagram (logical)––––(aka goods and services flow diagram)A node: a function or roleA needline: shows the need of one node for information from another.An arrow: shows information flow directionA flow can be named and annotated to describe the data carried contenttransport mechanism/mediumsecurity or other classification level,timelinessinteroperability requirements.Copyright Avancier Ltd 2009-2018

Node Connectivity Diagram in ArchiMateFunction Shows services offered by nodes to external entities and to each liveryMoneyhandlingA flow of goods,services or dataSupplierSupplierDriverCopyright Avancier Ltd 2009-2018A Role thatprovides orreceives a flowA one Actor RoleBACS

Node Connectivity Diagram in roductDevelopmentProduct ersPartsProductAssemblyProductsProductsCopyright Avancier Ltd 2009-2018ProductDeliveryCustomer

TOGAF mapping logical organization to physical organizationFunctionOrganization UnitOrg/Function Matrix “Structured Analysis: Identifies the key business functions within the scopeof the architecture, and maps those functions onto the organizational unitswithin the business.”Organization Marketing SalesDeliveryFunctionMarketing Might reveal a 1-1 “Functional organization” Or else an N-N DeliveryActivityActivityActivityCopyright Avancier Ltd 2009-2018

TOGAF artefact: Role CatalogRole Role Catalog––––The base artefact for people-oriented viewsProvides a foundation for mapping roles to processes, applications and dataLists roles by authorization level and/or zone .Helps to prevent difficulties when different local security standards arecombined, ensuring both a more seamless user experience and more secureapplications.– Supports change impact analysis for role definition and user trainingCopyright Avancier Ltd 2009-2018

Reverse engineering principles (2) Reverse engineer from– physical structure to logical structureOrganizationUnitFunction– structure to behaviorFunctionProcessServiceCopyright Avancier Ltd 2009-2018

TOGAF artefact: Process/Event/Control/Product CatalogProcess Process/Event/Control/Product Catalog– a hierarchical process structure including events that trigger processes, outputs from processes, and controls/rules (pre and post conditions).– enables gap, cluster and analysis of a portfolio: allows an architect to filter, report, and query across organization processes toidentify scope, commonality– enables impact analysis on changing a process.Processlevel 1Processlevel 2ProcessLevel 3Input / eventCopyright Avancier Ltd 2009-2018Output / productControl / rules

TOGAF artefact: Business Function/Service CatalogFunctionBusiness ServiceOrganization Unit Business Function/Service Catalog– provides a functional decomposition in a form that can be filtered, reported on,and queried. It can be used to identify capabilities of an organizationunderstand the level that governance is applied to the functions of an organization.identify new capabilities required to support business changedetermine the scope of change initiatives, apps, or technology components.Function level 1Function level 2Business ServiceCopyright Avancier Ltd 2009-2018Organization Unit

ArchiMateFunctionBusiness Service Hand madeInsureClaim onInsuranceFunction assigned to ServiceInsuranceFunction usesServiceCopyright Avancier Ltd 2009-2018

STRATEGIC APPS ARCHITECTUREEnterprise Strategy and Portfolio levelMotivationBusinessApp Portfolio CatalogApplicationsApp/Function MatrixRole/App MatrixApp Communications DiagramDataTechnologyCopyright Avancier Ltd 2009-2018Solution or Capability Increment level

TOGAF artefact: App Portfolio CatalogApplication Component App Portfolio Catalog– The base artefact in strategic applications architecture– provides the foundation for other artefacts.– lists all (logical and/or physical) applications in the enterprise that are to bedefined and governed– helps to scope change initiatives that impact applications.– may be extended to name IS Services provided ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

TOGAF artefact: App/Function MatrixFunctionApp/IS ServiceApplication Component App/Function Matrix– Enables gap, cluster and impact analysis of a portfolio.– Asking which business functions use an app reveals where the same appsupports different functions, which apps are essential and those little used.– Asking which apps are used by a business function may reveal requirementsfor interoperability and support.AppCRMERPBillingData warehouseFunctionSalesPlace orderRegister customerInvoicingPost invoice ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

App/Function matrix as a diagramStrategicmanagementfunctions akacapabilitiesVision and genceDataWarehouseManufactureDeliveryCustomer ServiceSales andMarketingSupply gProcessActivityManagementCall of goodsBills ofMaterialTime ualityControlCommissionsHuman ResourcesSupportfunctions akacapabilitiesProduct DesignCostingSales & MarketingOperationalfunctions edgerRosteringFixedAssetsTime andAttendanceCashManagementCopyright Avancier Ltd 2009-2018FacilitiesKnowledgeand TSMIdentitymanagementIT EAIMiddleware

TOGAF artefact: Role/App MatrixRoleApp/IS ServiceApplication Component Role/App Matrix––––Shows which roles use which apps.Enables gap, cluster and impact analysis of an app portfolio.Asking which apps support a role reveals permissions needed by that role.Asking which roles use an app may reveal requirements for availability,security and support.AppCRMERPBillingData warehouseRoleSalesPlace orderRegister customerInvoicingPost invoice ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

TOGAF artefact: App Communication DiagramApplication ComponentInterfaces renamedas data flows App Communication Diagram––––shows which apps communicate and what data passes between themmay associate data flows with data entitiesmay associate apps, via IS services, with business serviceslogical, only shows data transport technologies where architecturallysignificant.ABCLimitedBusiness Apps stomerSalesmanCopyright Avancier Ltd 2009-2018BACS

TOGAF supports the Diagram with an “interface” CatalogApplication ComponentApp Communication DiagramCRMN2 model, or Node Connectivity Diagram in sIntelligenceInterface (Aargh! Data Flow) CatalogData Flow idSource AppDestination AppData contentTrigger event1aCRMSalesSales order requestNew sales order1bSalesCRMSales order confirmationOrder created in the Sales system2aSalesStockRequisitionSubscribe/Publish timerCopyright Avancier Ltd 2009-2018

ArchiMateApplication ComponentCopyright Avancier Ltd 2009-2018

STRATEGIC DATA ARCHITECTUREEnterprise Strategy and Portfolio levelMotivationBusinessApplicationsConceptual data DiagramData Entity/Function MatrixDataApp/Data MatrixData Entity/Data Component CatalogData dissemination DiagramTechnologyCopyright Avancier Ltd 2009-2018Solution or Capability Increment level

TOGAF artefact: Conceptual data DiagramBusiness Data Entity Conceptual data Diagram (Better Catalog?)–––– The base artefact in strategic data architectureprovides the foundation for other artefactslists critical data entities within the enterpriseshows relationships between them. (TOGAF)ArchiMate information structure view– business/conceptual level(Aargh! Aggregates and compositionsinstead of properly named associations!)Copyright Avancier Ltd 2009-2018

TOGAF artefact: Data Entity/Business Function MatrixFunctionBusiness Data Entity Data Entity/Business Function Matrix– Shows which business functions create and use which data– Enables gap, cluster and impact analysis of a portfolio.– Asking which functions create and use an data entity reveals data entities thatare essential or appear unused, and indicates where functions do or mightexchange/share data.– Asking which entities each business function creates and uses revealsfunctions that use little data, and so might be better supported.– Supports data governance by data steward against data standards.Copyright Avancier Ltd 2009-2018

One of the most traditional EA artefacts Read Function for Process, and note clustering on “Create”Copyright Avancier Ltd 2009-2018

TOGAF artefact: Data Entity/Data Component CatalogBusiness Data EntityLogical Data EntityLogical Data Component Data Entity/Data Component Catalog– lists all data used across the enterprise, and the data components where datais stored.– encourages effective data sharing and re-use– enables the definition and app of information management and datagovernance policies ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

TOGAF artefact: App/Data MatrixApplication ComponentLogical Data Entity App/Data Matrix– shows which apps create, read, update and delete which data entities.– enables gap, cluster and impact analysis of a portfolio– asking which apps access a data entity reveals where the same data is use bydifferent apps, and they do or might exchange/share data– asking which data entities are accessed by an app helps understanding of dataentities and their lifecycles in the enterprise.– may classify data (master, reference, transactional, content, historic )– may classify apps (transactional, batch, warehouse )Data RMRUDRUDCRUDRDBillingRUDCRUDCRUDRDRDRDRDAppData warehouseCopyright Avancier Ltd 2009-2018

Partial match in ArchiMateApplication ComponentLogical Data Entity A hand made view: only a partial view of the App/data estate governed byEA (so not used for gap, cluster or impact analysis)InsurancePolicyRDamageClaimRCURRUClaims AppCURCustomerCopyright Avancier Ltd 2009-2018U

TOGAF artefact: Data Dissemination DiagramBusiness Data Entity Logical Data EntityApplication ComponentShows where business data entities are digitised in different applicationsAllows effective sizing to be carried out and the IT footprint to be refined.By attaching business value to data, an indication of the business criticality of appscan be gained.May show data replication and app ownership of the master reference for data Can show several copies and the master-copy relationship between them.Can include services; that is, services encapsulate data and they reside in an app,or services that reside on an app and access data encapsulated within the yMaster (1)CopyMaster (2)CopyMasterCopyData entityCustomerOrderInvoice(1) until Order Closed(2) after Order Closed.Copyright Avancier Ltd 2009-2018

STRATEGIC TECHNOLOGY ARCHITECTUREEnterprise Strategy and Portfolio levelMotivationBusinessApplicationsDataTechnology Standards CatalogTechnologyTechnology Portfolio CatalogTechnology Services Catalog (TRM)Technology/App MatrixCopyright Avancier Ltd 2009-2018Solution or Capability Increment level

TOGAF artefact: Technology Portfolio Catalog Technology Portfolio Catalog– the base artefact in strategic technology architecture– provides the foundation for other artefacts, and for management of technologylifecycles, versions and standards– lists all (logical and/or physical) technologies in the enterprise that are to bedefined and governed– includes hardware and platform applications (aka system software)– should be classified using the headings in the TRM or similar– may be extended to name platform Technology Services provided ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

Technology Service Catalog (aka TRM)User Interface ServicesTransaction Processing ServicesOperating System ServicesSoftware Engineering ServicesGraphical Client/Server servicesStarting a transactionKernel OperationsProgramming Language servicesDisplay Objects servicesCo-ordination of recoverable resources in a transactionCommand Interpreter and Utility servicesObject Code Linking servicesWindow Management servicesCommitting or rolling back transactionsBatch Processing servicesCASE Environment and Tools servicesDialogue Support servicesControlling timeouts on transactionsFile and Directory SynchronizationGraphical User Interface (GUI) Building servicesPrinting servicesChaining transactions togetherScripting Language servicesComputer-Based Training and Online Help servicesMonitoring transaction statusLanguage Binding servicesCharacter-Based servicesRun-Time Environment servicesApp Binary Interface servicesGraphics and Imaging ServicesData Management ServicesNetwork ServicesOO Provision of ServicesGraphics servicesData Dictionary/Repository servicesElectronic Mail servicesObject Request Broker (ORB) servicesGraphical Object Management servicesDatabase Management System (DBMS) servicesDistributed Data servicesImplementation Repository servicesDrawing servicesOO Database Management System (OODBMS) servicesDistributed File servicesInstallation and Activation servicesImaging functionsFile Management servicesDistributed Name servicesInterface Repository servicesQuery Processing functionsDistributed Time servicesReplication servicesInternational Operation ServicesScreen Generation functionsRemote Process (Access) servicesCommon Object servicesCharacter Sets and Data Representation servicesReport Generation functionsRemote Print Spooling and Output Distribution servicesChange Management servicesCultural Convention servicesNetworking/Concurrent Access functionsEnhanced Telephony functionsCollections servicesLocal Language Support servicesWarehousing functionsShared Screen functionsConcurrency Control servicesVideo-Conferencing functionsData Interchange servicesBroadcast functionsEvent Management servicesMailing List functionsExternalization servicesData interchange servicesLocation and Directory ServicesSystem and Network Management ServicesLicensing servicesDocument Generic Data Typing and Conversion servicesDirectory servicesUser Management servicesLifecycle servicesGraphics Data Interchange servicesSpecial-Purpose Naming servicesConfiguration Management (CM) servicesNaming servicesSpecialized Data Interchange servicesService Location servicesPerformance Management servicesPersistent Object servicesElectronic Data Interchange servicesRegistration servicesAvailability and Fault Management servicesProperties servicesFax servicesFiltering servicesAccounting Management servicesQuery servicesRaw Graphics Interface functionsAccounting servicesSecurity Management servicesRelationship servicesPrint Management servicesSecurity servicesText Processing functionsDocument Processing functionsSecurity ServicesNetwork Management servicesStart-Up servicesPublishing functionsSystem Entry Control servicesBackup and Restore servicesTime servicesVideo Processing functionsSecurity Management servicesOnline Disk Management servicesTrading servicesAudio Processing functionsAudit servicesLicense Management servicesMedia Synchronization functionsAccess Control servicesCapacity Management servicesMultimedia Processing functionsNon-Repudiation servicesSoftware Installation servicesInformation Presentation and Distribution functionsTrusted Recovery servicesHypertext functionsEncryption servicesTrusted Communication servicesTrouble Ticketing servicesCopyright Avancier Ltd 2009-2018

TOGAF artefact: Technology/App Matrix Technology/App Matrix– Enables gap, cluster and impact analysis of a portfolio.– Asking which apps use a technology helps when a technology is going out ofsupport or is to change.– Asking which technologies are used by an app may reveal interoperability andsupport implications. ArchiMate doesn’t feature catalogs and matrices use for portfoliomanagementCopyright Avancier Ltd 2009-2018

51. To support TOGAF‘s artefacts and principles (more comprehensive,coherent and consistent than some realise)2. To simplify and clarify definitions of TOGAF‘s architecture artefacts3. To distinguish EA artefacts from SA artefacts4. To illustrate EA artefacts using ArchiMate where possible5. To illustrate SA artefacts using ArchiMate where possible6. To raise awareness of a few points7. To generate a TOGAF meta model that is more demonstrably consistentwith its artefactsThe ArchiSurance examples are the widelypublished ones created by Marc Lankhorst.Copyright Avancier Ltd 2009-2018

2nd the Solution Architecture / Capability change level TOGAF defines diagram artefacts,better suited to this levelSACopyright Avancier Ltd 2009-2018

Solution level BUSINESS ARCHITECTURE

1. To support TOGAF‘s artefacts and principles (more comprehensive, coherent and consistent than some realise) 2. To simplify and clarify definitions of TOGAF‘s architecture artefacts 3. To disting