Oct 9, 2007 ... A Systematic Approach to Meta Model. Engineering. List of Relevant. Process.
Steps. Documents. Concerns. Viewpoint 1. Viewpoint 2.
Viewpoint-based Viewpoint based Meta Model Engineering g g EMISA 2007 October 8 - 9,, 2007 - St. Goar / Rhine,, Germanyy Stephan Kurpjuweit I it t off Information Insitute I f ti Management M t University of St. Gallen
[email protected] www iwi unisg ch www.iwi.unisg.ch
Research Context Approach: pp Method Engineering
Scope: Work Systems Engineering
Strategy
Organization
Integration
Software IT-Infrastructure © Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 2
Project Context Mid size financial service p provider in Germany y Goal: Establish a specific meta model (+ tool implementation) for the organization’s EAM processes. processes Approach: Iterative meta modeling Enterprise Architecture
Business model
Organizational Products / structure Services Organizational goals Success factors Performance indicatorsProcesses Activities
Applications Information Software components
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 3
A Systematic Approach to Meta Model Engineering Process Steps
Documents List of Relevant Concerns
1 Identification of Relevant Concerns
Viewpoint 1
5
Meta Model Fragment Integration
Viewpoint Relationship Diagram
Meta Model Fragment 1
Meta Model Fragment 2
…
Valiidation
Meta Model Fragment Selection or Design
Viewpoint Requirements Specification n
Design D
4
…
Valiidation
Viewpoint Relationship Overview
Viewpoint n
Viewpoint Requirements Specification 2
Design D
3
Viewpoint Requirements Specification 1
Valiidation
Requirements Elicitation
Design D
2
Viewpoint 2
Meta Model Fragment n
Integrated Meta Model © Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 4
Step 1: Identification of Relevant Concerns Application Architect IT Audit Cost of application d development l t
Correct implementation of ownership policies
P Process Owner O
Providing adequate IT for business processes
EA
…
Cost of application operation and maintenance Software Architect IT Operations
14 stakeholder groups 45 relevant requirements
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 5
Step 2: Requirements Elicitation Which parts of the work system will be modeled?
Object
Why will Wh ill the th object bj t be b modeled? (1) documentation and communication, (2) analysis and explanation (3) design
Purpose
Which concern will be modeled?
Concern
1. Representation of the Object As-Is How can the object as-is be modeled? (incl example models) (incl.
3. Modelers and Information Sources Who will create the models? On the basis of which information sources?
Which stakeholder perspective will be taken?
Stakeholder
In which situation (project types and context factors)?
Situation
2. Representation of the Object To-Be How can the object to-be be modeled? (incl example models) (incl.
4. Model Users and Information Targets Who will interpret the models? How will the information be used?
5 Design Strategies 5.
6 Compatible Approaches 6.
Which design decisions may impact the concern in a positive or a negative way?
To which approaches, standards, and frameworks should the model be comaptible?
Viewpoints Requirements Template (VRT)
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 6
Step 2: Requirements Elicitation Viewpoint
IT Consolidation
Business IT Alignment
Component Reuse
Ownership
Object
Processes, Processes ,Applications Applications
Processes, Applications
Software Architecture
IT-related Artifacts
Purpose
Analysis
Analysis
Design
Documentation
Concern
Cost of application operation and maintenance
Providing adequate IT for business processes
Cost of application development
Correct implementation of ownership policies
Stakeholder
Application architect
Process owner
Software architect
IT audit
Design Strategies
Consolidation of applications that are in use for similar purposes / Consolidation of system software of the same type (e.g., DBMS, WFMS)
Providing IT functionalities for each process step / reduction of media breaks
Reuse of software components accross multiple applications / reuse of system softwrae (e.g,. DBMS, WFMS)
Assigning explicit owners to applications and other ITrelated artefacts (like information objects, components, environments, etc.)
Questions
Which applications are used in the individual processes (sorted by organizational unit, product, distribution channel)? / Which system software of the same type is currently in use?
Which process activities are not IT supported? Which processes include media breaks? / Which applications are supported by multiple applications?
Which components are available in existing applications? / Which interfactes are available to use these components? Which system software of different types is currently in use?
Are there applications for which np owners have been defined? Are there applications that have not been audited for more than two years?
Meta Model Fragment
Step 3: Viewpoint Relationship Overview
Viewpoint Relationship Diagram
Viewpoint Relationship Diagram (Legend)
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 8
Step 4: Meta Model Fragment Selection or Design Viewpoint
IT Consolidation
Business IT Alignment
Component Reuse
Ownership
Object
Processes Applications
Processes, Applications
Software Architecture
IT-related artifacts
Purpose
Analysis
Analysis
Design
Documentation
Concern
Cost of application operation and maintenance
Providing adequate IT for business processes
Cost of application development
Correct implementation of ownership policies
Stakeholder
Application architect
Process owner
Software architect
IT audit
Design Strategies
Consolidation of applications that are in use for similar purposes / Consolidation Consolidtaion of system software of the same type tyepe(e.g., (e.g.,DBMS, DBMS,WFMS) WFMS)
Providing IT functionalities for each process step / reduction of media breaks
Reuse of software components across multiple applications / reuse of system software (e.g,. DBMS, WFMS)
Assigning explicit owners to applications and other ITrelated artefacts (like information objects, components, environments, etc.)
Questions
Which applications are used in the individual processes (sorted by organizational unit, product, distribution channel)? / Which system software of the same type is currenty in use?
Which process activities are not IT supported? Which processes include media breaks? / Which applications are supported by multiple applications?
Which components are available in existing applications? / Which interfactes are available to use these components? Which system software of different types is currently in use?
Are there applications for which no owners have been defined? Are there applications that have not been audited for more than two years?
Meta Model Fragment
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 9
Step 5: Meta Model Fragment Integration Integration Operations Adjusting Terminology Creating generalizations Creating specializations Avoiding redundancies Introducing interface modeling concepts Business Information Object
Distribution Channel
Product
part of
Information Flow
specialization
part of
Process
Org. Unit
Site
Application
Person
Position
part of Software Component
Data Entity
Interface
Application Environment
Complete p Meta Model (simplified)
System Software
Server
User Interface
Business Logic
Data Container
Physical Server
Sever Cluster
Virtual Server
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 10
Extended Method Engineering Meta Model described in N Notation i is part of
is part of
conforms to Meta Model Fragment
Meta Model
Design Result Conforms to
is part of expressed in Viewpoint
applied in
Design Strategy
produces / consumes
predecessor / successor
is part of
adresses Concern
Role
participates in
guides creation of
Design Activity
Technique
has has Stakeholder
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 11
Example Models Integration Architecture
Software Architecture
Environments, Platforms
System y Software
Servers, Clusters, Virtual Servers © Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 12
Compliance Analysis Are there applications for which no owners have been defined?
© Okt-07 IWI-HSG, Robert Winter Seite 13
Coverage Analysis Example p 1 Which business processes are performed for the individual p products?
© Okt-07 IWI-HSG, Robert Winter Seite 14
Coverage Analysis Example p 2 How are business processes supported by applications?
© Okt-07 IWI-HSG, Robert Winter Seite 15
Coverage Analysis Example p 3 Which applications are used for the individual products along the process chain? p
© Okt-07 IWI-HSG, Robert Winter Seite 16
Coverage Analysis Example p 4 How are the applications distributed across servers?
© Okt-07 IWI-HSG, Robert Winter Seite 17
1) Approach to meta model engineering Process Steps
Documents
2) Extension to the method engineering meta model
List of Relevant Concerns
1 Identification of Relevant Concerns
described in Notation is part of
is part of
conforms to
Viewpoint 1 2
Requirements Elicitation
Viewpoint 2
Meta Model Fragment
Viewpoint n
Meta Model
Viewpoint Requirements Specification 2
…
Viewpoint Requirements Specification n
Viewpoint
applied in
Design Strategy
4
Meta Model Fragment Selection or Design
Role
Design
Validation
Design
Validation
Viewpoint Relationship Diagram
Design
Viewpoint Relationship Overview
produces / consumes
guides creation of
predecessor / successor
is part of
adresses Concern
3
Design Result Conforms to
is part of expressed in
Viewpoint Requirements Specification 1
Validation
Contrib bution
Contribution and Future Work
Design Activity
participates in
Technique
has has Stakeholder
is part of
Meta Model Fragment 1
Meta Model Fragment 2
…
Meta Model Fragment n
Method Fragment influences
influences Adaptation Mechanism
5
Meta Model Fragment Integration
is part of
Integrated Meta Model
Situation
Futture Wo ork
Context
1) Handbook of viewpoints
2) Sit Situational ational viewpoint adaptation mechanisms h i
is part of
Project Type
3) Concrete modeling guidelines g
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 18
Thank you for your attention.
Stephan St h Kurpjuweit K j it
[email protected] www.iwi.unisg.ch +41 71 224 3316
© Oct-07 IWI-HSG, Stephan Kurpjuweit Slide 19
