Library management system se project

SUPERIOR UNIVERSITY LAHORE
Faculty of Computer Science & IT
Final Year Project
PROJECT REPORT (Part-1)
[Library Management Sysyem]
Project ID: [write ID here Issued by FYP Manager]
Project Team
Student Name Student ID Program Contact Number Email Address
Rehmat Qadeer Bcsm-f17-260 Bcsm 030464824 Bcsm-f17-260@superior.edu.pk
Farman Tariq Bcsm-f17-278 Bcsm 03024595683 Bcsm-f17-278@superior.edu.pk
[Project Supervisor]
([Designation])

Project Report: < write Project titlehere>
Faculty of CS&IT, Superior University Lahore, Pakistan ii

Faculty of CS&IT, Superior University Lahore, Pakistan iii
rrProject Report
[Title of Project]
Change Record
Author(s) Version Date Notes Supervisor’s Signature
1.0 <Original Draft>
<Changes Based on
Feedback from
Supervisor>
<Changes Based on
Feedback From Faculty>
<Added Project Plan>
<Changes Based on
Feedback from
Supervisor>

Faculty of CS&IT, Superior University Lahore, Pakistan iv
APPROVAL
PROJECT SUPERVISOR
Comments: ___________________________________________________________________
_____________________________________________________________________________
Name:______________________________
Date:_______________________________ Signature:__________________________
PROJECT MANAGER
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________
HEAD OF THE DEPARTMENT
Comments: ___________________________________________________________________
_____________________________________________________________________________
Date:_______________________________ Signature:__________________________

Faculty of CS&IT, Superior University Lahore, Pakistan v
Dedication
This work is dedicated to my . . . . . .

Faculty of CS&IT, Superior University Lahore, Pakistan vi
Acknowledgements
We are thankful to our instructor and also management who gave opportunity us to
make this project. This project improve our searching skills also improve our
analyzing of software requirements and documentation.

Faculty of CS&IT, Superior University Lahore, Pakistan vii
Executive Summary
We are developing Library Management System which will manage and store books
electronically according to the reader's need. It will help both reader and library management to
keep record of their library. It is necessary in almost every college nowadays. In this manager
keep record and organize in different categories which will help in searching. It will reduce
human effort and time.Librarians are increasingly called upon not only to collect information in
electronic form but also to organize it into digital libraries. The materials may be created and
held locally, or they may be created and accessed in a distributed fashion as a virtual library.
Digital libraries can provide material on a variety of topics, from children’s games to high-
energy physics. Their scope may be local, national, or even international; the audience may be a
small group with specialized interests or the broader public. Essential to the successful
implementation and use of any digital library is the organization of that library, either directly or
indirectly, by one or more knowledge organization systems .
Generally, what we see today is the manual library where the process of operation very much
hectic. Students need a lots books for their studies. Students often find problems because books
are limited and only few students can have the books. Students need to fall in line and then ask
for the related title of the books. Issuing of Books is Slow. The issuing of book is slow where
borrowers ( faculty, students, staff and clients) will have to wait for further library transactions.
Time Consuming. The library services in terms of issuing of books through library cards
consumed a lot of time. Lost books. There were books in the library which were not included in
inventory of books per semester. The data of the manual library were not secured with respect to
the confidentiality of reports and documents of library transactions, Lack of Data Storage.

Faculty of CS&IT, Superior University Lahore, Pakistan viii
Table of Contents
Dedication........................................................................................................................................v
Acknowledgements.........................................................................................................................vi
Executive Summary........................................................................................................................vii
Table of Contents..........................................................................................................................viii
List of Figures ...................................................................................................................................x
List of Tables....................................................................................................................................xi
Chapter 1......................................................................................................................................... 1
Introduction .................................................................................................................................... 1
1.1. Background....................................................................................................................... 2
1.2. Motivations and Challenges............................................................................................. 3
1.3. Goals and Objectives........................................................................................................ 5
1.4. Literature Review/Existing Solutions ............................................................................... 5
1.5. Gap Analysis ..................................................................................................................... 6
1.6. Proposed Solution ............................................................................................................ 6
1.7. Project Plan .......................................................................Error! Bookmark not defined.
1.7.1. Work Breakdown Structure .......................................................................................... 7
1.7.2. Roles & Responsibility Matrix....................................................................................... 7
1.7.3. Gantt Chart ................................................................................................................... 7
1.8. Report Outline.................................................................................................................. 8

