Online Library Management System SRS PHP MySql Abhishek Bhardwaj Live Demonstration Coding HTTP Abhishekbhardwaj TK

Online Library Management System Software Requirements Specification itchamps
Version 1.0 27-02-2011
itchamps
Online Library Management System

Synopsis Requirements Specification
Version 1.0
Team Name
: itchamps
Team Members : Abhishek Bhardwaj (0806813002) EMail: abhishekbhardwaj241@gmail.com Anshu Sagar (0806813009) Gaurav Kumar (0806813019) Submitted To : Ms. Anshika Nagpal Course : B.Tech. (I.T. 6th Semester)
College Name : Meerut Institute Of Enginerring & Technology. Meerut.

itchamps, MIET Meerut U.P. Page 1
Version 1.0 27-02-2011
State
Uttar Pradesh
Revision History
Date
27-02-2011
Version
1.0
Description
First SRS
Author
itchamps
itchamps, MIET Meerut U.P.
Page 2
Version 1.0 27-02-2011
Table Of Contents
Description 1.0 Page No.
Introduction05 1.1 1.2 1.3 1.4 1.5 1.6 Purpose..................................................................................05 Scope.....................................................................................05 Definition, Acronyms, and Abbreviations ............................06 References.............................................................................07 Technologies to be used........................................................07 Overview...............................................................................07
2.0
Overall Description........08 2.1 Product Perspective..............................................................08 2.2 Software Interface................................................................08 2.3 Hardware Interface...............................................................09 2.4 Communicational Interface.................................................09 2.5 Product Function..........09 2.6 User Characteristics.10 2.7 Constraints....10
Page 3
Version 1.0 27-02-2011
2.8 2.9
Use Case Model Description ..10 Database Design...12
2.11 Assumptions & Dependencies...20
3.0
Specific Requirements21 3.1 3.2 State Diagrams as System use case reports.21 Supplementary Requirements33
Page 4
Version 1.0 27-02-2011
Software Requirements Specification

1.0 Introduction
1.1 Purpose:
Conventionally the readers have to go to library for searching books & magazines and they may have to stand in long reservation lines for reserving/issuing the material. This kind of functionality leads in wastage of time and extra efforts. Here we have provided an online facility through which anyone, anywhere in campus, having a library account can search for and reserve books, find out who is having a particular book and put in a request to library for buying new books.
1.2
Scope: The scope of Online Library Management System includesCreate different system users based on their roles and permissions. Authenticate users at their login. Provide mechanism of searching available books and magazines using title, author name, or field of the book. Facility to reserve books or journals or magazines. An status page for all users to view books or magazines reserved by them, their respective due dates, their respective fines if any. Facility for cancelling a reservation for a book made earlier. Facility for reserving books that are borrowed by others currently. A facility for searching about a user having a particular book and its due date for the same. An interface to review user history. Impose fines on users considering holidays, exams or special leaves. Provide mechanism for changing account settings such as passwords, choosing from different skins & etc.
Reports exportable in .XLS, .PDF or any other desirable format.
Page 5
Version 1.0 27-02-2011
Place an automated email, on reserving a book, to the user who has currently reserved it and to all of the users who are having that book, stating that the particular book has been reserved. Place requests for purchasing new books to the library, by giving details about the name of the book, name of the author, publisher. Add new book details to the store. Removing particular book details from library.
1.3
Definitions, Acronyms, and Abbreviations:

Librarian- He is able to add new books/journals/magazines and remove books from inventory. Users- Those who visits the service for searching, reserving and requesting for a book/journal/magazine. The system is designed for two users students and the faculty. User Detail- Details of an user such as name, id, address, contact number, reserved books, requested books and etc. Book Detail- Details of a book such as its title,publisher,author name, subject or field of book, number of pages etc. HTML- Hyper Text Markup Language. It is used to create static web pages. PHP(Hypertext Processor) - It is used to create dynamic web content. JavaScript- It is a client side scripting language. Mainly use for form validation and interaction between user and html page. AJAX- Asynchronous java script and XML.-used to change page content without reload. MySQL- MySQL Database is the database management system that delivers a flexible and free database platform to build robust on demand business applications.
Page 6
Version 1.0 27-02-2011
Apache HTTP Server- Apache HTTP Server is an server that runs business applications and supports the PHP and web services standards. HTTP- Hypertext Transfer Protocol is a transaction oriented client/server protocol between web browser & a Web Server. XML (Extensible Markup Language):-It is a markup language that was designed to transport and store data.
1.4
References:
IEEE SRS format Problem Definition(Provided by IBM)
1.5
Tools & Technologies to be used: HTML Hypertext Markup Language. PHP Hypertext Processor, a Server-side scripting language. MySQL- MySQL community server, freeware database provided by
ORACLE.
AJAX - Asynchronous Java Script and XML. XML - Extension Markup Language. JavaScript Client-side scripting language. Apache Apache HTTP server 1.6 Overview Overall Description - will describe major components of the system,
interconnection and external interfaces.
Specific Requirements -
will describe the functions of actors, their role in the system and constraints.
Page 7
Version 1.0 27-02-2011
2.0 Overall Description

