Table of Contents

1.0. Introduction
1.1. Purpose
1.2. Scope of Project
1.3. Definition, acronyms, and abbreviations
1.4. References
1.5. Overview of Document
2.0.
Overall Description
2.1
Product Perspective
2.2
Functional Requirements Specification
2.2.1
Students and Faculty Users
2.2.2
Library Staff
2.2.3 System Admin Case
2.3
User Characteristics
2.4
Constraints
3.0 Specific Requirements
3.1 Functionality
3.1.1 Logon Capabilities
3.1.2 Mobile Devices
3.1.3 Alerts
3.2 Usability
3.3 Reliability
3.3.1 Availability
3.3.2 Mean Time Between Failures (MTBF)
3.3.3 Mean Time to Repair (MTTR)
3.3.4 Accuracy
3.3.5 Maximum Bugs or Defect Rate
3.3.6 Access Reliability
3.4 Performance
3.4.1 Response Time
3.4.2 Administrator/Librarian Response
3.4.3 Throughput
3.4.4 Capacity
3.4.5 Resource Utilization
3.5 Supportability
3.5.1 Internet Protocols
3.5.2 Information Security Requirement
3.5.3 Maintenance
3.5.4 Standards
3.6 Design Constraints
3.6.1 Software Language Used
3.6.2 Development Tools
3.6.3 Class Libraries
3.7 On-line User Documentation and Help System Requirements
3.8 Purchased Components
3.9 Interfaces
3.9.1 User Interfaces
3.9.2 Hardware Interfaces
3.9.3 Software Interfaces
3.9.4 Communications Interfaces
3.10 Legal, Copyright, and Other Notices
3.11 Applicable Standards
4.0 Supporting Information
5.0 Appendix

1
1
1
1
1
2
3
3
3
3
4
4
4
5
5
5
5
5
5
6
6
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
9
9
9
9
9
9
10

1.0. Introduction
1.1. Purpose
The purpose of this document is to present a detailed description of the Library
Management System. It will explain the purpose and features of the system, the interfaces
of the system, what the system will do, the constraints under which it must operate and
how the system will react to external stimuli. This document is intended for Admin and
the developers of the system and will be proposed to the faculty Library for its approval.
1.2. Scope of Project
This software system will be a Web Publishing System which will support four
types of users These are students, faculty, library staff, and administrators. This system
will support the following online functions for student and faculty users: resource
reservation, resource search, account validation, access to current reservation list and
check-out list, deadline notification and late fee payment.
More specifically, this system is designed to allow Library staff the following
additional capabilities: resource check-in/check-out, record modification, user account
modification, and database report generation. Administrative personal will have access to
the following additional database functionality: super user (top-level user) account access
and modification, and top-level database modification. The system will provide an
interface tailored to each user type.

1.3. Definition, acronyms, and abbreviations

Term
Active Student / Faculty
Online
Offline
Local Area Network
User

Definition
Student who still undergone their study at the university /
faculty staff who still work at the faculty.
Connected to the Internet
Not connected to the Internet
A computer network that interconnects computers within a
limited area.
User of the system, in this document- Student, Faculty,
Library Staff, System Admin

1.4. References
IEEE. IEEE Std 830-1998 IEEE Recommended Practice for Software Requirements
Specifications. IEEE Computer Society, 1998.

1.5. Overview of Document

The next chapter, the Overall Description section, of this document gives an
overview of the functionality of the product. It describes the informal requirements and is
used to establish a context for the technical requirements specification in the next chapter.
The third chapter, Requirements Specification section, of this document is written
primarily for the developers and describes in technical terms the details of the
functionality of the product.
Both sections of the document describe the same software product in its entirety,
but are intended for different audiences and thus use different language.

2.0. Overall Description

2.1

Product Perspective

Figure 1 - System Environment

