An Introduction to UML Modeling Resources Using UML

















- Slides: 17
An Introduction to UML & Modeling Resources Using UML Rahul Shah EE 249 Discussion Sept. 25, 2001
Talk Outline w An introduction to UML n n Different views in UML Examples from Pico. Radio UML documentation w Discussion of Bran Selic’s paper, “A generic framework for modeling resources with UML”
The Development Process Project Phases Process Components Requirements capture Analysis & Design Implementation Test Inception Elaboration Construction Transition }UML
Unified Modeling Language w Object oriented modeling language w Intended to model discrete systems such as software, firmware or digital logic “Models are used to capture and precisely state requirements and domain knowledge so that all stakeholders may understand agree on them. ” (Rumbaugh, Jacobson & Booch)
UML Views w Structural: things in the system and their relationship to other things n n n Class diagrams Use case diagrams Component diagrams w Dynamic: system behavior over time n n n Statechart diagram Activity diagram Sequence diagram w Model management, others
Class Diagram† †Pico. Radio UML documentation
Use Case Diagram† †Pico. Radio UML documentation
Activity Diagram† †Pico. Radio UML documentation
Sequence Diagram† †Pico. Radio UML documentation
A Generic Framework for Modeling Resources With UML Bran Selic IEEE Computer, June 2000.
Quantitative Analysis w Schedulability analysis n n Deterministic technique Good for hard real-time systems w Performance analysis n n Probabilistic characterization Good for soft real-time systems
Qo. S Contracts Peer interpretation Layered interpretation (realization mappings play the role of Qo. S contracts)
UML Model of Qo. S Contracts Composition Associations Association Class Aggregation
Management of Resources Generalization
Realization Mapping Realization relationship
Qo. S Analysis w Compare the required Qo. S with the offered Qo. S w The offered Qo. S should exceed the required Qo. S w Aggregated Qo. S characteristics can complicate the analysis: n n Different characteristics combine in different ways Resources are often shared
Conclusions w Models are useful to predict and quantify performance of software without actual construction w Incorporating a generic Qo. S framework in UML helps us in analyzing software models w UML is an industry standard, thus a common base to develop new techniques for analysis