VIPS Lab 1 Outline
1. Introduction:
Problem statement- Visitor parking is difficult to manage in a subscription-based
environment, resulting in visitor frustration and loss of revenue for Customer.
- Time wasted both Customer and visitor
- Effort wasted both Customer and visitor
- Complicated process
- Loss of revenue (general)
- Reference/data support Mr. Long
1.1 RWP
- Overview of RWP
- Solution statement
2. VIPS product description
-Solution
- Goal: Visitor Interface for Parking Services (VIPS) will provide an integrated
system to manage visitor parking for large organizations that utilize a
subscription based parking environment.
-Objectives:
1) Interface with current technology
2) Provide Internet based registration
3) Provide a database for visitor reservation management
4) Prevent abuse by subscription users
5) Allow reservations to be made by individual visitors and ODU faculty/staff
6) Be fee based
7) Provide data mining of transient visitors and historical summaries
8) Create a portable pass for use at garage entrance
2.1 Key Features and Capabilities
- Reserving spot
- Online reservation
- Ability of faculty to register their visitors
- Barcode technology
- Simple printable pass
- Interface with current technology.
- Trend history analysis
- Real time garage status
- Visitor validation
2.2 Major components
A. Hardware
-Barcode Scanner
-Radio Frequency Identification (RFID) antennae
- RFID tags
- Database server
- VIPS engine server
- VIPS web server
- Intercom
- Client Computer
- Existing Customer Database
B. Software
- VIPS Engine (schedules and handles garage application, Data Mining, Report
generation)
- VIPS Website (schedules visitor reservations, handles payment)
- VIPS database (Oracle)
- Communication (VIPS database and VIPS engine)
- Communication (VIPS database and VIPS Web Server)
- Communication (garage HW and VIPS Engine)
- Communication (VIPS Engine/ VIPS Web Server and Customer Database)
2.3 Target Market
- Who is it for- subscription based parking environments where space is at a
premium
- what is it for- allows our customer to provide a better service, by improving their
process
- Initial market of colleges and universities (1st customer ODU)
- Secondary market of urban business parking environments and airports
3 VIPS Prototype Description
- Barcode scanning
- RFID scanning
- VIPS reservation management
- Database functionality
- Website functionality
- Pass/barcode generation
- Garage simulation
- Customer Database emulation
- No fee collecting
3.1 Prototype goals and objectives
- Goal: Visitor Interface for Parking Services (VIPS) will prove the VIPS RWP
is feasible by providing an effective, functional demonstration with a lab
prototype.
- Objectives:
1) Interface with RFID technology
2) Provide Barcode based access to garage
3) Provide Internet based registration with secure account access control
4) Provide a simplified database for visitor reservation management
5) Prevent abuse by validating users against a blacklist
6) Create a printable pass for use at garage entrance
7) Simulate the parking garage environment
8) Simulate the arrival and departure of parking patrons
9) Provide a test harness graphical user interface environment for manipulation of
simulation
10) Demonstrate historical trends through either a data dump or through a db
report
11) Securing trend data (for parking services access only)
- Develop functional links between prototype design and the RWP (table)
3.2 Prototype architecture (HW/SW)
- Description of prototype Major Functional Component Diagram (MFCD)
- Description of the prototype process flow diagram
3.3 Prototype features and capabilities
- Description of how prototype shows garage reservation
- Description of how VIPS engine interacts with VIPS database
- Description of how VIPS engine interacts with garage simulation
- Description of how VIPS web server interacts with VIPS database
- Easy access through barcode and RFID scanning
3.4 Prototype development challenges
- Risks:
1.)
Prototype may not translate to the real world product.
Mitigation: VIPS inc. will ensure the prototype emulates the RWP as much as possible.
2.)
Prototype hardware is limited by budget.
Mitigation: VIPS inc. will use the best equipment available to construct the prototype.
3.)
Prototype simulated applications may not reflect the real environment accurately.
Mitigation: VIPS inc. will attempt to simulated the real world as completely as possible
with the given time limitations.
4.)
VIPS inc. can not model the wide range of existing customer hardware in the
prototype.
Mitigation: VIPS inc. will use the must standard hardware packages and model that
hardware setup.
5.)
Prototype database will not reflect all possible real life data needed in the RWP.
Mitigation: VIPS inc. will prove the system works with a test amount of data.
- ensure logical connection between prototype and RWP
- proving development can be achieved
- Payment will be taken care of based on customers existing technology
Glossary- under development
References- under development