Faculty of CS&IT, Superior University Lahore, Pakistan ix
Chapter 2......................................................................................................................................... 9
Software Requirement Specifications............................................................................................. 9
2.1. Introduction.................................................................................................................... 10
2.1.1. Purpose....................................................................................................................... 10
2.1.2. Document Conventions .............................................................................................. 11
2.1.3. Intended Audience and Reading Suggestions ............................................................ 11
2.1.4. Product Scope............................................................................................................. 12
2.1.5. References .................................................................................................................. 12
2.2. Overall Description......................................................................................................... 13
2.2.1. Product Perspective.................................................................................................... 13
2.2.2. Product Functions....................................................................................................... 13
2.2.3. User Classes and Characteristics ................................................................................ 13
2.2.4. Operating Environment .............................................................................................. 14
2.2.5. Design and Implementation Constraints.................................................................... 14
2.2.6. User Documentation................................................................................................... 14
2.2.7. Assumptions and Dependencies................................................................................. 15
2.3. External Interface Requirements ................................................................................... 15
2.3.1. User Interfaces............................................................................................................ 15
2.3.2. Hardware Interfaces ................................................................................................... 16
2.3.3. Software Interfaces..................................................................................................... 16
2.3.4. Communications Interfaces........................................................................................ 16
2.4. System Features ............................................................................................................. 16
2.4.1. System Feature 1 ........................................................................................................ 16
2.4.1.1. Description and Priority .......................................................................................... 16
2.4.1.2. Stimulus/Response Sequences ............................................................................... 17
2.4.1.3. Functional Requirements........................................................................................ 17
2.4.2. System Feature 2 ........................................................................................................ 17
2.4.2.1. Description and Priority .......................................................................................... 17
2.4.2.2. Stimulus/Response Sequences ............................................................................... 18
2.4.2.3. Functional Requirements........................................................................................ 18
2.4.3. System Feature 3 (and so on) ..................................................................................... 19
2.5. Other Nonfunctional Requirements .............................................................................. 19
2.5.1. Performance Requirements........................................................................................ 19
2.5.2. Safety Requirements .................................................................................................. 20
2.5.3. Security Requirements................................................................................................ 20
2.5.4. Software Quality Attributes........................................................................................ 21
2.5.5. Business Rules............................................................................................................. 21
2.6. Other Requirements....................................................................................................... 21
Chapter 3....................................................................................................................................... 24
Use Case Analysis.......................................................................................................................... 24
3.1. Use Case Model.............................................................................................................. 25
3.2. Fully Dressed Use Cases................................................................................................. 30
Chapter 4....................................................................................................................................... 38
System Design............................................................................................................................... 38

Faculty of CS&IT, Superior University Lahore, Pakistan x
4.1. Architecture Diagram..................................................................................................... 39
4.2. Domain Model................................................................................................................ 39
4.3. Entity Relationship Diagram with data dictionary ......................................................... 39
4.4. Class Diagram................................................................................................................. 40
4.5. Sequence / Collaboration Diagram...................................Error! Bookmark not defined.
4.6. Operation contracts ....................................................................................................... 42
4.7. Activity Diagram............................................................................................................. 42
4.8. State Transition Diagram................................................................................................ 45
4.9. Component Diagram...................................................................................................... 51
4.10. Deployment Diagram.................................................................................................. 51
4.11. Data Flow diagram [only if structured approach is used - Level 0 and 1].................. 52
Chapter 5....................................................................................................................................... 53
Implementation ............................................................................................................................ 53
5.1. Important Flow Control/Pseudo codes.......................................................................... 54
5.2. Components, Libraries, Web Services and stubs........................................................... 54
5.3. Deployment Environment.............................................................................................. 54
5.4. Tools and Techniques..................................................................................................... 55
5.5. Best Practices / Coding Standards.................................................................................. 55
5.6. Version Control............................................................................................................... 55
Appendices.................................................................................................................................... 56
Appendix A: Information / Promotional Material ........................................................................ 57
Reference and Bibliography.......................................................................................................... 60
Index.............................................................................................................................................. 62
List of Figures
1.1 Captionof firstfigure of firstchapter 6
1.2 Captionof secondfigure of firstchapter 7
2.1 Captionof firstfigure of secondchapter 14
2.2 Captionof second figure of secondchapter 22
2.3 Captionof third figure of secondchapter 26
5.1 Captionof firstfigure of fifthchapter 49
5.2 Captionof secondfigure of fifthchapter 49

Faculty of CS&IT, Superior University Lahore, Pakistan xi
List of Tables
1.1 label of firsttable of firstchapter 6
1.2 label of secondtable of firstchapter 7
2.1 label of firsttable of secondchapter 14
2.2 label of second table of secondchapter 22
2.3 label of third table of secondchapter 26
5.1 label of firsttable of fifthchapter 49
5.2 label of secondtable of fifthchapter 49

Faculty of CS&IT, Superior University Lahore, Pakistan xii

