Software Requirements Specification for Online Library and Digitization

1. Introduction
1.1 Purpose
The purpose of this document is to record the requirements for the design and development of Online Library and Digitization for general purpose. This document is used by designers, testers, programmers and others during the development and maintenance of the software. The document will also serve the basis for acceptance testing by the user. As such it is an evolving document reflecting the current requirement of the project as understood by the project team. This document is actually provided to provide the need of the product and how the needs are resolved for the end users.

1.2 Document Conventions

There are number of conventions that we have used which are as follows:

Font style used for headings and normal sentences is Times New Roman. Bold letter with font size 16 points showing the headings and with font size 14 points showing the sub headings and for normal sentences it is 12 points without bold. All the sub divided points are started with a bullet sign

1.3 Intended Audience and Reading Suggestions

Some of the different types of readers that the document is intended for are client, developers, testers, quality assurance team, faculties (for academic purpose), supporting higher authorities and the persons who are going to extend the project. Other then the above mentioned following will also be the intended audiences for this document.

The team members. The administrative staff of S.D. Bansal College of Technology. The Project Supervisor and Project Coordinator.

1.4 Product Scope

The different areas where we can use this application are: Any education institute can make use of it for providing information about author, content of the available books, and manage their library systems. It can be used in offices, which have their own bookstores, and modifications can be easily done according to requirements.

Software Requirements Specification for Online Library and Digitization

1.5 References
UML Guide Software engineering by Pressman Various websites such as: o www.wikipedia.org o www.google.co.in

2. Overall Description
2.1 Product Perspective
Online Library and Digitization deals with handling the library functionalities online from any workstation. The system is a duo application that provides the user to manage a library online as well as provides an online book storage The Digital Library, which is a type of information retrieval system. This system will be used by members who may be students or professors of that University to check the availability of the books and borrow the books, and by the librarian to update the databases. In addition, this system will help in setting up the alerts, dealing with penalties and keeping track of all the transactions. The books available in the digital library can be read by any member of the library but the books can not be downloaded and are write protected.

2.2 Product Functions

Member can perform following operations: Can view the List of books available in each category. Can own an account in the library. Can view the books issued to him. Can set Alerts for books. Can view the history of books issued to him previously. Can visit digital library for reading. Administrator/Librarian can perform following operations: A librarian can issue a book to the student. Can view the List of books available in each category. Add books and their information of the books to the database. Edit the information of the existing books. Can access all the accounts of the students.

Software Requirements Specification for Online Library and Digitization

2.3 User Classes and Characteristics

There are two types of users for Online Library and Digitization. These includes: Administrator: The administrator will be the developer who will be responsible for enhancing the product features to satisfy the end user requirements. He is the person responsible for the proper functioning of the product, and for providing the trust to the end users that their requirements will be best fulfilled by this website providing the efficient working of the features included in the service. The administrator will provide the access authentication to the end user. End Users: These include the users who are licensed by the administrator to use the services of this application.

2.4 Operating Environment

Software requirement: Database: MySQL 5.1. JAVA: jdk1.6. HTML. Development Tool: Netbeans 6.8. Web Server: Apache Tomcat 5.2. Operating System: Windows XP service Pack 2 Hardware Requirements: Processor: Pentium IV and above Memory: RAM: 256 MB or more Hard disk space: 10 GB

2.5 Design and Implementation Constraints

Regulatory Policies: There are no regulatory policies. Hardware Limitations: There are no hardware limitations. Interfaces to other Applications: There shall be no interfaces. Control Functions: There shall be no control functions. Signal Handshake Protocols: This is no signal handshake protocols. Reliability Requirements: Total number of bugs in the system shall not exceed 1% of the total line number of code, except connection reliability which is out of our range.

2.6 User Documentation

Software Requirements Specification for Online Library and Digitization

No additional documentation would be provided except this SRS.

2.7 Assumptions and Dependencies

For this the user must have an elementary knowledge of internet so that he can make the maximum benefit of the website. Roles and tasks of users are predefined. The details related to the borrowing books or any other functionality is filled manually.

3. External Interface Requirements

3.1 User Interfaces
We will provide a very easy GUI which will be very helpful to the users. If the user is new and is login first time on the website then he will be provided with a login id and password, with which he can easily update and get the useful information. So the security factor is also taken into consideration as we are providing a unique login id to each user so that his/her data is secured.

