13-puttingitalltogether

13-puttingitalltogether - Putting It All Together Kenneth...

Info iconThis preview shows pages 1–7. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: Putting It All Together Kenneth M. Anderson University of Colorado, Boulder CSCI 4448/5448 Lecture 13 10/06/2009 University of Colorado, 2009 1 Lecture Goals Introduce two new UML diagrams Review material from Chapter 10 of the OO A&D textbook The OO A&D project life cycle Compare to other OO A&D life cycles The Objectville Subway Map Example (in python) Dijkstras Algorithm Discuss the example application of Chapter 10 Emphasize the OO concepts and techniques encountered in Chapter 10 2 Two New UML Diagrams Activity Diagrams and State Diagrams Relationship to life cycles They represent alternate ways to record/capture design information about your system. They can help you identify new classes and methods that They are typically used in the following places in analysis and design After use case creation: create an activity diagram for the use case For each activity in the diagram: draw a sequence diagram Add a class for each object in the sequence diagrams to your class diagram, add methods in sequence diagrams to relevant classes Based on this information, see if you can partition an objects behavior into various categories (initializing, acquiring info, performing calcs, ) Create a state diagram for the object that documents these states and the transitions between them (transitions typically map to method calls) 3 Activity Diagrams Think Flow Chart on Steroids Able to model complex, parallel processes with multiple ending conditions Constructs Initial Node (circle)/Final Node (circle in circle)/Early Termination Node (circle with x through it) Activity: Rounded Rectangle indication an action of some sort either by a system or by a user Flow: directed lines between activities and/or other constructs. Flows can be annotated with guards [student on list] that restrict its use Fork/Join: Black bars that indicate activities that happen in parallel Decision/Merge: Diamonds used to indicate conditional logic. Swim Lanes: A way to layout the diagram to associate roles with activities 4 Example Activity Diagram Example adapted from <http://www.agilemodeling.com/artifacts/activityDiagram.htm >. Copyright 2003-2006 Scott W. Ambler Fill Out Forms Inspect Forms [problem found] Display Enrollment Screen [no problem found] Enter Applicant Information Validate Student Search for Student Record Need to Apply [not a student] Display Matches Create Student Record [matches found] [no matches] [on list] [not on list] [is a student] Enroll Student Calculate Fees Process Payment 5 State Diagrams Shows the major states of an object or system Each state appears as a rounded rectangle Arrows indicate state transitions Each transition has a name that indicates what triggers the transition (often times, this name corresponds to a method name) Each transition may optionally have a guard that indicates a condition that must be true before the transition can be followed...
View Full Document

This note was uploaded on 03/11/2010 for the course CSCI 5448 taught by Professor Anderson during the Fall '09 term at Colorado.

Page1 / 65

13-puttingitalltogether - Putting It All Together Kenneth...

This preview shows document pages 1 - 7. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online