Faculty of CS&IT, Superior University Lahore, Pakistan 2
Chapter 1: Introduction
This document is based on requirements for Library Management System. It will give the detail
description of functional as well as non-functional requirements. This project will make friendly
relation with user and admin.
A library can be defined as a room or building where books are kept andreferenced. It is an area
of multifarious activity on book management. A library as a repository of knowledge, houses
collections of books, bothreference and general, technical reports, periodicals, journals,
conferenceproceedings and the likes. The Library management system is the application software
that is developed to make a record of Book purchasing, book searching, book issuing and rent, book
returned, catalogs, stock creation, all other fine books, popular and bestsellers and other Library
related works. The aim of the project is to make the manual handling of Library system into
computerized system which includes all above features. The scope of this software application is to
generate the automatic process of manual handling of Library records and to handle the stock as well
as book issues related information. Maintaining records of application for estates, the annual system
is too complex & cumbersome. All the outset the application requirements were studied and analysis
and design were carried out. The development platform and software tool were identified as visual
basic 6.0 and access database. Using visual programming, object are manipulated directly and also
due to the feature of fast and easy prototyping and GUI building visual basic 6.0 as used.
1.1. Background
Now a day, human wants those software that can reduce efforts of the people and very best for
uses and easy to understandable. Library Borrowing/Returning System is a process of organizing
important information, used to track items borrowed, and the scheduled time for returning. This
system help users or people who responsible in recording the data appropriately, it also saves
time and more convenient to use than the traditional manual recording.
Lack of library system in a university collage and school can lead to chaos and troubles, and
because of it the librarian is having a problem to serve each students and faculties who wish to
use the library. It is extremely useful in the university collage and school to use that automated
system.This software is very high and good for using because it have very high features. We
developed the software which named as Library Management System (LMS). This system
have contains very best knowledge for all things and every man get the knowledge to use this
software. This system contains the knowledge in which (Books, Newspapers, Litrary Material,
magazines and other articles etc). Every people can get that books who help them by using this
software.

1.2. Motivations and Challenges
Some reason we motivate to select the project of library management system
Library - a quintessential part of an educational institution and a society as a whole! It is not just a
place containing books but also a storehouse of information not just in print but also on digital
media. An integral as well as crucial part of any educational campus, the library is one of the few
places where one can find genuine information on almost all kinds of subjects/topics. With prompt
advancements in the world of education, communication and information technology, the library,
too has seen a lot of changes over the recent years.
One of the most prominent changes is library automation - wherein every task related to
management of library is fully computerized. There are numerous reasons for you to automate
your library. Here listing the some reason of them.
Makes Your Library A Smart Library
An organized, neat and systematic library is sure to prosper rather than a poorly organized one.
The library automation software helps you make your library systematized, organized and smart.
A smart library is not just neatly organized but also the one which facilitates quick and effortless
searching of books. The software enables you or your patrons to find a book in your library in
some seconds via powerful search tools.
One more advantage of using the software is that you can also search for rare books or apply for
interlibrary loans and vice-versa. This makes it very easy for your students to access all the books
of many libraries from a single place.
Saves Time - Substantially
Library Stock Verification of approximately 75,000 to 1,00,000 books, when done manually or
using spreadsheets requires 6 months with 3 people to generate accurate reports! Assuming 25
working days, 8 hours a day for 6 months:
25*8*3*6 = 3,600 hours!
While MasterSoft's RFID based library management systemcan do the same in 5-7 hours! That
saves 99.8% of the time! Now surely that a substantial amount of time saved along with a lot of
hassles.

Makes Your Library A Smart Library
An organized, neat and systematic library is sure to prosper rather than a poorly organized one.
The library automation software helps you make your library systematized, organized and smart.
A smart library is not just neatly organized but also the one which facilitates quick and effortless
searching of books. The software enables you or your patrons to find a book in your library in
some seconds via powerful search tools.
One more advantage of using the software is that you can also search for rare books or apply for
interlibrary loans and vice-versa. This makes it very easy for your students to access all the books
of many libraries from a single place.
Reduces Operating Cost
Expenses incurred in manually managing the library is very high because of a lot of paperwork,
manpower, printing cost, etc. involved on a daily basis. Putting all the information on digital media
frees you of all the printing and papers, once and for all! You or your patrons can easily search the
whole library in just a matter of a few clicks and few minutes. The manual process takes a much
longer time and also requires one to be physically present in the library. The paperless solution,
reduced man-hours, increased efficiency all lead to lower operating costs.
Challenge:
Libraries have long been endless sources of information for students - for centuries this involved
row after row of books. However, the face of libraries is changing as content is moving toward a
digital platform and Internet access is becoming more of a human necessity than a privilege.
While this presents innovative and creative ways for libraries to remain relevant to students and
researchers, it also carries its fair share of challenges. Here are the some challenge being faced
by libraries today:
 Budget
 Making services engaging to researchers and students
 Demonstrating your value
 Role development

 Digital licensing
 Subject-matter expertise
1.3. Goals and Objectives
General Objective: The general objective of this study is to design and develop a library system
that will serve as a proposal to help librarians save time with the automation of its daily
operation. Specific Objectives:
* To computerize records keeping of books;
* To allow librarians to retrieve complete information of the book and its borrowers
Goals:
The main purpose of this system is to manage library daily operation efficiently. ...
This system will store all the books and members information that consist book numbers, book
titles, author names and racks to the system database. It also provides search function to help
students find the book by number of book.
A library management system reduces the cost of management. The system eliminates the need
to members many student and keep different manual files thereby reducing the cost.
LMS also have the online system or every computerized system or software which is base on the
online web system and mobile application development. Every people can access his her detailed
by the login this software and they can update their current status. This project is specially designed
for librarians and library users.
Reduce effort and time. It will reduce both time and effort for both user and librarians. Because
it is online system and you can access this even you sitting at any places.
1.4. Literature Review/Existing Solutions
One of the first things to note when performing a literature review on ERM is that there are no
independent literature reviews solely on this area. From the field of library acquisitions, the issues

