Strategy & Architecture Framework. Modeling Language Alain De Preter - All rights reserved - Tous droits réservés

Size: px

Start display at page:

Randall Barrett
5 years ago
Views:

1 Strategy & Architecture Framework Modeling Language

2 Modeling Language Performers People Tools & Repositories Competitive Advantage perform Knowledge & control Process Methods Guidelines & Techniques TO-BE Capabilities use / produce communicate Business Context AS-IS Capabilities Content Deliverables Artefacts Building Blocks Meta data Time & Value Roadmap 2

3 Architecture Modeling Language The Modeling language and toolboxes are inspired by several standards and best practices including systems semantics, modeling languages and frameworks. They simplify and rationalizes the modeling experience by merging these standards into a single homogeneous set and by concentrating on what is needed for the work at hand. The resulting set of simplified and integrated modeling toolboxes features precise and unambiguous modeling elements and connectors. The language is implement using the Sparx Enterprise Architect Modeling tool platform. 3

4 One Single Modeling Language & Terminology A subset of the modeling language elements and connectors You can navigate and zoominto the metamodel details on-line 4

Sample Functional Application Landscape View EA Team site FA - Strategy to Portfolio (S2P) JIRA SDEdit FB - Enterprise Architecture FB - Demand Portfolio FB - IT Investment Portfolio Archi

5 Sample Functional Application Landscape View EA Team site FA - Strategy to Portfolio (S2P) JIRA SDEdit FB - Enterprise Architecture FB - Demand Portfolio FB - IT Investment Portfolio Archi Sparx Enterprise Architect FB - Policy OTRS V2 FB - Service Portfolio Control Desk Excel This requires a specification of the language and the motivation FB - Proposal for such viewpoint 5

6 Prescriptive language for Functional Application Landscape views Functional Block A Functional Block is a level 3 business function that belongs to some functional area. The granularity and scope of a Functional Block is defined by identifying some homogenous set of information that the Functional Block is mastering a group of activities that fulfill the purpose of the functional block, that belong to some processes of same nature and that produce and use the information mastered by that Functional Block A business function is a behavior element that groups behavior based on a chosen set of criteria e.g. required business resources and/or skills, competencies, knowledge, etc. Inspired by Archimate Application An application Is a self-contained unit of functionality as perceived by end-users Can be clearly mapped to some functional blocks Has its own specific set of application attribute values Is used by and billable to one or several Organizations Is owned by a single Organization Can be part of an Application Platform or an Application Group Encapsulates Applications Components and Application Interfaces Can exist at one or many specific points in time called "plateaus". Possible plateaus are AS-IS, TRANSITION and TO-BE. The name of an application component should preferably be a noun. A Realization relationship indicates which concrete entities ( how ) realize which abstract entities ( what ). The realization relationship is used in a business operational sense (e.g., a role realizes a swim-lane of activities), but also in an IT context (e.g., an application realizes a functional block). Inspired by UML & Archimate 6

questions When used as enterprise-wide viewpoint Which applications support which functional blocks?

7 Motivation for creating Functional Application Landscape views Functional Domain1 Functional Area1 Functional Block1 Functional Block2 Functional Area2 Functional Domain2 Application 1 Application 2 This answers the following questions When used as enterprise-wide viewpoint Which applications support which functional blocks? When used as project-specific viewpoint Which applications are/will automate the functional blocks inside the scope of this project? 7

8 Sample Application Landscape View Architecture Automation Sparx Enterprise Architect Architecture Modeling Sparx EA Fat Client Sparx Model Repository Web Site Sparx Keystore License Service Diagram Generation Sparx LabNaf AddIn Architecture Data Publication Sparx Web Pages File Storage Sparx Robots HTML Publication Robot Architecture Data Acquisiton Architecture Data Publication Robot Architecture Data Acquisition Robot Sparx Shared Repository Model Validation Post-conditonal Model Validation Repository Backup Generation Robot Model Validation Robot Sparx Shared Folder Pre-conditional Model Validation 8

9 Sample Application Deployment View Sparx Application Server ADS Sparx Model Repository Web Site Sparx Keystore License Service Sparx EA Fat Client Sparx Robots Sparx Shared Repository Sparx Web Pages File Storage Sparx Shared Folder PRD (HA) 5 users PRD (HA) 50 users Sparx Application Server (Server) Muizen DC Sparx Database Server Internet Information Services Windows Server SQL Server 9

10 Elements and connectors When presented to end users, use verbs instead of connector names when the direction of the connector is ambiguous!!! These pictures do *not* represent the toolboxes in the tool

11 Language Metamodel See on-line documentation

12 For further information about the language Detailed documentation and contact information are available here: 14

ArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology

ArchiMate 2.0. Structural Concepts Behavioral Concepts Informational Concepts. Business. Application. Technology ArchiMate Core Structural Concepts Behavioral Concepts Informational Concepts interaction Technology Application Layer Concept Description Notation Concept Description Notation Actor An organizational