Scribd
Upload
77 views23 pages

Library Presentation

The document summarizes a library management system created by a group of students. It includes an introduction describing the basic functions of a library management system. It then lists some key functional requirements like allowing librarians to login, update member information and book details. It also discusses some non-functional requirements around performance, security, software quality and safety. An entity relationship diagram and use case diagram are presented to model the data and interactions. The presentation concludes by thanking the audience.

Uploaded by

ThànhTaku
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
77 views23 pages

Library Presentation

The document summarizes a library management system created by a group of students. It includes an introduction describing the basic functions of a library management system. It then lists some key functional requirements like allowing librarians to login, update member information and book details. It also discusses some non-functional requirements around performance, security, software quality and safety. An entity relationship diagram and use case diagram are presented to model the data and interactions. The presentation concludes by thanking the audience.

Uploaded by

ThànhTaku
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

Library

Management
System
Group Member

Nguyễn Đỗ Cường ITITIU16076

Lê Hoàng Phú Thành ITITIU18239

Nguyễn Trần Duy Thanh ITITIU18220


INTRODUCTION

• A library management system, also known as an


automated library system is software that has been
developed to handle basic housekeeping functions of
a library. It’s a well organized software solution for a
library. It help to provide information on any book
present in library to the user as well as staff member.
FUNCTIONAL REQUIREMENTS
FUNCTIONAL REQUIREMENTS

Some of the functional requirements of our system


are:
Librarian Librarian can login and access the required information
Login
Update
Librarian can update the fine, the number of books issued, any
member change in personal details of member.
infomation
Update Librarian can add new book details and can also change
book the status of the book (whether it is available or not).
details
NON FUNCTIONAL REQUIREMENTS
1. Performance Requirement

• The performance of the our system is fast and accurate.


• This system can handle expected and non-expected errors
in ways that prevent loss.
• Our system is able to handle large amount of data. Thus it
can accommodate high number of books and users
without any fault.
2. Security Requirements
• Our system will use secured database.
• Normal users can just read information but they cannot
edit or modify anything except their persona and some
other information.
• Every user of the system has access constraints.
3. Software Quality Attributes

• Our project is open source.


• The Quality of the database is maintained in such a way so
that it can be very user friendly to all the users of the
database.
• The users are able to easily download and install the
system.
4. Safety Requirements

• The database may get crashed at any certain time due to


virus or operating system failure.
• Therefore, it is required to take the database backup so that
the database is not lost.
• System use shall not cause any harm to human users.
ENTITY RELATIONSHIP DIAGRAM
ENTITY RELATIONSHIP DIAGRAM

• An entity-relationship diagram (ERD) is a data modeling technique that


graphically illustrates an information system's entities and the
relationships between those entities. An ERD is a conceptual and
representational model of data used to represent the entity framework
infrastructure.
• An Entity Relationship Diagram (ERD) is a snapshot of data structures.
• An ERD(Entity Relationship Diagram) shows entities tables in a database
and relationships between tables within that database.
ENTITY RELATIONSHIP DIAGRAM
USE - CASE DIAGRAM
USE-CASE DIAGRAM

• Used to gather requirements of a system.


• Used to get an outside view of a system.
• Identify external and internal factors influencing the
system.
• Show the interacting among the requirements are actors.
USE-CASE DIAGRAM
Use case 1: Register an account
Use case 2: Log in
Use case 3: Book Searching
Use case 4 : Mana ge Books
MODULES

• LOGIN
• SIGNUP
• BOOKS
• BOOK SEARCH
Thank you for listening to my
presentation

You might also like