ENTERPRISE ARCHITECTUser Guide SeriesEnterprise ArchitectureAuthor: Sparx SystemsDate: 2021-04-29Version: 15.2CREATED WITH

Table of ContentsEnterprise ArchitectureIntroductionEnterprise Architecture OverviewWhat is Enterprise ArchitectureContext for Enterprise ArchitectureLevels of ArchitectureTypes of ArchitectureScope of ArchitectureCharacteristics of Good ArchitectureLists, Diagrams and MatricesMeet the Enterprise Architecture ToolsActivity DiagramAuditingBalanced ScorecardBusiness Process DiagramCalendarClass DiagramComponent DiagramDashboard DiagramsDecision Tree DiagramDeployment DiagramDocumentationGap Analysis MatrixHeat MapImport and Export SpreadsheetsOrganizational Chart DiagramPatternsRelationship MatrixRequirements DiagramRoadmap DiagramSpecification ManagerStrategy MapLibraryTime Aware ModelingTraceability WindowValue ChainUses of an Enterprise ArchitectureMergers and AcquisitionsCorporate DivestitureArchitecture OversightBusiness and Systems ImprovementCommunicationEnterprise TransitionsImplementation GuidePortfolio ManagementArchitecture Program SetupManagement 6

Architecture FrameworkArchitecture ProcessArchitecture RepositoryTool SetupArchitecture PrinciplesManaging an Enterprise ArchitectureArchitecture GovernanceGovernance ProcessArchitecture Steering CommitteeArchitecture Review BoardGovernance RegisterDeveloping an Enterprise ArchitectureArchitecturesBusiness ArchitectureStrategic PlansMission and VisionDriversGoals and ObjectivesCapabilitiesBusiness ProcessesInformation ArchitectureConceptual Information ModelLogical Data ModelSchemas and MessagesPhysical Data ModelApplication ArchitectureApplication Lists Diagrams and MatricesApplication CommunicationInterface ListsCapabilities and ApplicationsBusiness Processes and ApplicationsTechnology ArchitectureApplication Platform ServicesTechnical Reference ModelInfrastructure FacilitiesStakeholder ModelingRequirements ModelingDocumenting an Enterprise ArchitectureArchitecture DescriptionArchitecture Requirements SpecificationArchitecture VisionCommunication PlanCompliance AssessmentProject GlossaryEnterprise Architecture TechniquesArchitecture GovernanceArchitecture Requirements ManagementArchitecture PartitioningApplication Portfolio ManagementBalanced ScorecardBaselines and 9192194197199

Business Goals and Objectives ModelingBusiness ScenariosCapability Based PlanningCapability ModelingCompliance AssessmentConcept ModelingData ModelingDriver ModelingFunctional DecompositionGap AnalysisGlossaryInterface AnalysisMind MappingOrganizational ModelingPattern AnalysisPrinciples ManagementProcess AnalysisProcess ModelingReviewsRisk Analysis and ManagementRoadmapsStakeholder ManagementStandards ModelingTechnical Reference ModelTime Aware ModelingUse Cases and ScenariosViews and ViewpointsWorkshopsAdditional Enterprise Architecture ToolsAuto-Names and CountersBaseline ToolBoundaryDocument ArtifactDiscussionsGlossaryImage ManagerList ViewMind Mapping DiagramModel MailModel ViewsModel SearchPackage BrowserPan and ZoomBrowser WindowRequirements ChecklistRequirement PropertiesRisk TaxonomySecurityStereotypingTagged ValuesVisual 1313315317

Working Sets319

