srs latest version

11
Online Library Management System Software Requirements Specification Date: 20/01/10 1 Online Library Management System Software Requirement Specification Team  Blackhawks4 Team Members K. Mahesh Kumar V. Vikram Varma  D. Lingam Sidharth Datar  Project Guide  Ms. Aruna Varanasi (Associate Professor)  Index: 1).overview & scope 2).Assumptions & Dependencies 3).Definitions, Acronyms & Abbreviations 4).Technologies to be used 5).Specific Requirements 6).Architecture diagram & Database Design 7).User Interface 8).References 

Upload: vikram-varma

Post on 29-May-2018

219 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 1/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

1

Online Library Management System

Software Requirement Specification 

Team Blackhawks4

Team MembersK. Mahesh Kumar 

V. Vikram Varma D. Lingam

Sidharth Datar 

 Project Guide Ms. Aruna Varanasi

(Associate Professor)

 Index:

1).overview & scope

2).Assumptions & Dependencies

3).Definitions, Acronyms & Abbreviations

4).Technologies to be used 

5).Specific Requirements

6).Architecture diagram & Database Design

7).User Interface

8).References 

Page 2: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 2/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

2

1).Overview & Scope

The aim of the project is to maintain the book information as online and to store

information maintains the members and lending and returning of the members as

well as maintain the reports for the members & books.

The Online Library Management System Project is done by using Java Servers

technology. The Online Library consists of many different modules each

 performing a particular task. When a new user has entered the site they need to

register themselves. Later 

when the user wants to take a book he/she simply submits their details. At this

stage the user can view the details of the book which are present in the online

library .The user can view the number of members in the list as well as the prices

of each book as well. If the user wants to

return the book, then at any time they can return it. After selecting the books they

want, then he/she will be asked with their name.The process and scope of the project is as follows:

i. 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.

ii. The user of this Online Library Management System can be able to see the

status of the books/journals that are borrowed/reserved by him and 

the respective due dates and other relevant details.

iii.The user can also 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 author/subject etc..,

iv.The Administrator can place requests for purchasing new books to the library,by giving details about the name of the book, name of the

author, publisher.

v. One can see the information regarding, who has borrowed a particular 

book/journal and when is the due date for the same.

vi. Any user of this system can cancel the reservation made earlier for a particular 

book/journal.

vii. There is an option of reserving a particular book/journal borrowed by others

currently.

viii. 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 thedetails. Then, a mail should be sent to people who are having the book 

currently, stating a reservation has been made on that book. 

Page 3: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 3/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

3

 Developing an Online Library initiative is a typically much larger endeavor than

that of an ordinary library. Consider the increased expenses, number of people

involved, development time, technological requirements, and delivery options.

This system can be used to search for books/magazines, reserve books, find out who is having a particular book, put in requests to buy a new book etc.

Users of the system:

College Students, Faculty, Book authors, Publishers.

These users are authenticated by issuing userid, password to the Admin and as

well as it is checked from the database. Suppose it is reserved, then the mail will

be sent to Admin and admin will send the mail to every one who requires the

books.

 Administration:This module deals with all the administration tasks like checking the user status,

checking the books status and performing the issues and return operations. This

can be done by both admin and librarian.

Student: They gives use rid and password if it is validated then they are allowed 

to get view details,

 Faculty: Likewise students, the faculties are giving the user id and password and 

after validating it should be entered inside of it. And search by name and author’s

name,etc. As like as, students, faculties, the publishers and authors, they can

contact and validated by userid and password. After it, they search and view

details.

 2).Assumptions $ Dependencies

•            The details related to the book, student, library and book issuing and 

returning details were provided manually..

•   Administrator is created in the system already.

•                 Roles and tasks are predefined..

Constraints

•  GUI is only in English.

•   Login and password is used for identification of customer a    nd there is no

 facility for guest.

•    This system is working for single server.

•    There is no maintainability of back up so availability will get effected.

•     Limited to HTTP/HTTPS. 

Page 4: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 4/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

4

 3).Definitions, Acronyms and Abbreviations

    HTML: Hypertext Markup Language is a markup language used to design static

web pages.

    EJB: Enterprise Java Beans.

    J2EE: Java 2 Enterprise Edition is a programming platform— part of the Java

Platform— for developing and running distributed multitier architecture Java

applications, based largely on modular software components running on an

application server.

    DB2: DB2 Database is the database management system that delivers a flexible

and cost effective database platform to build robust on demand business

applications.

   WAS: Web sphere application server is an application server that runs business

applications and supports the J2EE and web services standards.

   WSAD: Web sphere studio application developer is a toolkit which is designed for 

the creation of more complex projects, providing fully dynamic web application

utilizing EJB’s . This consist of EJB tools , CMP ,data mapping tools & a

universal test client that is designed to aid testing of EJB’s.

    HTTP: Hypertext Transfer Protocol is a transaction oriented client/server 

 protocol between web browser & a Web Server.

    HTTPS: Secure Hypertext Transfer Protocol is a HTTP over SSL (secure socket 

layer).

   TCP/IP: Transmission Control Protocol/Internet Protocol, the suite of 

communication protocols used to connect hosts on the Internet. TCP/IP uses

several protocols, the two main ones being TCP and IP.

 4).Technologies to be used 

    J2EE: Application Architecture

 Xml: configuration file

eForms: webtier 

 Ajax: using java script 

Web2.0: webservice

 DB2: Database

   WSAD: Development Tool

   WAS: Web Server 

    Rational: Design Tool

 5).Specific Requirements

 Have hours of operation that are 24 x 7- Because system can be an automated 

 process, so it can stay open for 24 hours a day. If the base is now the entire world,

