Software Requirements

Specification
Version 1.0
01.20.2012

Samar College Library

Information Management System
Authors:
Jeric G. Llorag
Melvin E. Lotoc
Edsil I. Uy
Rebekah Hannah A. Molleda

Submitted in Partial Fulfillment

of the Requirements of
IT 205 - Software Engineering
Samar College
Submitted to:
Ms. Prescilla F. Catalan

Instructor

Table of Contents
List of Figures.................................................................................................................................................iii
.........................................................................................................................................................................iii
1.0 Introduction.................................................................................................................................................1
1.1 Purpose.............................................................................................................................................1
..................................................................................................................................................................1
1.2 Scope of Project......................................................................................................................................1
1.3 Definitions, acronyms, and abbreviations..............................................................................................2
1.4 References...............................................................................................................................................2
1.5 Overview of Document...........................................................................................................................2
2.0 Overall Description.....................................................................................................................................3
2.1 System Environment...................................................................................................................................3
2.2 Functional Requirements Specification..................................................................................................3
2.3 User Interface Specification...................................................................................................................6
Log in interface Prototype (see Appendix A Fig. 1)..............................................................................6
Main Interface Prototype (see Appendix A Fig. 2).....................................................................................6
Issuing interface Prototype (see Appendix A Fig. 3)...................................................................................6
2.4 Non-Functional Requirements................................................................................................................7
3.0 Requirements Specification........................................................................................................................9
3.1 External Interface Requirements............................................................................................................9
3.2 Functional Requirements........................................................................................................................9
3.3 Detailed Non-Functional Requirements...............................................................................................11
3.4 System Evolution..................................................................................................................................12
Index...............................................................................................................................................................13

ii

List of Figures
List of Figures.................................................................................................................................................iii
.........................................................................................................................................................................iii
1.0 Introduction.................................................................................................................................................1
1.1 Purpose.............................................................................................................................................1
..................................................................................................................................................................1
1.2 Scope of Project......................................................................................................................................1
1.3 Definitions, acronyms, and abbreviations..............................................................................................2
1.4 References...............................................................................................................................................2
1.5 Overview of Document...........................................................................................................................2
2.0 Overall Description.....................................................................................................................................3
2.1 System Environment...................................................................................................................................3
2.2 Functional Requirements Specification..................................................................................................3
2.3 User Interface Specification...................................................................................................................6
Log in interface Prototype (see Appendix A Fig. 1)..............................................................................6
Main Interface Prototype (see Appendix A Fig. 2).....................................................................................6
Issuing interface Prototype (see Appendix A Fig. 3)...................................................................................6
2.4 Non-Functional Requirements................................................................................................................7
3.0 Requirements Specification........................................................................................................................9
3.1 External Interface Requirements............................................................................................................9
3.2 Functional Requirements........................................................................................................................9
3.3 Detailed Non-Functional Requirements...............................................................................................11
3.4 System Evolution..................................................................................................................................12
Index...............................................................................................................................................................13

iii

1.0 Introduction
1.1 Purpose
The purpose of Software Requirements Specification (SRS) document
is to describe the external behavior of the Samar College Library
Information Management System. The Vision Document captures very highlevel requirements and design constraints, which gives the reader an
understanding of the Samar College Library Information Management
System to be developed. Requirements Specification defines and
describes the operations, interfaces, performance, and quality
assurance requirements of the Samar College Library Information
Management System. The document also describes the nonfunctional
requirements such as the user interfaces. It also describes the design
constraints that are to be considered when the system is to be
designed. This document is for Samar College Library staff that will
serve as a guide about the specific system requirements. This document
will also use in future maintenance.

1.2 Scope of Project

The Samar College Library Information Management System that is
to be developed provides the members of the Library and employees of
the library with books information, tracking of books and many other
facilities. The Samar College Library Information Management System is
supposed to have the following features.

The product provides the members with easy access of books

capabilities and the Samar College Library Information Management
System is up and running all day.

The system provides logon facility to the users.

The system provides the members with the option to check their
account and/or change their options like informations of the
account whenever needed all through the day during the library
hours.

The system lets the library staff to check which all members whether
they can borrow any more books or not.

The system allows the Librarian to create the books catalog, add/delete
books and maintain the books catalog.

The features that are described in this document are used in the
future phases of the software development cycle. The features
described here meet the needs of all the users. The success criteria
for the system are based in the level up to which the features
described in this document are implemented in the system.

SRS V1.0

March 8, 2012

1.3 Definitions, acronyms, and abbreviations

SCLIMS Samar College Information management System.

LIMS Library Information Management System.
ID Identification Number.

1.4 References
The SRS document uses the following documents as reference:

http://en.wikipedia.org/wiki/Integrated_library_system
http://www.slideshare.net/vimal0212/open-source-library-managementsystems

1.5 Overview of Document

This vision document lists all the capabilities of Samar College
Library Information Management System. It also states all the risk
factors that are involved with the project and gives a time frame for
the implementation of the project.

SRS V1.0

March 8, 2012

2.0 Overall Description

2.1 System Environment

2.2 Functional Requirements Specification