Enterprise Architecture29 April, 2021Enterprise ArchitectureEnterprise Architecture has emerged as a discipline that can help steer the 'ship' of the enterprise through both quiet andturbulent waters, charting a course from its current location to a future location in a safe and streamlined way. Thediscipline has become more prevalent in recent years, but the precepts go back almost to the beginning of what is oftentermed the information age. An enterprise is one of the most complex man-made systems and is composed of human,political, social, software, hardware and technology components. In an enterprise of any appreciable size, it is impossiblefor a single person to understand the way the parts all work together, let alone understand its position in relation to thesystem of other organizations that form its environment, or to determine how it can evolve.Enterprise Architecture can be used to create visualizations of the enterprise at different levels of abstractions and tocreate Roadmaps that show how the enterprise can be transitioned from its baseline (current) state to a target (future)state.Unit: QuarterlyQ4'17Component 1'20Q2'20Q3'20Q4'20Windows 23Q3'22Q4'22Q1'23Q2'23Enterprise Resource Planning SystemCustomer ManagerThis developmentrepresents refactoring froma thick client to a web-basedinterface, maintaining theserver side componentdeveloped in 2002.Capture CRM Hosted ServiceThe replacement CRMsystem will beimplemented, and duringthis period adapters will beconfigured to ensure data isexchanged with a numberof other systems.This diagram shows the use of aRoadmap overlay to present thelifecycle phases of the CustomerRelationship component's existingand incumbent systems and theERP system, which it interfaces tofor sales figures.Q4'17Q1'18Unit: QuarterlyQ2'18Q3'18Q4'18Q1'19Q2'19Q3'19Segment LegendThe two applications(incumbent and thereplacement) will be runin parallel forapproximately 4 weeksor until the replacementcomponent can be fullyevaluated.ImplementationDevelopmentSupported FullySupported PartiallySupport End of 1'22Q2'22Component LifecycleEnterprise Architect is a powerful platform that can be used to define the strategic context for an Enterprise Architecture,the Enterprise Architecture itself, and the Implementation initiatives that realize the designs and that finally deliver thebusiness value. It can serve both as the architectural repository and as a tool for managing the process by whicharchitectures are created and maintained, including an architectural requirements management platform. Powerfulvisualization capabilities allow models to be transformed and presented in a variety of compelling ways that will delightstakeholders, from the executive level through to the implementation teams.(c) Sparx Systems 2021Page 6 of 321Created with Enterprise Architect

Enterprise Architecture29 April, 2021The tool can be used to define Strategic, Tactical and Solution Architectures and to provide compelling views for a widerange of stakeholders, from senior executives through to implementation partners. Business, Information, Applicationand Technology architectures can be created and managed, and baseline and target architectures defined, allowingtransitions to be visualized.This diagram shows a Pie Chart elementdepicting element priorities for all theRequirements in a selected Package.It provides a useful summary for aRequirements Manager and isdynamically updated when the prioritychanges and the diagram is reopened.A range of other pre-defined Charts anduser-defined Charts can also be added.A filter has been added to exclude allelements other than Requirements.(c) Sparx Systems 2021Page 7 of 321Created with Enterprise Architect

Enterprise Architecture29 April, 2021IntroductionThe discipline of Enterprise Architecture dates back to the mid-eighties when John Zachman recognized the need tomanage the complexity of distributed technology systems. Enterprise Architecture has since become one of the mostimportant disciplines in the business and information technology professions and has become increasingly relevant in anera dominated by digital disruption. When done well, Enterprise Architecture can be used to guide an organizationthrough the complex business and digital landscape that currently confronts business and technology leaders.Enterprise Architect has become the tool of choice for many leaders in the industry because of its flexible, extensible andpragmatic approach to modeling complex systems. As a platform, Enterprise Architect offers a unique capability insupporting the integration of strategic, business and technology models, from motivation models down to theimplementation of systems. The tool allows the architect to create Strategic models (including diagrams such as theBalanced Scorecard), Capability models, Tactical models such as Gap analysis, and Roadmaps and Operational models,appealing to stakeholders from the senior executives through to line managers and solution and implementation teams.Stakeholder Onion DiagramAffected External StakeholdersKatherine Celta:Training PartnerOrganization or EnterpriseFelicity NewtonJones: HumanResources ManagerYukiko Miakawati: ChiefFinancial OfficerAffected Organizational UnitKarl Zimmerton:Development andImplementationManagerPaul Magnolia: TestManagerHamyln Piper: ChiefFinancial OfficerSolution DeliveryAndre Douglas: ChiefTechnical OfficerAlessandro Taglia:Customer ExperienceManagerToni Rothland: StockControl ManagerBusiness Analysis tools, nested boundaries in Sparx Systems Enterprise ArchitectThis diagram indicates the level of involvement the stakeholders have with the solution, which stakeholders willinteract directly with the solution or participate in a business process, which are part of the whole organization, andwhich are outside the organization.(c) Sparx Systems 2021Page 8 of 321Created with Enterprise Architect

