Software requirement specification

(SRS)

Team member
Elishba shafaqat
Tayyaba khalid
kainat saif
Table of content
Introduction...........................1

Overall description..................2

System feature.......................3

Module Discription...............................4

External Interface requirement...............................5

User Interfaces...................................6

i.Hardware interface

ii. Software interface

iii. Communication interface

Other Non_ fuctional Requirement...................8

i. Performace Requirement

ii. Security Requirement

iii. Software Quality Attributes

Reference..................10

Aim & Objectives.......................................11

Conclusion..............................................................12

Introduction
A development process consist of various phase ending with a define output. the main
reason for having a phased process is that it break the problem of developing software
into successfully performing a set of phase each handling a different concern of software
development. this ensure the cost of the development is lower than what it would have
been if the whole problem was tackled together futhermore a phased processe allow
proper checking for quality and progress at some defined points during the development
( end of process) without this one would have to wait until the end to see what software
has been produced

Any problem solving in software consist of these steps

·0 Requirement analysis

Requirement analysis is done in order to understand the problem the software system is
to solve

There are two major activites in this phase problem understanding or analysis and
requirement specfication. In problem analysis, the aim is to understand the problem
and its context and the requirement of new system that is to be developed. Once the
problem is analyzed and the essential understood, the requirement must be specified in
the requirement specification document the requirement document must specify all
functional and performance requirement; the performance of input output etc

·1 Software design
The purpose of design phase is to plan a solution of the problem specified by the
requirement document this phase is first step in moving from the problem domain to
solution domain

The design activity often result in three seperate outputs: architecture design, high level
design and detailed design

·2 Coding

The main goal of coding phase is to translate the design of the system into code in given
programming languge the coding phase affect both testing and maintenance profoundly.
The goal of coding should be to reduce the testing ana maintenance effort, hence during
coding the focus should on developing programs that are easy to read and understand.

·3 Testing

The function of testing is to detect the defect in the software. The main goal testing is to
uncover requirement design and coding error in the program.

