Presentation is loading. Please wait.

Presentation is loading. Please wait.

Service Modelling Team (SMT#3) Topic: Service Architecture Walter Van Hamme WP8 contributor 7 May 2014.

Similar presentations

Presentation on theme: "Service Modelling Team (SMT#3) Topic: Service Architecture Walter Van Hamme WP8 contributor 7 May 2014."— Presentation transcript:

1 Service Modelling Team (SMT#3) Topic: Service Architecture Walter Van Hamme WP8 contributor 7 May 2014

2 enter your presentation title2 From wiki  Points to consider / discuss  Service architecture diagrams within ISRM.  Making clear the intention of the Service Architects.  In particular in showing several services together (similarity, difference, dependency, alternative, and much more) without having to go to fine details.  This is usally a good entry point for newcomers and external stakeholders.  How should these diagrams be handled in the next phases?

3 enter your presentation title3 Generic content  Objective & content  Improving understanding of ISRM services  Putting services in context & Promoting SOA  Status & problem / issue  ISRM focuses on isolated services  Architecture diagrams not in ISRM 1.1 Foundation  Examples  From FT9 & FT10  Discussion  Usefulness  Alternatives  Way Forward  Decisions & Actions

4 enter your presentation title4 FT9 – OFA 05.03.01 ASM & aFUA  Service Architectures  We used the SoaML service architecture diagram which is a collaboration diagram that depicts the high level functions (=role) that ATM participants provide to achieve a certain goal via service contracts. We have created a separate architecture for each business collaboration. The first reason is for readability. The second reason, more important, it to concentrate on specific business collaboration and to view the roles that are directly required to achieve the collaboration.  We leave the EAEA to depict the global service architecture and we concentrate on the service design making sure that the appropriate SOA design principles are applied.  The architecture diagrams are placed in the collaboration sections of the document.  Manage Airspace Reservation  Consolidate AUP  Manage Airspace Activation

5 enter your presentation title5 Manage Airspace Reservation

6 enter your presentation title6 Consolidate AUP

7 enter your presentation title7 Manage Airspace Activation

8 enter your presentation title8 FT10 – OFA 05.01.01 AIOM & A-CDM  Usage  Provide an overview of the services and the actors  Stress similarity, difference, dependency, alternative, and much more  Put services in context  Focus from 1 service  several services  Usually before looking into the detail of a service

9 enter your presentation title9 Visual overview of the Identified Services

10 enter your presentation title10 NSOV-5 Service Behaviour Function and Service Category

11 enter your presentation title11 Simplified view of the pattern service architecture The Consolidator checks incoming partner values and calculated results based on (local) business rules and combine them to provide one consolidated output that will become the reference value. Uses Business Logic to validate / filter the values: eg value in the past, max number of TOBT update after TSAT issue, etc.. The Calculator uses the raw information to provide calculated results following some Business logic. Examples are the Automatic TOBT Calculation, or the Pre-Departure Sequencer that calculates TTOT and TSAT. The A-CDM Publisher collates all consolidated information in a global picture. That global picture, or part of it, is then published to internal and external stakeholders that have subscribed to it.

12 enter your presentation title12 Identified Services mapped to the Service Architecture The diagram shows a complete picture. It is not necessary to implement each of the depicted services to be compliant with this architecture. The local situation at the Airport may dictate what is actually applicable. At some airport, there may be no need for Partner TSAT set, at some others the PDS may be within the ACISP, etc.

13 enter your presentation title13 Discussion  Usefulness of Service Architecture diagrams  Understanding  External stakeholder  SOA  Alternatives about Service Architecture diagrams  Disregard - Remove useful information for our stakeholders  Put outside of ISRM - Where? Consistency? Complete logical view?  Allow within ISRM - Adapt Foundation  Other? - Any?

14 enter your presentation title14 Way forward  Decisions  Actions  Concerning  Existing architecture diagrams  New architecture diagrams  ISRM Foundation

Download ppt "Service Modelling Team (SMT#3) Topic: Service Architecture Walter Van Hamme WP8 contributor 7 May 2014."

Similar presentations

Ads by Google