A Software requirements specification

On

Online Library Management System

MENTOR: SUBMITTED BY:

Name of faculty Ujjwal Madawat(14ESKIT092)
Pravesh ranawat(14ESKIT302)
(Dept. of information technology)
COORDINATOR:

(Dept. of Information technology)

 Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms and Abbreviations
1.4 Tools Used
1.5 References
1.6 Technologies to be used
1.7 Overview
2. Overall Description
2.1 Product Perspective
2.2 Software Interface
2.3 Software Interface
2.4 Hardware Interface
2.5 Communication Interface
2.6 Constraints
2.7 Functional requirements
3. Specific Requirements
3.1 E-R Diagram
3.2 Use-Case Diagram
3.3 Class Diagram
3.4 Activity Diagrams
3.5 Sequence Diagrams
 Introduction

1.1 Purpose
The SRS typically contains the brief description of the project. The purpose of the requirement
document is to specify all the information required to design, develop and test the software.
The purpose of this project is to provide a friendly environment to maintain the details
of books and library members.
The main purpose of this project is to maintain easy circulation system using
computers and to provide different reports.

1.2 Scope
The document only covers the requirements specifications for the Library Management
System. This document does not provide any references to the other component of the
Library Management System. All the external interfaces and the dependencies are also
identified in this document.

1.3 Definitions, Acronyms and Abbreviations

1 SRS -> Software Requirement Specification

2 JAVA -> platform independence
3 SQL -> Structured query Language
4 DFD -> Data Flow Diagram
5 CFD -> Context Flow Diagram
6 ER -> Entity Relationship
7 IDE -> Integrated Development Environment

1.4 Tools Used

1.4.1 Application architecture JAVA, J2EE

JAVA
 Java is an object-oriented programming language developed by Sun Microsystems a
company best known for its high end UNIX workstations. Java language was designed to
be small, simple, and portable across platforms, operating systems, both at the source and
at the binary level, which means that Java programs (applet and application) can run on
any machine that has the Java virtual machine (JVM) installed.
J2EE
Java Platform, Enterprise Edition or Java EE is a widely used platform for server
programming in the Java programming language. The Java platform (Enterprise Edition)
differs from the Java Standard Edition Platform (Java SE) in that it adds libraries which
provide functionality to deploy fault-tolerant, distributed, multi-tier Java software, based
largely on modular components running on an application server.

1.4.2 Web server WASCE

WebSphere Application Server Community Edition (from now on WASCE) is a free,
certified Java EE 5 server for building and managing Java applications. It is IBM's supported
distribution of Apache Geronimo that uses Tomcat for servlet container and Axis 2 for web
services. Over 15 WASCE developers are committers in the Apache Geronimo project.

1.4.3 Database platform DB2

DB2 Database is the database management system that delivers a flexible and cost effective
database platform to build robust on demand business applications and supports the J2EE and
web services standards.

1.4.4 Design tool Rational Software Modeler

IBM Rational Software Modeler, (RSM) made by IBM's Rational Software division, is a
Unified Modeling Language UML 2.0-based visual modeling and design tool. Rational Software
Modeler is built on the Eclipse open-source software framework and includes capabilities
focused on visual modeling and model-driven development (MDD) with the UML for creating
resilient, thought-out applications and web services.
1.5 References
Object Oriented Modeling and Design with UML-Michael Blaha, James Rambaugh.
Software Engineering, Seventh Edition, Ian Sommerville.
IBM Red Books.
IBM TGMC Sample Synopsis.
IBM www.ibm.in/developerworks.
Java - www.sun.com
Wikipedia - www.wikipedia.com
Database Management Systems - Navathe.
Complete Reference - J2EE - Keogh.

1.6 Technologies to be used

DB2: Relational Database Management System.
WASCE: Websphere Application Server Community Edition.
Rational Software Modeler.

1.7 Overview
The implementation of Library Management starts with entering and
updating master records like book details, library information. Any further transaction
like book issue, book return will automatically
update the current books. The proposed Library Management System will take care of
the current
book detail at any point of time. The book issue, book return will update the current book
details automatically so that user will get the update current book details.

Overall Description

2.1 Product Perspection

 The Online Library System is a package to be used by Libraries to improve the efficiency of
Librarians, Library employees and Users. The Online Library System to be developed
benefits greatly the members and the Librarian of University of Houston-Clearlake. The
system provides books catalog and information to members and helps them decide on the
books to borrow from the library. The Librarian can keep the books catalog updated all the
time so that the members (students and the professors) get the updated information all the
time.

The complete overview of the system is as shown in the overview diagram below:
The product to be developed has interactions with the users: Librarian, Members
who are the students and professors of the UHCL.

The product has to interact with other systems like: Internet, Billing System and
the UHCL Information Security System.

2.2 Product Functions

The Online Library System provides online real time information about the books
available in the Library and the user information. The Product functions are more
or less the same as described in the product perspective. The functions of the
system include the system providing different type of services based on the type of
users [Member/Librarian].

The member should be provided with the updated information about the books catalog.
Provisions for the members to borrow the books they want, if all the other required
rules hold good.
The member is given a provision to check his account information and change the
account information any time in the given valid period.
The members are provided with the books available roster and allowed to choose the
books, which they want to use in the coming up days.
The librarian can get the information about the members who have borrowed or
returned the books.
The librarian is provided with interfaces to add/delete the books available in the book
catalog.
The members when complete the book borrowing or returning process, the due to be
paid by the member must be calculated and the information about the member and
the due amount is sent to the university billing system.
The system uses the University information security requirements to provide the login
facility to the users.

2.3 Software Interface

 Client on Internet
Web Browser, Operating System (any)
Client on Intranet
Web Browser, Operating System (any)
Web Server
WASCE, Operating System (any)
Data Base Server
DB2, Operating System (any)
Development End
RAD (J2EE, Java, Java Bean, Servlets, HTML, XML, AJAX), DB2, OS (Windows),
WebSphere (Web Server)

2.4 Hardware Interface

Minimum Requirements:
Client Side
Processor RAM Disk Space

Internet Explorer - 6 Intel Pentium III or 128 MB 100 MB

AMD -800 MHz

Server Side
Processor RAM Disk Space
500 MB
DB2 - 9.5 Intel Core i5 2GB (Excluding Data
Size)

Recommended Requirements:
Client Side
Processor RAM Disk Space
Internet Explorer - 6 Intel Core i5 2GB 100 MB
2.5 Communication Interface
Client (customer) on Internet will be using HTTP/HTTPS protocol.
Client (system user) on Internet will be using HTTP/HTTPS protocol.

2.6 Constraints

The information of all the users must be stored in a database that is accessible by the
Online Library System.
The college information security system must be compatible with the Internet
applications.
The Online Library System is connected to the university computer and is running all 24
hours a day.
The users access the Online Library System from any computer that has Internet
browsing capabilities and an Internet connection.
The billing system is connected to the Online Library System and the database used by
the billing system must be compatible with the interface of the Online Library System.
The users must have their correct usernames and passwords to enter into the Online
Library System.

2.7 Functional requirements:

Book entry: In this module we can store the details of the books.
Register student: in this module we can keep the details of the new student.
Book issue: This module is used to keep a track of book issue details.
Book return: This module enables to keep a track of return the books.
 Specific Requirements

3.1 ER Diagram

3.2 Use Case Diagram

 Fig2.2: Use Case Model Survey

3.3 Class Diagram

3.4 Activity Diagrams
3.5 Sequence diagram