Library Management System Software Requirement Specification

LIBRARY MANAGEMENT SYSTEM
Software Requirement Specification
Project Code: LMS5045

Document Code: LMS5045SRS – v 1.0
Group’s Member
Nguyen Truong Giang – Group’s Leader
Đang Hoai Nam – Group’s Member
Luu Tien Son – Group’s Member
Hoang Duy Phuong – Group’s Member
Vy Quang Hao – Group’s Member
Instructor and Evaluator:

Tran Binh Duong
LMS5045 - Software Requirement Specification v.1.0
Hanoi – FPT University , November 9th

2010
FU/SE504/G5/LMS5045/SRS v1.0
2/19
RECORD OF CHANGE
*A - Added M - Modified D - Deleted

Effecti Changed Items A-M- Change New
ve D Description Versio
Date n
Nov 7th Requirements A Newly Created 1.0
Specification
3/19
SIGNATURE PAGE
ORIGINATOR: Nguyen Truong Giang Nov 7th,

2010
Group’s Leader
REVIEWERS: Luu Tien Son Nov 8th,

2010
Group’s Member
Dang Hoai Nam Nov 8th,

2010
Group’s Member
Hoang Duy Phuong Nov 8th, 2010

Group’s Member
Vy Quang Hao Nov 8th, 2010

Group’s Member
APPROVAL: Nguyen Truong Giang Nov

9th, 2010
Group’s Leader
4/19
TABLE OF CONTENTS
1 INTRODUCTION...........................................................................7
1.1 Purpose.......................................................................7
1.2 Scope..........................................................................8
Fig 1 : User’s use-case model ..........................................8
9
1.3 Definitions, Acronyms, and Abbreviations.................10
1.4 References................................................................10
1.5 Overview...................................................................10
2 OVERALL DESCRIPTION..............................................................12
2.1 Product perspective..................................................12

2.2 Product functions......................................................12
2.3 User characteristics...................................................12
2.4 General Constrains....................................................13
2.5 Assumptions and dependencies................................13
3 SPECIFIC REQUIREMENTS ..........................................................14
3.1 Functionality.............................................................14
3.2 Usability ...................................................................14
3.3 Reliability .................................................................15
3.4 Performance.............................................................. 15
3.5 Supportability............................................................ 15
3.6 Design Constraints....................................................15
5/19
3.7 On-line User Documentation and Help System

Requirements.................................................................. 15
3.8 Interfaces..................................................................16
3.9 Licensing Requirements............................................18
3.10 Legal, Copyright, and Other Notices........................18
4 SUPPORTING INFORMATION.......................................................19
6/19
1 INTRODUCTION
1.1 Purpose
The main objective of this document is to illustrate the

requirements of the project Library Management
system. The document gives the detailed description of
the both functional and non functional requirements
proposed by the system . The document is developed after
a number of team-working with all members of group and
considering the complete requirement specifications of the
given Project. The final product of the group will be meeting
the requirements of this document.
7/19
1.2 Scope
Fig 1 : User’s use-case model .
8/19
9/19
1.3 Definitions, Acronyms, and Abbreviations
Acronym Definitions Note

s
SRS Software Requirement Specification
GUI Graphic User Interface
1.4 References
No Document Issued Source Note

date
1 Introduction to Sommerville – Addison
Software Engineering, Wesley
8th edition
2 Template Software FPT Software
Requirements
Specification
1.5 Overview
The rest of the SRS document contains five chapters:
- Overall description: describes the general factors that

affect to the product and their requirements. Contain :
• Product perspective
• Product functions
• User characteristics
• General constraints
• Assumptions and dependencies
10/19
- Functional requirements: describes the functional

requirements of the system for
those requirements that are expressed in natural language
style.
- Non-functional requirements: describes non-functional

requirements of the system such as usability, reliability, safety,
security, and so on. Contain :
• Usability
• Efficiency
• Reliability
• Performance
• Supportability
• Design contraints
• Online or Help document
- Interfaces: defines user applet and administrator applet

interface.
- Supporting Information .
11/19
2 OVERALL DESCRIPTION
2.1 Product perspective
This system helps users check , loan and return books

easily and automatically , also help managers manage ,
check update and record book’s details and user’s
informations .
2.2 Product functions
- Log in and Log out for user .

- Change password for user .
- List book’s detail informations , contain name , ISBN ,
author , genre , price to buy , price to loan , in stock or out
stock .
- Marking books .
- Order to loan or return books .
- Record book’s informations .
2.3 User characteristics
- User : this system serves the demand of loaning and

returning books of user .
- Manager : this system supports manager to manage ,
check and record all information about users and books .
12/19
2.4 General Constrains
- Database of library system using SQL 2008 , doesn’t

support 2005 version or lower version or other database
server program .
- System for user who have not too much experience , so it
should have a simple interface and easy to use .
2.5 Assumptions and dependencies
The system has to be changed to be compatible with new

