SADM 7/ed - ESSS CASE STUDY - Milestone 7: Object Analysis Solution Page: 7-4

MILESTONE 7 – OBJECT MODELING

:  Activity Diagram

Answers could vary depending on student assumptions. One solution is shown below.

:  System Sequence Diagram

Below is one solution for one scenario of the use case. Answers may vary. Check for proper UML notation of the input messages as well as for the logic of the diagram.

:  Potential Object List

Again, answers could vary somewhat depending on student assumptions, although the objects and their relationships should be fairly clear from the list.

Potential Object / Notes / Obj / Reason
Annual Salary / The yearly salary of a salaried employee. / X / Attribute of SalaryEmployee
Building / A building where employees work in various rooms. / √
Calendar Year / The year for which a United Way contribution applies. / X / Attribute of UnitedWayContribution
Contact Address / The street address, city, state, and zip of an emergency contact. / X / Attributes of EmergencyContact
Contact Home Phone / The home phone number of an emergency contact. / X / Attribute of EmergencyContact
Contact Name. / The first name, middle name, and last name of an emergency contact. / X / Attributes of EmergencyContact
Contact Work Phone / The work phone number of an emergency contact. / X / Attribute of EmergencyContact
Contract Employee / A temporary employee. / √
Department / An organizational grouping of employees that fulfills a business function. / √
Dept ID / An abbreviated identifier for a department.. / X / Attribute of Department
Dept Name / The full name of a department. / X / Attribute of Department
DOB / An employee's date of birth. / X / Attribute of Employee
Emergency Contact / A person who should be contacted concerning a particular employee in case of emergency / √
Emp ID / A unique, sequentially-assigned identifier for an employee. / X / Attribute of Employee
Employee / A person who works for the organization. / √
Employee Address / The street address, city, state, and zip of an employee. / X / Attribute of Employee
Employee Home Phone / The home phone number of an employee. / X / Attribute of Employee
Employee Name / The first name, middle name, last name, and nickname of an employee. / X / Attribute of Employee
Employee Office Phone / The office phone number of an employee. / X / Attribute of Employee
Hire Date / The date an employee was hired. / X / Attribute of Employee
Hourly Employee / An employee who is paid a hourly wage. / √
Hourly Wage / The hourly wage of an hourly employee or a contract employee. / X / Attribute of HourlyEmployee and ContractEmployee
Job Title / An employee's job title. / X / Attribute of Employee
Life Insurance / A miscellaneous deduction. / X / An instance of MiscDeduction
Location / Where an employee can be found. / X / Synonym for room, building, and site.
Mail Stop / A room or an area of an office where employees can go and retrieve their mail. / √
Marital Status / The marital status (married, single) of an employee. / X / Attribute of Employee
Maximum Weekly Hours / The maximum hours per week that is scheduled for each hourly employee. / X / Attribute of HourlyEmployee
Misc Deduction / A Miscellaneous Deduction elected by an employee. / √
Permanent Employer / The permanent employer of a contract employee. / X / Attribute of ContractEmployee
Request Date / The date of a Miscellaneous Deduction request. / X / Attribute of MiscDeduction
Room / A room where employees may work. / √
Salary Employee / An employee who is paid a salary. / √
Site / A company location consisting of one or more buildings. / √
SSN / An employee's Social Security Number. / X / Attribute of Employee
Supervisor / An employee's supervisor / X / Attribute of Employee.
United Way Contribution / A contribution pledged to the United Way by an employee. / √

:  Class Diagram

Again, answers could vary depending on student assumptions. One solution is shown below.

·  Class diagrams should not include foreign key attributes. Foreign key is a relational database concept that is not used in object-oriented analysis.

·  A case could be legitimately made that an aggregation relationship exists between Department and Employee. The difference between an aggregation and a regular association is often a judgment call. It would not be a composition relationship because departments do not (in a literal sense) create or destroy their employees.

·  Site, Building, and Room have a natural composition relationship. If a site was purchased, all of its buildings would be added to the system. If a building was torn down, all of its rooms would be destroyed.

Prepared by Gary B. Randolph for

Systems Analysis & Design Methods 6ed

by J. L. Whitten, L. D. Bentley, & K. C. Dittman Copyright Irwin/McGraw-Hill 2004