1 / 12

Milestones: Mythical Signals in UML for Progress Analysis

Explore how mythical signals in UML are used to monitor progress in service behaviors, depicted through milestones passed during execution. This concept, embedded in UML models, aids in analyzing and understanding long-lasting service behaviors. Learn how to monitor interactions and progression using these specialized signals.

pekelo
Télécharger la présentation

Milestones: Mythical Signals in UML for Progress Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Milestones: mythical signals in UML to analyze and monitor progress Richard Sanders, SINTEF Øystein Haugen, SINTEF / University of Oslo

  2. Milestones - a means for depicting progress in behaviours • Semantics defined by mythical signals • a conceptual signal that is sent from the behaviour every time one of the associated milestones is passed during execution • sent to a conceptual observer outside the system • can be omitted in implemented systems • Modeled by specialized UML Comments in SoaML • Embedded in ordinary UML models • Used to understand, analyze and monitor service behavior • Particularly useful for behaviours that are long lasting

  3. Buyers Seller Example: a bidding service Bidding service • What are the steps of a bidding process? • Which buyers behave properly? • How far has a bidding session come?

  4. BiddingService seller:Seller[1] buyer:Buyer[1..*] «ServiceInterface» «ServiceInterface» SoaML: Service modelled as a collaboration «ServiceContract»

  5. Service behaviour described in sequence diagram

  6. «milestone» Buy <Prospect received> Steps expressed using milestones

  7. s:Seller GUI «milestone» Buy <Prospect received> «milestone» Buy <Won bid> Specification of interface behaviour b:Buyer

  8. b1:SimpleBuyer GUI s:Seller GUI b2:SeriousBuyer GUI Analysis of progress in interactions

  9. sm SimpleBuyer prospect / ^display(prospect) advertisement / ^interest Idle Awaiting Prospect Buyer that is safe but of little use / ^display(prospect) Interface behaviour • Milestone Buy <Prospect received> can be reached • No bid is ever sent • Milestone Buy <Bid acknowledged> cannot be reached

  10. Monitoring behaviour Buy <…> Sell <…> • Monitor Buy and Sell signals

  11. Metamodel for Milestones in SoaML • Milestone is a “mythical” signal sent when milestone is passed • Not necessarily present in implementation • progress tells relative degree of progress • value: signal data when the milestone is passed

  12. Support for milestones • SoaML – UML profile for Services • Tool support for design time validation of progress • EU IST FP6 SIMS (Semantic Interfaces for Mobile Service) • www.ist-sims.org: tools available for beta testing • Future work • End-user composition of services based on milestones • uComp – proposal for Call 5 in November 2009

More Related