DOC

MaintainProfessorInfo

By Terry Long,2014-03-20 22:14
96 views 0
MaintainProfessorInfo

OOAD v4.2 Version: 4.2

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

    9360047.doc

1. Maintain Professor Information

    1.1 Brief Description

    This use case allows the Registrar to maintain professor information in the registration system. This

    includes adding, modifying, and deleting professors from the system.

    1.2 Flow of Events

    1.2.1 Basic Flow

    This use case starts when the Registrar wishes to add, change, and/or delete professor information in the

    system.

    1. The system requests that the Registrar specify the function he/she would like to perform (either Add a

    Professor, Delete a Professor, or Delete a Professor)

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

    If the Registrar selected “Add a Professor“, the Add a Professor subflow is executed.

    If the Registrar selected “Update a Professor “, the Update a Professor subflow is executed.

    If the Registrar selected “Delete a Professor “, the Delete a Professor subflow is executed.

    1.2.1.1 Add a Professor

    1. The system requests that the Registrar enter the professor information. This includes:

    name

    date of birth

    social security number

    status

    department

    2. Once the Registrar provides the requested information, the system generates and assigns a unique id

    number to the professor. The professor is added to the system.

    3. The system provides the Registrar with the new professor id.

    1.2.1.2 Update a Professor

    1. The system requests that the Registrar enter the professor id.

    2. The Registrar enters the professor id. The system retrieves and displays the professor information.

    3. The Registrar makes the desired changes to the professor information. This includes any of the

    information specified in the Add a Professor sub-flow.

    4. Once the Registrar updates the necessary information, the system updates the professor record. 1.2.1.3 Delete a Professor

    1. The system requests that the Registrar enter the professor id

    2. The Registrar enters the professor id. The system retrieves and displays the professor information.

    1. The system prompts the Registrar to confirm the deletion of the professor.

    2. The Registrar verifies the deletion.

    3. The system deletes the professor from the system.

    Confidential Page 1 ;Rational Software, 1999

OOAD v4.2 Version: 4.2

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

    9360047.doc

1.2.2 Alternative Flows

    1.2.2.1 Professor Not Found

    If in the Update a Professor or Delete a Professor sub-flows, a professor with the specified id number

    does not exist, the system displays an error message. The Registrar 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 A Professor sub-flow, the Registrar decides not to delete the professor, the delete is

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

    1.3 Special Requirements

    None.

    1.4 Pre-Conditions

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

    If the use case was successful, the professor 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