Enterprise Architecture29 April, 2021How it will help youReaders will typically come to the topic of Enterprise Architecture with some existing knowledge or experience, even ifit is something that has been learnt in lectures or by on the job training, or perhaps by using a different tool. Readers willbenefit by understanding the product's features and the tools that are available to develop and manage EnterpriseArchitectures in Enterprise Architect, and this will enable them to be more productive as an individual and as a memberof a team.Who will benefitAnyone involved in the development or management of architectures, whether at a strategic level, a business value levelor a technology level will benefit from reading this information. This includes a wide range of roles including StrategicThinkers, Senior Management, Business, Information, Application and Technology Architects, Solution Architects andImplementation teams whose work and decisions will ultimately be guided by the architectures.What you will learnThis topic will teach you how to use the powerful features of Enterprise Architect to develop and manage EnterpriseArchitectures, to create documentation and to work collaboratively as a member of a team using a formal or informalarchitecture framework. You will learn what tools are available, how to use them and which tools should be used toperform a particular technique. For example, regardless of the process or framework that is adopted, at some pointArchitectural Partitioning will need to be performed; this topic will describe the technique and how to best achieve itusing the tools and facilities you have at your fingertips using Enterprise Architect.Overview of the DocumentationThis table provides a list and a description of the subjects that are included in this work, giving an overview of thematerial.Enterprise ArchitectureOverviewThis topic gives a high level view of Enterprise Architecture, describing what it isand the levels, types and styles of architecture. It describes some of thecharacteristics of good architecture and the outputs and content of an architectureprocess such as catalogs, matrices and diagrams. It also puts EnterpriseArchitecture into the context of other disciplines, from the strategic level through tothe operational level, including Solution Architectures.Meet the EnterpriseArchitecture ToolsThis topic lists the key tools that are used in Enterprise Architecture, including apicture of the tool in action, where to find the tool, how to use it and how to becomeproficient in using the tool. There are many additional tools that will be useful,which are described in the last topic entitled Additional Enterprise ArchitectureTools.Uses of an EnterpriseArchitectureThis topic describes how an Enterprise Architecture can be utilized, who will getbenefit and how that benefit can be realized. This includes the use of an architectureas a communication tool and strategic guide for senior management, or as a guidefor solution architects and implementation teams and for the purposes of theoversight of implementation projects. It will also describe the use of an architecturefor portfolio management, business systems improvement and for analyzing,defining and documenting enterprise transitions, including Acquisitions andMergers.(c) Sparx Systems 2021Page 9 of 321Created with Enterprise Architect