Describes the general factors that affect the product and its requirements.
2.1
Product Perspective :
The web pages (XHTML/PHP) are present to provide the user interface on client side. Communication between client and server is provided through HTTP/HTTPS protocols. The Client Software is to provide the user interface on system user client side and for this TCP/IP protocols are used. On the server side web server is for PHP and database server is for storing the information.
2.2
Software Interface:
Client on Intranet - Web Browser, Operating System (any) Web Server - Apache Http Server, Operating System (Windows based) Data Base Server - MySQL, Operating System (Windows based)
Page 8
Version 1.0 27-02-2011
Development End - PHP, MySQL, Windows based OS, Web Server.
2.3
Hardware Interface:
Minimum hardware requirements Client Side IE6.0 & above, Chrome, Mozilla firefox Processor Pentium III at
500MHz
RAM 128 MB
Disk Space 1GB
Server Side Processor Apache HTTP Server V2.2.17 MySQL V5.5.8 Pentium IV at 1.3 GHz Pentium IV at 1.3 GHz RAM 512MB Disk Space 100MB
512MB
200MB(Excluding Data Size)
2.4 2.5
Communication Interface :
Client on Internet will be using HTTP/HTTPS protocol.
Product Functionalities:
A Person Should be able to login to the system through the first page of the application and change the password after login into the system. see the status of the books/journals borrowed/reserved by him and the respective due dates and other relevant details search for a particular book/journal based on the name of the book/name of the author/subject/etc and also list for books/journals based on the name of the autor/subject etc
Page 9
Version 1.0 27-02-2011
place requests for purchasing new books to the library, by giving details about the name of the book, name of the author, publisher. see who has borrowed a particular book/journal and when is the due date for the same cancel the reservation made earlier for a particular book/journal reserve a particular book/journal borrowed by others currently As soon as a reservation is made for a particular book, an automatic mail should be sent to the person who made the reservation about the details. Then, a mail should be sent to people who are having the book currently, stating a reservation has been made on that book.
Reports exportable in .XLS, .PDF or any other desirable format.
2.6
User Characteristics
Every user should be comfortable of working with computer and net browsing. He must have basic knowledge of English too.
2.7
Constraints
GUI is only in English. Login and password is used for identification of customer and there is no facility for guest.
2.8
Use Case Diagram-
Page 10
Version 1.0 27-02-2011
1. Librarian- Responsible for activities such as adding book records, deleting book records, updating book status such as if book is issued & etc.
2. Library Database- Responsible for keeping records of all present & requested books in library. 3. Guest- Registers for a new account for becoming a library member. 4. User- Already registered member who can access library services such as searching books, registering books, requesting for new books and etc.
2.9
Database DesignPage 11
Version 1.0 27-02-2011
ER Diagram-
Page 12
Version 1.0 27-02-2011
1 Database library
1.1 Table structure for table books
Field id name author publisher subject type days Type int(5) Null Default No
varchar(100) No varchar(100) No varchar(100) No varchar(50) No varchar(20) No int(3) No No No Yes NULL
fine_per_day int(3) copies available int(3) int(3)
1.2 Table structure for table books

Field id name author publisher subject type days Type int(5) Null Default No
varchar(100) No varchar(100) No varchar(100) No varchar(50) No varchar(20) No int(3) No No Page 13
fine_per_day int(3)
Online Library Management System Software Requirements Specification itchamps copies available int(3) int(3) No Yes NULL
Version 1.0 27-02-2011
1.3 Table structure for table course

Field id name Type int(2) Null Default No
varchar(20) No No 0 Yes NULL
max_books int(2) tbl int(2)
1.4 Table structure for table course

