The Quality Management Metamodel in the Enterprise Architecture

Transcription

1 Jerzy Roszkowski Management Systems Consulting, Poznańska 28/ Street, Łódź, Poland Agata Roszkowska Baden-Württemberg Cooperative State University Stuttgart, Faculty of Technology, Jägerstraße 56, 7074 Stuttgart, Germany 9 th International Conference on Perspectives in Business Informatics Research The Management Metamodel in the Enterprise Architecture The paper presents the methodology for determining, management, simulation and optimization of the quality of an enterprise architecture based on defined by the author of two metamodels: classes and processes for quality management of this architecture. The second of them (the process metamodel) of quality management developed in BPMN has undergone simulation and optimization using ARIS Business Process Simulator. The results of this simulation and optimization are presented in the article. The presented research method developed by the author, and the results are related to and are a creative extension of the following ISO standards: ISO/IEC [], ISO/IEC 2207 [2], ISO / IEC 4200 [3] and the well-known methodologies: A Framework for Information Systems Architecture. - Zachman, J. A., and TOGAF : The Open Group Architecture Framework

2 Actually used standards CMMI (Capability Maturity Model Integration) is a process improvement approach whose goal is to help organizations improve their performance TOGAF 9 The Open Group Architecture Framework for Enterprise Architecture framework, which provides for a comprehensive approach to the design, planning, implementation and management of enterprise information architecture. The architecture is typically modeled at four levels (domains): Business Processes, Applications, Data, Technology. Group of The Open Group TOGAF specification available free of charge to organizations for their personal. ISO Standards Software Engineering - a Metamodel for Development Methodologies - ISO / IEC Systems and Software Engineering - Software Life Cycle Processes - ISO / IEC 2207 Systems and software engineering - Architecture description - the ISO / IEC 4200 Sector Standards 2

3 CMMI Fixed representation Level5 Optimized The focus on process improvement. Level 4 Managed quantitatively The process is measured and controlled. Level 3 Defined At the level of organisation was implemented standardizing normalized processes. Level 2 Managed Achieving the objectives in an area is based on a pre-determined plan Level Initial Process unpredictable, poorly controlled. 3

4 Achitecture Development Method for TOGAF. Source: The TOGAF is Architecture Development Method (ADM) used for the determination of business needs and the construction of such an architecture that achieves these needs. 4

