CSPA within the Enterprise Architecture (part 1)

Transcription

1 CSPA within the Enterprise Architecture (part 1) Mauro Bruno THE CONTRACTOR IS ACTING UNDER A FRAMEWORK CONTRACT CONCLUDED WITH THE COMMISSION

2 Outline The problem statement EA main features EA frameworks Zachman framework TOGAF The Open Group Architecture Framework ESS Enterprise Architecture Reference Framework (ESS EARF)

3 The problem statement Many statistical organizations are facing common challenges Existing threats to statistical organisations are: Rigid processes and methods Inflexible ageing technology environments Emerging Threats include: The need to be able to quickly respond to emerging information needs Challenges (and opportunities) of increasing use of administrative data and the move to harness alternative sources of data (sensor, satellite etc)

4 The problem statement The underlying model for statistical production is sample survey based. Increasingly there is a need for organizations to make use of administrative or alternative source data to deliver efficiencies, reduce provider burden and make richer use of existing information sources. Statistical organizations have developed their own business processes and IT-systems for producing statistical products. Although the products and the processes conceptually are very similar, the individual solutions are not

5 The problem statement Technical solutions built for a very specific purpose: strong difficulty to share information with other adjacent applications in the statistical cycle limited ability to handle similar but slightly different processes and tasks. Accidental architecture Processes and solutions are not designed from a holistic view.

6 The problem statement How to face these problems? Many statistical organizations are modernizing and transforming their organizations using enterprise architecture to underpin their vision and change strategy. An Enterprise Architecture aims to create an environment which can change and support business goals. It shows what the business needs are, where the organization wants to be, and ensures that the IT strategy aligns with this. Enterprise architecture helps to remove silos

7 Enterprise Architecture: Main features

8 Definitions Architecture is the fundamental organisation of a system embodied in its components, their relationships to each other, and to the environment, and the principle guiding its design and evolution Stakeholder: an individual, team, or organisation (or classes thereof) with interests in, or concerns relative to, a system [ISO/IEC Systems and software engineering Architecture description]

9 Definitions Enterprise: any collection of organisations that has a common set of goals and/or a single bottom line Enterprise architecture: a coherent whole of principles, methods, and models that are used in the design and realisation of an enterprise s organisational structure, business processes, information systems, and infrastructure.

10 Main features of Enterprise Architecture Holistic view of an enterprise: Architectures often developed for individual domains Not optimized as a whole Communication Need to share common languages and models across domains Change management Ensures alignment with business objectives when environment and technology change

11 Communicating via EA Viewpoints: different views that stakeholder have on the architcture Architects: use architcture models, views, presentations to bridge the communication gap

12 Internal Drivers Business-IT alignment Strategic alignment model by Henderson and Venkatraman 1993 EA can be a valuable help in executing business or IT strategy

13 Internal Drivers Management instrument EA as a management instrument EA offers a holistic perspective of the current and future operations and on the actions that should be taken to achieve the company s goals

14 Internal Drivers Integration and standardisation Operating model of enterprises (Ross at al.2006)

15 External drivers Regulatory frameworks: transparency and compliance with laws Competitive market: higher quality, better timeto-market

16 Enterprise Architecture: Zachman Framework

17 Zachman Framework First and best known EA framework introduced in 1987 Products abstractions Roles in design processes Design artifact

18 Zachman Framework Rules 1. Columns have no order 2. Each column has a simple basic model 3. Basic model of each column is unique 4. Each row represents a distinct view 5. Each cell is unique 6. Combining the cells in one row forms a complete description from that view

19 Zachman Framework Executive perspective (Scope contents): The first architectural sketch is a bubble chart, which depicts in gross terms the size, shape, partial relationships, and basic purpose of the final structure. It corresponds to an executive summary for a planner or investor who wants an overview or estimate of the scope of the system, what it would cost, and how it would relate to the general environment in which it will operate.

20 Zachman Framework Business Management Perspective (Business Concepts): Next are the architect's drawings that depict the final building from the perspective of the owner, who will have to live with it in the daily routines of business. They correspond to the enterprise (business) models, which constitute the designs of the business and show the business entities and processes and how they relate.