Field id name Type int(2) Null Default No
varchar(20) No No 0 Yes NULL
max_books int(2) tbl int(2)
1.5 Table structure for table faculty

Field uname fname lname email pass reg Type Null Default
varchar(25) No varchar(20) No varchar(20) No varchar(25) No varchar(50) No char(15) No
Page 14
Online Library Management System Software Requirements Specification itchamps department varchar(25) No photo activated varchar(35) No int(1) No
Version 1.0 27-02-2011
1.6 Table structure for table faculty

Field uname fname lname email pass reg Type Null Default
department varchar(25) No photo activated varchar(35) No int(1) No
1.7 Table structure for table faculty_activity

Field Type Null Default
uname varchar(30) No time timestamp No CURRENT_TIMESTAMP
status varchar(500) No doc varchar(100) Yes NULL
1.8 Table structure for table faculty_activity

Page 15
Online Library Management System Software Requirements Specification itchamps uname varchar(30) No time timestamp No CURRENT_TIMESTAMP
Version 1.0 27-02-2011
status varchar(500) No doc varchar(100) Yes NULL
1.9 Table structure for table failed_reservations

Field bookid uname Type int(3) Null Default No
varchar(30) No
last_rep_date varchar(10) No
1.10 Table structure for table failed_reservations

varchar(30) No
last_rep_date varchar(10) No
1.11 Table structure for table holidays

Field date month year Type int(2) int(2) int(2) Null Default Yes NULL Yes NULL Yes NULL
description varchar(100) Yes NULL
1.12 Table structure for table holidays

Page 16
Online Library Management System Software Requirements Specification itchamps date month year int(2) int(2) int(2) Yes NULL Yes NULL Yes NULL
Version 1.0 27-02-2011
description varchar(100) Yes NULL
1.13 Table structure for table issue

varchar(30) No No No No
return_dd int(2) return_mm int(2) return_yyyy int(4) type
varchar(15) No
1.14 Table structure for table issue

varchar(30) No No No No
return_dd int(2) return_mm int(2) return_yyyy int(4) type
varchar(15) No
1.15 Table structure for table librarian

Page 17
Online Library Management System Software Requirements Specification itchamps id int(2) No
Version 1.0 27-02-2011
uname varchar(25) No pass char(50) No
1.16 Table structure for table librarian

Field Type id int(2) Null Default No
uname varchar(25) No pass char(50) No
1.17 Table structure for table new_book_request

Field name author Type Null Default
varchar(100) Yes NULL varchar(100) Yes NULL
publisher varchar(100) Yes NULL subject time varchar(100) Yes NULL timestamp No CURRENT_TIMESTAMP
1.18 Table structure for table new_book_request

Field name author Type Null Default
varchar(100) Yes NULL varchar(100) Yes NULL
publisher varchar(100) Yes NULL subject time varchar(100) Yes NULL timestamp No CURRENT_TIMESTAMP
Page 18
Version 1.0 27-02-2011
1.19 Table structure for table reserve

Field Type res_id int(10) bookid int(3) Null Default No No 0
uname varchar(30) No type dd mm yyyy varchar(20) No int(2) int(2) int(4) No No No
1.20 Table structure for table reserve

Field Type res_id int(10) bookid int(3) Null Default No No 0
uname varchar(30) No type dd mm yyyy varchar(20) No int(2) int(2) int(4) No No No
1.21 Table structure for table student

Field uname fname lname Type Null Default
varchar(25) No varchar(20) No varchar(20) No
Page 19
Online Library Management System Software Requirements Specification itchamps email pass reg course photo varchar(25) No varchar(50) No char(15) No
Version 1.0 27-02-2011
varchar(25) No varchar(35) No No
activated int(1)
1.22 Table structure for table student

Field uname fname lname email pass reg course photo Type Null Default
varchar(25) No varchar(35) No No
activated int(1)
2.11 Assumptions and Dependencies

