Mẩu SRS librarymanagement

Software Requirements
Specification
LIBRARY MANAGEMENT
Version: 1.0
Date: 26/09/2017


Project Information
Project Title
Start Date – End Date
Lead Institution
Project Mentor
Project Manager &
Contact detail
Partner Organization
Team member

Library Management
26/09/2017 – 25/12/2017

None

Document name
Document Title
Reporting period
Author
Role
Filename

Library Management Software Requirement Spectification
26/09/2015

Team leader
SRS_Group3_LibraryManagement

Revision History
Name
Library

Date
26/09/2015

Library Management

Comments

Page 1

Version
1.0


TABLE OF CONTENTS
Contents
1. Introduction.......................................................................................................3
1.1.

Purpose......................................................................................................3

1.2.

Document Conventions..............................................................................3

1.3.

Intended Audience and Reading Suggestions............................................3

1.4.

Scope..........................................................................................................3

1.5.

References..................................................................................................3

2. Overall Description...........................................................................................4
2.1.

Background................................................................................................4

2.2.

Function.....................................................................................................4

2.3.

User Characteristics..................................................................................5

2.5.

Design and Implement...............................................................................5

3. External Interface Requirements....................................................................6
3.1.

User Interface............................................................................................6

4. System features..................................................................................................6
5. Non-function....................................................................................................12

Library Management

Page 2


1. Introduction
1.1.Purpose
The document describe function, non-function, quality attributes for software
products and provides development project team.

1.2.Document Conventions
Bold: Emphasize.
Italic:Attention.
Underline: Important part.

1.3.Intended Audience and Reading Suggestions
-

Users:Part 2-Overall Description
Project Manager: Part 2-Overall Description and Part 3-External Interface
Requirement.
Development Project Team:Part3-External Interface Requiremt , Part 4System features and Part 5-Nonfunction

1.4.Scope
-

-

-

This document provides an overview of project will be developed. It
includes overview of the product, overview of the process and overview of
the project team
This document provides a plan for each phase of software development
process based on waterfall process include: requirement, design,
implementation, verification and maintenance. This is the general plan and
will be updated with detail of the software development process in the next
version of document.
Proposal includes the introduction of solutions, determine the best way to
develop software that we make, the total estimated costs, payback period,
breakeven volume for the project.

1.5.References
No.
1
2

Description
Waterfall process

Location
/>

Business case

nt)



2. Overall Description
2.1.Background

Library Management

Page 3


Nowadays, information technology is extremely developed and makes searching
information easier. Libraries are no longer simply traditional libraries that combine
internet connections with titles. Thousands of libraries, including public and private
libraries, are operating efficiently, suggesting that library needs never cease to be
needed. A library with hundreds of thousands of books, we can not manage paper
manuscripts, notes or some software to manage disconnected networks. Need to have
a general management software on the book code, borrowers name or borrow time
and return books ... To easily manage the above problems, we have studied separately
management software library. This software is highly application, easy to manage, has
been used in many libraries nationwide.

2.2.Function

Library Management

Page 4

2.3.User Characteristics
User group

Description
The person responsible for management the librarians and
operating the system. They can : Login – logout , Add – View –
Delete Librarian.

Admin
Librarian

The person responsible for management the books and support
customers. They can: Login-logout , Add – View – Return
books and Issue book.

2.4.Operating Envirement
 Online Enviroment:
o Need network to install software.
 Offline Enviroemnt:
o Need Local Area Network to connect with another computer.
 Other:
o Accessories: Personal computer or Laptop.
o Software Application.
o Operating System: Windows 7, 8, 10 or Linux.

2.5.Design and Implement
-

Operating System: Windows 7,8,10 or Linux.
Programming language: Java, SQL.
Database: MySQL.
System Requirements:
o OS:
 Windows 7,8,10 or Linux
o Memory: 256MB or more (all OS).
o Storage: 10.00 MB.

Library Management

Page 5


Library Management

Page 6


3. External Interface Requirements
3.1.User Interface
- Rules about button: Is rectangle
- Rule about display: Notice,input-output, display information.
Arrange Button:
- Library Management Interface
o Admin login
o Librian login
- Admin Section Interface
o Add Librian
o View Librian

o Delete Librian
o Logout
- Librian Section Interface
o Add book
o View book
o Issue book
o View issue book
o Return book
o Logout

4. System features
Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

Library Management

UC1
Login
How to access the system
Admin and Librarian
PC or laptop has installed software.
Step 1. Install software
Step 2. Access the system and click Log-in
with Admin
Step 3. Enter username and password

Page 7


Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

UC2
Logout
How to log out of the system
Admin and Librarian
Actor must login and access the system
Step 1. Find and Click Log-out
Step 2. Confirm “Exit system”

Use Case ID
Name
Description
Actor
Pre-Conditions

UC3
Add Librarian
Add new a librarian
Admin
Admin must have an account and are
accessing the system

Step 1. Admin Log-in the system
Step 2. Enter id librarian in the Add Section
The system will check id of
librarian
 If the id librarian is not exist, the
screen will display "Add Success".
 If the account is available, the screen
will display "Account already exist"

Basic flow of events

Library Management

Page 8


Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

Library Management

UC4
Delete Librarian
How to delete a librarians out of system
Admin
Admin must have an account and are

accessing the system
The Librarian has already account available
Step 1. Admin Log-in the system
Step 2. Enter id user in the Delete Section
The system will check if the user is
real or not
 If this id has librarian rights, the
system will cancel the librarian of
this id.
 If this id does not have librarian's
rights, the system will report an
error on the screen : "Error".

Page 9


Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

Library Management

UC5
View Librarian
See information for each Librarian
Admin
Admin must have an account and are
accessing the system
The Librarian has already account available
Step 1. Admin Log-in the system
Step 2. Admin click View Librarian
Step 3. The screen will appear to the list of
the information of the engine of librarians.

UC6
Add books
Add new a book for the system
Librarian
Librarians must access the system
Step 1: Log-in the system
Step 2: Choice “ Add books “
Step 3: Enter information about book and
click Save

Page 10


Use Case ID
Name
Description

Actor
Pre-Conditions
Basic flow of events

UC7
View books
See information book
Librarian
Librarians must access the system
Step 1: Log-in the system
Step 2: Choice " View books "
Step 3: View information for book , change
information (if have) and click Save

Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

UC8
Return book
Manage books that are returned
Librarian
Librarians must access the system
Step 1: Log-in the system
Step 2: Choice " Add books "
Step 3: Enter information for book that are
returned and click Save

Library Management

Page 11


Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

UC9
Issue book
Manage about issue book for library
Librarian
Librarians must access the system
Step 1: Log-in the system
Step 2: Choice " Issue book"
Step 3: Enter information about issue book
and click Save

Use Case ID
Name
Description
Actor
Pre-Conditions
Basic flow of events

UC10
View issue book
View the books that have been issued
Librarian
Librarians must access the system
Step 1: Log-in the system
Step 2: Choice " View books "
Step 3: View information about issue
book , change information (if have) and
click Save

Library Management

Page 12


5. Non-function
-

-

-

-

Performance: 98 percent of the queries in the database need to completed
within 3 seconds . Use memory >256MB or more and Windows 7 or more,
storage system > 10MB.
Security:
o If admin has deleted the librarian who will not be able to access the

system.
o If users turn off LAN, they will not be able to access the system with
another computer.
Safety:
o If the app is turned on but not used for five minutes then it will
automatically escape.
Other:
o Support many languge such as: English , Vietnamese , France ,
Chinese,...
o Flexible OS.

Library Management

Page 13