staying open 24 hours a day becomes critical. System is required to be available

Page 5: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 5/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

5

24X7 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.

 Reduce the cost of a sales transaction- To the extent that one can automate the

sales process through this system, one can start to reduce the cost of that sales

transaction. This is particularly true of mundane sales transactions where thecustomer knows what they want.

 Make the existing Web site more dynamic in nature- 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.

Tie the existing Web site into 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 enterpriseservers that can be connected to the Web servers to make this process far more

effective.

 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

6).Architecture diagram & database design

Fig: Architecture Diagram

 Database DesignTABLE #1 NAME: ADDBOOKS

Page 6: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 6/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

6

  BN VARCHAR2(30 BYTE),

  BC VARCHAR2(30 BYTE)

  AUT VARCHAR2(30 BYTE),

  DOA VARCHAR2(30 BYTE),

PR NUMBER(10),

  RN NUMBER(10),SUB VARCHAR2(30 BYTE),

PUB VARCHAR2(30 BYTE),

STATUS VARCHAR2(30 BYTE)

TABLE#2 NAME: BOOKSRESERV 

USERID VARCHAR2(30 BYTE),

 BOOKID VARCHAR2(30 BYTE),

  DOR DATE 

TABLE#3 NAME: FINES

SID VARCHAR2(30 BYTE),

FINE NUMBER,

  DOR DATE 

TABLE#4 NAME: ISSUE 

  LIN VARCHAR2(30 BYTE),  LBN VARCHAR2(30 BYTE),

  LDOI DATE,

  LDOE DATE 

TABLE#5 NAME: MAIL

  ID NUMBER(5),

FROMADD VARCHAR2(20 BYTE),

TOADD VARCHAR2(20 BYTE),

 DETAILS VARCHAR2(454 BYTE),SUBJECT VARCHAR2(100 BYTE),

  DOM DATE 

TABLE#6 NAME: ONLINEREG

UNAME VARCHAR2(30 BYTE) NOT NULL,

Page 7: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 7/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

7

PWD VARCHAR2(30 BYTE),

FNAME VARCHAR2(30 BYTE),

  LNAME VARCHAR2(30 BYTE),

  EMAIL VARCHAR2(30 BYTE),

PHONE VARCHAR2(15 BYTE),

  ADDR VARCHAR2(30 BYTE),CITY VARCHAR2(30 BYTE),

STATE VARCHAR2(30 BYTE),

PIN NUMBER(10),

COUNTRY VARCHAR2(30 BYTE),

 MEMTYPE VARCHAR2(15 BYTE),

  BRANCH VARCHAR2(10 BYTE)

TABLE#7 NAME: REQUESTNEWBOOKS

USERID VARCHAR2(20 BYTE),  BNAME VARCHAR2(20 BYTE),

SNAME VARCHAR2(20 BYTE),

  ANAME VARCHAR2(20 BYTE),

PNAME VARCHAR2(20 BYTE),

  ENAME VARCHAR2(20 BYTE),

  ID NUMBER(10)

7).User Interface

   Client on Internet will be using HTTP/HTTPS protocol.

Client     on Intranet will be using TCP/IP protocol.

Software Interface:Client on Internet: Web Browser, Operating System (any)

Client on Intranet: Client Software, Web Browser, Operating System (any)

Web Server: WAS, Operating System (any)

 Data Base Server: DB2, Operating System (any)

 Development End: WSAD (J2EE, Java, Java Bean, Servlets, HTML),

 DB2, OS (Windows), Web Server.

 Hardware Interface: Client Side

· Processor RAM Disk Space

· Internet Explorer 6.0

· Pentium II at 500MHz

· 64 MB 1 GB

· MINIMUM 1GB HARD DISK SPACE 

· STANDARD I/O PERIPHERALS

Page 8: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 8/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

8

Server Side

Software Requirements:

· OPERATING SYSTEM: WINDOWSXP/ 

2000,UNIX 

· LANGUAGE: JAVA (JDK1.5 OR HIGHER VERSION)

· Web sphere application server V6.1· Pentium III at 1GHz

· 512 MB 2 GB

· DB2 Express- C or DB2 UDB

· 512 MB 1GB (Excluding data size)Data flow Model Survey: 

 Data Flow Diagrams

Page 9: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 9/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

9

Page 10: Srs Latest Version

8/9/2019 Srs Latest Version

http://slidepdf.com/reader/full/srs-latest-version 10/11

Online Library Management System 

Software Requirements Specification  Date: 20/01/10

10

8).References

•     Java Complete Reference by Herbert Shield  

•     Database Programming with JDBC and Java by George Reese 

•     Java and XML by Brett McLaughlin 

•     Wikipedia, URL: http://www.wikipedia.org.

•     Answers.com, Online Dictionary, Encyclopedia and much more,URL: http://www.answers.com

•     Google, URL: http://www.google.co.in 

•     H.M.DIETEL.P.J.DIETEL, Java How to Program, PhL, Second Edition 

•    Gray Cornett, Horstmann, CorelJava, Sunsoft Press, 1996. 

•    Patrick Naughton & Herbert Schildt, Java: The Complete Reference,

Tata McGrawHill,March 1997 .

•    Grady Booch, Object Oriented Analysis and Design with Applications,

The Benjimin/Cummings, 1994.

      Java 1.3 unleashed ”

•    The JDK1.4 tutorial” by Greg Travis•     Complete Reference Java, 2nd  Edition” by Herbert Schlitz.

•    Core Java Foundation Class by Kim Topley 

•     Introduction to Programming Using Java: An Object Oriented Approach

by

 David M.Arnow and Gerald Weiss.

•    Thinking in java by Bruce Eckel.