21 Zachman Framework Architect Perspective (System Logic): The architect's plans are the translation of the drawings into detail requirements representations from the designer's perspective. They correspond to the system model designed by a systems analyst who must determine the data elements, logical process flows, and functions that represent business entities and processes.

22 Zachman Framework Engineer Perspective (Technology Physics): The contractor must redraw the architect's plans to represent the builder's perspective, with sufficient detail to understand the constraints of tools, technology, and materials. The builder's plans correspond to the technology models, which must adapt the information systems model to the details of the programming languages, input/output (I/O) devices, or other required supporting technology.

23 Zachman Framework Technician Perspective (Tool Components): Subcontractors work from shop plans that specify the details of parts or subsections. These correspond to the detailed specifications that are given to programmers who code individual modules without being concerned with the overall context or structure of the system.

24 Zachman Framework: Pros and Cons Pros: Easy to understand Addresses enterprise as a whole Independent of tools and methodologies Cons: Large number of cells Relations between cells not well specified

25 Enterprise Architecture: TOGAF Framework

26 TOGAF: Generalities The Open Group Architecture Framework (TOGAF) is a framework for enterprise architecture which provides a comprehensive approach for designing, planning, implementing, and governing an enterprise architecture. TOGAF is a registered trademark of The Open Group in the United States and other countries 26

27 TOGAF: Layers Divides enterprise architecture into four layers: 1. Business architecture - Describes the processes the business uses to meet its goals 2. Application architecture - Describes how specific applications are designed and how they interact with each other 3. Data architecture - Describes how the enterprise datastores are organized and accessed 4. Technical architecture - Describes the hardware and software infrastructure that supports applications and their interactions 27

28 TOGAF: Components TOGAF has 4 main components: Architecture Capability Framework Architecture Development Method (ADM) Architecture Content Framework Enterprise Continuum Only ADM will be briefly described

29 TOGAF: Architecture Development Method It is the core of TOGAF Provides architects a way of working Stepwise cyclic approach for the development of the overall EA

30 TOGAF: Architecture Development Method At each iteration a new decision must be taken as to: the breadth of coverage of the enterprise to be defined the level of detail to be defined the extent of the time horizon aimed at the architectural assets to be leveraged in the organisation's enterprise;

31 TOGAF Architectures (Contextualized to Official Statistics)

32 ESS Enterprise Architecture Reference Framework (ESS EARF)

33 ESS EARF ESS EARF denotes a set of documents containing a number of key artefacts, which can be used at various stages in projects as well as in the overall governance of the realization of Vision 2020

34 ESS EARF The ESS EARF consists of a set of modules: The ESS Business Capabilities model The ESS EA Building Blocks Principles for the ESS EARF The Statistical Production Reference Architecture (SPRA)

35 The ESS Business Capabilities model The Business Capabilities model summarizes the key capabilities required for producing official statistics. It provides a framework to view which capabilities are already sufficiently present in the ESS versus those on which development effort is needed to rely. It can be used as a mapping tool to e.g. understand the scope of projects in terms of the capabilities it is trying to develop

36 The ESS EA Building Blocks The Building Blocks are the major (potentially reusable) components that can be combined to deliver the information systems needed in ESS. Examples include: Metadata Management, Process Orchestrator, Primary Data Storage.

37 Principles for the ESS EARF These are principles that give guidance to the decisions in projects involved in realizing the Vision Examples of principles (headline) are: Projects deliver re-usable capabilities; Existing standards are used where applicable; Projects are designed to continuously deliver outputs & outcomes.

38 The Statistical Production Reference Architecture (SPRA) This element is a subset of the enterprise architecture which breaks it down further for individual process steps, using the GSBPM model as a basis. It identifies the major services that the architecture needs to provide to support the phases and activities and specifies in which building block they should be realized. Examples of services include: Create Sample, Validation, Aggregation

39 ESS EARF architecture CSPA

40 CSPA within EARF ESS EARF artefacts build on the conceptual and global frameworks for Officials Statistics and aim to fill the gap between concepts and implementation ESS EARF refers to CSPA for statistical services identification, specification and design