OOAD——Use-Case Diagram of Library System and Requirement Analysis

Lab1:https://blog.csdn.net/qq_43629690/article/details/91492306

1. 用况图

2.需求分析

1. G-Map
   1.1 Brief Description
   This use case allows a student to gain the panorama of the library.
   1.2 Flow of Events
   1.2.1 Basic Flow
   This use case starts when a student wishes to sign up to the system and want to get the map of the library.
   1. When actors have logged onto the system, the system retrieves and displays the list of function menu which includes the function that display the panorama of the library.
   2. The visitors of the library choose the function what is gaining the map.
   3. The system verifies the operation and display the map of the library on the screen.
      1.2.2 Alternative Flows
      None
      1.3 Special Requirements
      None.
      1.4 Pre-Conditions
      The register must be logged onto the system before this use case begins.
      1.5 Post-Conditions
      If the use case was successful, the actor is now logged into the system. If not, the system state is unchanged.
      1.6 Extension Points
      None.

2.L-information
2.1 L-Information
This use case allows the manager of the library to change and check the lending-condition about the library on the system.
2.2 Flow of Events
2.2.1 Basic Flow
This use case starts when a manager wishes to register for lending-condition, or to change all existing book lending-condition.
1. The system requests that the manager login in system and choose function from menu in screen.
2. If the manager select the function ‘display the lending-information’,the system will display the all books’ lending-information on screen.
2.2.2 Alternative Flow
None.
2.3 Special Requirements
None.
2.4 Pre-Conditions
The manager must be logged onto the system before this use case begins.
2.5 Post-Conditions
If the use case was successful, the lending-information schedule is created, updated, or deleted. Otherwise, the system state is unchanged.
2.6 Extension Points
None.

3.Login
3.1 Brief Description
This use case allows the Registrar to login the system and choose the different function from the menu.
3.2 Flow of Events
3.2.1 Basic Flow
This use case starts when the Registrar has logged in the system successfully to choose different function from the menu.
1. The system requests that the Registrar input special information to log in system.
2. Then the screen display the function menu to registers.
3.2.2 Login
When register click the function Login, the system call the relevant class and function about ‘Login’.
3.2.2.1 Get User
When register click the function Login, the system call the relevant class and function about ‘Get User’.
3.2.2.2 Get Map
When register click the function Login, the system call the relevant class and function about ‘Get Map’.
3.2.2.3 Get Book
When register click the function Login, the system call the relevant class and function about ‘Get Book’.
3.2.2.4 Get Information
When register click the function Login, the system call the relevant class and function about ‘Get Information’.
3.2.3 Alternative Flows
None
3.3 Special Requirements
None.
3.4 Pre-Conditions
The Registrar must be logged onto the system before this use case begins.
3.5 Post-Conditions
If the use case was successful, the register information will be entering system.But if register type the wrong login information, the system will display the wrong message in the screen.
3.6 Extension Points
None.

4. Managers
   4.1 Brief Description
   This use case allows a Registrar to choose user’s identity as manager. Different registers can choose different function.
   4.2 Flow of Events
   4.2.1 Basic Flow This use case starts when the Registrar login the system and will set register’s identity based on the typing number.

   1. The system checks to see if registration is in progress. If it is, then a message is displayed to the Registrar and display register’s identity.
   2. When the register successfully login the library system, the system will display the relevant function menu in the screen based on register’s position.
      4.2.2 Alternative Flows
      4.2.2.1 Error Message
      If register import the id is not the manager id, the system will output the error message on the screen.
      4.3 Special RequirementsNone.
      4.4 Pre-Conditions
      The Registrar must input id into the system in order for this use case to begin to login successfully.
      4.5 Post-Conditions
      If the use case was successful, register successfully login in system by manager identity. If not, the system will refuse register’s logging operation.
      4.6 Extension Points
      None.

5. Query
   5.1 Brief Description
   This use case allows the Registrar to maintain book information in the library system.
   5.2 Flow of Events
   5.2.1 Basic Flow
   This use case starts when the Registrar wishes to borrow, return, and/or renew book information in the system.

   1. The system requests that the Registrar specify the function he/she would like to perform (either Borrow a Book, Return a Book, or Renew a Book)
   2. Once the Registrar provides the requested information, one of the subflows is executed.
      If the Registrar selected “Add a Professor“, the Borrow a Book subflow is executed.
      If the Registrar selected “Update a Professor “, the Return a Book subflow is executed.
      If the Registrar selected “Delete a Professor “, the Renew a Book subflow is executed.
      5.2.1.1 Borrow a Book
   3. The system requests that the Registrar enter the Book Id.
   4. The Registrar enters the Book Id. The system retrieves and displays the Book information.
   5. The Registrar makes the desired changes to the book information. This includes any of the information specified in the Add a Book sub-flow.
   6. Once the Registrar updates the necessary information, the system updates the Book record of the register.
      5.2.1.2 Return a Book
      1.The system requests that the Registrar enter the Book Id.
      2.The Registrar enters the Book Id. The system retrieves and displays the Book information.
      3.The Registrar makes the desired changes to the book information. This includes any of the information specified in the Return a Book sub-flow.
      4.Once the Registrar updates the necessary information, the system updates the Book record of the register.
      5.2.1.3 Renew a Book
      1.The system requests that the Registrar enter the Book Id.
      2.The Registrar enters the Book Id. The system retrieves and displays the Book information.
      3.The Registrar makes the desired changes to the book information. This includes any of the information specified in the Renew a Book sub-flow.
      4.Once the Registrar updates the necessary information, the system updates the Book record of the register.
      5.2.2 Alternative Flows
      5.2.2.1 Book Not Found
      If in the Borrow a Book or Return a Book sub-flows, a professor with the specified Book id 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.
      5.2.2.2 Return Cancelled
      If in the Return A Book sub-flow, the Registrar decides not to return the book, the return is cancelled and the Basic Flow is re-started at the beginning.
      5.3 Special Requirements
      None.
      5.4 Pre-Conditions
      The Registrar must be logged onto the system before this use case begins.
      5.5 Post-Conditions
      If the use case was successful, the book information is borrowed, returned, or renewed from the system. Otherwise, the system state is unchanged.
      5.6 Extension Points
      None.

6. Students
   6.1 Brief Description
   This use case allows a Registrar to choose user’s identity as student. Different registers can choose different function.
   6.2 Flow of Events
   6.2.1 Basic Flow
   This use case starts when the Registrar login the system and will set register’s identity based on the typing number.

   1. The system checks to see if registration is in progress. If it is, then a message is displayed to the Registrar and display register’s identity.
   2. When the register successfully login the library system, the system will display the relevant function menu in the screen based on register’s position.
      6.2.2 Alternative Flows
      None.
      6.2.2.1 Error Message
      If register import the id is not the student id, the system will output the error message on the screen.
      6.3 Special Requirements
      None.
      6.4 Pre-Conditions
      The Registrar must input id into the system in order for this use case to begin to login successfully.
      6.5 Post-Conditions
      If the use case was successful, register successfully login in system by manager identity. If not, the system will refuse register’s logging operation.
      6.6 Extension Points
      None.