The Quality Management Metamodel in the Enterprise … · · 2014-07-30(C) Jerzy Roszkowski 2...

Jerzy Roszkowski Management Systems Consulting, Poznańska 28/1 Street, 93-234 Łódź , Poland

Agata Roszkowska Baden-Württemberg Cooperative State University Stuttgart, Faculty of Technology,

Jägerstraße 56, 70174 Stuttgart, Germany

The Quality Management

Metamodel in the Enterprise Architecture

9th International Conference on Perspectives in Business Informatics Research

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 24744 [1],

ISO/IEC 12207 [2], ISO / IEC 42010 [3] and the well-known methodologies:

”A Framework for Information Systems Architecture”. - Zachman, J. A., and

TOGAF :“The Open Group Architecture Framework”

(C) Jerzy Roszkowski 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

24744

Systems and Software Engineering - Software Life Cycle Processes - ISO / IEC 12207

Systems and software engineering - Architecture description - the ISO / IEC 42010

Sector Standards

http://en.wikipedia.org/wiki/Process_improvement


CMMI – Fixed representation

Level1

Initial

Level 2

Managed

Level 3

Defined

Level 4

Managed

quantitatively

Level5

Optimized

Process unpredictable, poorly

controlled.

Achieving the objectives in an area is

based on a pre-determined plan

At the level of organisation was

implemented standardizing

normalized processes.

The process is measured and

controlled.

The focus on

process improvement.


Achitecture Development Method for

TOGAF. Source: http://www.opengroup.org/sib.htm

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.

http://www.opengroup.org/sib.htm








What is quality ?

What is metamodel ?

Quality 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 24744 (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


System Architecture Project Metamodel

class meta-model-NEW JR

5 Component View

0 Requirement Diagram View (SIWZ)2 UC Diagram View

6 Deployment Diagram View

4 Class View3 UML Function View

Base Element

Project Model

+ Goal

+ Objectives [1..n]

::Base Element

+ Description

+ Name

+ Status: StatusEnum

notes

Organizes the entire project

repository and project Master

Data

Base Element

System Activ ity

- Level in hierarchy: int

::Base Element

+ Description

+ Name


notes

based on SIWZ

Base Element

High Lev el Requirements

+ ToBeImplementedBy

+ Type

::Base Element

+ Description

+ Name


notes

based on SIWZ

Base Element

Use Case

+ Level

+ Post-Condition

+ Pre-Condition

+ Steps [1..n]

::Base Element

+ Description

+ Name


Base Element

Actor

+ RWE Consultant

+ Tasks [1..n]

::Base Element

+ Description

+ Name


Base Element

Test Case

::Base Element

+ Description

+ Name


Base Element

Non Functional

Requirement

+ Source

::Base Element

+ Description

+ Name


Base Element

Entity

+ Attributes [1..n]

::Base Element

+ Description

+ Name


Connection

Entity Connection

::Connection

+ Direction

+ Multplicity [1..2]

+ Stereotype

+ Type

::Base Element

+ Description

+ Name


Base Element

Deliv erable

+ Version

::Base Element

+ Description

+ Name


notes

Software Component

Artifact - Documentation -

Policy etc

Hardware

Other

Connection

Deliv erale Connection

::Connection

+ Direction

+ Multplicity [1..2]

+ Stereotype

+ Type

::Base Element

+ Description

+ Name


«enumeration»

StatusEnum

Proposed

Accepted

Implemented

Verified

Obsoleded

All dependency

connections should be

monitored by

Traceability Matrix

Base Element

Data Object

::Base Element

+ Description

+ Name


notes

based on SIWZ

Step 0 - based on SIWZ

Step 1 - Projekt funkcjonalny

Step 2 -Implementation

Step 3 optional

Other

New Element -JR

Legend

Base Element

Component

::Base Element

+ Description

+ Name


Base Element

Prov ided Serv ice

::Base Element

+ Description

+ Name


Base Element

Required Serv ice

::Base Element

+ Description

+ Name


Base Element

Sequence Diagram

::Base Element

+ Description

+ Name


Base Element

Activ ity Diagram

- Level in hierarchy: int

::Base Element

+ Description

+ Name


Base Element

Function Hierarchy

Diagram

Connection

Activ ity

Connection Connection

Activ ity Data Object

Flow

Base Element

Business Class

+ Attributes [1..n]

+ Class type: char

+ Operations() : void

Base Element

State

Connection

State connection

Base Element

Class Connection

1..*

1

+source

0..*

+target

0..*

«derive» +source

0..*

+target

0..*«derive»

«derive»

0..*

1

1..*

1

1..*

1

«use»

1..* 1

«verify»

«verify»

1..*

1

1..

1

1

0..*

0..*0..*

«implement»

0..* «mapping» 0..*

0..* 0..*

«Deployed by»

0..*

1

1..*

1

1..*

1..*

«satisfy»

«use»

«satisfy»

1

Extend/Uses

0..*0..*

0..*


Metamodel of classes for the Quality Management

class Quality Manager View

Stakeholder Architecture Model

Correspondence

Quality

Requirement

Pattern

AD Element

Management

Process

Model

View Point

Quality

Manager

AD Link

Generic Enterprise Architecture Submodel

QM Related Models

Quality

Management

Process

Model

Product

AD

Attribute

Steering

Committee

Project

Manager

Architecture

Quality

Assessment

Model

Quality Report

Product Pattern

Quality Products Submodel

Analyst

Organization Structure

Submodel

0..*

0..*

0..*1

0..*

1

0..*0..*1..*

needs

1..*

0..*

organizes QM check

1..*

0..1

specific rules

0, 2..*

0..*

0..1

supervizes

creates

controls

defines

controls

manages

manages

organizes Report

0..*

general rules

0..1

reads

1..*

stores

1

is based

on

1..*

conitains

1

creates


BPMN proces model

Final metamodel of processes for the topic "Architecture quality

management” vor the optimization )


