An Introduction to UML Modeling Resources Using UML Rahul Shah EE249 Discussion Sept 25 2001 Talk Outline An introduction to UML Different views in UML Examples from PicoRadio UML documentation 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 Object oriented modeling language 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 and agree on them Rumbaugh Jacobson Booch UML Views Structural things in the system and their relationship to other things Class diagrams Use case diagrams Component diagrams Dynamic system behavior over time Statechart diagram Activity diagram Sequence diagram Model management others Class Diagram Piconode Application Layer 1 11 1 Send Pkt Receive Pkt Network Layer Node Addres s Pkt form at Src Des t Data Next Hop Send Receive Pkt from Application Receive Pkt from Neighbor Check if Pkt arrived at Des t Select next hop Routing algorithm Forward next hop 1 Neighbor 1 Send Pkt Receive Pkt PicoRadio UML documentation Use Case Diagram Req Data Pkt from Application Select Next Hop Req Data Pkt to Application PicoRadio UML documentation Forward to Next Hop Arrived at Dest Req Data Pkt to Next Node Req Data Pkt from Next Hop Activity Diagram Check if Req or Data Pkt Request Pkt Data Pkt Store Update Request Read Neighbor Table Select among Neighbors geo Forward to selected Neighbors PicoRadio UML documentation Sequence Diagram PicoRadio UML documentation A Generic Framework for Modeling Resources With UML Bran Selic IEEE Computer June 2000 Quantitative Analysis Schedulability analysis Deterministic technique Good for hard real time systems Performance analysis Probabilistic characterization Good for soft real time systems QoS Contracts Peer interpretation Layered interpretation realization mappings play the role of QoS contracts UML Model of QoS Contracts Composition Associations Association Class Aggregation Management of Resources Generalization Realization Mapping Realization relationship QoS Analysis Compare the required QoS with the offered QoS The offered QoS should exceed the required QoS Aggregated QoS characteristics can complicate the analysis Different characteristics combine in different ways Resources are often shared Conclusions Models are useful to predict and quantify performance of software without actual construction Incorporating a generic QoS framework in UML helps us in analyzing software models UML is an industry standard thus a common base to develop new techniques for analysis
View Full Document
Unlocking...