The document discusses object oriented analysis and design (OOA/OOD) processes and concepts. It then provides an example case study of analyzing and modeling the timekeeping system for a grocery store chain. Key aspects of the case study include identifying relevant classes like Employee, TimekeepingEvent, and PayPeriod, defining their attributes and relationships, and creating conceptual models, use cases, sequence diagrams, and state diagrams.

1. Object Oriented Analysis & Design

9. Requirement Matrix As we develop some use cases, you can expect to discover additional required functions

11. High Level Essential Use Cases A common use case:

12. High Level Essential Use Cases Course of Events: Tracking the course of even we can see another requirement we didn’t document yet: R1.3 The times displayed and recorded by different timekeeping terminals must be within 5 seconds of each other

16. A Conceptual Model PayPeriod Timekeeper Employee Break Supervisor Timekeeping Event Shift EmployeeBadge TimekeepingLog TimekeepingSystem EmployeeID TimekeepingReport PayrollSystem

17. A Conceptual Model - with associations PayPeriod Timekeeper Employee Break Supervisor Timekeeping Event Shift EmployeeBadge TimekeepingLog TimekeepingSystem EmployeeID TimekeepingReport PayrollSystem Is-A Uses Modifies Creates Is-part-of Is-A Owns Modifies Belongs-to Uses Is-part-of Is-part-of Contains possession owner user usee creator createe part whole part whole part whole user usee 1 1 1 0..* 0..* 0..* 1 1 1 0..* 0..* 1 1 1 0..1 2

18. A Conceptual Model - with attributes TimekeepingEvent PayPeriod Timekeeper Employee Break Supervisor Shift EmployeeBadge TimekeepingLog TimekeepingSystem employeeID TimekeepingReport PayrollSystem Is-A Uses Modifies Creates Is-part-of Is-A Owns Modifies Belongs-to Uses Is-part-of Is-part-of Contains possession owner user usee creator createe part whole part whole part whole user usee 1 1 1 0..* 0..* 0..* 1 1 1 0..* 0..* 1 1 1 0..1 2 when:time start:time end:time

24. Detailed Use Cases A common use case:

25. High Level Essential Use Cases Course of Events: This use case involves classes that are not in the previous class diagram - a timekeeping terminal’s user-interface, which in turn be further broken down to other classes.

27. Class Diagram - Ver. 3 TimekeepingEvent START_SHIFT:int = 0 {frozen} START_BREAK:int = 1 {frozen} END_SHIFT:int = 2 {frozen} END_BREAK:int = 3 {frozen} getEmployee():Employee getTime():Date createEvent(eventType:int):TimekeepingEvent Timekeeper Supervisor PayPeriod getStart():Date getEnd():Date Break Shift TimekeepingLog TimekeepingReport PayrollSystem Uses-symbolic-names-defined-by Uses Request- event-object-creation Stores-and-fetches-data-for Plays-role Plays-role role role player player 1 1 1 1 1 1 1 1 1 0 1 0 requestor creator UserInterface getEventType():int TimekeepingController doTransaction(employeeID:String) Database lookupEmployee(employeeID:String):Employee storeEvent(event:TimekeepingEvent) Employee getEmployeeID():String

29. State Diagrams (cont’) StartPayPeriod StartPayPeriod Enter / incompleteShift=false startTime=event.getTime() StartBreak Enter / breakTime=event.getTime() EndBreak Enter / unpaidHours += event.getTime()- breakTime regularHours -= eventTime()-breakTime EndShift Enter / regularHours += event.getTime()-startTime if (regularHours>40) { overtimeHours += regularHours - 40; regularHours = 40; } regularPay = regularHours * payRate; overtimePay = overtimeHours * payRate * 1.5; createShift(); regularHours=0; overtimeHours=0; unpaidHours=0; regularPay=0; overtimePay=0; StartShift StartBreak EndBreak StartBreak EndShift StartShift EndShift