Initiative for an open method   +33 (0)  ? Reference Version Protection A classification of skills based on the enterprise reality SLB-29 The Interdisciplinary Ensemble of Disciplines (TIED) « Theory without practice is useless; practice without theory is blind. » Immanuel Kant

« A classification of skills… » /28 SLB-29 Presentation objective  Objective  Topics  Enterprise Architecture, Business Architecture…  Enterprise transformation  Methodology Specify and link together the disciplines involved in the enterprise transformation Document protection 2

« A classification of skills… » /28 SLB-29 Content 1.The available definitions of the disciplines 2.A comprehensive approach to the enterprise 3.Inference of the disciplines and their relations 3

« A classification of skills… » /28 The available definitions  Definitions that come from various sources  TOGAF  BABoK  ISO  … SLB

« A classification of skills… » /28 TOGAF Definitions  Architecture  “A formal description of a system, or a detailed plan of the system at component level, to guide its implementation”  (source: ISO/IEC 42010:2007).  “The structure of components, their inter-relationships, and the principles and guidelines governing their design and evolution over time.”  Business Architecture  “The business strategy, governance, organization, and key business processes and information, as well as the interaction between these concepts.” SLB-295

« A classification of skills… » /28 Enterprise Architecture in TOGAF  What Kind of Architecture Does TOGAF Deal With?  “There are four architecture domains that are commonly accepted as subsets of an overall enterprise architecture, all of which TOGAF is designed to support:  The Business Architecture defines the business strategy, governance, organization, and key business processes.  The Data Architecture describes the structure of an organization's logical and physical data assets and data management resources.  The Application Architecture provides a blueprint for the individual application systems to be deployed, their interactions, and their relationships to the core business processes of the organization.  The Technology Architecture describes the logical software and hardware capabilities that are required to support the deployment of business, data, and application services. This includes IT infrastructure, middleware, networks, communications, processing, standards, etc. “  Extract from TOGAF v. 9 SLB-296

« A classification of skills… » /28 BABoK Definitions  Business Analysis  “Business analysis is the set of tasks and techniques used to work as a liaison among stakeholders in order to understand the structure, policies and operations of an organization, and recommend solutions that enable the organization to achieve its goals.”  Business Architecture  “A subset of the enterprise architecture that defines an organization’s current and future state, including its strategy, its goals and objectives, the internal environment through a process or functional view, the external environment in which the business operates, and the stakeholders affected by the organization’s activities.”  Enterprise Architecture  “Enterprise architecture is a description of an organization’s business processes, IT software and hardware, people, operations and projects, and the relationships between them.” SLB-297

« A classification of skills… » /28 Discussion  Flaws of the definitions  No attempt to link the concepts together  The meaning of a term stems from its position inside a semantic network…  Mainly definition by content  “A set of…”  Typical of a bottom-up approach  Consequences of insufficient definitions  Confusion  Lack of coordination between disciplines  Criteria 1.Aspects of the Enterprise  Business (knowledge, activity…) versus support (logistics, IT…) 2.Reach of the endeavor  Local (application, service, department, function…) vs overall (entire system) 3.Time frame  Short-, medium-, long terms SLB-298

« A classification of skills… » /28 A comprehensive approach to the enterprise  If enterprises are deemed complex systems, how should we address them?  What should be represented?  How should we deal with the amount of information to be collected and the decisions to be made?  Notion and value of a methodological framework  “Separation of concerns” principle  Mindset related to every framework SLB

« A classification of skills… » /28 Pragmatic aspect Business: the “right” description  Approach by activities  Classical approach  Flawed with local variation  Functional & hierarchical breakdown structure  Semantic modeling  Additional approach  Move to genericity  New solution to cope with complexity Actors & organizational entities Process & use-cases Business objects, real objects (Information+Transformation+Action) Semantic aspect Refers to SLB-2910

« A classification of skills… » /28 Software: the optimal structure Pragmatic aspect Actors & organizational entities Process & use-cases Business objects, real objects (Information+Transformation+Action) Semantic aspect  Determine the software structure from the business description  Applying MDA standard  Independently from technical choices  Technical Target free  Long term Logical aspect Derives Logical services & aggregates (logical machines…) Core StratumOrganization StratumInteraction Stratum SLB-2911

« A classification of skills… » /28 FD Caricature of an architecture based upon functional approach Logical blocks take charge of functional domains which structure the pragmatic model. Important dependencies or redundancies stem from this, as the same business objects are used inside many functional domains. BO FD OD Outlined logical architecture according to Praxeme method Several logical blocks match with the object domains from the semantic model. Dependencies obey topological constraints Between strata (“Business Core”, “Organization”, “Interaction”) Coupling reduced, No dependency between FD, unless special cases, etc. Logical architecture: the change FD: functional domain BO: business object OD: object domain SLB-2912

