Synopsis of Library Management System
Synopsis of Library Management System
Synopsis of Library Management System
Page - 1
Topic Title
10
11
Identification of need
12
Feasibility Study
13
14
15
17
Project Category
18
Implementation Methodology
19
19
20
System Analysis
22
Data Dictionary
23
24
25
26
Page - 2
Page - 3
Page - 4
Library Management System also manage the Address details online for
Librarian details, Member details, Student.
Page - 5
Page - 6
In computer system the person has to fill the various forms & number of copies of
the forms can be easily generated at a time.
In computer system, it is not necessary to create the manifest but we can directly
print it, which saves our time.
To assist the staff in capturing the effort spent on their respective working areas.
The system generates types of information that can be used for various
purposes.
Page - 7
You can also export the report into csv format for Student, Books, Member
the Books.
Issues Module : Used for managing the Issues details
Librarian Module : Used for managing the Librarian informations
Login Module: Used for managing the login details
Users Module : Used for managing the users of the system
Page - 8
All the fields such as Student, Issues, Member are validated and does not take
invalid values
Each form for Student, Books,Address can not accept blank value fields
Preparation of the possible test data with all the validation checks.
Page - 9
The software quality plan we will use the following SQA Strategy:
In the first step, we will select the test factors and rank them. The selected test
factors such as reliability, maintainability, portability or etc, will be placed in the
Page - 10
Accuracy in work.
Page - 11
Page - 12
Documents and reports that must be provided by the new system: there can also
be few reports, which can help management in decision-making and cost
controlling, but since these reports do not get required attention, such kind of
reports and information were also identified and given required attention.
Page - 13
Page - 14
B. Technical Feasibility
This included the study of function, performance and constraints that may affect
the ability to achieve an acceptable system. For this feasibility study, we studied
complete functionality to be provided in the system, as described in the System
Requirement Specification (SRS), and checked if everything was possible using
different type of frontend and backend plaformst.
C. Operational Feasibility
No doubt the proposed system is fully GUI based that is very user friendly and all
inputs to be taken all self-explanatory even to a layman. Besides, a proper training has
been conducted to let know the essence of the system to the users so that they feel
comfortable with new system. As far our study is concerned the clients are comfortable
and happy as the system has cut down their loads and doing.
Page - 15
The general tasks involved in the design process are the following:
1.
2.
3.
4.
5.
6.
7.
Page - 16
Page - 17
Benefit to Organization
The organization will obviously be able to gain benefits such as savings in
operating cost, reduction in paperwork, better utilization of human resources and more
presentable image increasing goodwill.
The Initial Cost
The initial cost of setting up the system will include the cost of hardware software
(OS, add-on software, utilities) & labour (setup & maintenance). The same has to bear
by the organization.
Page - 18
Page - 19
Page - 20
Model - The lowest level of the pattern which is responsible for maintaining data.
View - This is responsible for displaying all or a portion of the data to the user.
Controller - Software Code that controls the interactions between the Model and
View.
MVC is popular as it isolates the application logic from the user interface layer and
supports separation of concerns. Here the Controller receives all requests for the
application and then works with the Model to prepare any data needed by the View. The
View then uses the data prepared by the Controller to generate a final presentable
response. The MVC abstraction can be graphically represented as follows.
MVC (Model View Controller Flow) Diagram
DATA FLOW DIAGRAMS
Tools/Platform,
Requirement
specifications:
Software
Requirements:
Name of component
Operating System
Specification
Windows 98, Windows XP, Windows7,
Page - 21
Language
Database
Browser
Web Server
Software Development Kit
Scripting Language Enable
Database JDBC Driver
Linux
Java 2 Runtime Environment
MySQL Server
Any of Mozilla, Opera, Chrome etc
Tomcat 7
Java JDK 1.7 or Above
JSP (Java Server Pages)
MySQL Jconnector
Hardware Requirements:
Name of component
Processor
RAM
Hard disk
Monitor
Keyboard
Specification
Pentium III 630MHz
128 MB
20 GB
15 color monitor
122 keys
Page - 22
Page - 23
Security of data.
Ensure data accuracys.
Proper control of the higher officials.
Minimize manual data entry.
Minimum time needed for the various processing.
Greater efficiency.
Better service.
User friendliness and interactive.
Minimum time required.
Page - 24
= equivalent to
+ and
[] either/ or
() Optional entry
Following are some rules, which defines the construction of data dictionary
entries:
1. Words should be defined to understand for what they need and not the
variable need by which they may be described in the program .
2.
3.
Page - 25
A description of the background and context of the project and its relation to work
already done in the area.
We describe the requirement Specifications of the system and the actions that
can be done on these things.
We understand the problem domain and produce a model of the system, which
describes operations that can be performed on the system.
Page - 26
We can give more advance software for Library Management System including
more facilities
Create the master and slave database structure to reduce the overload of the
database queries
Implement the backup mechanism for taking backup of codebase and database
on regular basis on different servers
The above mentioned points are the enhancements which can be done to increase
the applicability and usage of this project. Here we can maintain the records of Student
and Books. Also, as it can be seen that now-a-days the players are versatile, i.e. so
there is a scope for introducing a method to maintain the Library Management System.
Enhancements can be done to maintain all the Student, Books, Issues, Librarian,
Member.
We have left all the options open so that if there is any other future requirement
in the system by the user for the enhancement of the system then it is possible to
implement them.In the last we would like to thanks all the persons involved in the
development of the system directly or indirectly. We hope that the project will serve its
purpose for which it is develop there by underlining success of process.
Page - 27
Excel export has not been developed for Student, Books due to some criticality.
The transactions are executed in off-line mode, hence on-line data for Issues,
Librarian capture and modification is not possible.
Page - 28
Page - 29