Visiondocument

UHCL Library
1.1.1.1
Online Library System
Vision Document
Version 1.2

Online Library System Version: 1.2
Vision Document Date: October 3, 2006
Revision document History
Date Version Description Author
1.0 Vision Document Initial
Release.
Author
1.1 Vision Document Release 1.1. Author
1.2 Vision Document Final
Release.
Author
UHCL Library © James C. Helm, October 4, 2006 Page 2

Table of Contents
2. Introduction 5
2.1 Purpose 5
2.2 Scope 5
2.3 Definitions, Acronyms and Abbreviations 6
2.4 References 6
2.5 Overview 6
3. Positioning 6
3.1 Business Opportunity 6
3.2 Problem Statement 7
3.3 Product Position Statement 7
4. Stakeholder and User Descriptions 7
4.1 Market Demographics 8
4.2 Stakeholder Summary 8
4.3 User Summary 9
4.4 User Environment 9
4.5 Stakeholder Profiles 9
4.5.1 Librarian 9
4.5.2 Employees of the Library 10
4.5.3 Users 10
4.6 User Profiles 11
4.6.1 Librarian 11
4.6.2 Employees of the Library 11
4.6.3 Users 12
4.7 Key Stakeholder / User Needs 12
4.8 Alternatives and Competition 13
4.8.1 None 13
4.8.2 None 13
5. Product Overview 13
5.1 Product Perspective 13
5.2 Summary of Capabilities 15
5.3 Assumptions and Dependencies 15
5.4 Cost and Pricing 15
5.5 Licensing and Installation 16
6. Product Features 16
6.1 Alerts 16
6.2 Authorization 16
6.3 Billing System 16
6.4 Time Restriction 16
6.5 Data Backup 16
7. Constraints 16
8. Other Product Requirements 17

8.1 Applicable Standards 17
8.2 System Requirements 17
8.3 Performance Requirements 17
8.4 Environmental Requirements 17
9. Documentation Requirements 17
9.1 User Manual 17
9.2 Installation Guides, Configuration, Read Me File 17
9.3 Labeling and Packaging 17

Vision
2. Introduction
The purpose of this document is to collect, analyze and define the high-level
needs and features of the Library Management System. It focuses on the
capabilities and facilities needed by the stakeholder who is University of
Houston – Clearlake (as the project is being developed for University of
Houston – Clearlake Library) and target users the Librarian, employees of
the Library, users of the Library (Students, Professors, etc.). The details of
what all are the needs Library Management System fulfils these needs are
detailed in the use-case and supplementary specifications.
2.1 Purpose
The purpose of this document is to describe the external behavior of the
Library Management System. The Vision Document captures very high-
level requirements and design constraints, which gives the reader an
understanding of the Library Management System to be developed.
Requirements Specification defines and describes the operations, interfaces,
performance, and quality assurance requirements of the Library
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.
2.2 Scope
The Library Management System that is to be developed provides the
members of the Library and employees of the library with books
information, online blocking of books and many other facilities. The Library
Management System is supposed to have the following features.
• The product provides the members with online blocking of books
capabilities and the library 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 password of the account
whenever needed all through the day during the library hours.
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 is based in the level
up to which the features described in this document are implemented in the
system.
2.3 Definitions, Acronyms and Abbreviations
• UHCL – University of Houston Clearlake.
• LMS – Library Management System.
• PIN – Personal Identification Number.
2.4 References
The Vision document uses the following documents as references:
1. UHCL Information Security Requirements: To provide security to
the system based on the current security system currently used by
UHCL.
2. The Billing System: To provide the interface between the system
being developed and the billing system currently in use by UHCL to
update the member account due as and when they borrow and return
the books.
2.5 Overview
This vision document lists all the capabilities of Library 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.
3. Positioning
3.1 Business Opportunity
There are hostels everywhere. Keeping records of difference services availed
by different
tenets is getting harder and harder by the day. This system will digitize the
whole
process.
This type of system has not been made at a professional level yet thus there
is a void
that needs to be filled. Where one see that there is no market and gives up
we see
opportunity and take the initiative to create a new market.