« A classification of skills… » /28 The Enterprise System Topology Logical aspect Semantic aspect Pragmatic aspect Geographic aspect Hardware Technical aspect Software Physical aspect Political aspect SLB-2913

« A classification of skills… » /28 Logical Aspect Semantic Aspect Pragmatic Aspect Geographic Aspect Hardware Technical Aspect Software Physical Aspect Dependencies between aspects derives from refers to knowledge activity kernel source periphery source translates distributes organization location equips logistics geography applies specification implementation result guideline hosts projection configuration determination possibility considers constrains fills space content * * * * SLB-29

« A classification of skills… » /28 Inference of the disciplines  Given the content framework…  Which guides our approach to the enterprise  …how can we define the disciplines needed?  In accordance with the natural structure of the Enterprise System SLB

« A classification of skills… » /28 “Architecture”  A metaphoric use of the term  Business Architecture, Enterprise Architecture, IT Architecture, etc.  Usual meaning  “The art and study of designing buildings”  “The design or style of a building or buildings”  Source: Oxford Dictionary  In our context  A discipline that deals with the enterprise or an aspect of the enterprise as a whole and establishes the high-level decisions needed  Architecture is about the main decisions that structure and transform the system  Preliminary questions  Which aspects? 16SLB-29

« A classification of skills… » /28 “xxx Architecture”  “Enterprise Architecture”  “The discipline of architecting the enterprise”  This definition applies to the object of the enterprise  “Business Architecture”  Part of the Enterprise Architecture that focuses on the business aspects  According to the Enterprise System Topology, there are three “business” aspects that must be isolated for a proper description: semantic (core business knowledge), pragmatic (action), geographic (location)  See slide 21  “IT Architecture”  … 17SLB-29

« A classification of skills… » /28 Another approach to the concept  The Enterprise Transformation Manifesto  “The golden principles for improving enterprises while respecting society's fundamental values and interests”  Meant for decision-makers  Enterprise Architecture Enterprise Architecture is the discipline that analyzes the strategy and determines the main decisions for transforming the Enterprise System. SLB-2918

« A classification of skills… » /28 Overview: 7 chapters SLB-2919

« A classification of skills… » /28 Enterprise transformation  Disciplines involved Operation Transformation 20SLB-29

« A classification of skills… » /28 Clarifying responsibilities Logical Architect Organization designer Technical Architect Strategist Business view IT view Business Architect Business Analyst 21SLB-29

« A classification of skills… » /28 Roles related to business description  Business Architect  The one who makes the overall decision and is the guardian of the long-term vision  Business Analyst  Involved in operations (projects), brings the details  Business Designer  The mandate for creating new business practices must be explicit  Need to distinguish both roles? (analysis versus design)  Business Expert  They have the knowledge, not necessarily the skills for expressing it in the right way  Modeler  They master the techniques of representation, not necessarily the content (the knowledge)  Can be specialized (by aspects…) 22SLB-29

« A classification of skills… » /28 Possible negotiation Contribution Exclusive responsibility + ownership Exclusive responsibility + ownership Business Architecture & Analysis  As a result, Praxeme situates the disciplines of BAs against the Enterprise System Topology SLB-2923

« A classification of skills… » /28 Recap  Business Architecture  Overall view  Decision making at the system level  Business Analysis  Detailed view  Expressing the business knowledge, describing the business practices  Business Design  Praxeme encourages design in matters of business  Organizational innovation  Innovation in terms of business concepts SLB-2924

« A classification of skills… » /28 Responsibilities of business architecture/analysis/modeling  Take into account the general directives (strategy…)  Understand the business: practices, needs, opportunities  Anticipate the changes  Describe the business in such a way that:  The business knowledge is captured and protected  The description can be easily enacted by other actors (e.g., IT designers) Upstream Downstream 25SLB-29

« A classification of skills… » /28 Relation between BA & BA  Business Architecture  Establish the frame  In line with the corporate strategy  Administrate the repositories  Promote the best practices  Select and link the investments in accordance with priorities  Business Analysis  Assess the overall decisions  Coping with constraints at grassroots level  Fill the frame and repositories  Project after project  Benefit from synchronization between investments SLB-2926

« A classification of skills… » /28 Two levels of action Enterprise System Need Solution Projects Strategic analysis Visioning Overall design Consolidation Monitoring SLB-2927

« A classification of skills… » /28 Conclusion  Towards the right definitions of disciplines  The Enterprise System is the only valid starting point  Better than the current practices  Need for a comprehensive methodology  Enterprise Architecture ought to live up to its more ambitious definition  The indispensable link between strategy and transformation  To stay informed  The Praxeme Institute web site   List for major announcements  SLB-2928 T he I nterdisciplinary E nsemble of D isciplines