DOC

MaintainEmployeeInfo

By Rose Campbell,2014-08-10 00:25
77 views 0
MaintainEmployeeInfo

OOAD v4.2 Version: 4.2

    Maintain Employee Information Use Case Specification Issue Date: 12/July/1999

    9360034.doc

1. Maintain Employee Information

    1.1 Brief Description

    This use case allows the Payroll Administrator to maintain employee information. This includes adding,

    changing, and deleting employee information from the system.

    1.2 Flow of Events

    1.2.1 Basic Flow

    This use case starts when the Payroll Administrator wishes to add, change, and/or delete employee

    information from the system.

    1. The system requests that the Payroll Administrator specify the function he/she would like to perform

    (either Add an Employee, Update an Employee, or Delete an Employee)

    2. Once the Payroll Administrator provides the requested information, one of the subflows is executed.

    If the Payroll Administrator selected “Add an Employee“, the Add an Employee subflow is executed.

    If the Payroll Administrator selected “Update an Employee“, the Update an Employee subflow is

    executed.

    If the Payroll Administrator selected “Delete an Employee“, the Delete an Employee subflow is

    executed.

    1.2.1.1 Add an Employee

    1. The system requests that the Payroll Administrator enter the employee information. This includes:

    name

    employee type (hour, salaried, commissioned)

    mailing address

    social security number

    standard tax deductions

    other deductions (401k, medical)

    phone number

    hourly rate (for hourly employees)

    salary (for salaried and commissioned employees)

    commission rate (for commissioned employees)

    hour limit (some employees may not be able to work overtime)

    2. Once the Payroll Administrator provides the requested information, the system generates and assigns a

    unique employee id number to the employee and sets the pay check delivery method to default of

    “pickup”. The employee is added to the system.

    3. The system provides the Payroll Administrator with the new employee id.

    1.2.1.2 Update an Employee

    1. The system requests that the Payroll Administrator enter the employee id.

    2. The Payroll Administrator enters the employee id. The system retrieves and displays the employee

    information.

    3. The Payroll Administrator makes the desired changes to the employee information. This includes any

    of the information specified in the Add an Employee sub-flow.

    4. Once the Payroll Administrator updates the necessary information, the system updates the employee

    record with the updated information.

    Confidential Page 1 ;Rational Software, 1999

OOAD v4.2 Version: 4.2

    Maintain Employee Information Use Case Specification Issue Date: 12/July/1999

    9360034.doc

1.2.1.3 Delete an Employee

    1. The system requests that the Payroll Administrator specify the employee id.

    2. The Payroll Administrator enters the employee id. The system retrieves and displays the employee

    information.

    3. The system prompts the Payroll Administrator to confirm the deletion of the employee.

    4. The Payroll Administrator verifies the deletion.

    5. The system marks the employee record for deletion. The next time the payroll is run, the system will

    generate a final paycheck for the deleted employee and remove the employee from the system. 1.2.2 Alternative Flows

    1.2.2.1 Employee Not Found

    If in the Update an Employee or Delete an Employee sub-flows, an employee with the specified id

    number does not exist, the system displays an error message. The Payroll Administrator can then enter a

    different id number or cancel the operation, at which point the use case ends. 1.2.2.2 Delete Cancelled

    If in the Delete An Employee sub-flow, the Payroll Administrator decides not to delete the employee, the

    delete is cancelled and the Basic Flow is re-started at the beginning.

    1.3 Special Requirements

    None.

    1.4 Pre-Conditions

    The Payroll Administrator must be logged onto the system before this use case begins. 1.5 Post-Conditions

    If the use case was successful, the employee information is added, updated, or deleted from the system.

    Otherwise, the system state is unchanged.

    1.6 Extension Points

    None.

    Confidential Page 2 ;Rational Software, 1999

Report this document

For any questions or suggestions please email
cust-service@docsford.com