3.2 Problem Statement
The problem of Traditional ways of keeping records is highly
tedious and
affects Trusts between administration and students
as the records are liable to be changed to
serve an individual
the impact of which is Students often complain that they are being
charged more for mess then they actually
should have. The same goes for laundry, rent
and maintenance.
a successful solution
would be
This digital way of keeping record that will
revolutionize the field.
3.3 Product Position Statement
For small private hostels to huge government
hostels.
Who Need to digitize the regular and tedious
paper records keeping method.
The (Library
Management System)
is a Windows based application.
That that eases the access to records for both
students and administrators
Unlike Hand written records
Our product Hostel Management System can keep up
with the growing needs and modern busy
time.
4. Stakeholder and User Descriptions
The Library Management System that is to be developed provides the
members of the Library and employees of the library with books
information, online blocking of books and many other facilities. The Library
Management System is supposed to have the following features.
• The product provides the members with online blocking of books
capabilities and the library 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 password of the account
whenever needed all through the day during the library hours.
• The system allows the members to block the books 24 hours a day and
all the through the semester.
• The system lets the library staff to check which all members have
blocked the books and 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 system updates the billing system as and when the member
borrows or returns a book.
• The book catalog is automated and the decision of offering the book
based on the category of the book is automatically decided.
• We also have an order department, which manages to add or remove a
book from the Library.
The stakeholders for this system are the University of Houston-Clearlake
and the users of the library. The University of Houston-Clearlake employees
consist of the Librarian and the employees of the library.
4.1 Market Demographics
Most libraries use a local area network, that does not support mobile and
offsite monitoring. This feature is vital for users who are on the move. This
product aims to replace the existing system.
4.2 Stakeholder Summary
Name Represents Role
Librarian
Employees of the
This system evolved
around the need of the
librarian.
The information needed
by the librarian is vital.
They have reasonably
good computer skills.
The librarian can use the
system to update the
database of books, users,

Library
Users
The nurses use the
system to monitor the
books, users, etc.
The users use the
system to update their
accounts, block the
books, renew the
books, etc.
etc.
They may not have
adequate computer skills.
The user needs to be
comfortable and safe to
use the system.
4.3 User Summary
Name Description Stakeholder
Librarian They are the key users
of the system.
Since the stakeholder is
also a Librarian, their
needs are also taken into
consideration.
4.4 User Environment
The users of the system are members, librarian of the University and the
administrators who maintain the system. The members and the librarian are
assumed to have basic knowledge of the computers and Internet browsing.
The administrators of the system 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.
The system needs to be supported on mobile devices. It requires Internet
Explorer or Netscape. It should be able to work on both PC and MAC.
4.5 Stakeholder Profiles
4.5.1 Librarian
Representativ
e
Description Librarian
Type Librarian with 30 years of Library Management experience.
Responsibiliti The librarian can get the information about the members

es who have borrowed or returned the books, and is provided
with interfaces to add/delete the books available in the book
catalog.
Success
Criteria
The Librarian is able to update the database of the books
and also the user without going through the process
manually.
Involvement The Librarian can test the success or failure of the project
by trying to give the information of the book in the Library
to be searched and also by trying to update the user
information.
Deliverables None
Comments /
Issues
None
4.5.2 Employees of the Library
Representativ
e
Description Employees
Type Employees who have already worked with the Library
Systems.
Responsibiliti
es
Maintain the Library and give suggestions on priority
issues.
Success
Criteria
Able to monitor users more effectively.
Involvement Gives regular inputs and feedback on the needs of the
system.
Deliverables None
Comments /
Issues
None
4.5.3 Users
Representativ
e
Description User who checks-out books from the Library.
Type User with a valid Library card.
Responsibiliti
es
The user is responsible to maintain the rules and regulations
of the system.
Success
Criteria
The User is able to update his/her account, renew the books,
etc.

Involvement The User can test the success of the system by trying to
create an account and by performing certain user involved
operations.
Deliverables None
Comments /
Issues
None
4.6 User Profiles
4.6.1 Librarian
Representativ
e
Description Librarian
Type The Librarian is highly qualified and experienced person
working with UHCL.
Responsibiliti
es
The Librarian is responsible for regularly reviewing the
user profiles, maintains the Library Catalogue.
Success
Criteria
Using the system, the work of the Librarian will be reduced.
Involvement The Librarian can try to use the system and test it to the
maximum extent before the release of the system.
Deliverables None
Comments /
Issues
None
4.6.2 Employees of the Library
Representativ
e
Description Employees
Type The Employees are highly qualified and experienced people
working at UHCL Library.
Responsibiliti
es
The Employee is responsible for regularly reviewing the
Library Catalogue.
Success
Criteria
Using the system, the work of the Employees will be
reduced. If the User needs a book, the Employee can look
up in the System and tell where the book is located instead
of manually looking for the book throughout the Library.
Involvement The Employee can try to use the system and test it to the