3.2 Hardware Interfaces

Server side hardware requirements: Hard Disk: 20 GB minimum Processor: Pentium or higher Ram: 512 MB or higher Any network connection Client side hardware requirements: Hard Disk: 10 GB minimum Processor: Pentium or higher Ram: 256MB or higher

3.3 Software Interfaces

Server side hardware requirements: JSP as Front-end tool MySQL 5.1 Net-Beans 6.8
Apache Tomcat 5.2

Client side hardware requirements: Operating system with internet facility A web browser

Software Requirements Specification for Online Library and Digitization

3.4 Communications Interfaces

The Customer must connect to the Internet to access the Website: Dialup Modem of 52 kbps. Broadband connection. Dialup or Broadband Connection with a Internet Provider

4. System Features
The system includes the following features: Provide interface to User. Loading from the Database. Delete/Update record. Create/Delete User. Logon Capabilities Alerts of any changes.

4.1 Description and Priority

Proposed Database is intended to store, retrieve, update and manipulate information related to library of the institute and the registered user which include the full profile information of the end user of this service.

4.2 Stimulus/Response Sequences

Member can perform following operations: Can view the List of books available in each category. Can own an account in the library. Can view the books issued to him. Can set Alerts for books. Can read books online at digital library. Can search for a particular book. Administrator/Librarian can perform following operations: Librarian will manage the database as well as digital library. Can view the List of books available in each category Add books and their information of the books to the database

Software Requirements Specification for Online Library and Digitization

Edit the information of the existing books. Can access all the accounts of the students.

4.3 Functional Requirements

Librarian gets the updates about the books which are in demand or on which the alerts have been set. A dynamic list is displayed on clicking this link. The librarian can add new member, edit member details, view member details and search any member. He can also add new book in library, edit book details, trace a book, search a book and delete a book. It helps the librarian to keep a track of all the books in the library. Librarian as well as the member will be able to see the penalty on a book. A member can view all the books issued to him with the date of issue and alerts for the books to be returned or reissued and fine to be paid for any book. All the members of the library will also be able to read the books online at digital library. Users can logout to end the session.

4.4 Use Case Diagram

Librarian View:

Software Requirements Specification for Online Library and Digitization

User View:

Software Requirements Specification for Online Library and Digitization

5. Other Nonfunctional Requirements

5.1 Performance Requirements
The proposed system that we are going to develop will be used as the chief performance system for the different types of the end users that will use the services therefore, it is expected that the database would functionally perform all the requirements that are specified by the developers of the project and that are required by the end users of the project.

5.2 Safety Requirements The database may get crashed at any certain time due to virus or operating system failure.
Therefore, it is required to take the database backup.

5.3 Security Requirements

Each user will be asked to provide username and password to verify if the user is an authentic member of the library. The books available in the digital library are not modifiable and can not be downloaded by any user.

5.4 Software Quality Attributes

The quality of the product and the database is maintained in such a way so that it can be very user friendly to the end user other than that the product will be having certain qualities like adaptability, availability, correctness, flexibility, interoperability, maintainability, portability, reliability, robustness, testability and usability

6. Project Plan
6.1 Team Members
1. Aditya Gangrade (0829cs081005) 2. Amit Neema (0829cs081010) 3. Jatin Adwani (0829cs081039)

Software Requirements Specification for Online Library and Digitization

6.2 Division of Work

The work has been broadly divided into four main phases:
Phase Analysis Design Coding Testing Names Aditya Gangrade, Amit Neema, Jatin Adwani Aditya Gangrade, Amit Neema, Jatin Adwani Aditya Gangrade, Amit Neema, Jatin Adwani Aditya Gangrade, Amit Neema, Jatin Adwani

6.3 Time Schedule

SYNOPSIS SUBMISSION: 10 Days hence project allotment. SRS SUBMISSION: 15 Days after SYNOPSIS submission. SDS SUBMISSION: 15 Days after SRS submission. FINAL PROJECT SUBMISSION: 75 Days after SDS submission.

Appendix A: Glossary
Definitions, Acronyms, and Abbreviations 1) SRS: Software Requirement Specification 2) RAM: Random Access Memory 3) SQL: Structured Query Language 4) SDS: Software Design Specification 5) JSP: Java Server Pages 6) HTML: Hyper Text Markup Language 7) UML: Unified Modeling Language 8) JDK: Java Development kit