technologies that they’ll apply .
13/19
3 SPECIFIC REQUIREMENTS
3.1 Functionality
- User :
+ List book’s details : name , ISBN , author , genre ,
price to buy , price to loan , in stock or out stock .
+ View book’s demo : some pages insteading .
+ Marking book : add book to order list . User can
marking books which are being out of stock and add
information that which day he or she’ll come back to loan that
books . That books’ll be no longer can be marking by others
users .
+ Order : Consider which book is loaned , which book
is returned .
+ Log in and log out system with his or her account .
If account’s ID or password is incorrect more than 5 times ,
user must answer security question that they created when
register to continue type account’s informations .
+ Change their password : user can change
password with old password or security question if they lose it .
- Manager :
+ Check book’s detail : informations of books must
be the same before its was loaned . If incorrect , manager’ll
warning to user and request them pay to compensation . All
informations’ll be recorded and updated to database .
+ Manage user’s information : check account ID ,
password and security question .
3.2 Usability
The interface is designed simple for user can use it
14/19
fluently . System’ll also has a guide document to help and

support who have no experience to use it before .
3.3 Reliability
System is 100% available .

Accuracy of system’s output is 100% .
Maximum bugs of defect rate : 2 bugs/function-point .
3.4 Performance
Log in and Log out : respone time from 1 – 3 seconds .

List books : respone time from 1 – 5 seconds .
Others fuctions : respone time from 1 – 2 seconds .
Number of users or transactions the system can
accommodate : over 100 ones .
3.5 Supportability
System support win-form application , use in Windows 2000

up to Windows 7 ( both x86 and x64 ) . System is not
support IOS Operating system but available for Ubuntu OS .
3.6 Design Constraints
System’ll be built by Microsoft Visual C# and .Net tool .

Database manage by SQL 2008 .
System’ll be built in windows form and base classes of
Visual C# , also connect with database from SQL 2008 .
3.7 On-line User Documentation and Help System Requirements
System only has a offline guide document .
15/19
3.8 Interfaces
User and Manager Interfaces
Contain button and menu for access system with all

function .
Hardware Interfaces
Fig 3 : Computer system .
User and manager use personal computer and LAN network

connect with a server computer to access system .
Software Interfaces
The system has 2 main interfaces :

- Connect System window : contain Log in , Log out and find
Password if user lose it . It has a option for person who hasn’t a
account to register a new account . Manager also must log in to
use system .
- Main program window : contain or function of list , mark ,
order loan and return books .
16/19
Fig 4 : GUI .
17/19
3.9 Licensing Requirements
This system is created by Group 5 of SE 504 Class – FPT

University . It’s only use for study . All copies of others must
has a agreement of us .
3.10 Legal, Copyright, and Other Notices
This system is just a practice exercise . All copies use for

other destination is not recommend and secure .
18/19
4 SUPPORTING INFORMATION
N/A .
19/19

Library Management System Software Requirement Specification

Uploaded by

Document Information

Original Description:

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

Library Management System Software Requirement Specification

Uploaded by

Copyright:

Available Formats

LIBRARY MANAGEMENT SYSTEM

Software Requirement Specification

Project Code: LMS5045

Instructor and Evaluator:

Hanoi – FPT University , November 9th

*A - Added M - Modified D - Deleted

ORIGINATOR: Nguyen Truong Giang Nov 7th,

REVIEWERS: Luu Tien Son Nov 8th,

Dang Hoai Nam Nov 8th,

Hoang Duy Phuong Nov 8th, 2010

Vy Quang Hao Nov 8th, 2010

APPROVAL: Nguyen Truong Giang Nov

2.1 Product perspective..................................................12

3 SPECIFIC REQUIREMENTS ..........................................................14

3.7 On-line User Documentation and Help System

The main objective of this document is to illustrate the

Fig 1 : User’s use-case model .

1.3 Definitions, Acronyms, and Abbreviations

Acronym Definitions Note

No Document Issued Source Note

The rest of the SRS document contains five chapters:

- Overall description: describes the general factors that

- Functional requirements: describes the functional

- Non-functional requirements: describes non-functional

- Interfaces: defines user applet and administrator applet

2.1 Product perspective

This system helps users check , loan and return books

2.2 Product functions

- Log in and Log out for user .

2.3 User characteristics

- User : this system serves the demand of loaning and

2.4 General Constrains

- Database of library system using SQL 2008 , doesn’t

2.5 Assumptions and dependencies

The system has to be changed to be compatible with new

The interface is designed simple for user can use it

fluently . System’ll also has a guide document to help and

System is 100% available .

Log in and Log out : respone time from 1 – 3 seconds .

System support win-form application , use in Windows 2000

3.6 Design Constraints

System’ll be built by Microsoft Visual C# and .Net tool .

3.7 On-line User Documentation and Help System Requirements

System only has a offline guide document .

User and Manager Interfaces

Contain button and menu for access system with all

Fig 3 : Computer system .

User and manager use personal computer and LAN network

The system has 2 main interfaces :

3.9 Licensing Requirements

This system is created by Group 5 of SE 504 Class – FPT

3.10 Legal, Copyright, and Other Notices

This system is just a practice exercise . All copies use for

You might also like