maximum extent before the release of the system.
Deliverables None
Comments /
Issues
None
4.6.3 Users
Representativ
e
Description Users
Type The User is either a student or an employee of UHCL.
Responsibiliti
es
The User is responsible for regularly reviewing his/her
account.
Success
Criteria
Using the system, the work of the User will be reduced. If
the User needs to check whether the book is available in the
Library, he/she can look up in the Library Management
System from a remote system instead of coming all the way
to the Library.
Involvement The User can try to use the system and test it to the
maximum extent to check if it is full-filling his/her
requirements before the release of the system.
Deliverables None
Comments /
Issues
None
4.7 Key Stakeholder / User Needs
Need Prior
ity
Concer
ns
Current
Solution
Proposed
Solutions
Download time should
be less.
Database failing
should be 0%
High
High
Upgrade the
Database.
Database should
never fail.
Increase the Server
speed.
Maintain the
Database and take
care that the server
never fails.

4.8 Alternatives and Competition
4.8.1 None
4.8.2 None
5. Product Overview
5.1 Product Perspective
This system creation idea is based upon the problems that are faced by
students and management of hostels in Punjab University, Lahore, Pakistan.
The Hostel Management System to be developed benefits greatly the
students and hostel management. This system provides student information
to the management, their pending and paid arrears and their attendance and
check in or check out times. Student can just check in or check out by
logging into system and also can view his details. This system automates
this process of calculating arrears and saves both management and students
to get in trouble of consulting different people.
And they can have updated information any time. And also it can manage
Mess system for students.
The product to be developed has interactions with the users: Students,
Warden, and Administration.

Administrator
Hostel
Management System
Users
Billing System

5.2 Summary of Capabilities
Hostel Management System
Customer Benefit Supporting Features
Warden can easily monitor the user
accounts more effectively.
The data of the students in the
hostel is available to the Warden
when he is in the System.
The Students will be informed with
the latest updated news and
notifications.
The Students can know his/her
account information and the
status in the hostel.
Warden can identify problem areas
and gauge staff workload.
The problem area can be figured
out and assigned with more staff.
Enables information sharing
between the Hostels of the same
University.
Updating and retrieval of data is
simplified.
Warden can check report daily or
monthly.
Warden can check arrears of
student and can update them and
also can see report daily like,
attendance , Mess details etc.
5.3 Assumptions and Dependencies
• The users have sufficient knowledge of computers.
• The Hostel must have at least a terminal for students to check in and a
computer for warden.
• The users know the English language, as the user interface will be
provided in English
• University will provide required hardware.
• As there is no automated system implemented so there will not any
dependencies except University Management.
5.4 Cost and Pricing
• Within a year of release, Library Management System will be
installed in all the campuses of hostels that are available in hostel.
• There will not be development cost for this system.
• But, cost for hardware for installation will be paid by University so, it
does not concern with product.
• There will be no maintenance contract..

5.5 Licensing and Installation
• Our software professionals will do the installation of the product.
• The product is licensed under Open Source License Policies.
6. Product Features
6.1 Alerts
The system can alert the Librarian or the administrator in case of any
problems.
6.2 Authorization
Only authorized person (Student, warden) can login to the system. With
password and username.
6.3 Billing System
This system will automatically generate bills for students according to
expense details provided by Warden to the system.
6.4 Time Restriction
System will unavailable to student after a given time.
6.5 Data Backup
System will create backup after a certain time for recovery.
7. Constraints
• The information of all the users must be stored or entered in database
as this is first time all students will be entered.
• The hardware provided must be capable of running application
developed by using latest developing techniques.
• Main system must be always running on so that other sub computers
can contact to it.
• The users must have access to terminal computers.
• Hardware like, printers must be connected with the system.
• The users must have their correct usernames and passwords to enter
into the Hostel Management System.

8. Other Product Requirements
8.1 Applicable Standards
Proper Hardware must be provided.
8.2 System Requirements
• The system needs to have .net environment installed.
• The system must be configured with a database.
8.3 Performance Requirements
• Data must be retrieved within a minute.
• The information is refreshed every two minutes.
8.4 Environmental Requirements
None
9. Documentation Requirements
9.1 User Manual
The User Manual describes the use of the system to Students and
Employees. The user manual should be available as a hard copy.
9.2 Installation Guides, Configuration, Read Me File
This document 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. Most users also
appreciate documentation defining any known bugs and workarounds in the
Read Me file.
9.3 Labeling and Packaging
As this system is Open Source so there will be no sales for it and Package
label will defined by Company.

Visiondocument

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to Visiondocument (20)

Recently uploaded (20)

Visiondocument