Enterprise Architecture29 April, 2021Architecture PracticeSetupMany architects suffer from the blank canvas syndrome, because much of theliterature describes how to develop architectures but is silent about setting up anarchitecture practice. This topic will guide you in using Enterprise Architect to setup an Architecture Practice, including Framework options and how to set up thetool to support the practice. This includes repository structure, principles, teamcollaboration, documentation generation using templates, meta-model definition,governance structures, language support and more. It loosely aligns with thePreliminary phase of The Open Group Architecture Framework ArchitectureDevelopment Method (TOGAF ADM).Planning an EnterpriseArchitectureAn architecture is a project and needs to be planned. This topic explains how to setup an architecture project, including the definition of the scope, constraints and thedesired enterprise outcomes, including problems or opportunities that thearchitecture is addressing. It describes how the architecture aligns with enterprisestrategy and how it relates to solution architectures that will ultimately implementthe architecture in practice. It loosely aligns with the Vision phase of the TOGAFADM.Managing an EnterpriseArchitectureThe management of an architecture involves the set up, monitoring and control ofthe architecture project from its inception through to its delivery. Team capabilities,tool usage, the quality of architectural artifacts, communication mechanisms,governance structures and stakeholder management are all described in this topic.The use of Enterprise Architect as a tool for the management of an architecture willbe fully described and exemplified.Developing an EnterpriseArchitectureThis topic describes how Enterprise Architect can be used to create and maintain anEnterprise Architecture. It is the centerpiece of the discussion and articulates howthe architecture is used to describe the way the organization will transition from abaseline to a target state, resulting in the attainment of business goals andobjectives and new or augmented capabilities.Documenting anEnterprise ArchitectureThis topic describes the powerful documentation features of Enterprise Architect,allowing Architects, Analysts, Managers and others to generate a range ofdocumentation, from ad-hoc reports to publication of quality documents directly outof the architecture repository. It will describe creating organization-specificdocumentation using a sophisticated and flexible template system for generatingdocuments into a range of formats, including PDF, DOCX and HTML.Enterprise ArchitectureFrameworks andStandardsThis topic describes Enterprise Architect's support for frameworks, languages andstandards. This consists of a wide range of frameworks, including The Open GroupArchitecture Framework (TOGAF), the Federal Enterprise Architecture Framework(FEAF) and the Zachman Framework. Languages such as the Unified ModelingLanguage (UML), ArchiMate and Business Process Model and Notation (BPMN)are described, as are standards such as the National Information Exchange Model(NIEM).Enterprise ArchitectureTechniquesThis topic describes the important techniques that are used by Architects whenworking with architectures, from the setup phase through planning, managing,developing and documenting architectures. Each technique is described, with a listof the tools available in Enterprise Architect that can be used to perform thetechnique, explaining the use of the tool in the context of the technique.Additional EnterpriseArchitecture Tools(c) Sparx Systems 2021This topic lists a series of additional tools that can be used for EnterpriseArchitecture, including a picture of the tool in action, where to find the tool, how touse it and how to become proficient in using the tool. There are a number of keytools that are considered to be most important for enterprise architecture, which aredescribed in the Meet the Enterprise Architecture Tools section.Page 10 of 321Created with Enterprise Architect

Enterprise Architecture(c) Sparx Systems 202129 April, 2021Page 11 of 321Created with Enterprise Architect

Enterprise Architecture29 April, 2021Enterprise Architecture OverviewEnterprise Architecture has emerged as a critical discipline to ensure that an enterprise and the organizations it compriseshave an understanding of the significant elements from which it is made, from strategic goals through to the business andinformation technology components that assist in achieving those goals. The discipline also allows enterprises to createarchitectures that will transition from where they are to where they need to be. Now more than ever in this age of digitaldisruption, when organizations can no longer rely on length of tenure in a field or being bigger than their competition asa safeguard against competitive forces, Enterprise Architecture as a discipline is vital.The profession of Enterprise Architect is rarely taught as a separate degree course at tertiary institutions, and it alsosuffers under the proliferation of large, conflicting and at times burdensome frameworks and a lack of tool support. Thishas led to architecture practitioners finding it difficult to articulate or demonstrate the value of their 'profession'.This section addresses the questions:···What is Enterprise Architecture?Where does it fit into the context of other disciplines?What are the characteristics of good architecture?The section also discusses the levels, types and styles of architecture that exist, and describes the notational mechanismsthat are at an architect's disposal.Enterprise Architect's pragmatic approach to modeling, and the extensive set of facilities available to the architect andothers, make it a powerful tool both as an architecture repository and as a platform for creating, managing anddisseminating architectural work.Financial PerspectiveHow should we appear to our shareholders?- Broadening Revenue Base- Improving Operating Efficiency- Reducing Reliance on Domestic CustomersCustomer PerspectiveBusiness Process PerspectiveHow should we appear to our Customers?What Business Processes must we excel at?- Working through the Internet Channel- Reducing Processing Time- Broadening Product Offering- Understanding Customer SegmentsVISION&STRATEGY- Good Product Range- Service Excellence- Innovative and Reliable- Trusted Business PartnerLearning & Growth PerspectiveHow can we maintain our ability to change andimprove?- Increase Employee Job Satisfaction- Increase Employee Productivity- Hire Internet Aware Technical Staff- Hire multi-Channel Sales Executives(c) Sparx Systems 2021Page 12 of 321The Balanced Scorecard diagram is one of theStrategic Diagrams used by managers andothers to manage activities performed by thestaff under their control.Created with Enterprise Architect

Enterprise Architecture29 April, 2021What is Enterprise ArchitectureThere is s