most readily identified in recent years have been the switch from print processing to ERM and the
continued struggle to find management tools that work within the local library context.
1.5. Gap Analysis
There are some ways for Gap analysis and improve your software.
1: Analyze your present situation
We analyze our current problems like competition many projects of LIBRARY MANAGEMENT
SYSTEM are working now a day but this project have all the feature and very easy to
understandable. It will be help all that people who can analyze their problems. It is better way that
you analyze your current situation and decide where you want to go in future. This process should
be team work regard your quality.
2. Overcome from that gap
You have to list problems which hurdles to your goal. Some problems weekness, lack of
opportunities and threats like LMS is failing to achieve attention in the market.
3.Nadler-Tushman mode
Most dynamic of model each process affects another part of the business. We have to identify
which gap affect efficiently. It is based only on input and output, after examine output you have to
analyze the process and fix the gaps by transorformation..
1.6. Proposed Solution
we can find proposed solution after gap analysis, cause of inefficient performance, document a
solution and description of before implement and after implement. For example job is not done
properly by the workers. We find the problems like in-appropriate training of employees,
document this all proposed the solution.
The proposed system deals with the management of data taken from the library management such
as the log book of the library. Reports that generated by the proposed system are limited to
predefined reports to be provided by the user such as their manual way of managing the library,
while no ad-hoc reports will be provided. On security, the proposed system allows access to
unauthorized users. It can only be operated if the user provides user name and password which is
already validated by the database administrator of the system to be assigned by authorized
personnel. Students, however, may borrow books without opening restricted files.
We only focus on processing which part is effecting whole output.

1.6.1. Work BreakdownStructure
2. Requirement Gathering
3. Designing
4. Implementation
5. Testing
6. Conflict resolving
7. Deployment
8. Marketing
8.1.1. Roles & Responsibility Matrix
Our team divided all the roles and responsibilities.
Farman Tariq was assigned to gather all the information and analyse it and also develop user
interface by using java language. Another team member Rehmat Qadeer duty was to do market
survey and resolve database issues. Rehmat also role was to resolve errors in code and develop
backend of the Application.
8.1.2. Gantt Chart
[Paragraph Text 12 pt, Calibri, 1.5 Line Spacing, Justified]

8.2. Report Outline
In this chapter we discussed about scope of the project and project background also developing
the project of library management system. After gap analysis we came to know about difficulties
also we have some resources but they have lack of information about Library management so we
work on it by our self.

Chapter 2
Software Requirement
Specifications

Chapter 2: Software Requirement Specifications
9.1. Introduction
10. Nowadays, in a highly technological society, human productivity is made more
efficient through the development of electronic gadgets. Technologies are important
and helpful in everyone life. Libraries around the world are quickly adopting
technology to better manage their inventory and staff. The problem for libraries is
that they can’t afford I.T. departments to help secure data and the like, so there are
always common risks that libraries face. A library management system is made to
have fast process transaction for searching book title, borrowing books, returning
books computing penalties and generating an accurate report. library is important
part of the academic sector as well as some professional too like, the efficiency of
library management system lies how the books are arranged and how easily one can
get the books of their choice. Generally, what we see today is the manual library
where the process of operation very much hectic. Students need a lots books for
their studies. Students often find problems because books are limited and only few
students can have the books. Students need to fall in line and then ask for the related
title of the books. Issuing of Books is Slow. The issuing of book is slow where
borrowers ( faculty, students, staff and clients) will have to wait for further library
transactions. Time Consuming. The library services in terms of issuing of books
through library cards consumed a lot of time. Lost books. There were books in the
library which were not included in inventory of books per semester. The data of the
manual library were not secured with respect to the confidentiality of reports and
documents of library transactions, Lack of Data Storage. There were a lot of library
files, reports and documents which are not well-accommodated/saved. Poor Data
Storage. The data storage of the manual library management was not enough to
accept a number of files and reports. Lack of Information. Reports and updates with
respect to library transactions and services are not well disseminated. Slow Retrieval
of Data . So, students face the many problem. Library is the place in which we get
the information in any format and form many sources.
10.1.1. Purpose
The purpose of library system management is to maintain the data like update, delete , create,
date of books , magazines, and all those persons which are members of library system, issues
books .
The real purpose of this library management system is to maintain all its daily operation very
effectively.
Purpose of our project is to make the system is an automated “library management system”.
User can add books, add members, search the book they want, search the members, add the
information, update the information, edit the information if require, borrow the books, return the
books in a quick time. Our project has so many advantages in the following
 User friendly interface

 Fast and easily access the data in the database
 Less error during the process
 Storage capacity will be high for users
 Facility of search users desired
 Look feel free environment
 Immediately transaction
Librarian handles all types of data in library they are the most active actor in library management
system.
Build a system like we enter any input it automatically generates an output according to our
input. This will save our time.
Also build a system like monitoring system so it is able to monitor all activities happening in
library management system.
For the maintenance of security we properly store library data items.
10.1.2. Document Conventions
For the main selection titles
 Font will be “times new roman”
 Face will be bold
 Size:14
Sub selectiontitles
 Font “time’s new roman”
 Face bold
 Size : 12
Others text explanations
 Font “time’s new roman”
 Face normal
 Size 12
