1 / 11

Work Package 2: Component Modeling Task 2.1 – UML/RT Task 2.2 – Reuse Contracts

Work Package 2: Component Modeling Task 2.1 – UML/RT Task 2.2 – Reuse Contracts. Prof. Dr. Viviane Jonckers, Tom Toutenel. Software Modeling for RT-Systems. Recapitulation:. Timing Specification & Notation. UML/RT Detailed Timing Diagrams MSCs with Free-Form Timing Constraints ROOM

warren
Download Presentation

Work Package 2: Component Modeling Task 2.1 – UML/RT Task 2.2 – Reuse Contracts

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. Work Package 2: Component Modeling Task 2.1 – UML/RTTask 2.2 – Reuse Contracts Prof. Dr. Viviane Jonckers, Tom Toutenel

  2. Software Modeling for RT-Systems Recapitulation:

  3. Timing Specification & Notation • UML/RT • Detailed Timing Diagrams • MSCs with Free-Form Timing Constraints • ROOM • No Explicit Timing • Octopus • Derive Process Priorities • CAPS • Timed Petrinets • Scheduler Generation

  4. Timed Message Sequence Charts R1 R3 R2 Msg X a { 75 ms } Msg P b { 500 ms } Msg Y c { d - c > 1 s } { 75 ms } Msg Q d • Timed MSCs in UML/RT Text Description More Text Description

  5. Timed MSCs R1 R3 R2 T1.1 [1,2] Msg X T3.1 [2,3] Msg P (2,4] Msg Y [1,3] [2,3] Msg Q • Ongoing Research Towards Standardization of Timing Constraints in MSCs: Timers & Delay Intervals • ITU-T Recommendation Z.120 • H. Ben-Abdallah, S. Leue. Expressing and Analyzing timing constraints in Message Sequence Chart Specifications.

  6. Components & Contracts • A. Beugnard, J.-M. Jézéquel, N. Plouzeau, D. Watkins.Making Components Contract Aware.IEEE Computer, July 1999. • Contract Levels • Syntactic Level • Provided and Required Interfaces • Behavioral Level • Pre- and Postconditions • Synchronization Level • Quality of Service Level • Timing • Resources • Bandwith

  7. Base of Departure AUTOMATA • MSCs to Document Typical Use of Components • MSCs to Document Composition of Components • Conformance Checking • Glue Code Generation

  8. b a 1 3 2 a Comp3 Comp2 Comp1 Envi Envi Envi Envj Envj Envj Subscribe Subscribe Subscribe LOOP LOOP LOOP Set Set Set Notify Notify Notify OPT OPT OPT Get Get Get R1 R2 R3 Subscribe LOOP Set Notify OPT Get 

  9. Research Path - Step 1 • Add QoS to Component Documentation • Initially only Timing Information • Timing on MSC of Component is a Contract • Add QoS to Composition Documentation • Timing Information Represents Global Requirements • Tools: Enrich MSC Editor and Component & Composition Repositories • Extend Conformance Checking Algorithms • Modify Glue Code Generation

  10. Conformance Checking with Timing • Undecidable for Dense-Time • E. Asarin, P. Caspi, and O. Maler. A Kleene Theorem for Timed Automata. In Proc. of the 12th IEEE Symposium on Logic in Computer Science, Warsaw, Poland, June 1997. • Need not Matter for Practical Purposes • Thesis on Undecidability Problems

  11. Research Path - Step 2 • Add Test-Cases to Documentation to Obtain Typical-Use Timing with Little Effort • Interaction with Component System Necessary • Component System Needs Monitoring Constructs in VM

More Related