2.2.1 Library Employee Use Cases
Use Case: Employee Logon
Diagram:

Use Case for Employee Logon:

1. Employee initiates use case by entering user name
2. System prompts for password
3. If password is valid, employee is logged on and now has access
to employee commands.

SRS V1.0

March 8, 2012

Use Case: Check out book

Diagram:

Use Case for Check out book:

1. Employee initiates use case when the library user presents a book
at the counter.
2. Employee enters the user's ID number
3. The system verifies the ID by checking the Users Database.
4. If the ID# is valid and the user has no overdue books or
periodicals, the employee continues:
5. The book's record in the catalog is updated with the user's ID
and the due date.
6. The Users Database is updated with users check-out status.
Use Case: Check in book
Diagram:

Use Case for check in book

1. Employee initiates use case when there is a new arrival of books.
2. The employee adds the information of the book by filling up the
book information form.
SRS V1.0

March 8, 2012

3. The system
4. If all the

checks the fields that require important information.

fields that require important importation are all
provided, the system will prompt if the user wants to save the
importation.
5. If the user click saves and there are still important fields
which are empty the system returns an error.
6. If saving is successful, the database is updated by the book
information.
2.2.2 Library User Use Cases
Use Case: Check book availability
Diagram:

Use Case for Check book availability:

1. User/Employee initiates use case by selecting the check book
availability option.
2. System prompts for choice of search by title, author, or call
number.
3. User makes selection and enters title, author or call number
4. System performs search through the library catalog database.
5. If a match is found, system displays item status (not checked
out, checked out and due date, overdue).

Use Case:

Recall book

Diagram:

SRS V1.0

March 8, 2012

Use Case for recall book

1. A student makes a book request to the library employee.
2. The library employee eventually orders the book, and updates the
corresponding book record within the system.
3. The book is ordered and the corresponding record is updated.

2.3 User Interface Specification

Log in interface Prototype (see Appendix A Fig. 1)
This is the first interface that the user would encounter, to
secure the systems security; the system will provide functions
depending on the staff position in the library. For example, you
are the administrator or a librarian, you can delete books, add
staff, and modify informations etc. unlike with those other staff
like working students they cant use those functions like
librarians or administrators did. If the user provides incorrect
information the system will return an error message. If all the
information entered is correct the system will return a successful
message.

Main Interface Prototype (see Appendix A Fig. 2)

This is the main interface, this is where the users can
navigate to all the facilities of the system, at the bottom of the
interface shows the date and time and the name of user that
currently uses the system. If the user is the administrator he/she
can use all the function of the system, if not the function is
limited depending on the position of the user.

Issuing interface Prototype (see Appendix A Fig. 3)

These interface are use in issuing books, magazines, and
other library materials, in issuing theres a search function so
that it would we easier for the issuer to provide the specific
SRS V1.0

March 8, 2012

type of library materials that that clients want. The staff would
simply type the item ID number and the members ID this will
automatically updates the members activity in the database.

Returning interface Prototype (see Appendix A Fig. 4)

This inter face is for returning library materials, the will
just enter the item ID number and the members ID number and hit
the return button, this will automatically removes the record of
the item that the member has been borrowed.

2.4 Non-Functional Requirements

2.5

Samar College Information

Management

System

2.6 Book Information in the database table

Field

Type

Comment

ItemID

int

Title

varchar

Title of the item.

Author_1

varchar

Author name.

Author_2

varchar

Author name for more than one author.

Publication

varchar

Name of publication where the book was

published.

SRS V1.0

March 8, 2012

Edition

varchar

The edition of the book.

Volume

varchar

Volume of the item if there are any.

DateRecieve

date

SourceOfFund

varchar

Date the book was recieved

Source of fund if the item if it was
purchased or a donation.

Class

varchar

Type of the item

Subject

varchar

Type of subject of an item.

ISBN_No

varchar

ISBN No. of the item this can be found

mostly in the books.

Pages

varchar

Number of pages of the item has.

Price

varchar

TotalCopies

varchar

Price of the item, if in case of lost.

Total copies of the item that exist in
the record.

2.7

Members information in the database table

Field

Type

comment

MemberID

varchar

Members ID number .

FirstName

varchar

First Name of the member.

MiddleName

varchar

Middle Name of the member.

LastName

varchar

Last Name of the member.

Age

varchar

Age of the member.

Gender

varchar

Gender of the member.

Course

varchar

Course of the member, if a student.

Year

varchar

Year of the member, if a student.

ContactNo

int

ContactNo of the member.

Address

varchar

Address of the member.

SRS V1.0

March 8, 2012

3.0

Requirements Specification

3.1 External Interface Requirements

3.2

none

Functional Requirements

3.2.1 Employee Logon

Use Case Name

Employee Logon

Xref

Section 2.2.1, Library Employee Use Cases

Trigger

The staff/user opened the System

Precondition

Login sreen is displayed

Basic Path

3.2.2

Check out book

Use Case Name

Check out book

Xref

Section 2.2.1, Library Employee Use Cases

Trigger
Precondition

Basic Path