10.1.3. Intended Audience andReading Suggestions
Our project is library management system. We are developing our project “library management
system“ for university, colleges, or any institute. Also this project can be used in any
management. We developed it in SRS form. Mostly this SRS is developed for project
management team. In our project team there will be project manager, developer, coder, tester and
documentation writer.
User customer
This intended belongs to customer and user. It is just for to make them ensure that document is
correctly meeting their need.
Project Manager

Project manager also need this SRS document. It is very important for the project manager to
determine the cost that will be occur during the making of this project. This is done by
implementation to the SRS document. And that documents consist of all type of information that
is require for planning the projects.
Project developer
When SRS is formed the next step is to name it and project developer will name this SRS
document to confirm that it is what customer requires.
For the project developer it is very important.
Tester
Tester duty is very important when SRS document is formed tester will carefully read it and he
will tell that the requirements are fully satisfied with the customer so that he able to test that
software and handles its working.
Document writer
Document writer will review this document to assure that this document is well competent that is
able to write the users standard. It is mandatory that document standard will meet users standard.
Maintenance
Engineers will used this document to understand the total functionality of the system, this
information about functionality can help engineers to briefly explain the design and code of
project.
10.1.4. Product Scope
All the requirements capture in one document by software requirements specification. The project
that is to be developed provides members of library management system and employee with all
books information and online blocking of books and all other facilities. Library management
system will defend the following statements Members handover with the product with online
blocking of books of facility and library management system is running all the day. The system
will give facility of login to the users. Users have the right to check their account and have a right
to change their password and others content of the account whenever they want to all over the day
during library hours. System allow the members they can block the book for them 24 hours a day
or for a semester. System allow the library employee to check which members have blocked the
book for them for how many lifetime and they can get more books or not. The system will give
right to librarian to make books catalog. To know when the member get and returns a book, the
system will refresh the billing systems.
Books catalog are computerized and selection of contribution of books is based on which category
the book is automatically clear. We also have a department in which administer add or delete the
book from the library. This feature that is categorize in this documents are used for the future of
software development circle. And this feature is customized here to justify that it meet with needs
of all users.
10.1.5. References
Web address
www.google.com

https://www.studymode.com
https://www.answers.com
https://www.bibliotechzw.com
10.2. Overall Description
10.2.1. Product Perspective
To improve the power of librarians, library employees and users libraries used the combination of
online library system. This system is generated to developedthe interest of members and institute
librarians. In this way system established books catalog and all type of information and help the
members to select the book which the book to be hire from library. In the system librarian should
remain the books catalog improved all the time so all the members of the system may get the
restore information all the time.
10.2.2. Product Functions
Online system provide us the fast information about the books in library. Its takes no time to search
it gives immediately result about the books. System object is also include in the functions of system
that provide different types of services arranged on the type of users
 The members will apply with the latest information of the books stack.
 If all the others rights rules follow fine then feed for the division to hire the books they
want.
 Every person should give the chance to check their account data and change the mount of
processes data any time in the default time.
 The librarian get the information whose members have returned or borrowed the books
from the library.
 They provide such environment so that they itself add or delete the books that is available
in the catalog.
10.2.3. User Classes andCharacteristics
Persons, the administer who manage the system and institute librarians they all are the users of
the system. All librarians and members have little knowledge about the computers and the
internet browsing so they are able to use their seat in a right way. The little problems that may

arise due to some interruption in the disk or crashes in the disk, failure of power and other
crashes to manage the system, this all problem is justify by the administrator of the system which
have more knowledge about the internet. To install the system there must be proper users
manual, online help, interface and guideline. And user must be educate in this way how to use
the system in a right way without any problems.
10.2.4. Operating Environment
Software requirements
Language : PHP
Operating systemwindow 7,
Database: MySQL
Hardware requirements 512 RAM, Pentium 5/ 40GB hard disk
10.2.5. Designand ImplementationConstraints
All user’s information should be save in the database so it is easy for online library management
system to accessible. The security system of university or any other institute information should
be suitable with the internet application. All computers of institute is connected with the online
library management system and it is executing all the 24 hours a day. The user or any other
authorized person can access data online from any computer that has good ability of browsing and
good speed of internet which is connected to online data server. This online system is also
connected with the online billing system and all the data of online billing system saved in database
that database should be suitable with combination of online library management system. To login
in online library management system user must have a correct information of their password and
user names.
10.2.6. User Documentation
For each feature that is available with online library management system the online help should be
provided. User will assist all the applications provided an online help system. All the system
nature will be unique from application development. The users will manually describe the uses of
system to librarian and employees. They describe the use of system in cells called mobile system.
All the instruction of installation and guideline is provided in installation document as they are
offering a full solution. “Read me” file also included as a standard component. And this file consist
of “what’s new with this release” section. Mostly users will define the bugs and any errors in this
file of documentation. Installation guideline will not provided to any user since the installation of
online library management system process becomes more complex our genius expert employee
will do this installation.