The end user should have a basic knowledge of English and computer usage. Administrator is created in the system already. Roles and tasks are predefined.
Page 20
Version 1.0 27-02-2011
3.
3.1
Specific Requirements
State Diagrams As System Use Reports
3.1.1 State diagram of whole system
Totally 12 windows. All states except "Display Exit Info" can go back to Main Menu. Help Content
Get Help Enter Book Info 14 do/ Insert a student into DB Reset Search books View Mylist Enter Search Info 2 Update/Delete Display Exit Info Display MyList 5 New Search exit/ Send from List message Check In/Out Exit Enter Search Info 11 Search Back Add a book Main Menu 1 Add a student
Enter Student Info 7 Search students do/ Insert student into DB
Display Results 12 entry/ Search students in DB
Search Add to list View Detail / UpdateDelete Update,Delete Check In/Out Update Detail 60 do/ Update,Delete Display Results 3 entry/ Search books in DB Check In/Out Enter books. student Info 13 do/ Check In, Check Out View Detail Check In/Out
Add to list Back
Display Book Detail 4 do/ Update, Delete
Page 21
Version 1.0 27-02-2011
3.1.2 Activity diagram of each operation
Student class
AddStudent : add a new student
validat eStudent
[ exists ]
return error message
[ not exist s ]
add the student record to Student table
return success message
DeleteStudent : delete an existing student
validat eStudent
[ not exist s ]
return error message
[ exists ]
delete t he student record to Student table
UpdateStudent : update information of existing student
Page 22
Version 1.0 27-02-2011
Update the student record in the Student table
SearchStudent : search students
Query the student record in Student table
return Resultset
ValidateStudent : validate student
Page 23
Version 1.0 27-02-2011
Query the student in Student table according to studentID
Return Resultset
[ not empty ]
Ret urn true
[ empty ]
Return false
Page 24
Online Library Management System Software Requirements Specification itchamps Book class
Version 1.0 27-02-2011
addBook: Add a new book in database
Check Book record in database
exist
yes
Return "Book already exist" message
no Insert book record in database
Page 25
Version 1.0 27-02-2011
exist: Check if the book record already exist in database.
Search Book record in database
found record?
no
return not exist message
yes return exist message
Page 26
Version 1.0 27-02-2011
searchBook: Search books in database
search book record in database
return resultset
updateBook: modify book info
update record in database
Page 27
Version 1.0 27-02-2011
deleteBook: Delete a book in database
check existence
exist? yes
no
delete the record
return fail message
Page 28
Online Library Management System Software Requirements Specification itchamps Transaction class
Version 1.0 27-02-2011
checkIn() : check in one book
SQL Statement (Update.....)
Exception? No return true
Yes Print "error message"
ret urn false
Page 29
Version 1.0 27-02-2011
checkOut() : check out one book
SQL Statement (Update.....)
ret urn false
Page 30
Online Library Management System Software Requirements Specification itchamps MyList class
Version 1.0 27-02-2011
addTolist() : add one book to mylist
SQL Statement (Insert.....)
ret urn false
Page 31
Version 1.0 27-02-2011
deleteFromList() : delete one book from mylist
SQL Statement (Delete.....)
ret urn false
Page 32
Version 1.0 27-02-2011
Mylist.viewList() : retrieve books in mylist
SQL Statement (Select....)
ret urn false
3.2
Supplementary Requirements
24 x 7 Availability - If the base is now the entire world, staying open 24 hours a day becomes critical. Because system can be an automated Process, so it can stay open for 24 hours a day. So UPS support must be on server site for at least 8 hours in case of power failure. System will remain inaccessible to users at 2:00 to 4:00 am for backup and maintenance purpose. Dynamic Website - Many early Web implementations consisted of static HTML pages. This becomes very difficult to manage if the number of pages gets too large. An effective system should be largely dynamic taking advantage of technology that automates this process rather than relying on manual processes. Application should serve dynamic user based customized web pages to its clients from server.
Integration with existing enterprise systems Any existing Web site that relies on the manual duplication of data from another system is one that can be improved. Most of the business data in the world today exists in enterprise servers that can be connected to the Web servers to make this process far more effective.
Page 33
Version 1.0 27-02-2011
Provide good performance and the ability to scale the server The Web application Server should provide good performance and the ability to manage performance with techniques, such as support for caching, clustering, and load balancing. Providing session management capability - Web application developers should not spend valuable time worrying about how to maintain sessions within the application. The Web Application Server should provide these services.
Page 34

Online Library Management System SRS PHP MySql Abhishek Bhardwaj Live Demonstration Coding HTTP Abhishekbhardwaj TK

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Online Library Management System SRS PHP MySql Abhishek Bhardwaj Live Demonstration Coding HTTP Abhishekbhardwaj TK

Uploaded by

Copyright:

Available Formats

Online Library Management System Software Requirements Specification itchamps

Version 1.0 27-02-2011