Library Management System: Database Project - Part II - Functional & Non Functional Requirements

  LMS
  Library Management System for Imaginary University
  2nd year Database Project



Functional Requirements

 Administrator
  • Add/delete/update details of a member for the library staff.
  • Add/remove/change privileges of library staff to access the system
  • All functionalities of an operator ( mentioned below )
Operator
  • Add/delete/update book details (location)
  • Issue/accept lent books
  • Issue fine receipts
Member
  • Search books (for location, availability, other related books, etc.)
  • Check user history
Guest
  •  only allowed to view data about resources available in the library



Non Functional Requirements

Data validation
Data validation is having valid data for a given type of variable. Data must be validated to ensure the consistency of data.

Security
The security to the data base from unauthorized access is prevented by proper authentication giving access privileges for users. In addition security from SQL injection is prevented at the implementation using HTML methods and php (eg: using php function like mysql_real_escape_string(trim($variable) )

Performance
Both the throughput and low response time is achieved by making proper views and indices. They are explained later in the report.


 Usability
User friendly interfaces are provided. Also in order to prevent mistakes from users proper warnings and alerts are implemented.



Comments

Post a Comment

Popular posts from this blog

Library Management System: Database Project - Part III - Database Design

Image
  LMS   Library Management System for Imaginary University    2nd year Database Project There are Four main entities Item : a book or as CD which can be borrow from the library Member : a registered member of the library who will be a student or a staff member Location : the physical location where an item is stored in the library Operator : a library staff member who will interact with members of the library. That is they will add/update data about members, transactions and items in the library Entity Relationship Diagram (ER Diagram) ER diagram There can be many copies of the same item (Book or CD). However since we need to identify each item separately so that each of them are given a unique id which is the 'item_id'. Storing common details of the same copies of items make redundancy, the details of items are decomposed into separate tables named 'book_details' and 'CD_details'. A member can borrow four books (or CDs) at a time and
Read more

Library Management System: Database Project - Part I - Introduction

Image
  LMS   Library Management System for Imaginary University    2nd year Database Project Database management is a wide area of computer science which is essential in most of the applications in order to store and handle data proper and efficient way. Library management system is one of a most frequently used application of database management systems where there is a chunk of information to store and record daily. Background University of ABC is a imaginary university of about 12000 students and 1000 of staff. The library system of the university facilitates all students, academic and non academic staff by providing access to the library. Anyone of the university can read books or other documents at the library, but in order to borrow them one should register and get the membership. The membership is valid only for a year and that should be updated afterwards. After getting the membership, a member can borrow 4 books at a time and maximum burrowed period is 2 weeks. Users
Read more

Library Management System: Database Project - Part V - Finalize Database

Image
  LMS   Library Management System for Imaginary University    2nd year Database Project In order to maximize the use of system resources to perform work as efficiently and rapidly as possible the views and indices to be used were confirmed and some of the views were decided to materialize. In the application a user can search a book based on its authors, title and subject as well as ISBN number. Therefore by creating indices on tilte, authors and subjects the database can access relevant entries more efficiently. Since the table book_details is not updated frequently this will not cause for any low performance of the database. book_details create index book_title on book_details(title); create index book_publisher on book_details(publisher); create index book_category on book_details(category); cd_details create index cd_title on cd_details(title); create index cd_publisher on cd_details(publisher); create index cd_category on cd_details(category); borrows create
Read more