Академический Документы
Профессиональный Документы
Культура Документы
Vision
Public High School Library
Vision
Version 1.2
Page | 1
Revision History
Date
Version
Description
25 May 2015
1.0
First draft
30 May 2015
1.1
10 June 2015
1.2
Author
Page | 2
Table of Contents
1. Introduction
1.1 Purpose
1.2 Scope
1.3 Definitions, Acronyms, and Abbreviations
1.4 References
1.5 Overview
2. Positioning
2.1 Business Opportunity
2.2 Problem Statement
2.3 Product Position Statement
3. Stakeholder and User Descriptions
3.1 Stakeholder Summary
3.2 User Summary
3.3 User environment
3.4 Stakeholder Profiles
3.4.1 MGM Store Manager
3.4.2 MGM Business Manager
3.4.3 MGM Software Architect
3.4.4 MGM Project Manager
3.5 User Profiles
3.5.1 MGM System End User
3.5.2 MGM System Administrator
3.6 Key Stakeholder/User Needs
3.7 Alternatives and Competition
3.7.1 Stay with the current system.
3.7.2 Buy an existing online securities trading service company.
4. Product Overview
4.1 Product Perspective
4.2 Summary of Capabilities
4.3 Assumptions and Dependencies
4.4 Cost and Pricing
4.5 Licensing and Installation
5. Product Features
6. Constraints
7. Quality Ranges
7.1 Reliability
7.2 Availability
7.3 Usability
5
5
6
6
7
7
7
7
8
9
10
10
11
12
12
12
13
14
14
15
15
16
16
17
17
17
17
18
18
18
18
18
18
19
19
19
19
19
Page | 3
21
19
20
20
20
20
20
20
20
20
20
20
20
21
21
21
21
21
21
Page | 4
Public High School Library Book Circulation and Inventory System Project
Vision
1.
Introduction
The purpose of this document is to collect, analyze, and define high-level
needs and features of the Generic High School Book Circulation and
Inventory System. It focuses on the capabilities needed by the librarians
and the patrons, and why these needs exist. The details of how the
Generic High School Book Inventory System fulfills these needs are
detailed in the use-case and supplementary specifications.
Information is what is needed to make current and future decisions and
are data that have been evaluated in the context of a specific problem
situation. Most librarians would contend that it is the proper management
of data and information that is one of the keys to a successfully managed
operation. However, most decision makers are more often than not
overwhelmed with the large amounts of data, but only limited supply of
information. The value of information is directly related to the decisions
of the superiors have to make.
A major decision making component in any organization is stock keeping
and checking. It can be a real challenge for most businesses and may
become a major problem especially if the inventories are long and in- and
outflow is huge. Manual reports are time consuming and difficult to
construct. Inadequacy, duplication, irrelevance and inefficiency are just
few of the many problems with the current manually operated systems.
List of files and papers in these files are difficult to document and
maintain, thus prone to risk of loss or damage, making the system
inefficient. Automation is the obvious solution to make transactions faster
and easier.
The introduction of the Vision document provides an overview of the
entire document. It includes the purpose, scope, definitions, acronyms,
abbreviations, references, and overview of this Vision document.
Page | 5
Purpose
The purpose of this document is to define the high level requirement of
the Public High School Library Book Circulation and Inventory System.
The objective of writing a Vision document for the Public High School
Book Circulation and Inventory System is to enable agreement among
librarian and developer. Another purpose of writing a vision document is
to provide a common platform for agreement between the developers
themselves.
Scope
This document records the vision for the Public High School Library Book
Circulation and Inventory System. The purposes of this document are to:
identify and agree on the problems faced by end users and the effects of
those problems on productivity and efficiency, gather and describe
customer requests for software features, propose a solution identify any
constraints to the proposed solution, identify librarians and users, and
also identify the software development team.
Page | 6
Lend It refers to the transaction when patrons carried the book outside
the library.
User a person who can interact with the software can be a librarian
or assistant library(library aide).
References
[This subsection provides a complete list of all documents referenced
elsewhere in the Vision document. Identify each document by title, report
number if applicable, date, and publishing organization. Specify the sources
from which the references can be obtained. This information may be provided
by reference to an appendix or to another document.]
Overview
The following sections outline the software product in higher detail. The
key features that will be implemented are also defined. The constraints
that will be imposed upon the software and the quality ranges, in other
words, the robustness, fault tolerance and usability of the software
product amongst other things are also covered.
In the precedence and priority section, the comment will be the most
important functionalities that the software product must have and the
integrity of the sales system. In the following sections will discuss all
other product requirements, such as, performance requirements,
platform requirements and environmental requirements. Lastly, we will
comment on the documentation requirements, such as, user manuals,
online help & support, installation and packaging.
This document contains product positioning statements, an analysis of
the systems stakeholders, an analysis of the expected system users, and
a list of features that the system should deliver. These features are
derived from the input obtained from stakeholders.
2.
Positioning
Business Opportunity
Page | 7
Is not up to date.
Time consuming
affects
a successful solution
would be
Page | 8
For
Who
That
Unlike
Our product
Not up to date.
Time consuming
Very tedious
Stakeholder Summary
There are typically a large number of stakeholders to a project. Here we
list the ones that have primary responsibilities and have the largest
influence on the success of the project.
Name
Represents
Role
Librarian
This is a stakeholder
that is primary for
leading the system
development.
Public High
School Library
- End User
User Summary
Name
Description
Stakeholder
Page | 10
Public High
School
Library Book
Circulation
and
Inventory
System- End
User
End User-Nave
Public High
School
Library Book
Circulation
and
Inventory
System - End
User
Public High
School
Library Book
Circulation
and
Inventory
System Project
Manager
Public High
School
Library Book
Circulation
and
Inventory
System Project
Manager
Public High
School
Library Book
Circulation
and
Inventory
System Page | 11
Project
Manager
User Environment
Most of the end users work alone. They have logged on to the Computer
Terminal with the book circulation and inventory management system
desktop application installed into it.
Except for the people who share an account, there is no interplay
between the different end users. They are independent of each other.
It is expected that some of end users will be encoding at the same time.
End user accesses the system through a standard computer terminal
(network). They do not need to learn new user interface (UI) techniques
of any type.
They access the system through windows platform.
Stakeholder Profiles
Public Secondary HS Inventory Management System Librarian
Representative
Description
Type
Responsibilities
Success Criteria
Involvement
Deliverables
Page | 12
Comments /
Issues
Description
Type
Responsibilities
Success Criteria
Involvement
Deliverables
Comments /
Issues
Description
Type
Responsibilities
Success Criteria
Involvement
Deliverables
Comments /
Issues
User Profiles
Users are listed in two categories: end users and Public Secondary HS
Inventory Management System administrators which is the Librarian. The
breakdown shown above is too detailed for this section.
Public Secondary HS Inventory Management System End User
Representative
Description
Type
Responsibilities
Success Criteria
Page | 14
their needs.
Involvement
Deliverables
Comments /
Issues
Description
Type
Responsibilities
Success Criteria
Involvement
Deliverables
Comments /
Issues
Page | 15
Requirements
Origin
Item Encoder
Librarian/Assistant
Librarian/Job
Orders
Librarian/Supply
Officer
Librarian/Supply
Officer
Librarian/Supply
Officer
Librarian/Assistant
Librarian/Job
Orders
Librarian/Supply
Officer
Page | 16
different features than what are needed in the public high school
libraries.
4. Product Perspective
Public High School Library Book Circulation and Inventory System is planned
to run the system in a standalone desktop application.
4.1
Summary of Capabilities
Public High School Library Book Circulation and Inventory
System
User Benefit
Supporting Features
Convenient, flexible access Local access
to the system
Secured access to the
Secured access to the system
system
New support staff can
Knowledge base assists support
quickly get up to speed.
personnel in quickly identifying
known fixes and workarounds.
Customer satisfaction is
Problems are uniquely
improved because nothing
itemized, classified and
falls through the cracks.
tracked throughout the
resolution process. Automatic
notification occurs for any
aging issues.
Management can identify
Trend and distribution reports
problem areas and gauge
allow high level review of
staff workload.
problem status.
4.2
Page | 17
The product can be installed by the end user with the basic knowledge on
software installation.
5. Product Features
Features
FEAT1: The System provides real-time inventory of books.
FEAT2: The system view patrons book in hand.
FEAT3: The system automates book circulation like book borrowing, lending
and returning.
FEAT4: The can automatically generates book inventory reports.
6. Constraintss
Security for the Public High School Book Circulation and Inventory
System includes authentication, access control, data integrity, and data
privacy.
7. Quality Ranges
7.1.
7.2.
7.3.
Reliability
The system shall be designed to be robust and be able to
handle a large amount of traffic.
The system must be able to handle improper user input.
7.4.
7.5.
7.6.
Documentation Requirements
10.1. User Manual
A user manual will provided as a PDF document to staff. It will
outline, in detail, the systems functions.
10.2. Online Help
System documentation will also be available online; it will
include the user manual, FAQ section and an email support
system.
10.3. Installation, Guides, Configuration and Read Me File
Page | 20
Page | 21