The Library Management System has two categories of user which is Local
Network User/Offline User and Online User. Offline User is serving by Local Area
Network Server and Online User is serving by Web Interface Server. Library Staff is the
contributor and has certain data modification access. System Admin is the Super User
(Top-Level User) which has maintenance functionality with full data modification access.
Local Area Network Server and Web Interface Server are synchronizing each
other. Any update or modification will be applied on both servers.
2.2

Functional Requirements Specification

2.2.1 Students and Faculty Users

Students and Faculty Users have the following sets of use cases:

Figure 2 Student/Faculty Use Cases

2.2.2 Library Staff

Library Staff have the following additional sets of use cases:

Figure 2 Library Staff Use Cases

2.2.3 System Admin Case
System Admin has the following additional sets of use cases:

Figure 4 System Admin Use Cases

2.3

User Characteristics

Student and faculty are the members of the faculty expected to use the system
either at the library which using Local Area Network or Internet literate and be able to
use the system by the internet.
Library Staff are expected to mainly use the system from the Library are assumed
to have basic knowledge of the computers and Internet browsing.

System Admin to have more knowledge of the internals of the system and is able
to rectify the small problems that may arise due to disk crashes, power failures and other
catastrophes to maintain the system. The proper user interface, users manual, online help
and the guide to install and maintain the system must be sufficient to educate the users on
how to use the system without any problems.
2.4

Constraints
The information of all the users must be stored in a database that is
accessible by the Library Management System.
Offline system can only be access at the library.
Librarys computer must install with Microsoft Access Software.
The Library Management System must be compatible with the Internet
applications.
The Library Management System is connected to the facultys computer
and is running all 24 hours a day.
The users access the Online Library Management System from any
computer that has Internet browsing capabilities and an Internet connection.
The users must have their correct usernames and passwords to enter into
the Library Management System
Assumptions and dependencies:
The users have sufficient knowledge of computers.
Facultys computer should have Internet connection and Internet server
capabilities.
The users know the English language or Bahasa Melayu language, as the
user interface will be provided in English and Bahasa Melayu.
The product can access the facultys student database

3.0 Specific Requirements

This section describes in detail all the functional requirements.
3.1 Functionality
3.1.1 Logon Capabilities
The system shall provide the users with logon capabilities.
3.1.2 Mobile Devices
The Online Library System is also supported on mobile devices such as cell phones.

3.1.3 Alerts
The system can alert the Librarian or the administrator in case of any problems.
3.2 Usability

The online system shall allow the users to access the system from the Internet
using HTML or its derivative technologies. The system uses a web browser
as an interface.
For Online system, since all users are familiar with the general usage of
browsers, no specific training is required.
For Offline system, Microsoft Access Database is user-friendly and selfexplanatory, no specific training is required.

3.3 Reliability
The system has to be very reliable due to the importance of data and the damages
incorrect or incomplete data can do.
3.3.1 Availability
The system is available 100% for the user and is used 24 hrs a day and 365 days a year.
The system shall be operational 24 hours a day and 7 days a week.
3.3.2 Mean Time Between Failures (MTBF)
The system will be developed in such a way that it may fail once in a year.
3.3.3 Mean Time to Repair (MTTR)
Even if the system fails, the system will be recovered back up within an hour or less.
3.3.4 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.
3.3.5 Maximum Bugs or Defect Rate
Not specified.
3.3.6 Access Reliability
The system shall provide 100% access reliability.
3.4 Performance
3.4.1 Response Time
The information is refreshed every 1 minutes. Online server and Offline server
will be synchronized at minimum 1 minutes. The access time for a mobile device

