Use Case Diagram

Functional and Non Functional Requirements

Functional Requirements

Librarian

• Add book: New entries must be entered in the database.
• Update book: Any changes in books should be updated.
• Remove book: Wrong entry must be removed from the system.
• Return book:librarian can add return books in stocks means student books return functionalities.
• Search book: librarian can search any book.

Member

• Search book: User can search any book.
• Borrow book: Student can borrow the book.

Non Functional Requirements

Performance requirements

• System should be fast and accurate.
• System should be able to handle large amount of data.
• It should handle expected and unexpected errors to prevent the loss of data from the system.

Safety requirements

• It is required to take a database backup to handle database crash that may occur due to virus or Operating System failure.

Security requirements

• System will use secure database.
• Normal users can just read information but they cannot edit or modify anything.
• Every user has access constraints.
• Proper user authentication should be provided.
• No one should be able to hack users' passwords.
• There should be separate accounts for librarian(admin) and members.

Usability

• Quality of system is maintained in such a way it can be user friendly.
• It is required to have a proper user interface.
• There should be user manual, help to guide.