The completness and correspondence of

models

Ana

lyst

Crea

te F

inal

Rep

ort

CRU

D A

D E

lem

ents

Def

ine

Core

spon

denc

e - A

D

Def

ine

Qua

lity

Proc

ess

&

Def

ine

Qua

lity

Requ

irem

ents

EA P

roce

ss

Iter

atio

n A

ccep

tanc

e

Iter

atio

n M

anag

emen

t

Iter

atio

n re

ady

for Q

ualit

y

Iter

atio

n St

art

Mes

sage

1

Pass

?

PM Proj

ect F

inis

h

Proj

ect F

inis

h?

Proj

ect S

tart

QM

Qua

lity

Val

idat

ion

Stee

ring

Com

met

ee

AD Attribute X X

AD Element X X

AD Link X X

Analyst X X

Architecture Model

Architecture Quality Assesment Model X X

Correspondence X X

High Level Quality Report X X

Management Proces Model X

Project Manager X X X

Quality Management Process Model X X

Quality Manager X X X X X X X X X

Quality Report X X

Quality Report Pattern X X

Quality Requirement Pattern X X

Stakeholder

Steering Committee X X X X X X X X

View Point

RELATIONSHIP

MATRIX

PROCESSES

VERSUS CLASEES


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)

Business Process Parameters:

o average frequency of the input event / time period

o relational operators (the probability of each output)

o 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)


Steps of the process simulation execution Commissioned

preparationdata

simulation

Preparation

datasimulation

Automaticgenerate

diagram

activity

Datamining

ProcesMining

Process

simulationprepared

Conductingsimulation

Analysis resultsand choiceof strategy

optimization

Simulation

performed

Result of

simulation

Model non-optimized

final

End

Optimizedmodel

Bottleneck

resourcesassigned

Processeswaiting

dynamically

Bottleneckprocessing

times

Processeswaiting

statically

Bottleneckdowntime

Stoppedactivation

process

"bottleneck" associated with

downtime (which means to stop the

activation process instance) -

resulting in too long total duration of the

simulation. The solution to this is

optimization in order to less downtime

for process simulation has been

completed within the described period.

”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

instances called "dynamically waiting" for

the execution until the release of resources.

The optimization solution is to increase

resources in order to have disappeared

processes "waiting dynamically”.

"bottleneck" associated with the processing

time (execution) process – exist if possibility to

increase the resources are already exhausted and

the only solution is to reduce the execution

time if the whole simulation process is to be

completed within a specified period. The result

is in the simulation model process are created

instances called "statically waiting" to execute

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."


Parameters of the running process (example)


Sector Standards (Example BI)–Quality(1)

F.3-B

QualityControl

Contract withclient

was signed

Study ofproductscataloqueand PSD

F.3.1

F.5

Changemanagement

Change in productswas

introduced

Requirementschange

was introduced

Cataloque of productsand DSP were

worked out

