Methods (AM) Applications architecture diagrams It is illegal to copy, share or show this document without the written permission of the copyright holder but you can share a link to it. Copyright Limited 2008-2016
TOGAF Information Systems: entities and artifacts Artifacts showing business use of applications Process Function (Capability) Role Org Unit Location Process App. Real Diagram Application/ Function Matrix Role/Application Matrix App/Organization matrix Application User Location Diagram Application Use Case Diagram IS architecture entities and artifacts IS Service App. Comm. Diagram Logical App Comp t App. Portfolio Catalog Physical App Comp t Atomic Function = Process Data Lifecycle Diagram Data Entity Application Data Matrix Data Dissemination Diagram Logical Data Diagram Logical Data Component Physical Data Comp t TOGAF generic meta model Required Behaviors Assigned to Logical Structures Realised by Physical Structures Copyright Ltd 2008-2016
Context for application(s) architecture If you work at the application portfolio management level, you might find data flow diagrams suffice. For an EA context, go to the Enterprise Architecture roles and realities page. If you work on an application s internal structure, you may consider UML more appropriate. For a software architecture context, go to the Software Architecture principles and patterns page. Copyright Limited 2008-2016
Organisation/capability view Applications View TOGAF artefacts ArchiMate viewpoints Application Portfolio catalog Organisation/capability view Application/Organisation catalog Application/Function matrix Copyright Limited 2008-2016
Application Portfolio catalog [an artefact] listing business applications and recording their properties. Usually structured so as to reflect the business function hierarchy. Generic App App App CRM App App Core business functions Marketing Sales Delivery Customer Service App App App App App App App App App App App App App App App App App App App App App App App App Support business functions HR IT Accounts Legal App App App App App App App App App App App App App App App App App App App App App CRM App App Copyright Limited 2008-2016
Application Portfolio Map - Gas Utility Company (c1985) Copyright Limited 2008-2016
Telemanagement forum Applications Map Copyright Limited 2008-2016
See previous slides for variations on Application/Organisation catalog Application/Function matrix Copyright Limited 2008-2016
Process view Applications View TOGAF artefacts ArchiMate viewpoints Process-Application Realisation Application Behaviour (2.1) Process view diagram Copyright Limited 2008-2016
Process/Application Realization Diagram to clearly depict the sequence of events when multiple applications are involved in executing a business process. enhances the Application Communication diagram by augmenting it with any sequencing constraints, and hand-off points between batch and real-time processing. would identify complex sequences that could be simplified possible rationalization points in the architecture in order to provide more timely information to business users. May also identify process efficiency improvements that may reduce interaction traffic between applications. Copyright Limited 2008-2016
Process/Application Realization Diagram UML Interaction/Sequence diagram CRM ERP DW / BI Application cooperating in the process Process What applications cooperate in the execution of a process? How and when are applications triggered by invocations? What data flows or messages are passed along with an invocation? Useful in analysing the efficiency of a process Shows the overall sequence of a process Limited representation of logic (loops, options & quits) Copyright Limited 2008-2016
ArchiMate: v2.1 Application Behavior Viewpoint A process run in an application In the application domain, process step shown using function symbol A kin to a use case header Service realised by Process Function accesses data Transition arrow Copyright Limited 2008-2016
Note the function / process confusion ArchiMate standard diagrams use different symbols for processes in the business layer Post Letter Find Pen And Paper Write Letter Put in Letter Box And in the application layer What show a process using function symbol? Email Client App Display Email Template Send Email Validate Fields Send Email Copyright Limited 2008-2016
People view Applications View TOGAF artefacts ArchiMate viewpoints Role/Application matrix Application Usage People (roles) view Application and User Location diagram Application Usage Application Use Case diagram Application Usage Copyright Limited 2008-2016
Role/Application matrix Copyright Limited 2008-2016
Application and User Location Diagram to clearly depict the business locations from which business users typically interact with the applications, but also the hosting location of the application infrastructure. The diagram enables: Identification of the number of package instances needed Estimation of the number and the type of user licenses Estimation of the level of support needed Selection of system management tools, structure, and management system Planning for the technological components of the business Performance considerations while implementing solutions Customer location (where 1,000 salesman work) Laptop Salesman Kitchen Drawing App PAN Kitchen Ordering App Printer WA N LAN Product Management Order Management Copyright Limited 2008-2016 HQ location
ArchiMate: Application & User Location Diagram Customer location (where 1,000 salesman work) Laptop Salesman Kitchen Drawing App PAN Kitchen Ordering App Printer WAN LAN Product Management Order Management HQ location Copyright Limited 2008-2016
Application Use Case Diagram displays the relationships between consumers and providers of application services. Application services are consumed by actors or other application services and the Application Use- Case diagram provides added richness in describing application functionality by illustrating how and when that functionality is used. What processes do external entities want our app to enable or support? to help to describe and validate the interaction between actors and their roles with applications. As the architecture progresses, the use-case can evolve from functional information to include technical realization detail. Application use-cases can also be re-used in more detailed systems design work. Copyright Limited 2008-2016
Application Use-Case diagram Use case = a system process that an actor engages with One use can extend another use case be included in one or more other use cases http://www.modernanalyst.com/resources/articles/tabid/115/articletype/articlevi ew/articleid/353/enterprise-architect-for-business-analysts.aspx Copyright Limited 2008-2016
ArchiMate 3.0: Application Usage Viewpoint Cf. Application use case diagram. describes how applications are used to support one or more business processes, and how they are used by other applications. can be used in designing an application by identifying the services needed by business processes and other applications, or in designing business processes by describing the services that are available. since it identifies the dependencies of business processes upon applications, it may be useful to operational managers responsible for these processes. Business process Process uses App Service Service realised by Component 1 component provides > 1 service Copyright Limited 2008-2016
Use case definition or description Application Service Use case definition [an artefact] that defines a use of a system by an actor, in the course of an OPOPOT business process or role. Use Case Diagram It is normally named as a goal in verbnoun form (e.g. assess claim). It is usually defined by its service contract (trigger event, inputs and outputs, preconditions and post conditions, and non-functional requirements) and process flow (main path and alternative or exception paths). The details of each process step (including any services or transactions invoked) may be documented separately from the use case. Use Case Definition / Specification Service Contract Trigger, I/O, pre & post conditions Process Main path Extension paths Non-functional requirements Copyright Limited 2008-2016
Data flow view Applications View TOGAF artefacts ArchiMate viewpoints Application Interaction matrix Application Cooperation Data flow view Application Communication diagram Application Cooperation Interface catalog Copyright Limited 2008-2016
Application Interaction matrix Copyright Limited 2008-2016
Application Communication Diagram to depict all models and mappings related to communication between applications in the metamodel entity. shows application components and interfaces between components. ABC Limited Retail Business Applications Manager Supplier ERP DW-BI CRM Money handling BACS Customer Salesman Interfaces may be associated with data entities. Applications may be associated with business services Communication should be logical and should only show intermediary technology where it is architecturally relevant. Copyright Limited 2008-2016
Application Communication & Security diagram: illustration Which applications and/or data stores are in which security domain? Which data flows pass between security domains? A variation of Application Communication diagram with security domains Data Flow diagram showing Security Domains ABC Limited Security domain 1 Security domain 2 Manager ERP DW-BI Supplier CRM Money handling BACS Customer Security domain 3 Salesman Copyright Limited 2008-2016
ArchiMate 3.0: Application Co-operation Viewpoint TOGAF Application communication diagram describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. typically used to create an overview of the application landscape of an organization. also used to express the (internal) cooperation or orchestration of services that together support the execution of a business process. Composed of Serves Could be info flow Copyright Limited 2008-2016
Interface catalog Data Flow (Application Communication) Diagram CRM 1b 1a Sales 2a 1c E.g. a UK gov. dept has 300 apps and 550 data flows Stock 3a 3c 3b Billing 4a 1d (cf. N2 model, or Node Connectivity diagram in FEAF) 3d 4b Business Intelligence Data Flow (Interface in TOGAF) Catalogue Data Flow id Source App Destination App Data content Trigger event 1a CRM Sales Sales order request New sales order 1b Sales CRM Sales order confirmation Order created in the Sales system 2a Sales Stock Requisition Subscribe/Publish timer Copyright Limited 2008-2016
Data store view Conceptual Data diagram (Business Data Model) Data Entity/Business Function matrix Application/Data matrix Logical Data diagram Data Entity/Data Component catalog Data Dissemination diagram Data Security diagram Data Lifecycle diagram See Information/Data Architecture for more detail. Copyright Limited 2008-2016
TOGAF: Two more applications architecture diagram types Application/Migration Diagram Identifies application migration from baseline to target application components. enables a more accurate estimation of migration costs used to identify temporary applications, staging areas, and the infrastructure required to support migration Software Distribution Diagram a composite of the Software Engineering diagram and the Application-User Location diagram. Depending on the circumstances, this diagram alone may be sufficient, or may not be needed. Copyright Limited 2008-2016
Beware the duplication between TOGAF diagrams Application and User Location Diagram shows the geographical distribution of applications, where applications are used by the end user; where the host application is executed and/or delivered in thin client scenarios; where applications are developed, tested, and released; etc. Application/Technology Matrix documents the mapping of business systems [i.e applications] to technology platform. Processing Diagram focuses on deployable units of code/configuration and how these are deployed onto the technology platform. Software Distribution Diagram shows how application software is structured and distributed across the estate shows how physical applications are distributed across physical technology and the location of that technology enables a clear view of how the software is hosted Environments and Locations Diagram depicts which locations host which applications what technologies and/or applications are at which locations Networked Computing/Hardware Diagram to document the mapping between logical applications and the technology components (e.g., server) that supports the application both in the development and production environments to show the as deployed logical view of logical application components in a distributed network computing environment Enable understanding of which application is deployed where in the distributed network computing environment. Copyright Limited 2008-2016
Application Communication diagram: MODAF style Copyright Limited 2008-2016
Methods at http://avancier.website Methods can be used on their own and/or to supplement any architecture framework that shares similar domains and entities ArchiMate Language Framework CSC s domains of change (POLDAT) BCS E&SA reference model Methods TOGAF The Open Group IBM s view EA EA as Strategy MIT Copyright Limited 2008-2016