should be less than a minute. The system shall respond to the member in not less
than two seconds from the time of the request submittal. The system shall be
allowed to take more time when doing large processing jobs.
3.4.2 Administrator/Librarian Response
The system shall take as less time as possible to provide service to the
administrator or the librarian.
3.4.3 Throughput
The number of transactions is directly dependent on the number of users, the users
may be the Librarian, employees of the Library and also the people who use the Library
for checking-out books, returning books and checking online library account.
3.4.4 Capacity
The system is capable of handling 250 users at a time.
3.4.5 Resource Utilization
The resources are modified according the user requirements and also according to the
books requested by the users.
3.5 Supportability
The system designers shall take in to considerations the following supportability and
technical limitations.
3.5.1 Internet Protocols
The system shall be comply with the TCP/IP protocol standards and shall be
designed accordingly.
3.5.2 Information Security Requirement
The system shall support the UHCL information security requirements and use the
same standard as the UHCL information security requirements.
3.5.3 Maintenance
The maintenance of the system shall be done as per the maintenance contract.
3.5.4 Standards
The coding standards and naming conventions will be as per the American
standards.
3.6 Design Constraints
3.6.1 Software Language Used
For Local Area Network Server will be use Microsoft Access Database, for
Online server will be use Microsoft Visual Interdev 6.0 as web interface.

3.6.2 Development Tools

Will make use of the available Java Development Tool kits for working with Java
Beans and Java Server Pages. Also will make use of the online references available for
developing programs in ASP, HTML and the two scripting languages, JavaScript and
VBScript.
3.6.3 Class Libraries
Will make use of the existing Java libraries available for JSP and Servlets. Also we
need to develop some new libraries for the web-based application. Also will develop new
programs using ASP and scripting languages.
3.7 On-line User Documentation and Help System Requirements
Online help is provided for each of the feature available with the Online Library
System. All the applications provide an on-line help system to assist the user. The nature
of these systems is unique to application development as they combine aspects of
programming (hyperlinks, etc) with aspects of technical writing (organization,
presentation). Online help is provided for each and every feature provided by the system.
The User Manual describes the use of the system to Librarian and Employees. It
describes the use of the system on mobile systems. The user manual should be available
as a hard copy and also as online help.
An installation document will be provided that includes the installation instructions
and configuration guidelines, which is important to a full solution offering. Also, a Read
Me file is typically included as a standard component. The Read Me includes a Whats
New With This Release section, and a discussion of compatibility issues with earlier
releases. Most users also appreciate documentation defining any known bugs and
workarounds in the Read Me file.
Since the installation of Online Library System is a complex process, our experts will
do it. So an installation Guide will not be provided to the user.
3.8 Purchased Components
The System Administrator will need to purchase the license for IIS Server. Mostly it
is available with Windows Environment. So the system need not purchase any licensing
products.

3.9 Interfaces
3.9.1 User Interfaces
Will make use of the existing Web Browsers such as Microsoft Internet Explorer or
Netscape. The user-interface of the system shall be designed as shown in the userinterface prototypes.
3.9.2 Hardware Interfaces
The existing Local Area Network (LAN) will be used for collecting data from the
users and also for updating the Library Catalogue.
3.9.3 Software Interfaces
A firewall will be used with the server to prevent unauthorized access to the
system.
3.9.4 Communications Interfaces
The Online Library System will be connected to the World Wide Web.
3.10 Legal, Copyright, and Other Notices
Online Library System is a trademark of Open University Malaysia and cannot be
used without its consent.
3.11 Applicable Standards
The IEE 830-1998 guidelines for the documentation of computer based application
systems will be followed.
4.0 Supporting Information
The use-case storyboards or the user-interface prototypes are not available. The
appendices are not to be considered as part of the requirements.

10

5.0 Appendix

Admin, 1, 2, 4, 5, 6

Microsoft Access Database, 7, 9

Microsoft Visual Interdev 6.0, 9

document, 2, 3, 10

Server, 4, 9, 10
Software, 1, 3, 6, 9, 10
Student, 2, 5, 6
System, 1, 2, 4, 5, 6, 7, 9, 10, 11

E
Editor, 6

Faculty, 1, 2, 4, 5, 7

Use Cases, 5, 6
User, 1, 2, 4, 6, 9, 10

Hardware, 1, 10

Web Publishing System, 2, 4

L
Local Network, 4

11