10.2.7. Assumptions andDependencies
Applicable users have more knowledge about computers. The university computer or any other
institute computer must have internet connection and server capabilities. If interface of system is
provided in English then user must know the English language. And all the type of product can
access the student database.
10.3. External Interface Requirements
10.3.1. User Interfaces
Design and layout for each form will be very good and clear and very attractive for all users
so they cannot distract.
Welcome window will appear immediately when the user open this software.
User can easily enter their password and usernames in the login window.
Login message will appear when login done.
For the user there must be a relative link in all window for others window so user can go
easily to other window.
There will be a help for the user in every window and Mac there must be support option
window for ease of user.
There must be all collection of graphical user interface that provide good look and feel.
Graphic and font family size will be in a good manner and well organized and the color of
the background should be very light in the screen layout.
Error message will be displayed in a proper way whenever users write any error statement
by mistakenly.
For displaying message in each and every window there will be alert and confirm message.
By using guideline which is in the window and Mac user will be able to search and find
the data from the record.
When user enter in the system there will be menu window and this window will contain all
the table contents of software and user can use this window to go any desired window and
Mac he want.
Menu window is displaying according to the login (user normal or admin) so it will provide
a satisfied security data.
User and other authenticated person can save data in the database very easily and control
the path of records of users purchases and others vendor.

System software will be understandable and very easy to understand by the normal user.
10.3.2. Hardware Interfaces
Networks that are already exists local area network LAN will be used for taking the data from
the users and update the library management system catalogue.
10.3.3. Software Interfaces
Unauthorized person is present everywhere so to prevent this type of user in the system we use
firewall.
10.3.4. Communications Interfaces
Our project that is connected to online library management and this will online library
management system will be connected to the World Wide Web.
10.4. System Features
10.4.1. SystemFeature 1
10.4.1.1. Description and Priority
First priority will be the welcome form as we know whenever user or any other person who
has authority want to enter in the system they have to login in the system. For the logging
there must be a welcome page or screen before login form which ensure to the user he
wants to enter or exist.
Login form comes after the welcome form. Users and other authenticated person used this
form to login in the system by entering their password and good usernames.
As we know priorities is important thing so priorities of the user always be given through
his basic.

Menu form will show according to activities of the users and they can use this and users
can approach all the time all reports.
10.4.1.2. Stimulus/Response Sequences
User authentication for the all registered members they should have their id and unique
key in the system so they have their own choice of reading for their favorite courses.
10.4.1.3. Functional Requirements
Student functional Requirement
FR-001 Can search book
FR-020 Can view book
FR-003 Can reserve book
FR-004 Can return book
FR-005 Can view report
FR-006 Can’t not allowed to see the record or personal data of any other user
FR-007 Can check book
FR-008 Can issue book
Faculty member functional Requirement
FR-009 Can view
FR-010 Can search
FR-011 Can reserve
FR-012 Can return
10.4.2. SystemFeature 2
10.4.2.1. Description and Priority

2nd(second) priority will be menu form. This menu form consists of contents, manuals, and
other functions of the system. User can go any form from the menu form throughout the
system.
In the menu form as we know there are many options to select this form provide so many
facility to the users and user can select choices as many as they can for working as he want
to select only one option like select the book then he will select only this option to select
the book.
In addition if the user only wants to show the result then he will definitely go the result
section and will show the result as a report in a format as he want
10.4.2.2. Stimulus/Response Sequences
Software require proper monetizing by the admin he should be given authority to update
account.
Admin could also tackle the member and fine the member who did not return the data related
to library rules and regulation.
10.4.2.3. Functional Requirements
Librarian Functional Requirement
FR-013
update member card
FR-014 Can issue book
FR-015 Can remove book
FR-016 Can add remove books
FR-017 Can view
FR-018 Can update books
FR-019 Can add book
Admin functional Requirement
FR 020 Can view
FR 021 Can remove book

FR 022 Can check
FR 023 Can add remove book
FR 024 Can add remove member
FR 025 Can remove member record
FR 026 Can update
FR 027 Search Book
10.4.3. SystemFeature 3 (andso on)
As we know priorities is important thing so priorities of the user always be given through his
basic.
Menu form will show according to activities of the users and they can use this and users can
approach all the time all reports.
Librarian could also tackle the member and fine the member who did not return the data
related to library rules and regulation
10.5. Other Nonfunctional Requirements
10.5.1. Performance Requirements
Non Functional
Requirement ID
Functional Requirement ID Non Functional
Requirements
NFR-001 FR-001 Performance,

10.5.2. Safety Requirements
Non Functional
Requirement ID
Requirements
NFR-008 FR-002 Safety,
NFR-009 FR-007 Safety,,
NFR-011 FR-019 Safety,,
10.5.3. Security Requirements
11.
12.
Non Functional
Requirement ID
Requirements
NFR-015 FR-004 Security,
NFR-018 FR-022 Security,,,

