Scribd
Upload
13 views5 pages

FPT University Book Manager System

This document outlines the key objects and functional requirements for a book management system project. It defines the human objects like administrator, manager, librarian, and reader along with non-human objects like books and categories. It then lists the functional requirements including login/logout, viewing details, searching books, adding/removing books. Finally, it evaluates the use case relationships for include, extend, and generalizations and provides a use case diagram for the system.

Uploaded by

Nguyễn Hưng
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
13 views5 pages

FPT University Book Manager System

This document outlines the key objects and functional requirements for a book management system project. It defines the human objects like administrator, manager, librarian, and reader along with non-human objects like books and categories. It then lists the functional requirements including login/logout, viewing details, searching books, adding/removing books. Finally, it evaluates the use case relationships for include, extend, and generalizations and provides a use case diagram for the system.

Uploaded by

Nguyễn Hưng
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

FPT UNIVERSITY

ASSIGNMENT PROJECT DOCUMENT


-----------------------------

BOOK MANAGER
SYSTEM

Student: Pham Ngoc Hoa | SE05740


Student: Do Quang Hiep | SE05627
Student: Tran Quang Nhat | SE05439
Student: Do Ngoc Hai | SE05745
Student: Trinh The Hoan | SE05537
Instructor: Tran Dinh Tri
Courses: SWE102
I. DEFINE HUMAN OBJECTS AND NO-HUMAN
OBJECTS

Object Role Functionalities


Administrator - Manage account
Manager - Manage Books
- Manage Librarian
- View account detail (Manager, Librarian)
Librarian - Search/Edit/View book
- Add/ Cancel book borrowing
Human - Penalties for returning books late
Object - View student detail
- Check book is booked
Reader - View account detail
- Search books
- Borrow books
- View borrowed books
- Send feedback, Q&A

Books - Display detail


Non - Categories - Filter by ( publisher, language, faculties,
Human semester )
Object Penalty - Filter by Penalty

II. LIST ALL FUNCTIONAL AND REQUIREMENTS

1. Actors of the Library Management System


1.1. Administrator
1.2. Manager
1.3. Librarian
1.4. Student

2. Functionalities of Library Management System


2.1. Login/Logout
2.2. View User Details
2.3. View Books
2.4. View Members
2.5. Reserve Books
2.6. Search Books
2.7. Add/Remove Books
2.8. Add/Remove User

III. USE CASE DIAGRAMS


4.1 Evaluate use cases for relationship dependency <<include>>
a. Administrator
Admin have a major role in managing the university's accounts. So, they are entitled
to add, edit, delete the account there.

b. Manager
They are responsible for book management and librarian management. So, they are
entitled to add, edit, delete the book the books of library and the tasks for librarians
c. Librarian
They don’t have use cases for relationship dependency <<include>>
d. Reader
They don’t have use cases for relationship dependency <<include>>

4.2. Evaluate use cases for relationship dependency <<extend>>


All of actors don’t have use cases for relationship dependency <<extend>>
4.3. Evaluate use cases for relationship <<generalizations>>
All of actors don’t have use cases for relationship dependency <<generalizations>>

Use Case Diagram Book Manager System

Link view online : [Link]

You might also like