The main goal of the requirement phase is to produce the software requirement
specfication which accurately capture the client`s requirement. SRS is a document that
describe what the software should do the basic purpose of SRS is to bridge the
communication gap between the clients, the End user and the software developers.
Another purpose is helping user to understand their own needs.

PURPOSE
1: The purpose of this project is to provide a friendly environment to maintain the
details of books and library members.

2:The main purpose of this project is to maintain easy circulation system

using computers and to provide different reports.

3:The library system is a package to be used by libraries to improve the effeciency of

librarians, library employee and users.

4:The system provides book catalog and information to members and helps them decide
to the books to borrow from library.

5:The librarian can keep the book catalog updated all the time so that the member
(Student and professor) get the updated information all the time.

SCOPE
 ·4 The document only covers the requirements specifications for the Library

Management System.

·5 All the external interfaces and the dependencies are also identified in this

document.

·6 The overall scope of the feasibility study is to provide sufficient information

to allow a decision to be made as to whether the Library Management

System project should proceed and if so, its relative priority in the context

of other existing Library Management Technology.

·7 This document does not provide any references to the other component of

the Library Management System.

OVERVIEW
·8 The implementation of Library Management updating master records like book
details, library information.

·9 Any further transaction like book issue, book return will automatically updated
the current books.

·10 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 the user will get the update current book
detail.

Functional requirements
·11 Administrator Menu

In this module we can do the following

Ø Admin should be able to insert, modify and delete books.

Ø Can accept or reject a new user according to the library policy.

Ø Can get the information of any member who has borrowed a

book.

Ø Add and edit book categories and arrange books by categories.

Ø Can record books returned by users.

 ·12 Book entry

In this module we can enter a new book and store it.

·13 Book issue

In this module we can issue a book to the student.

·14 Book record

In this module we can keep the records of various books

being issued and returned.

 ·15 Register student

In this module we can keep the record of how many

students have we registered.

 ·16 Non-Functional requirements

performance requirement
1. Data base should be updated within a second

2. Search result should be display with in a second

3. User interface shall not take more than 3 second to load

4. login should be validated within 2 seconds

·17 Security requirements

5. Every external communication between data server and end user takes place
through VPN

6. Payment information are protected and encrypted

·18 Safety requirement

In the event of failure there should be another data server be on standby to provide
fault tolerance capability

·19 Capacity requirement

Not more than 10,000 student to be register

Feasibilty study
The overall scope of feasibilty study was to provide sufficient information to allow a
decision to be made as to whether the library management system project should
proceed and if so its relative priority in the context of other existing library management
technology

The feasibilty study phase of this project had undergone through verious steps which
has describe under

·20 Identify the origin information at different level.

·21 Identify the expectation of user from computerrized system.

·22 Analyze the drawback of existing system (manual system)

Defination, Acronyms, Abbreivation

·23 JAVA -> Platform independance
 ·24 SQL -> Structured query language

·25 DFD -> Data flow diagram

·26 CFD -> Context flow diagram

·27 ER -> Entity relationship

·28 IDE -> Integrated development enviroment

·29 SRS -> Software requirement specification

·30 Reference

7. Java:- Balaguru swamy

8. SQL:- Josephl jordon

9. Other links

www.slideshare.net

e.wikipedia.org

Link: books.google.co.in/books?isbn=8120348982

·31 Flow chart of library management system

 ·32 Over view

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.

·33 Overall Description

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.

·34 Product function

10. The main purpose of this project is to reduce the manual work.

11. This software is capable of managing Book Issues, Returns, and

Calculating/Managing Fine. Generating various Reports for Record-Keeping
according to end user requirements.

·35 User characteristics:

We have 2 levels of users

12. User module: In the user module, user will check the availability of the books.

·36 Book return

ii. Administration module: The following are the sub module in the administration
module.

·37 Register user

·38 Entry book details

·39 Book issue

·40 General Constraints:

Any update regarding the book from the library is to be recorded to have update &
correct values.

·41 Assumption and dependencies:

All the data entered will be correct and up to date. This software package is
developed using java as front end which is supported by sun micro system. Microsoft
SQL server 2005 as the back end which is supported by Window 7.

·42 Specific Requirement:

·43 External Interface Requirement:

The user should be simple and easy to understand and use. Also be an interactive
interface .The system should prompt for the user and administrator to login to the
application and for proper input criteria

·44 User Interface:

The software provides good graphical interface for the user any administrator can
operate on the system, performing the required task such as create, update, viewing
the details of the book.

Allows user to view quick reports like Book Issues/Returned etc in between
particular time.

Stock verification and search facility based on different criteria.

 ·45 Hardware interface:

13. Operating system : window

14. Hard disk :40 GB

15. RAM : 256 MB

16. Processor : Pentium(R)Dual-core CPU

·46 Software interface :

17. Java language

18. Net beans IDE 7.0.1

19. MS SQL server 2005

·47 Communication interface:

Window

·48 Functional requirements:

20. Book entry: In this module we can store the details of the books.

21. Register student: in this module we can keep the details of the new student.

22. Book issue: This module is used to keep a track of book issue details.

23. Book return: This module enables to keep a track of return the book

·49 Performance requirements:

The capability of the computer depends on the performance of the software. The
software can take any number of inputs provided the database size is larger enough.
This would depend on the available memory space.

·50 Design constraints :

Each member will be having a identity card which can be used for the library book
issue, fine payment etc. whenever library member wish to take a book, the book
issued by the library authority will be check both the book details as well as the
student details and store it in library database. In case of retrieval of book much of
human intervention can be eliminated.

·51 System attributes :

24. Maintainability:
There will be no maintained requirement for the software. The database is provided
by the end user and therefore is maintained by this user.

ii. Portability:

The system is developed for secured purpose, so it is can’t be portable.

iii. Availability:

This system will available only until the system on which it is install, is running.

iv. Scalability:

Applicable.

·52 Non_ Functional requirements

·53 Security requirement

There will be proper security regarding to the accessing of data.

The external security can be provided by given the login authentication.

The data that are stored in the database must be private.

There is also required a user authentication.

There is also the facility that the admin can lock his private data that will not
beaccessed by anyone.

The whole software is secure from the outside accessing.

·54 Data flow diagram

·55 Context level DFD
·56 0- LEVEL DFD

·57 Detailed DFD

·58 ERD Entity relationship diagram

·59 Relational schema

 ·60 Use Case Diagram

- Actors
25. Administrator (category user)

26. Staff (category user)

27. Student (category user)

28. Library account (category system)

29. Book (category system)

 30. Transcation (category system)

31. Report (category system)

32. Search (category system)

33. Registration (category system)

Objects that define the system

34. Book (Attributes: Title , author , isbn, price

Functions: add book , remove book

Extended functions: login, login_failed, search_book)

ii. Transcation (Attributes: student_Id, Book_Id, Staff_Id

Functions:Borrow_book, Return_book

Extended functions: search_book, search_student, search_staff )

iii. Registration (Attributes: Student_name, student_rollno, student_id

Staff_name, staff_designation, staff_id

Functions: register_student, register_staff

Extended functions: login, login_failed, search_student

search_staff, search_unsucessful)

iv. Report (Attributes: book_id, student_id, date of return,

Functions: defaulters_list, borrower_list, requsition_list

Extented functions: login, login_failed)

v Search (Attributes: student_id, book_id, staff_id

Functions: login, login_failed, search_book, search_student

search_staff, search-unsucessful)

vi. Administratoe (Attributes: name, administrator_id,

Extended functions: login, register, search, transction

report)
vii. Staff (Attribute: name, staff_id
Extended function: login, register, sraech, view)

viii. Student: (Attributes: name, student_id

Functions: login, search)

ix. Login (Attributes: student_id, staff_id, administrator_id, password

Functions: login, login_failed

Extended function: register_student, register_staff)

x. View/Edit (Attributes: student_id, staff_id, administrator_id

Functions: view_student, edit_student, view_book

edit_book, view_staff, edit_staff

Extended functions: login, loin_failed, search_student, search-book

search_staff, search_unsucessful)

Use Cases-
1. Registration
2. Search

3. Transcation
4. Book (add/remove)

5. Report
6. Login

7. View/Edit
·61 Additional information
·62 Data Base Design
 ·63 Activity Diagram

Activity of Issuing books to member: The librarian checks the availability of book.if
the book is not available,then an error message will be displayed else the check the
rack no were the book is placed will be displayed.the member is validated.depending
upon the type of member if more books can be issued to member ,the transaction
will be created and issue details are added to the transaction.the book and member
details are updated accordingly
·64 Class Diagram
 ·65 Concept used

·66 Classes & Objects

A class is a user defined type or data structure declared with

keyword class that has data and functions (also called methods) as its

members whose access is governed by the three access

specifiers private, protected or public (by default access to members of a

class is private).

When class is defined, only specification for the object is defined.

Object has same relationship to class as variable has with the data

type. Objects can be defined in similarly way as structure is defined

as objects.

Our project will include mainly two classes one of student details

and the other of books details and the corresponding objects will

be accessed using objects.

 ·67 File handling:

The records of students as well as books will be maintained using

files in c++.

·68 Conclusion

·69 The project library management system is for computerizing the working in a
library

·70 The software takes care of all the requirement of an a library and is capable
to provide easy and effective storage of information related to the books &
users