12.1.1. Software Quality Attributes
13.
Non Functional
Requirement ID
Requirements
NFR-021 FR-003 Software quality attributes
13.1.1. Business Rules
Main business rule for software development is to widely accept the development work.
Analyzation of requirement specification is paly vital role in software development.
Crucial stage for him is to analyze and express in phase of system development process.
Every field is classified into many types software development is also classified SLDC
and requirement specification. Focus on access control and policy of the company. There
are some rules like offering the customer in library management system when customer
order quantity is greater than 10 give him bonus.
13.2. Other Requirements
. Performance requirements
1. Whenever information is updated from the system on formal time intervals. System
should update that information within two second for all the users.
2. System should give more time when it is performing big processing.
3. Its performance should be fast that response to task within 5 seconds of clicking.
4. System should capacity for more load means it should not hang if thousands of user are
logging in at one time.
It should in discipline and categorized form e.g. documents, files.
Safety requirements
The system should be safe it is necessary for running all functions in the software.
1. System coding should be in a sequential way which is basic for the safety of
the system.

2. System should not overflow the work e.g. should not perform irrelevant task.
3. System should be able to tackle all the hazards which can be occurred while
running.
4. System should be less time consuming and in less cost.
5. The number of complexity should not be display on the screen which are not
relevant to admin or general user.
6. System should be tested before providing remove all the errors in the working
of the software.
Security requirements
Security is important for the functionality of the system.
1. System should provide security to the customer and the admin.
2. If user is entering his id and password make sure all his data is secure.
3. User should not allowed to see personal data of any other user through this system.
4. System should not be attacked by another source or another person is not allowed
to steal sensitive information about the system.
5. System should able to identify and notify all threats and irrelevant links to the
admin.
6. System should identify and differentiate generic and external threats to the system
which will help for admin to tackle the problem.
7. There must a storage of all data and material in case data is deleted by external
viruses.
8. System should able to delete all the data which can be cause of harm viruses.
9. System should use password protection, firewalls and virus detection tools these
tools will help to prevent system from upcoming hazards.
10. All the id including admin and users should be safe by a password.

Software quality attributes
Library management system will be user friendly it will provide all user activity regarding
borrow and returning all transactions will save in the database.
Different form of data which is entered by user will not collected in similar external system.
This system should be work in a way that users will meet their requirements in a safe and secure
way.
This system will provide application for both android and apple. All mobile user can be facilitate
by it.
External system will up-to-date good quality and standard.
LMS will provide different forms of book material e.g. about literature, history, religious etc.
It will fast system that user can access and reach to his requirement within 5 seconds after
clicking.
Reliability it will perform under predefined condition. Reliability will tell the success of
architecture.
Availability will also tell software quality attributes. Available time of the system during total
working time.

Chapter 3
Use Case Analysis

Chapter 3: System Analysis
3.1. Use Case Model
Use case Diagram

USE CASES

3.2. Fully Dressed Use Cases
Use Case ID 01
Use Case Name: Add Student record
Scope Library Management System
Level User goal
Primary Actor Admin
Stakeholder and Interest:
Admin: wants to change Membership record of the specific student.
Student/faculty member: whose record will be manipulated
Pre-Conditions:
 The password entered is correct.
Success Guarantee:
 The record of student membership is changed in the Library management software.
Main Success Scenario:
 Admin: Select the menu to change the membership record of the specific student.
 Admin: Enter the name of the category and correct data of he student.
 Library management system

 Save the change in the membership record of the student and update the precious record.
Extension:
 Error message will be show with reason.
 Student name is not unique, show error message “student name is not unique”.
 Student email is not unique, show error message “student email is not unique”.
 student contact number is not unique, show error message “student contact number is not
unique”.
 If the network connection is slow then form will be submitted but it will update later in
database.
Special Requirements:
The System can support Urdu and English language.
Use Case ID 02
Use Case Name: Add Book record
Level User goal
Primary Actor Admin
Admin: wants to see all the books in detail.
Librarian: wants accurate books supplies record.
Admin: wants to keep record of books.
Pre-Conditions:
Success Guarantee:
 Books successfully added and its record saved in database.
 Admin will fill the required form of to add books.
 Book name, supplier name, quantity and per item price must be authentic.
 Then he will submit the form.
 The success message will show that “Item is added successfully”.
Extension:
 While adding the book if the supplier name is not added before then it will go to the add
supplier page.
 If the same book is saved twice then it will show error message “That item is already
saved”.
database.

Use Case ID 03
Use Case Name: Delete record
Level User goal
Primary Actor Admin
Admin: wants to see all the books in detail.
Librarian: wants accurate books supplies record.
Admin: wants to delete record of books.
Pre-Conditions:
Success Guarantee:
 Record successfully deleted and its record saved in database.
 Admin will fill the required form of to delete books.
 Then he will submit the form.
 The success message will show that “Item is delete successfully”.
Extension:
 While deleting the record if the member name is not added before then it will go to the
add member page.
 If the reord is not deleted then it will show error message “That record is not deleted”.
database.
Use Case ID 04
Use Case Name: Search book
Level User goal
Primary Actor Librarian

o librarian: Wants to see the book.
o librarian: Wants to reserve book.
Pre-Conditions:
Success Guarantee:
Show accurate data against the required book.
 The librarian will enter the name of required book click on button “Search”.
 Bio data of the required book will be show.
Extension:
 If the Book is not found then show the error message “Book not found”.

Use Case ID 05
Use Case Name: Issue book
Level User goal
o librarian: Wants to view the book.
o librarian: Wants to reserve book.
Pre-Conditions:
Success Guarantee:
 The librarian will enter the name of required book which he want to view click on button
