BR001 – Parking & Traffic Decal System
BR001 – Parking & Traffic Decal System
Detailed Business Requirements
Author:
Date Last Revised:
Document Revision #:
Business Group:
Business Unit:
Business Sub-Unit:
Sean Griffin
Krystal McDonald
Richard Rohrman
9/6/2005
1.0
UTDallas
Parking & Traffic Department
Signatures
Note: Sign-off of this document constitutes acceptance of the following detailed business
requirements as acceptable to perform a detailed analysis and provide a solution proposal.
Required Signatures
Authorized UTD
Representative
Authorized Next Level
Representative
Name
Signature
Document Revision Log
Revision #
1.0
Revision Date
09-06-2005
Name
Sean Griffin, Richard
Rohrman
Description/Impact to Document
Initial Document Draft
UTDallas / Next Level – Confidential
Date
BR001 – Parking & Traffic Decal System
Table of Contents
Document Revision Log ............................................................................................ 1
Table of Contents ..................................................................................................... 2
Introduction ............................................................................................................. 3
Document Purpose .................................................................................................. 3
Document Assumptions ............................................................................................ 3
Document References .............................................................................................. 3
Document Contributors ............................................................................................. 3
Overall Project Request Description ............................................................................ 4
Project Perspective.................................................................................................. 4
Constraints ............................................................................................................ 4
Assumptions .......................................................................................................... 4
Dependencies ........................................................................................................ 4
Project Value ......................................................................................................... 4
Critical Success Factors ........................................................................................... 4
Risks.................................................................................................................... 4
Notes ................................................................................................................... 4
Detailed Business Requirements ................................................................................ 5
Attachments ............................................................................................................ 7
UTDallas / Next Level – Confidential
BR001 – Parking & Traffic Decal System
Introduction
Document Purpose

This requirement document defines the detailed business requirements and business rules for a
project/service request. This information will be utilized to identify and propose solutions. The rigor applied
to completing this document has been proven, throughout the industry, to be the foundation for a successful
release. The targeted audience of this document includes the client, who provides key concepts for one or
more sections, and Service Line team members. The content of all subsequent release documentation is a
further extension of the specifications contained in this document.
Document Assumptions
The detailed business requirements document assumptions are:

The audience must be familiar with the related standards

The element names may change and should be updated in this document, as necessary
Document References
Document References
Title
Source
Author
Date
Revision
Document Contributors
Document Contributors
Person
Sean Griffin
Krystal McDonald
Richard Rohrman
Lydia Watts
Role
IT Analyst
IT Analyst
IT Analyst
Project Manager
Degree of
Involvement
High
High
High
Med
UTDallas / Next Level – Confidential
Notes
BR001 – Parking & Traffic Decal System
Overall Project Request Description
Project Perspective
Current website design does not allow for electronic registration and distribution of parking decals. This current market
flaw leads to volumes of disgruntled students and faculty flooding the small Parking & Traffic Department office,
extended transaction completion times, manual workarounds and overall inadequate and inefficient procedures.
BR001 Parking & Traffic Decal System has been approved by the UTD Administration and targeted to be implemented
end of November 2005. The new process and design changes will have the capability to handle online decal
registration transactions, effectively process the requested need, bill the consumer and distribute the decals via mail.
With these defined rules, UTD can better serve their customers with ease and efficiency.
System impacts include Integration Services, UTD Website, and …….
Constraints

Market Implementation Date: 11.22.2005
Assumptions

Implementation of TX SET 2.0 is scheduled for December 2005.
Dependencies

N/A
Project Value
This project will not only enhance the UTD Online System, but will improve the current manual decal registration
process. Also, it will appease the consumer because of reduced wait times, and less time spent manually registering
and picking up their decal.
Critical Success Factors
Risks

