1 / 19

Turning Clockwise: Using UML in the Real-Time Domain

Turning Clockwise: Using UML in the Real-Time Domain. “You mustn’t forget one thing,” the fairy godmother said. “Do not stay past midnight, for when the hour strikes, everything will return to the way it was before. “I promise,” said Cinderella. A Brief History of UML.

abdalla
Download Presentation

Turning Clockwise: Using UML in the Real-Time Domain

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. Turning Clockwise: Using UML in the Real-Time Domain “You mustn’t forget one thing,” the fairy godmother said. “Do not stay past midnight, for when the hour strikes, everything will return to the way it was before. “I promise,” said Cinderella.

  2. A Brief History of UML • Rumbaugh joins Booch at Rational Software Corporation. • The UML effort officially starts in October 1994. • The version 0.8 draft of the Unified Method (as it was then called) releases in October 1995. • UML consortium established. • Partners contributing to the UML 1.0 definition include DEC, I-Logix, Intellicorp, IBM, ICON Computing, MCI Systemhouse, Microsoft among others • UML 1.0 was offered for standardization to the Object Management Group (OMG) in January 1997

  3. Real-Time Systems and the Object Paradigm • A real-time system is a software system that maintains an ongoing and timely interaction with its environment.

  4. Requirements for Modeling Real-Time Systems • Infrastructure modeling requirements • Behavior modeling requirements • Structure modeling requirements

  5. Infrastructure Modeling Requirements • Engineering Infrastructure • Networks • Processors • Logical Devices • Scheduling • Timing • Memory Management

  6. Behavior Modeling Requirements • Event-driven • Time-driven

  7. Structure Modeling Requirements • Peer Relationships • Containment Relationships • Layering Relationships

  8. Using UML for Modeling Real-Time Systems

  9. Model • A model is a simplification of reality • Models help us visualize a system as it is or as we want it to be • Models permit us to specify the structure or behavior of a system • Models give us template that guides us in constructing a system • Models document the decisions we have made

  10. Modeling the Engineering Infrastructure • Modeling resources and system services. • Element-to-resource mapping. • Resource-to-value mapping. • Modeling time and timing facilities.

  11. Modeling Real-Time Behavior • Event-driven (reactive) behavior modeling • Time-driven behavior modeling • Object interaction modeling

  12. Modeling Real-Time Structure • Architectural Modeling

  13. Strengths • Strengths • UML stereotypes has enabled to capture real-time concepts and allowed smooth integration of already proven techniques developed in previous generations of real-time methods. • This allows for creation and exploitation of complicated software. • Traditional engineering techniques applied to UML, and hence to real-time systems.

  14. Weaknesses • UML still in its infancy. • Real-time systems model physical reality. • Not always possible to capture the complexities of nature through a modeling language.

  15. . . . And they lived happily forever.

More Related