“Search”.

Extension:
 If the Book is not found then show the error message “Book not found”.

Use Case ID 06
Use Case Name: Update book record
Level User goal
o librarian: Wants to update the book record.
o librarian: Wants to see the book record.
Pre-Conditions:
Success Guarantee:
 The librarian will enter the name of update book which he want to update click on button
“Search”.
Extension:
 If the Book is not upadte then show the error message “update book not found”.


Use Case ID 07
Use Case Name: Reserve book
Level User goal
Primary Actor Student
o Student: Wants to reserve the book.
o Student: Wants to rsee the book book.
Pre-Conditions:
Success Guarantee:
 The student will enter the name of required book which he want to reserve click on button
“Search”.
Extension:
 If the Book is not reserve then show the error message “Book reserve not found”.

Use Case ID 08
Use Case Name: view book
Level User goal
Primary Actor Student
o Student: Wants to view the book.
o Student: Wants to see the book book.
Pre-Conditions:
Success Guarantee:

 The student will enter the name of required book which he want to view click on button
“Search”.
Extension:
 If the Book is not view then show the error message “Book view not found”.

Use Case ID 09
Use Case Name: Download book
Level User goal
Primary Actor Faculty member
o Faculty member: Wants to download the book.
o Student: Wants to see the book.
Pre-Conditions:
Success Guarantee:
 The faculty member will enter the name of required book which he want to download click
on button “download”.
Extension:
 If the Book is not download then show the error message “Download book not found”.


Use Case ID 10
Use Case Name: search book
Level User goal
Primary Actor Faculty member
o Faculty member: Wants to search the book.
o Student: Wants to see the book.
Pre-Conditions:
Success Guarantee:
 The student will enter the name of required book which he want to view click on button
“Search”.
Extension:
 If the Book is not view then show the error message “Book view not found”.


Chapter 4
System Design

Chapter 4: System Design
[Between 4 to 8 lines describe what is this chapter all about]
4.1. Architecture Diagram
4.2. Domain Model
4.3. Entity Relationship Diagram with data dictionary

4.4. Class Diagram
4.5. Sequence / Collaboration Diagram

Issue book
Member id Book id
error
Clear fieldserror
error
error
Issue book
confirm
Database updation
Both not filled
Both filed
Incorrect inputs
Correct inputs
Not avail
available
Borrowed book>4
Borrowed book<4

4.6. Operation contracts
4.7. Activity Diagram

login
Member Id password
Error message
Both not filles
Clear fields
Both filled
Error meesage
Display user
interface
Correct inputs
Clear fields
Incorrect
Inputs
View Books

User type
memberguest administrator
View book page
Display results
Print detailsDon’t print

4.8. State Transition Diagram
Reserve Book

Reservve book
Memberr id Book id
Error
Clear fields
error
Reserve book
Confirm
Database updation
Both not filed
Both filed
Incorrect inputs
Correct inputs
Search Book

Correct data
Error
error
View results
Incorrect data
available
Not avail
Search data
By categoryBy name
Search type
memberguest
User type

Issue Book

Issue book
Member id Book id
error
Clear fieldserror
error
error
Issue book
confirm
Database updation
Both not filled
Both filed
Incorrect inputs
Correct inputs
Not avail
available
Borrowed book>4
Borrowed book<4

Return Book
Return book
Member id Book id
error
Clear fieldserror
Return book
confirm
Database updation
Both not filled
Both filed
Incorrect inputs
Correct inputs

4.9. Component Diagram
4.10. Deployment Diagram

4.11. Data Flow diagram [only if structured approach isused - Level 0 and 1]
Library management
ysytem
Library
managemnet
Authors management
Books
management
Book issue
management
Login management
System user
management
Generate
Library report
Generate authors
report
Generate
Books report
Generate book
Issue report
Check user
Login details
Generate system
User report

Chapter 5
Implementation

Chapter 5: Implementation
5.1. Important Flow Control/Pseudo codes
5.2. Components, Libraries, Web Services and stubs
5.3. Deployment Environment

5.4. Tools and Techniques
5.5. Best Practices / Coding Standards
5.6. Version Control

Appendices

Appendix A: Information / Promotional Material
[Between 4 to 8 lines describe what is this appendix all about]
A.1. Broacher
A.2. Flyer
A.3. Standee
A.4. Banner

A.5. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.5.1.Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.1. Third level heading [12 pt, Calibri, Bold, Left aligned]

Appendix [no.]: Appendix Title
A.1. First Level heading [16 pt, Calibri, Bold, Left aligned]
A.1.1.Second level heading [14 pt, Calibri, Bold, Left aligned]
A.1.1.2. Third level heading [12 pt, Calibri, Bold, Left aligned]

Reference and
Bibliography

Reference and Bibliography
[1] M. Sher, M. Rehman, “Title of the Paper” Conference name/Journal Name, Edition,
Volume, Issue, ISBN/ISSN, PP, Publisher/City-Country, Year.
[2] ……

Index

Index
[A]
[B]
[C]

Library management system se project

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Library management system se project

Similar to Library management system se project (20)

Recently uploaded

Recently uploaded (20)

Library management system se project