SRS V1.0

1. Employee initiates use case by

entering user name
2. System prompts for password
3. If password is valid, employee is
logged on and now has access to employee
commands

The staff/user opened the issuing area of

the system
issue screen is displayed
1. Employee initiates use case when the
library user presents a book at the
counter.
2. Employee enters the user's ID number
3. The system verifies the ID by checking
the Users' Database.
4. If the ID# is valid and the user has
no overdue books or periodicals, the
employee continues:
5. The book's record in the catalog is
updated with the user's ID and the due
date.
6. The Users Database is updated with
users check-out status.

March 8, 2012

3.2.3 Check book availability

Use Case Name

Check book availability

Xref

Section 2.2.2, Library User Use Cases

Trigger
Precondition

Basic Path

The user asks the staff if the book is

available.
Search screen is displayed
1. User/Employee initiates use case by
Selecting the check book availability
option.
2. System prompts for choice of search by
Title, author, or call number.
3. Staff makes selection and enters title,
author or call number
4. System performs search through the
Library catalog database.
5. If a match is found, system displays
Item status (not checked out, checked
out and due date, overdue).

3.2.4 Recall book

Use Case Name

Recall book

Xref

Section 2.2.2, Library User Use Cases

Trigger

The user makes a book request to the staff.

Precondition

Book records screen is displayed

Basic Path

1. A student makes a book request to the

library employee.
2. The library employee eventually orders
the book, and updates the corresponding
book record within the system.
3. The book is ordered and the
corresponding record is updated.

3.2.5 Check in book

SRS V1.0

Use Case Name

Check in book

Xref

Section 2.2.2, Library User Use Cases

Trigger

The staff will add new book record.

Precondition

Book records screen is displayed

10

March 8, 2012

Basic Path

1. A student makes a book request to the

library employee.
2. The library employee eventually orders
the book, and updates the corresponding
book record within the system.
3. The book is ordered and the
corresponding record is updated.

3.3 Detailed Non-Functional Requirements

Technical Non-Functional Requirements:
Usability

The system shall allow the users to access the system

The system is user friendly and self-explanatory.

Reliability
The system has to be very reliable due to the
importance of data and the damages incorrect or incomplete
data can do.
Availability
The system is available 100% for the user and is used
12 hrs. a day and 365 days a year. The system shall be
operational 12 hours a day and 7 days a week
Accuracy
The accuracy of the system is limited by the accuracy
of the speed at which the employees of the library and users
of the library use the system.
Capacity
The system is capable of handling 25 users at a time.
Maintenance
The system shall be easy to maintain. The maintenance
of the system shall be done as per the maintenance contract.
Security
Controlling the access
security to the system.

to

the

database

provides

Stability
The system is inherently stable. As such no changes to
the present format are foreseen. The review will be taken
after the second release.

SRS V1.0

11

March 8, 2012

Testability
The system is
computer systems.

testable

any

time

at

any

different

Scalability
Adding more facilities to the system should be easy and
possible.
Interoperability
The system can interact to other external devices such
as printers.
Installation
After the release the System installation should only
take few steps.
Non-Technical Non-Functional Requirements:
Cultural
Naming conventions will be as per the American English
standards.
Legal
The usage is restricted only to Samar College Library
who will use the Library Information Management System and
signs the contract, Samar College Library Information
Management System is a trademark of College of Information
Technology Education and cannot be used without its consent.

3.4 System Evolution

Because of time limitation only those basic and important
facilities of the system that the developers can offer, in the
future the system will have the fallowing features: user
information with picture, can interact with mobiles, like for
example, the system will automatically send text message to the
borrowers if its already their due date to return the book they
borrowed. Finally to make this system online so that user can
browse books and borrow them whenever they are.

SRS V1.0

12

March 8, 2012

Index
abbreviations.......................................................................2
Accuracy...........................................................................11
acronyms.............................................................................2
Authors................................................................................i
Availability.......................................................................11
Capacity............................................................................11
Cultural.............................................................................12
Definitions..........................................................................2
External Interface...............................................................9
Figures...............................................................................iii
Functional...........................................................................9
Installation........................................................................12
Instructor.............................................................................i
Interface Prototype.............................................................6
Interoperability.................................................................12
Issuing.............................................................................6, 7
Legal.................................................................................12
Maintenance.....................................................................11

Non-Functional.................................................................11
Non-Technical Non-Functional........................................12
Overall Description............................................................3
Purpose...............................................................................1
References..........................................................................2
Requirements......................................................................9
Samar College.....................................................................i
Scalability.........................................................................12
Scope..................................................................................1
Security.............................................................................11
Software Engineering..........................................................i
Specification.......................................................................9
Stability.............................................................................11
Technical Non-Functional................................................11
Testability.........................................................................12
Usability...........................................................................11
User Interface.....................................................................6

Appendix A

(Fig. 1 Login interface prototype)

SRS V1.0

13

March 8, 2012

(Fig. 2 Main interface prototype)

(Fig. 3 Issue interface prototype) (Fig. 4 Return interface prototype)

SRS V1.0

14

March 8, 2012