This is the initial version of this project and could potentially have conversion issues.
Notes
UTDallas / Next Level – Confidential
BR001 – Parking & Traffic Decal System
Detailed Business Requirements
This section is used to convey the detailed business needs to Next Level. It must contain details that should be
considered in the entire scope of this project from a business perspective.
BRD
Req. ID
1.0
High Level Business
Requirement
Online Order
Criticality
Must
2.0
Online Payment
Must
3.0
Scheduled Pickup
Want
4.0
Receipt of Payment
Must
5.0
Multi-Vehicle Registration
Must
6.0
Payment Due Notification
Want
7.0
Pickup Location Map
8.0
Usable Period Notification
9.0
Update Inventory
Option
al
Option
al
Must
10.0
Upgrade Hang Tag
Option
al
(Future
Want)
11.0
Downgrade Hang Tag
Option
al
Detailed Business Requirements
Allow user to fill out an online form that
requires personal and automobile information.
This form should be located within the SIS and
integrates with the proposed database.
The system should allow the user to make an
online payment using MasterCard, Visa, Comet
Card, or E-Check via a secure website.
System should suggest a scheduled time for
the user to pick up the hang tag. This is
intended to allow the user to pick up the hang
tags during non peak Bursar’s office hours.
This will:
1. Reduce the wait time for the customer
2. Allow the Bursar’s office to balance and
distribute their load
Notify user of receipt of payment and create a
printable online receipt.
Allow user to register up to 3 vehicles under
one hangtag.
Notify user of balance due: 1) at time of sale,
and issue an email via Pipeline email. (User
may not want to pay with credit card online or
would prefer to pay in person).
Provide a printable map of the UTD campus
with direction to the Police Department.
Clearly notify the user of the active period of
the hang tag.
Provide a screen for the police department to
enter new arriving inventory of hang tags.
Keep a tally of the number of remaining gold,
purple, green, and orange spaces.
Promote the sale of all the gold spaces to
maximize revenues by 1) allowing users to
upgrade their green tag to a gold tag anytime
during the Fall semester before January 1st,
only so long as gold spaces are available, for a
$50 fee, 2) allowing users to upgrade from
green to gold after Fall Semester, only so long
as gold spaces are available, for a reduced $30
fee.
In the case that a student erroneously
purchased a gold instead of a green, allow for
the $50 refund, within 10 business days of
purchase, and put a procedure in place
(student comes to Bursar’s office) to reclaim
the gold in exchange for the green.
UTDallas / Next Level – Confidential
BR001 – Parking & Traffic Decal System
BRD
Req. ID
12.0
High Level Business
Requirement
Track Sales / Revenue
Criticality
13.0
Pickup or Mail Option
Must
14.0
Online Sales, Window
Sales, Window Pickup
Reports
Option
al
(Future
Want)
15.0
Citation Leniency
Option
al
16.0
Seniority System
Option
al
17.0
Add Hang Tag Fees to
Tuition Fee List
Want
Must
Detailed Business Requirements
Keep track of all the appropriate accounting
associated with the original purchase, upgrade
and downgrade scenarios.
Allow the user to pick up the hang tag at the
Police Dept or, optionally, choose to have it
mailed for an additional $2.50 convenience
fee. User will need to agree that a) the
registered address is correct and b) UTD is not
obligated to reissue hang tags sent through
the mail (disclaimer in case the user claims the
hangtag never arrived).
Generate daily online printable reports of daily
sales activity – one for online sales, one for
window sales, and one for window pickups.
We want to compare online sales versus
windows sales. We also want to be able to see
the time savings at the window for when a
customer purchases online and is simply
picking up versus a window sale. These
reports will help us more accurately forecast
next year’s resources (manpower and system
requirements) and help us keep track of ROI.
Reduction in the number of inconsistent fines
and citations may be outside of the scope of
this project. However, we know that the
Bursar’s office places holds on students who
have unpaid fines. Therefore, it would be nice
if our system provided the Bursar’s office with
the ability to check to see:
If a student has a hangtag
If no, then student’s ticket is not dismissed
If yes:
Check to see if this is the student’s first
hangtag citation
If no, student’s ticket is not dismissed
If yes, student’s ticket is dismissed
Implement a seniority system such that,
during a 15 day registration period, seniors
have first pick at the gold spaces, juniors are
next, etc.
Priority
Aug 1- 15 Aug 16 on
Seniors
1
Open
Juniors
2
Open
Sophomores
3
Open
Freshman
4
Open
Allow the option to itemize hang tag fees on
the tuition fee list. Users will have a better
sense of the total cost of attendance at UTD.
UTDallas / Next Level – Confidential
BR001 – Parking & Traffic Decal System
BRD
Req. ID
18.0
High Level Business
Requirement
Online Update (Bursar)
Criticality
19.0
Reduce Cost of Hang Tags
20.0
Match SIS Availability
Out of
Scope
Must
21.0
Payment Deadlines
Want
22.0
Must
23.0
Reduce Police Department
Traffic
Secure User Information
24.0
Refund
Want
25.0
Distinguish Users
Must
26.0
Bursar Holds
Must
27.0
Verify Login Id
Must
28.0
Create New Order
Must
29.0
Lookup Decal Inventory
Must
30.0
Calculate Payment
Must
31.0
Verify Payment
Must
32.0
Update and Query Records
Must
Want
Must
Detailed Business Requirements
Provide a method for Police Department
window clerks to associate a Hang Tag with a
particular student via online web pages.
Online registration guarantees a hang tag but
the hang tag ID must be associated with the
user at the time of pickup (or when mailed).
Reduce the rising costs of Hang Tags through
strategic management of the entire process.
The Hang Tag system should be available
during the posted SIS hours.
Payment deadlines should be posted in a
location common to nearly all students –
possibly the tuition screen.
Eliminate the need for UTD Police staff to
process requests, forms, and handle money.
Provide adequate security measured to insure
the safety and integrity of user data.
Provide a method for the user to receive a
refund.
The system should not sell a purple or orange
tag to a student.
The system should not allow students with
tickets or holds to purchase tags
System will verify user ID and password to
ensure user is a registered student or staff.
System will generate an application in order to
store the type of permit the user has
requested. Application will be stored in
database once approved based on verity of
information provided.
System will check database to ensure
availability of requested permit.
If the requested decal is available, system will
generate an invoice with a payment amount
that is due to the university based on the type
of permit requested.
Once invoice is created, user makes payment.
The system will then verify the payment type
and either approve or reject it.
Once transaction is complete, system will
update database by listing the issued permit as
purchased by user.
Attachments
Note: Please attach copy of approved Project Request (which includes the initial business requirements)
UTDallas / Next Level – Confidential