60 likes | 184 Vues
This resource explores the use of activity diagrams for capturing execution flows in use cases and details of process dynamics. It highlights useful stereotypes for presenting information effectively, managing states, and handling exceptions. Key concepts include the relationships between decisions, actions, and controls, and how these elements fit within the MVC architecture. A practical task is provided to model the UVic course registration page, leveraging insights from Benjamin Lieberman's presentation to enhance your understanding of structured modeling.
E N D
Reference • http://www.ibm.com/developerworks/rational/library/4697.html • Benjamin Lieberman , Ph.D.,
What Does an Activity Diagram Provide? • [can] be used effectively to capture use-case flows of execution • [can] be used effectively to capture details of the dynamic aspects [of process]
Useful Stereotypes Perspective A • Presentation • manages appearance • Exception • handles edge cases • Connector • links models Perspective B • Presentation • manages appearance • Control • manage state • Navigation • manages location
Possible Framework for an Activity Diagram (Lieberman) Things to think about • Frame color • Relationship between Decision and Exception • Relationship between Actions, Controls and Decisions • How do Actions, Controls and Decisions relate to MVC?
Task • Model the UVic course registration page • Hint – take a look at Libermans presentation to see how to use his stereotypes