SADM 7/ed – ESSS CASE STUDY - Milestone 12: Object Design Solution
Page: 12-1
ESSS
MILESTONE 12 – OBJECT DESIGN
 Design Use Case
A sample design use case has been provided. Design use cases should contain implementation
details such as messages, controls, attribute names, and the like. Most likely you will receive
many different answers, each based on how the student would implement the use case in a GUI
environment. You can limit the range of responses by providing additional details and
constraints.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 7ed
by J. L. Whitten & L. D. Bentley,
Copyright Irwin/McGraw-Hill 2007
SADM 7/ed – ESSS CASE STUDY - Milestone 12: Object Design Solution
Page: 12-2
Employee Self Service System
Author:__Kira Webster
Use-Case Name:
Use-Case ID:
Priority:
Source:
Primary System Actor:
Primary Business Actor:
Other Participating Actors:
Other Interested
Stakeholders:
Description:
Precondition:
Trigger:
Typical Course Of Events:
Alternate Courses:
Conclusion:
Postcondition:
Business Rules:
Implementation
Constraints and
Specifications:
Assumptions:
Open Issues:
Search Employee Directory
ESSS-001D
High
Requirement – MSS-R1.00
Requirements Use Case ESSS-001
Employee
Employee
None
Management
Date:__05/29/06_
Use Case Type
Business Requirements 
System Analysis:

System Design:

This use case describes the event of searching the employee directory.
The user must have previously logged on.
The use case is initiated when the user selects this option from the user interface.
Actor Action
System Response
Step 1: This use case is initiated
Step 2: The system displays web page dir_search
when a user selects the option to
with text boxes for first name, last name, job title,
search the employee directory from
and supervisor and dropdowns with lists of
the web page home.
departments and building. The user can use any
of these controls to enter search criteria. There is
also a Cancel button to cancel the search.
Step 3: The user will fill in search
criteria for one or more of the onscreen options and clicks the
Submit button.
Step 4: The system displays dir_result, which lists
the name, department, and job title for all
employees matching the criteria. A "view detail"
hyperlink is displayed beside each employee in
the list. There is also a hyperlink back to
dir_search.
Step 5: User clicks a "view detail"
link for an employee.
Step 6: The system will display dir_detail with the
phone number, employee's office location,
department, job title, mail stop, and supervisor.
The screen will include hyperlinks to return to
dir_result and dir_search.
Step 7: The user views the
information on the selected
employee and exits the use case.
Alt Step 3a: If the user cancels the search, the use case will exit.
Alt Step 4a: If no employees match the criteria, the system will display a message
informing the user and then return to step 2.
Alt Step 5a: If the user selects the option to return to the search screen, the use case
returns to step 2.
Alt Step 7a: If the user selects the option to return to the list of employees, the use case
returns to step 4.
Alt Step 7b: If the user selects the option to return to the search screen, the use case
returns to step 2.
This use case concludes when the user cancels the search or exists the detailed
information screen.
None
None
The selected architecture will employ an Oracle back-end database and a front-end Java
web application running over the Internet for remote access.
None
None
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 7ed
by J. L. Whitten & L. D. Bentley,
Copyright Irwin/McGraw-Hill 2007
SADM 7/ed – ESSS CASE STUDY - Milestone 12: Object Design Solution
Page: 12-3
 Sequence Diagram
Student answers will vary depending on assumptions and decisions concerning object responsibility. One answer is shown below. This
solution has been simplified by leaving off:
 Most return messages
 Housekeeping behaviors, such as the open behavior for each interface
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 7ed
by J. L. Whitten & L. D. Bentley,
Copyright Irwin/McGraw-Hill 2007
SADM 7/ed – ESSS CASE STUDY - Milestone 12: Object Design Solution
Page: 12-4
 Partial Design Class Structure Diagram
A sample solution is shown below. Student solutions will vary depending on their sequence
diagrams. They should include all interface and controller objects identified in the sequence diagram
and assign behaviors to objects consistent with the sequence diagram.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 7ed
by J. L. Whitten & L. D. Bentley,
Copyright Irwin/McGraw-Hill 2007
SADM 7/ed – ESSS CASE STUDY - Milestone 12: Object Design Solution
Page: 12-5
 State Machine Diagram
A sample solution is shown below. Student solutions will vary depending on assumptions.
Prepared by Gary B. Randolph for
Systems Analysis & Design Methods 7ed
by J. L. Whitten & L. D. Bentley,
Copyright Irwin/McGraw-Hill 2007