CSC 480Software Engineering

PSP Project 3September 6, 2002

CSC 480 - Software Engineering 29/6/2002

Topics

OO Modeling Review static (or structural) modelsDynamic (or behavioral) models

Case Study – Displaying Punch-in Info

CSC 480 - Software Engineering 39/6/2002

Basic Structural Modeling

Class members (or responsibilities)AttributesOperations

Relationships InheritanceStructural relationships

Aggregation Composition

CSC 480 - Software Engineering 49/6/2002

UML Notations – Inheritance

Stock

SmallCapStock LargeCapStock

CSC 480 - Software Engineering 59/6/2002

UML Notations – aggregation & composition

School Department

Student Course Instructor

has

chairteachesattends

member assigned to

CSC 480 - Software Engineering 69/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

i1:item

product = prod1quantity = 3

Object diagram

CSC 480 - Software Engineering 79/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 480 - Software Engineering 89/6/2002

Message Passing

YourBicycle.changeGears(lowerGear)

CSC 480 - Software Engineering 99/6/2002

Use Case Diagram

Print invoice

system

actor

use case1. …2. …3. …

CSC 480 - Software Engineering 109/6/2002

Sequence Diagram

CSC 480 - Software Engineering 119/6/2002

Collaboration Diagram

CSC 480 - Software Engineering 129/6/2002

Statechart Diagram

CSC 480 - Software Engineering 139/6/2002

Case Study

The PunchIn program from chapter 14Programming & Problem Solving with C++

Dale, Weems, and Headington Classes used

TimeTimeCardTCList