Case1-BObjectDesign

SADM 5/ed - CASE STUDY 1 - Milestone B: Object DesignPage: B-4 MILESTONE B OBJECT DESIGN This milestone is only feasible if combined with Milestone A.: SynopsisIn performing object-oriented analysis (Milestone A) we identified objects and use cases based on ideal conditions and independent of any hardware or software solution. During object-oriented design we want to refine those objects and use cases to reflect the actual environment of our proposed solution.In this milestone you will first transform the use case course of events prepared in Milestone A to be a design use case. Secondly, we update our object class structure diagram to include any additional attributes we have discovered. Finally, we will create an ideal object diagram that models the object interactions for each use case.: ObjectivesAfter completing this milestone, you should be able to Transform an analysis use case to a design use case. Construct an ideal object model diagram to model the high-level object interactions for a use case. Construct a sequence diagram to model the detailed object interactions. Revise an object class diagram to include methods and any additional attributes and relationships.: PrerequisitesBefore starting this milestone the following topics should be covered:1. Object-oriented design Module B.2. Milestone A solution.: AssignmentThe three general activities when performing object-oriented design are as follows:1. Refine the use case model to reflect the implementation environment.2. Model object interactions and behavior that support the use case scenarios.3. Update the object class diagram to reflect the implementation environment.: Activities1. Transform the analysis use cases (from Milestone A) to design use cases. For the scenario of the candidate being a past employee, document those steps in an extension use case. Make assumptions where necessary. 2. Construct an ideal object model diagram. Make assumptions where necessary.3. Construct a sequence diagram for the scenario of the use case, which looks to see if an employee record already exists, and if so displays the information. Make assumptions where necessary.4. Document the object methods listed in Exhibit B.1. Also, update the class diagram to include full-time and part-time employees. Exhibit B.1 includes attributes for those objects. Make the necessary changes to the object class diagram to reflect the proposed environment.Your instructor will specify the deliverable format and software to be used. Deliverables should be neatly packaged in a binder, separated with a tab divider labeled “Milestone B,” and accompanied with a Milestone Evaluation Sheet.References:Milestone A SolutionProvided by your instructor.Design notesExhibit B.1TemplatesSee the online learning center website for the textbook.Deliverables:Design Use Case:Due: _/_/_Time:_Ideal Object Model Diagram:Due: _/_/_Time:_Sequence Diagram:Due: _/_/_Time:_Refined Object Class Diagram:Due: _/_/_Time:_Milestones Point Value:_: Exhibit B.1Update the class diagram to include the following methods: isEmployee reportEmployee setEmployeeStatus setEmployeeProfile reportActivity reportOrganization reportDepartment listDepartmentEmployeesUpdate the class diagram to include the following attributes:Employee Current Annual SalaryNine-digit field that includes two decimal points, consisting of a full-time employees annual salaryEmployee Hourly RateSix-digit field that includes two decimal points, consisting of a part-time employees hourly rate. Number of Hours ScheduledTwo-digit numeric field consisting of the number of hours a part-time employee is scheduled to work per