F.3.3

Studyof quality

requirementsfor the products

D.01

Productscataloque and

PSD

Productregistrationin projectdatabase

F.3.2

Connector fromthe process

Repositoryof project

Cataloque ofproductsand PSD

was registered

FK.1

ClientAcceptance

Product cataloqueand DNP was

acceptedAdministratorof a projectrepository

QualityManager

ProjectManager

ProjectPhaseLeader

Requirementsof quality

for products

QualityManager

Qualityrequirementswere worked

out

Connectorto the process

Analysis ofchange

F.3.4

Change wasaccepted

ClientRepresentative


Quality Requirement Definition reference model


Sector Standards (Example BI)–Quality(2)

Product wasregisteredfor quality

control

Qualitycontrol

F.3.5

Notitication of theProject Leader

concerning of thecompletion the qualitycontrol process and

deadlines for the prodictimprovement

M.02

Product wascreated


Preparation of alist of a remarksand/or quality

control protocol

F.3.6

D.05

Productwith remarks

D.06

Controlminutes

F.3.5.1

ProductStatus

Change

Product hasinternal

acceptation

Qualityrequirements

werefulfilled

Qualityrequirements

were notfulfilled


D.04

Templateof product

D.03

Product

F.6

Construction


D.03

Product

F.6

Construction

Productregistrationin projectdatabase

F.3.2



Remarksregistrationin projectdatabase

F.3.7

Change concernedrejected productwas registered

Quality controlwas finished

Requirementsof quality

for products

QualityManager

QualityManager

ProjectPhaseLeader

Notificationof productto control

M.01

QualityManager

F.5

Changemanagement


Quality

Control

reference

model


Sector Standards (Example BI)– Devel.(3)

F.5

Changemanagement


Repository ofETL project

Universumand raportsrepository

ReportsDesigner

F.6.3

Study ofETL technical

design

Product DMwas finished

ProductUniversumand raportswas finished

Analyticalreporting

tools

CASETools

UniversumDesigner

CASETools


Changemanagement

tools

supports

F.6.1

Study ofData Mart

technical project D.11

DMtechnicalproject

Data Martdesigner

performs

F.6.2

Study ofuniversumand reports

technical project

F.3-B

QualityControl


F.3-B

QualityControl

Change concernedrejected productwas registered

Changerequest

was serviced


supports

supports

supports

Ruleoperator

Change concerns<EITHER > DM

<OR> UNIVERSUM/RAP <OR> ETL<OR> IMPLEMENTATION

Product ETLwas finished

F.6.4

ImplementationReportsdesigner performs

D.12

TechnicalProject

of "Universum"and reports

D14

ETLproject

Implementationpackage

Implementationwas finished

F.4

TestingConnector

to the process

ETLDesigner

performs

Data BasePlatform

supports

DB Programmerperforms

performs

Excel

D.11

DMtechnicalproject

D.13

Dictionaries

DM projectrepository

supports

ETLdesigntools

Development reference process model


Some results (1)

Number of the products instancess/year 10

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

1 Define Quality Requirements 0010:00:00:00 0006:00:00:00 14,20%

2 Define Quality and product

Patterns

0014:00:00:00 0007:00:00:00 16,60%

3 New Product Activation

(Preparation time- organizing the

team and tools)

0000:05:00:00 0001:00:00:00 2,40%

4 Iteration Management 0002:00:00:00 0001:00:00:00 2,40%

5 Define Correspondence AD

Model to Product Report Patterns

0005:00:00:00 0005:00:00:00 11,80%

6 Create AD Elements 0010:00:00:00 0015:00:00:00 35,50%

7 Quality Validation 0010:00:00:00 0006:00:00:00 14,20%

8 Product and Iteration Acceptance 0005:00:00:00 0001:00:00:00 2,40%

9 Create Final Report 0001:00:00:00 0000:05:00:00 0,50%

TOTAL 0057:05:00:00 0042:05:00:00 100,00%

INPUT DATA BEFORE AND

AFTER OPTIMIZATION


Some statistical results (2)


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 1: " 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 1 which should be compatible with the corresponding

ADM metamodels (are their refinement (specialization) in the relevant sector).

The Quality Management Metamodel in the Enterprise … · · 2014-07-30(C) Jerzy Roszkowski 2...

Documents

Transcript of The Quality Management Metamodel in the Enterprise … · · 2014-07-30(C) Jerzy Roszkowski 2...