The Title of the Project is“सससससससस ससससससससस ससससससससससससस ससससससससस सससससससस” . From the Title it is clear that we have to design the System like a Library Management for this Institution . This System is Specially Developed for Spiritual Books category . The purpose of this document is to collect, analyze and define the high-level needs and features of the Library Management System . This project consists of managing all the detail of Library of this Institution . It consists types of books, writers , section of the books , like rack number where it can easily found by any person or member who searching a book in the library . The user will find it easy in this automated system rather than using the manual writing system . The system contains a database where all the information will be stored safely . The system is user-friendly . OBJECTIVE OF PROJECT The Primary objectives of the project are: Easy Books Searching By Book Name, Author or Publishers. Effective Books Handling Easy Keeping All The Records Into The Database Tracking All The Transactions Easily. 1 INTRODUCTION TO THE PROJECT
Transcript
The Title of the Project is“सं�स्कृ� ति� तिद्या�पी ठ कृम्प्यू�टरी कृ� � पी�स्�कृ�लयू व्यस्था�” . From the Title it is clear that we have to design the System like a Library Management for this Institution . This System is Specially Developed for Spiritual Books category . The purpose of this document is to collect, analyze and define the high-level needs and features of the Library Management System .
This project consists of managing all the detail of Library of this Institution . It consists types of books, writers , section of the books , like rack number where it can easily found by any person or member who searching a book in the library . The user will find it easy in this automated system rather than using the manual writing system . The system contains a database where all the information will be stored safely . The system is user-friendly .
OBJECTIVE OF PROJECT
The Primary objectives of the project are:
Easy Books Searching By Book Name, Author or Publishers.
Effective Books Handling
Easy Keeping All The Records Into The Database
Tracking All The Transactions Easily.
Effective System compared to the Manual Handling.
PROBLEM WITH THE PRESENT SYSTEM
The current system of Library Management is Manually handling . So always be the probability of Loss of data by theft , Natural Disaster or etc.
1
INTRODUCTION TO THE PROJECT
In Manual System separate Registers are maintained for all the types of Data . So always be probability of Delay in the Updating the Master Record for New Member Addition, New Book Arrival into the Library or Transaction from the library.
In Manual System the chances of the Human Error is most like a Librarian forgot to Update the data after the book returned by the member .
In Checking the Volume of the books present in the Library by manually always be the complex.
In Manual System Data duplication can be occurred due to repetition of same data over and over.
In Manual System lots of Space needed to record the data, so too much paper wastage in manual system compared to Computerized system.
The type of Information is stored in the different files , so it takes a long time to retrieve the particular data.
BRIEF DETAILS ABOUT MICROSOFT SQL SERVER 2012
Microsoft SQL Server 2012 is a relational database management system (RDBMS) designed for the enterprise environment . SQL Server 2012 comprises a set of programming extensions to enhance the Structured Query Language (SQL), a standard interactive and programming
2
PROJECT CATEGORY
language for getting information from and updating a database. SQL Server architecture is the part where all components work together and independently to process or execute services in a proper or defined manner so that SQL Server could work in a smooth way. The external interface to the SQL Server is created by the protocol layer and all operations on SQL Server are communicated via a defined format called TDS (Tabular Data Stream). It is an application layer protocol, which is used to transfer data between client and database server.
The Major Components of SQL Server are : Relational Engine Storage Engine SQL DATABASE
THE RELATIONAL ENGINE
It is also called as the query processor . Relational Engine includes the components of SQL Server that determine what the SQL query exactly needs to do and the best way to do it. It manages the execution of queries as it requests data from the storage engine and processes the results returned.
Storage Engine is responsible for storage and retrieval of the data on to the storage system . Any database in SQL Server, there are two types of files that are created at the disk level – Data file & Log file . Data file physically stores the data in data pages. Log files that are also known as write ahead logs, are used for storing transactions performed on the database.Data File :- Data File stores data in the form of Data Page (8KB) and these data pages are logically organized in extents .
Extents :- Extents are logical units in the database . They are a combination of 8 data pages i.e. 64 KB forms an extent . Extents can be of two types, Mixed and Uniform. Mixed extents hold different types of pages like index, system, data etc. (multiple objects). On the other hand, Uniform extents are dedicated to only one type (object).
Log File :- Every SQL Server database has a transaction log that records all transactions and the database modifications made by each transaction . The transaction log must be truncated on a regular basis to keep it from filling up. It stores modification to the database (DML and DDL).
Sufficient Information is logged to be able to : Recover the database in case of failure Write Ahead Logging is used to create log entries Transaction logs are written in chronological order in
a circular way
4
Truncation policy for logs is based on the recovery model
SQL DATABASE
In the Previous Versions Scalability was the Major issue with SQL Server because it supported only for small or medium sized workloads due to its engine capabilities . This lies between the host machine (Windows OS) and SQL Server. All the activities performed on database engine are taken care of by SQL Database . SQL Database provides various operating system services , such as memory management deals with buffer pool , log buffer and deadlock detection using the blocking and locking structure . Other services include exception handling , hosting for external components like Common Language Runtime(CLR) etc. The SQL Database does not bypass Windows, it simply manages the resources within the SQL Server process space in a way that is efficient for SQL Server .
BENEFITS OF USING SQL SERVER 2012 Increased productivity for systems engineers and
database administrators due to time savings, better security and higher data quality.
Increased productivity for application developers due to higher availability, improved workflow, and also due to the improvements incorporated with the new SQL Server.
In SQL Server 2012 with Power View we can extract live data into PowerPoint Presentations , saving the
5
time and ensuring up to date information . This feature enhances the visualization and interactivity with the data .
SQL Server 2012 Improved his Data Quality by improving the accuracy and consistency of the data.
SQL Server 2012 greatly improves query performance by interactive exploration of the data allowing user to get even more business value, even quicker, thus resulting in faster and more accurate decisions.
SYSTEM ANALYSISSystem analysis is a detailed study of the various operation performed by a study and their relationships within the meeting members of the system . System analysis is a detailed study of the various operation performed by a study and their relationships within the meeting members of the system. Analysis is defining the boundaries of the system and determining whether or not a candidate system* should consider other related system.
During analysis, data are collected from the available files, decision, points, and transactions handled by the present system .
*CANDIDATE SYSTEM :- A candidate System is needed while
6
PROJECT ANALYSIS
designing a system. It represents the original System to be made and analyzed by the analyst so that changes and improvements can be made in it on the basis of Feasibility studies . And when the Candidate System approves all the requirements of the customer, The final system is made on the basis of this Candidate System .
System Analysis is conducted on the basis of following Objectives :
Identify the end users Evaluate the system concept for feasibility Allocate functions to hardware, software, members,
database, and other system elements. Establish cost and schedule constraints . Apply principles of database design and effectively
design database schemas based on conceptual business models.
FEASIBILITY STUDY OF THE PROPOSED SYSTEM
Feasibility study is the preliminary investigation into the system to evaluate the possibility of a computer system
7
and estimate costs and benefits where quality and time also involve . This is the most effective method of solution. Feasibility and risk analysis are related in many ways . If project risk is great, the feasibility of producing quality software is reduced .
There are eight steps in feasibility study : Form a project team and appoint a project leader. Prepare system flow chart Enumerate potential candidate system Describe an identify characteristic of the candidate
system Determine and evaluate performance and cost
effectiveness of candidate system Weight system performance and cost data Select the best candidate system Prepare and report project directive to management
8
DATA FLOW DIAGRAM
LIBRARYMANAGEMENT
SYSTEM
MEMBER
BOOKS
UPDATING BOOK RECORD
UPDATING MEMBER RECORD
BOOK STATUS MEMBER RECEIVING
BOOK REQUEST
CONTEXT LEVEL DIAGRAM
+
9
LIBRARIAN
PAYMENTS/FINES
REPORTS
DISPLAYS
COMPLETE LIBRARY TRANSACTION REPORT
LOGIN
ISSUE BOOK
LIBRARIAN
ADD NEW
BOOK
BOOKACCESSION
SEARCHBOOK
CATALOGUE
BOOK RECORD
ACCESSION MASTER
FILE
NEW BOOK ENTRY
ACCESSION
ENTER BOOK NAME
BOOK INFORMATION
NEW BOOK UPDATED
ACCESSIONEDBOOK DATA
RETRIEVING BOOK DATA
CATALOGUING BOOK
DFD LEVEL 1
DFD LEVEL 2
ADD NEW
MEMBER
LIBRARIAN
FINEOR
DUES
NEW MEMBER ENTRY
FULL DETAILSOF MEMBER
MEMBER RECORD
REPORT
MEMBER UPDATED
FULLTRANSACTION
REPORT
BOOK_RECORD SEARCHBOOK
10
Book ID (PK)ISBN (FK)Book NameAuthor PublisherPagesBinding TypePurchase
Book ID (FK)Book Name PublisherAuthor Name
DATABASE MODEL
Login IDNamePassword
LOGIN RECORD
SEARCHMEMBER
ENQUIRYFOR FINE
RETRIEVING FINE DATA
DFD LEVEL 3
ADD NEW
MEMBER
UPDATEExisting
MEMBER
DeleteExistingMember
Determine Operation
MEMBER RECORD
Member Addition
&Updation
ADDITION OF MEMBERS
Updatiing MembersVERIFICATION OF
MEMBER DATA
ADDITION OFMEMBER
MEMBER IDVERIFICATION
AUTHOR_RECORD
MEMBER_RECORD
PUBLISHER_RECORD
9
LIBRARY CARD DETAIL LIBRARY TRANSACTION
11
Book ID (PK)ISBN (FK)Book NameAuthor PublisherPagesBinding TypePurchase
Author NameBook NameISBN (PK)Publisher_Name
Member ID (PK)TitleFirst NameLast NameDate Of BirthAddressPostal CodeContact No.E-Mail IDCity Country
Library Card ID (PK)First NameLast NameAddressPostal Code
Trans_ID (PK)Library Card ID (FK)Book ID(FK)Issue DateReceive Date
DATABASE TABLE
(1) Table-Name: BOOK_RECORD This table is used for add book details into the Library.
Field Name Datatype
Size Constraints Description
Book_Id Varchar 25 Primary-keyISBN Number 12 Foreign key ISBN No. BookBook_Title Varchar 30 Name Of The BookPublishers Varchar 30 Publisher Of BookAuthor Varchar 20 Author Of BookPages Number 4 Pages In The BookBinding_Type Varchar 20 Soft Binding or Hard
BindingPurchase_Date Varchar 20 Comes In LibraryPrice Date Actual Price Of The BookStatus Number 10,2 Availability In The LibraryYear Varchar 30 Print YearPurchase_Source
Varchar 30 Dealer Name
Description Varchar 50
(2) Table-Name: MEMBER_RECORD This table is used for the Member Registration.
Field Data-type
Size Constraints Description
Member_ID Varchar 25 Primary key Name Of MemberTitle Varchar 25 Title Of Person Mrs/Ms.First_Name Varchar 16Middle_Name Varchar 50Last_Name Varchar 12Date_Of_Birth DateAddress Varchar 50 Address Of The MemberPostal_Code Number 6City Varchar 20Country Varchar 10Contact_No. Number 10E-Mail _ID Varchar 50Category Varchar 15 Student/Employee
12
(3) Table-Name : LibraryCard_Record This table is used for the keeping the record of Library card
13
Field Name Data type
Size Constraints
Description
LibraryCard_ID
Number 6 Primary key
First_Name Varchar 20Last_Name Varchar 20Address Varchar 50 Address Of the
MemberPostal_Code Number 6City Varchar 10
(4) Table-Name : LibraryTransaction_Record This table is used for the keeping the record of transactions in the Library
Field Name
Data type Size Constraints
Description
Trans_ID Number 20 Primary Key
LibraryCard_ID
Number 6 Foreign Key
Book_ID Number 20 Foreign keyIssue_Date Date Issuing DateReceive_Date Receiving Date
(5) Table-Name : Author_Record This table is used for the keeping the Author of The Books Separately.
Field Name Data type
Size Constraints
Description
ISBN Number 12 Primary Key
Author_Name Varchar 30 List Of AuthorsBook_Name Varchar 30 List Of BookPublisher_Name
Varchar 30 Publisher Of The Book
(6) Table-Name : SearchBook The table is used for search books by Book ID, Name, Publisher & Author.
Field Name
Data type Size Constraints
Description
Book_ID Number 12 Foreign Key
Book_Name Varchar 30 List Of AuthorsAuthor Varchar 30 List Of BookPublisher Varchar 30 Publisher Of The
Book
14
(7) Table-Name : PublisherDetail_Record The table is used for List all the Publisher who publish the Books.
Field Name
Data type Size Constraints
Description
Publisher_Name
Number 12 Unique Key
Type_Of_Books
Varchar 30 Puran/Upnishad/Ved etc.
Address Varchar 30 Address Of The Publisher
Postal_Code Varchar 30
City Varchar 20
Country Varchar 20
E-Mail_ID Varchar 30 E-Mail ID Of The Publisher
Website Varchar 40 Webiste Of The Publisher
(8) Table-Name : LoginDetails_Record The table is used as Login Master where the Login ID and Password record for the Librarian/Administrator.
Field Name
Data type Size Constraints
Description
User_ID Varchar 12 Primary Key
Unique Login ID
Password Varchar 20 Unique PasswordName Varchar 30 Name Of
AdministratorContact_No. Number 10 Contact No. Of
Admin
15
16
BOOK RECORD
YEAR AUTHORISBN
PRICE
STATUS
PUBLISHER
BOOK ID
TITLE
ENTITY RELATIONSHIP DIAGRAM
STATUS
BOOK ID
DESCRIPTION
HAS
SEARCH
BOOKID
AUTHOR HASISBN
AUTHORNAME
BOOKNAME
PUBLISHER
HAS
PUBLISHERNAME
TYPES OFBOOK
CONTINUED(ER DIAGRAM)……
17
STOREDIN
LIBRARY
WORKSIN
SINCE
LIBRARIANLOGINMEMBER
MEMBERID
NAME
ADDRESS
DOB
PHONE
OWN
LIBRARYCARD DUESNUMBE
R
HOLDS
UNTILL
QUEUE
EXIT
PAY
Number of Modules :1) Main Menu 2) Administrator Login Module3) User Module4) Book Management5) Member Management6) Book Issue Module 7) Book Return Module8) Transaction Module9) Reporting Module
10) Security Module
Processing Logic of The Above Modules :
1) Main Menu This module contains number of options like Book enquiry, New Book, Member Registration, Library Card details, transactions from the Library rules and reports.
2) Adm inistrator Login Module This is the main module of this Project where a Librarian can Login for managing the Library.
The administrator can read and write information about any member. The administrator can also update, create and delete the record of membership as per requirement and implementation plans.
3) User Module In this module the members or members of the Library can check the availability of books present in the Library.
18
MODULES AND THEIR PROCESSING LOGIC
4) Book Management The book module is deal by the Administrator who has to capable of introduce new books , modify Book details , Author and Publisher details which created separately for ease in finding the books either by Publisher or Author name.
5) Member Management This module is concerned with the Members of the Library. In this module the Administrator add the new members of the Library , update the details of the existing members .
6) Book Issue Module This module allows members to give their books to the librarian for issuing that book from the library. A particular member can borrow a maximum of three books only at a time. Each book can be borrowed for a maximum of 14 days.
7) Book Return ModuleThis module allows members to return books in library. This module is accessible by administrator and librarian both. Books, which are returned after 14 days from the borrowed date, are charged 1 Rupee per day. The member must pay for the fines when returning their books. Fines that are not paid, does not allow the member to borrow and more books from the library and the account of the member is locked . The library administrator can only unlock the member account by logging into the system and unlocking the member account.
19
8) Transaction ModuleThis module contains all the transaction related information as well also for transaction from the Library. Information like when the books was issued to the particular member, when it will return etc.
9) Reports ModuleThis portion of the Project generates all the reports of the Library like trasanction related , issue or return related, member addition /removal related, addition or subtraction of books from Library related . The whole activity happened in the Library is contained in this portion.
10) Security Module This module contains the information of user (Administrator and Member) authentication details like User ID and Password.
Software testing is a critical element of software quality assurance and represents the ultimate review of specifications, design and coding . The testing phase involves the testing of system using various test data; Preparation of test data plays a vital role in the system testing . After preparation the test data , the system under study is tested.
Unit testing conducted to verify the functional performance of each modular component of the software . Unit testing verifies the each smallest unit of the software design i.e module. Each unit was thoroughly tested to check if it might fall in any possible situation. This testing was carried out during the programming itself. Unit testing focuses on testing a unit of the code.
INTEGRATION TESTING
Integration testing is the next level of testing. This level of testing focuses on testing the integration of“Units of Code”or components.Integration testing is a symmetric technique for constructing tests to uncover errors associated with the interface. All modules are combined in this testing step. Then the entire program was tested as a whole.
VALIDATION TESTING
After the integration testing, software is completely assembled as a package . Interfacing errors have been uncovered and corrected. Validation testing can be defined in many ways, but in a simple way validation succeeds when the software functions is reasonably expected by the consumer.
21
Software validation is achieved through a series of black box tests that expose the requirement. After validation test has been conducted, one of two conditions exists.
The function or performance characteristics confirm to specification that are accepted.
A validation from specification is uncovered and a deficiency created.
OUTPUT TESTING
After performing the validation testing, the next step is output testing of the proposed system. Since a system does not produce the required output in the specific format required by user then then this testing act as test the output generator displayed on the system under consideration. Here the output is considered in two ways- one is onscreen and the other is printed format. The output format on the screen is found to be correct as the format was designed in the system design phase according to the user requirement. Hence output testing does not result any correction in the system.
ACCEPTANCE TESTING
User acceptance of the system is a key factor for success of any system. After the Output Testing we involved the User to make sure that the system worked according to their expectation.
22
Details Of Book Present in The Library Approved Member of the Library Issued Library Card of the Member Details Of Author in the Library Details Of Publisher in the Library Total number of modules and Sub Modules into the
Library Report for the Transaction done from the Library
HARDWARE SPECIFICATION
1) PROCESSOR : Intel Core i5 4th Genration2) HARD DISK : 20 GB and Above3) RAM : 8GB and Above
SOFTWARE SPECIFICATION
1) OPERATING SYSTEM : Windows 8.1 and Above
2) DOCUMENTATION TOOL : Microsoft Word 2013
TECHNOLOGY USED
1) OPERATING SYSTEM :- Windows 8.1
2) DEVELOPMENT TOOLS :
23
SYSTEM REQUIREMENTS
PROJECT REPORT
A. FRONT END :- Microsoft Visual Studio 2012B. BACK END :- SQL SERVER 2012
Once the system was tested ( module wise as well as integrated ) then comes we at the implementation of the system. In Implementing the new system, all the data to be transmitted from the old system to the new system but In this case the existing system was manual one and there was no need of transferring any old data.
TOP DOWN IMPLEMENTATION
A top-down approach (stepwise design or decomposition) is essentially the breaking down of a system to gain insight into its compositional sub-systems. In a top-down approach an overview of the system is formulated. A top-down model is often specified with the assistance of "black boxes", these make it easier to manipulate.
BOTTOM-UP IMPLEMENTATION
This Implementation begins with modules that do not call any other modules and works toward the main program. A Bottom-Up approach is the piecing together of systems to give rise to more complex systems , thus making the original systems sub-systems of the emergent system. Bottom-up processing is a type of information processing.
24
SYSTEM IMPLEMENTATION
FUTURE SCOPE OF THE PROJECT
Library Management system providing a complete solution for all the library requirements of Medium and small scale libraries. Currently we have few public libraries in the country with even few of them are computerized. Also the Title of My Project ( सं�स्कृ� ति� तिद्या�पी ठ कृम्प्यू�टरी कृ� � पी�स्�कृ�लयू व्यस्था� ) which indicates that this project is specially developed for Vaidic School Libraries. But in these days almost these types of Libraries are Manual. So the scope of this Project have the surety to grow that Libraries with Computerized System.
In any System there is always of chance of enhancement and extension. To enhance the library management level and work efficiency, using the Library Network Management System and this would greatly increases the work efficiency This System is also enhanced with the change of facilities. Here we can add more facility to the system for its growth. This System is developed for only for administrator of the system. So in future it can be enhance by the Online Library Management System. So a user can also request for the book.
25
FUTURE ENHANCEMENT OF THE PROJECT
The End
26
THANK
YOU
DECLARATIONI solemnly declaring that the
above project proposal created is true according to best of my knowledge or other collected contents . Signature Avinash Kumar Dubey Enrol. No. 126578740
