8th IEEE/IFIP Network Operations and Management Symposium. A Case Driven Methodology for Applying the MNM Service Model

Size: px

Start display at page:

Download "8th IEEE/IFIP Network Operations and Management Symposium. A Case Driven Methodology for Applying the MNM Service Model"

Beatrice Edwards
10 years ago
Views:

1 8th IEEE/IFIP Network Operations and Management Symposium April, Florence, Italy A Case Driven Methodology for Applying the MNM Service Model M. Garschhammer, R. Hauck, H.-G. Hegering, B. Kempter, I. Radisic, H. Roelle, H. Schmidt Presenter: Harald Roelle Department of Informatics, University of Munich [email protected]

Hauck, H.-G. Hegering, B. Kempter, I. Radisic, H. Roelle, H.

2 MNM Service Model Motivation Customer-oriented conceptual meta model Defines common view and terminology Immediately useable for theoretical studies Applicable for all kinds of concrete scenarios Applying the model includes Identifying and collecting relevant information Deriving concrete classes in appropriate order In-detail specification of classes But: By now no guidelines available Reasonable order of steps Adequate information representation Methodology for easier model application needed 2 Harald Roelle

relevant information Deriving concrete classes in appropriate order In-detail specification of classes But: By now no guidelines

3 MNM Service Model: Basic Service Model Gives overview over the service environment Specifies: Roles of participating entities Participating services Separates service from customer and provider side Recursive application shows hierarchies 3 Harald Roelle

Participating services Separates service from customer and

4 MNM Service Model: Service View 4 Harald Roelle

5 MNM Service Model: Realization View 5 Harald Roelle

6 MNM Service Model: Realization View 5 Harald Roelle

7 MNM Service Model: Realization View 5 Harald Roelle

8 Basic Modeling Cases Reverse engineering: Gain formal description of existing service infrastructures Demanded for internal restructuring or outsourcing decisions Bid invitation: Future customer requests offers from providers Unambigous and complete specification needed Independence from realization for comparable offers Offering: Offer new services to potential customers Presenting only customer relevant parts Specifying in a customer understandable way Modeling cases form basis for methodology 6 Harald Roelle

specification needed Independence from realization for comparable offers Offering: Offer new services to potential customers

9 Methodology: Overview Inspired by software engineering Workflow based Actions deliver objects step-by-step Artifacts Input/output of actions Used for in-detail specification of objects Deliver structuring and refinement Two basic processes Top-down: bid invitation Bottom-up: reverse engineering Both: offering 7 Harald Roelle

specification of objects Deliver structuring and refinement Two basic processes

10 Methodology: Overview Inspired by software engineering Workflow based Actions deliver objects step-by-step Artifacts Input/output of actions Used for in-detail specification of objects Deliver structuring and refinement Two basic processes Top-down: bid invitation Bottom-up: reverse engineering Both: offering 8 Harald Roelle

11 Role identification Basic Service Model s Workflow Transparencies define depth of modeling Modeling case influences availability of information 9 Harald Roelle

12 Service naming Basic Service Model s Workflow Naming of all identified services Associations between roles and services 10 Harald Roelle

13 Basic Service Model s Workflow Finished deriving Basic Service Model Next in top-down process: Service View 11 Harald Roelle

14 Service View s Top-Down Workflow Functionality definition: Defines usage and management functionality Use cases refined by activity diagrams 12 Harald Roelle

15 QoS definition: Service View s Top-Down Workflow Begin/end of activities as reference points QoS dimensions: duration, capacity, correctness 13 Harald Roelle

16 Service View s Top-Down Workflow Client and access point (AP) definition Ability to fulfill QoS parameters Access points must match corresponding clients 14 Harald Roelle

17 Service View s Top-Down Workflow Service agreement definition Include information from all artifacts Specify concrete boundaries 15 Harald Roelle

18 Service View s Top-Down Workflow Finished deriving Service View Next: Realization View 16 Harald Roelle

19 Realization View s Top-Down Workflow Provider s service management (SM) process TOM / ITIL as structured starting points Activities and use cases extended by internal processes 17 Harald Roelle

20 Realization View s Top-Down Workflow Outsourcing decision Every process marked as either internal or outsourced Former Basic Service Model refined/extended 18 Harald Roelle

21 Realization View s Top-Down Workflow Resource and basic management functionality identification Analysis of every single internal activity Logics extended by collaboration diagrams modelling interactions 19 Harald Roelle

22 Realization View s Top-Down Workflow Finished deriving Realization View Finished applying whole MNM Service Model to specific scenario 20 Harald Roelle

23 Basic modeling cases identified: Reverse engineering Bid invitation Offering Conclusion Modeling case determines basic decisions Methodology Simplifies model application in all modeling cases Delivers step-by-step guidelines Artifacts for in-detail class specification Ensures comparable results Creation of all views supported MNM Service Model with methodology serve as a checklist in all modeling cases 21 Harald Roelle

24 Current Work Development of integrated tool support Incorporates workflow and document management component Implementation by extension of existing CASE tool Design Patterns for model application Underlines relations to software engineering Similarities in structures were found Rapid model application Delivers design decision support Investigations on impact of context-awareness Modeling of mobile service scenarios Basis for automatic service composition 22 Harald Roelle

Towards generic Service Management Concepts A Service Model Based Approach

7th IEEE/IFIP International Symposium on Integrated Network Management (IM 2001), Seattle, Washington USA, IEEE Publishing, May 2001 Towards generic Service Management Concepts A Service Model Based Approach