CSC 480 Software Engineering PSP Project 3 September 6, 2002

CSC Software Engineering2 9/6/2002 Topics OO Modeling  Review static (or structural) models  Dynamic (or behavioral) models Case Study – Displaying Punch-in Info

CSC Software Engineering3 9/6/2002 Basic Structural Modeling Class members (or responsibilities)  Attributes  Operations Relationships  Inheritance  Structural relationships Aggregation Composition

CSC Software Engineering4 9/6/2002 UML Notations – Inheritance Stock SmallCapStockLargeCapStock

CSC Software Engineering5 9/6/2002 UML Notations – aggregation & composition SchoolDepartment StudentCourseInstructor has chair teaches attends memberassigned to

CSC Software Engineering6 9/6/2002 Class V.S. Object Invoice -billingAddress -items +add(aProd, qtty) +format() +getAmountDue() Class diagram i:Invoice street = “123 Main” city = “Macon” state = “GA” addr:Address i1:item product = prod1 quantity = 3 Object diagram

CSC Software Engineering7 9/6/2002 Behavioral Modeling Use case diagram  Organizes the behaviors of the system Sequence diagram  Focused on the time ordering of messages Collaboration diagram  Focused on the structural organization of objects Statechart diagram  Focused on the changing state of a system

CSC Software Engineering8 9/6/2002 Message Passing YourBicycle.changeGears(lowerGear)

CSC Software Engineering9 9/6/2002 Use Case Diagram Print invoice system actor use case 1.… 2.… 3.…

CSC Software Engineering10 9/6/2002 Sequence Diagram

CSC Software Engineering11 9/6/2002 Collaboration Diagram

CSC Software Engineering12 9/6/2002 Statechart Diagram

CSC Software Engineering13 9/6/2002 Case Study The PunchIn program from chapter 14  Programming & Problem Solving with C++ Dale, Weems, and Headington Classes used  Time  TimeCard  TCList