5 What is quality? What is metamodel? The quality concept in for the development process of the enterprise architecture is understood as a set of measurable and immeasurable characteristics of the product required by the customer (customer, product). Product quality is monitored at all stages of its manufacture, especially in the so-called Checkpoints. Metamodel (ISO standard ISO / IEC (A metamodel for Development Methodologies ) According to a metamodel is the specification of the concepts, relationships and rules that are used to define a methodology. Any metamodel consists from elements. An element is a simple component of a methodology. Usually, methodology elements include the specification of what tasks, activities, techniques, models, documents, languages and/or notations can or must be used when applying the methodology. Methodology elements are related to each other, comprising a network of abstract concepts 5

6 System Architecture Project Metamodel class meta-model-new JR Legend Project Model All dependency connections should be monitored by Traceability Matrix Step 0 - based on SIWZ Step - Projekt funkcjonalny Step 2 -Implementation Step 3 optional Other New Element -JR Connection State connection + Goal + Objectives [..n] :: notes Organizes the entire project repository and project Master Data «enumeration» StatusEnum Proposed Accepted Implemented Verified Obsoleded Actor + RWE Consultant + Tasks [..n] :: 2 UC Diagram View..*..* Extend/Uses Use Case + Level + Post-Condition..* + Pre-Condition..* + Steps [..n] :: Sequence Diagram :: «verify» Test Case :: «derive» State Connection Activ ity Connection 3 UML Function View.. System Activity - Level in hierarchy: int :: notes based on SIWZ «satisfy» Required Service Activ ity Diagram - Level in hierarchy: int ::..* «verify» ::..* 5 Component View Data Object :: notes based on SIWZ Component Function Hierarchy Diagram :: «use» Connection Activ ity Data Object Flow «satisfy» Provided Service :: 0 Requirement Diagram View (SIWZ) High Level Requirements + ToBeImplementedBy + Type :: notes based on SIWZ «derive» Non Functional Requirement «derive» + Source :: «Deployed by»..* «use» +target «implement» +source Entity + Attributes [..n] :: Connection Entity Connection ::Connection + Direction + Multplicity [..2] + Stereotype + Type :: 4 Class View 6 Deployment Diagram View +target Connection Deliverale Connection Deliv erable + Version :: notes Software Component Artifact - Documentation - Policy etc Hardware Other +source..* ::Connection + Direction + Multplicity [..2] + Stereotype + Type :: Business Class + Attributes [..n] «mapping» + Class type: char + Operations() : void Class Connection 6

7 Metamodel of classes for the Management class Manager View Organization Structure Submodel Generic Enterprise Architecture Submodel AD Link Stakeholder..* needs..* View Point 0.. Architecture Model AD Element AD Attribute 0, 2..* creates Analyst specific rules general rules Project Manager Manager controls manages controls defines Management Process Model manages Architecture Assessment Model stores Management Process Model QM Related Models Correspondence conitains..* organizes QM check organizes Report Requirement Pattern..* Product Pattern supervizes Products Submodel..* Steering Committee reads creates Report is based on Product 7

8 BPMN proces model Final metamodel of processes for the topic "Architecture quality management vor the optimization ) 8

9 Analyst Create Final Report CRUD AD Elements Define Corespondence - AD Define Process & Define Requirements EA Process Iteration Acceptance Iteration Management Iteration ready for Iteration Start Message Pass? PM Project Finish Project Finish? Project Start QM Validation Steering Commetee The completness and correspondence of models RELATIONSHIP MATRIX PROCESSES VERSUS CLASEES AD Attribute X X AD Element X X AD Link X X Analyst X X Architecture Model Architecture Assesment Model X X Correspondence X X High Level Report X X Management Proces Model X Project Manager X X X Management Process Model X X Manager X X X X X X X X X Report X X Report Pattern X X Requirement Pattern X X Stakeholder Steering Committee X X X X X X X X View Point 9

10 The required input data for simulation: Graphical model for BPMN business process Organizational units (see diagram allocation functions) Possible variants of the process flow (a set of activities performed, the combined symbols of the movement control process) Relational operators (types of operators, XOR, AND, OR) o o o Business Process Parameters: average frequency of the input event / time period relational operators (the probability of each output) times of the various stages of the process (waiting time static execution time of an elementary process) The degree of involvement of human resources (number of participants in the process / number of persons employed in the organizational unit responsible for the implementation phase of the process) 0

11 Steps of the process simulation execution Commissioned preparation data simulation Data mining Preparation data simulation Process simulation prepared Conducting simulation Simulation performed Automatic generate diagram activity Result of simulation Proces Mining bottleneck" associated with the allocation of resources - resources are too small, or during the calling of the process instance are busy handling another process, and therefore can not be used until the end of this process as the result in the simulation model are created process "bottleneck" associated with "bottleneck" instances associated called "dynamically with the processing waiting" for downtime (which means to stop the time (execution) the execution process until the exist release if possibility of resources. to increase activation The the optimization resources process are solution instance) already is exhausted to - increase and the only resulting resources solution in too in is order to long reduce total to have the duration execution disappeared of the time simulation. if processes the whole The simulation "waiting solution dynamically. process to this is to be completed optimization within in a specified order to less period. downtime The result is in for the process simulation simulation model process has been are created instances completed called within "statically the waiting" described to execute period. until the end of the previous instance of the process. Optimization solution is to shorten the implementation time of such processes, in order to have disappeared processes "statically waiting." Model non-optimized final Analysis results and choice of strategy optimization Bottleneck resources assigned Bottleneck processing times Processes waiting dynamically Processes waiting statically Optimized model Bottleneck downtime Stopped activation process End

12 Parameters of the running process (example) 2

13 Sector Standards (Example BI) () Requirement Definition reference model FK. Client Representative Client Acceptance Connector to the process D.0 Products cataloque and PSD F.3. Contract with client was signed Study of products cataloque and PSD Cataloque of products and DSP were worked out Project Phase Leader Manager Project Manager Change in products was introduced F.5 Connector from the process Change management Product cataloque and DNP was accepted F.3.2 Product registration in project database Administrator of a project repository Repository of project Requirements change was introduced F.3.4 Analysis of change Change was accepted Cataloque of products and PSD was registered Requirements of quality for products F.3.3 Study of quality requirements for the products Manager requirements were worked out Control F.3-B Connector to the process 3

14 Sector Standards (Example BI) (2) Connector from the process Construction Control reference model Notification of product to control D.03 Product M.0 F.6 F.3.2 Product was created Product registration in project database Product was registered for quality control Project Phase Leader Repository of project Requirements of quality for products Template of product Manager F.3.5 control D.04 Repository of project Product D.03 F.3.5. requirements were fulfilled Product Status Change Product has internal acceptation requirements were not fulfilled Preparation of a list of a remarks and/or quality control protocol F.3.6 Change concerned rejected product was registered Manager Product with remarks Control minutes D.05 D.06 Change management Connector to the process Notitication of the Project Leader concerning of the completion the quality control process and deadlines for the prodict improvement F.3.7 M.02 Remarks registration in project database control was finished Manager Repository of project F.5 F.6 Construction Connector to the process 4

15 Sector Standards (Example BI) Devel.(3) Change supports management tools Change management Connector from the process Development reference process model Change concerned rejected product was registered F.5 Excel CASE Tools supports supports Change request was serviced F.6. DM project repository Data Mart designer performs Study of Data Mart technical project DM technical project D. F.3-B Connector from the process Control Rule operator Change concerns <EITHER > DM <OR> UNIVERSUM/RAP <OR> ETL <OR> IMPLEMENTATION Analytical reporting tools Universum Designer Reports Designer Product DM was finished supports F.6.2 Study of universum and reports technical project performs Product Universum and raports was finished Universum and raports repository Technical Project of "Universum" and reports Dictionaries D.2 D.3 Control Connector to the process F.3-B Repository of project ETL design tools CASE Tools supports Study of ETL technical design F.6.3 ETL project Repository of ETL project D4 D. ETL Designer performs Product ETL was finished DM technical project F.6.4 Reports designer performs Implementation Implementation package DB Programmer performs Implementation was finished supports Data Base Platform Testing Connector to the process F.4 5

16 Some results () Number of the products instancess/year 0 INPUT DATA BEFORE AND AFTER OPTIMIZATION Number of the process Name of the process instantion Processing time for the optimization (dddd:hhhh:mmm:se c) Processing time after the optimization (dddd:hhhh:mmm:se c) The share (%) of time in the total time Define Requirements 000:00:00: :00:00:00 4,20% 2 Define and product Patterns 3 New Product Activation 0000:05:00:00 000:00:00:00 2,40% (Preparation time- organizing the team and tools) 4 Iteration Management 0002:00:00:00 000:00:00:00 2,40% 5 Define Correspondence AD Model to Product Report Patterns 004:00:00: :00:00:00 6,60% 0005:00:00: :00:00:00,80% 6 Create AD Elements 000:00:00:00 005:00:00:00 35,50% 7 Validation 000:00:00: :00:00:00 4,20% 8 Product and Iteration Acceptance 0005:00:00:00 000:00:00:00 2,40% 9 Create Final Report 000:00:00: :05:00:00 0,50% TOTAL 0057:05:00: :05:00:00 00,00% 6

17 Some statistical results (2) 7

18 Conclusions CMMI and TOGAF are the frameworks in the called level of so called good practices Clarification of them should rely on their transformation into ISO standards. This requires the construction and optimization Metamodefls for each stage of ADM (for TOGAF) Therefore, should be introduced in the Enterprise Architecture the following architectural principles: Principle : " For each stage of ADM should be developed and optimized the metamodel describing each of this stage " Principle 2: "Reference Models in the appropriate businnes sectors are architectural guidelines, for Principle which should be compatible with the corresponding ADM metamodels (are their refinement (specialization) in the relevant sector). 8