University Parking Solutions

Because Parking Should Be Simple

GROUP 15
Sara Irfan, Software Developer
Safa Sadatyar, Software Developer
Ramsey Robinson, Application Developer

Table of Contents
Executive Summary .3
System Proposal and Problem Statement ...............................................................................4
Requirements Definition .6
Structural Model .....7
Behavioral Model .8
Dynamic Model ...13
Design Documents 15
Testing .....20
Project Management Documents ..21
Lessons Learned .23

Executive Summary

Brief
Over the past several years The University of Texas at Dallas has experienced tremendous
growth in student enrollment. Due to this growth, there have been many issues involving parking
such as lack of spot availability (especially during peak hours) and extended time wasted
searching for available spots. University Parking Solutions would like to modernize the campus
parking system and make the experience less stressful and more efficient for the users. The UP
solutions parking application project has been proposed to address and correct these parking
issues and prevent poor student parking experiences. By creating an app that updates users in
real time on where certain parking spots are located on campus, it will allow them to go straight
to the spot saving time and making the overall experience hassle free.

Solution
Students who use the application will be provided with parking recommendations based
on their current location, desired destination and current available parking. The outcomes of the
project will make parking recommendations to student by real-time data feed of the current
availability of parking locations supported by the UP solutions platform. Parking supervisors will
have the ability to monitor and support real-time parking activity through a graphical user
interface(GUI). This will provide current campus parking activity, parking frequency, parking
reports through the application internal database tables. The project will integrate improved
technology solutions with the current university parking system with UP solutions next-gen
parking platform in order to establish a more dynamic university parking infrastructure.
We believe that there is a growing market for these solutions, and as schools grow in size,
especially commuter schools, the need for efficient parking systems does as well. The University
of Texas at Dallas is a great candidate for our system.

System Proposal
This document highlights the requirements of the proposed system U-Park created by
University Parking Solutions. It includes the following: project objectives, background, scope,
testing and other deliverables important to the completion of the application.

Problem Statement
A growing student and faculty population at The University of Texas at Dallas has resulted in
parking to be hectic, difficult and a time consuming process. Students, faculty and visitors often
face issues with parking lot congestion, especially during peak hours. Finding and reserving a
parking spot in a specific lot within a short period of time isnt possible without having an
overview of the lot and reserving it beforehand, thus the creation of the U-Park parking
application for the university.

System Request
Project Title: University Parking Solutions
Project Sponsor: Richard C. Benson
Project Start Date: September 7th, 2016

Projected Finish Date: December 5, 2016

Budget Information: The firm has allocated has allocated $120,000 for this project. The
majority of costs for this project will be internal labor and the purchasing and installation of the
PTZ cameras.
Project Manager: Carol Haines, (214) - 331- 1983, carolhaines@upsolution.com
Project Need and Value:
The University of Texas at Dallas is a growing school with a need of an updated routine when it
comes to parking. Most students and faculty are commuters so the need to park in a timely
manner is extremely relevant and important. With UP solutions new software and application
users will be able to track available parking with ease. There will be less congestion during peak
parking and traffic hours and better use of time.

Project Objectives:
Develop a software with compatible application that connects to cameras installed on
the UT Dallas campus
Real time images on the application that show users where there is available parking for
their permit types
Ensure a clear and concise interface for users
Reduce parking times for students arriving on campus
Increase usage of current parking capacity
Store parking lot data over time
Provide data on parking capacity and usage for UTD decision makers
Provide parking spot suggestions to UT Dallas students
Assumptions:

Staff working hours occur on an 8:00am-5:00pm schedule.

New hardware is functional.
Dedicated staff will cross train one another.

Summary of Project Deliverables:

The main deliverable of this project is a fully functioning mobile application that is user friendly,
compliant with installed hardware, and manageable.
Project Scope:
This project will start off by only including the following parking lots: Lot Q, Lot M East, Lot M
West and Armstrong Drive. These lots will be the initial testing phase of the project, and based
upon their success, the system will expand to the rest of the school which includes Lot A, Lot B,
Lot C, Lot D, Lot E, Lot H, Lot T, Lot J, Lot P and also residential parking for students who live on
campus.
The project will generate information on available parking, provide parking suggestions to
students on demand given current parking conditions, store parking spot availability
information, and provide an interface for UTD decision makers to see how each parking lot is
used throughout the day.
The project will not be permanently storing images used in determining parking spot
availability. It will also not provide recommendations for future parking lot expansion or
modifications.

Project Success Criteria:

Our goal is to complete this project in the allotted three months for no more than $120,000.
The project sponsor, Dr. Richard C. Benson, has emphasized the importance of completing the
project in a timely manner and to have the application running by Spring 2017.
Project Sponsor and Stakeholders:
Our project sponsor is Dr. Richard C. Benson, the president of The University of Texas at Dallas.
Stakeholders include students and the community as well as various investors.

Requirements Definition
1.1

The user interface will display the available parking spaces, parking locations, and
suggested parking location(s) based on users preference. (Functional)

1.2

The application will allow users to create an account and login with credentials.
(Functional: Authentication)

1.3

Parking administrators will have the ability to create and view reports of the daily
parking activity volumes. (Functional: Reporting)

1.4

Parking administrator will have the ability to make adjustments to parking capacity and
to update adjustments made to the application for users. (Functional)

2.1

The parking system will have the ability to search available parking areas. (Non
Functional: Interoperability)

2.2

The parking system will be operational 24/7 days a week. (Non-functional: Reliability)

2.3

The parking system will perform an interval update every 5 minutes and update the
application on parking activity. (Non-functional: Serviceability)

Structural Model: Class Diagram

Behavioral Model: Use Case Diagram & Descriptions

Use Case Name:

Create Account

Primary Actor:

Application User

Brief Description:

This use case diagram describes how the application user creates an account
for the University Parking Solutions application at the University of Texas at
Dallas (U-Park Solutions).

Stakeholders:

Application User, The University of Texas at Dallas Parking Office

Trigger:

A need for a quick and efficient parking system is needed for the growing
university.

Normal flow of events:

1.

Download U-Park application.

2.

Select Create New Account icon in the application.

3. Enter required information (net ID, email address, phone number, first
name, last name, permit ID, vehicle license plate).

Sub-flows:

4.

Create password.

5.

Confirm email address.

6.

Confirm phone number.

4a. System sends a confirmation email to user with a confirmation link and
information provided by user.
5a. System sends a confirmation text message to phone number.

Alternate/Exception flow:

1. Unable to confirm email address and/or phone number, user must adjust
information provided to successfully create an account.

10

Use Case Name:

Log-in

Primary Actor:

Application User

Brief Description:

This use case diagram describes how the application user logs into the
application.

Stakeholders:

Application User, The University of Texas at Dallas Parking Office

Trigger:

The application user wants to look for a parking spot so they must log
in.

Normal flow of events:

1.

User opens the application.

2.

User enters their Net ID as the username for the account.

3.

User enters password.

4. User is logged into the system and can view details about their
account, parking lot maps and update preferences.
Sub-flows:

4a. System confirms Net ID and password combination and allows user
access to account.

Alternate/Exception
flow:

2a. Net ID is incorrect so the username must input correct Net ID.
3a. Password is incorrect so user must input correct password.

11

Use Case Name:

Find Parking Space

Primary Actor:

Application User

Brief Description:

This use case diagram describes how the application user used the
application to search for and find available parking spots.

Stakeholders:

Application User

Trigger:

User wants to quickly find all available parking spaces in a certain lot at
that moment.

Normal flow of events:

1.

User selects preferred parking lot.

2.

User sees all available spots in that lot per their permit type.

3. User temporary reserves a spot based on proximity and drives to

the spot and parks their vehicle (GPS must be turned on to avoid double
parking accounts and have accurate parking spot proximity).
4.

User confirms vehicle parking by clicking the Im Parked button.

Sub-flows:

2a. System is constantly updating the application to provide an accurate

map of available parking spots.

Alternate/Exception
flow:

4a. User forgets to click the Im Parked button so the system prompts
user to select if parked or Cancel.

12

Use Case Name:

Update Account

Primary Actor:

Application User

Brief Description:

This use case diagram describes the steps the user needs to take to
update their account.

Stakeholders:

Application User, The University of Texas at Dallas Parking Office

Trigger:

The user needs to update information on their account to continue

using the application.

Normal flow of events:

1. User needs to update permit ID at the end of every school year

(Fall-Summer).
2.

User confirms vehicle(s) registered.

3.

User confirms phone number.

4. User can continue to use the application to find available parking

spots.
Sub-flows:

4a. System updates and confirms the account information any time there
is a change made.

Alternate/Exception
flow:

1a. User can update permit ID mid semester if they want to

upgrade/downgrade their parking permit.
2a. User can add/remove vehicle(s).
3a. User can update phone number if its changed.

13

Dynamic Model: Sequence Diagrams

14

15

Design Documents: Interface Design, Control Specifications, Software

Design Specifications and Architecture Diagram.

Mobile Application:
Left: Map screen of the parking lot and the parking colors in each lot.
Middle: Login screen for the application
Right: Main menu of the application

16

Controls:
Detection Parking administrators are equipped to detect possible process breakdowns in the
parking system by monitoring daily parking activity. If for example a parking camera begins to
malfunction or provide inaccurate information to users, application users can submit the incident
report through the application. Once the report is received parking administrators can act and
perform troubleshooting methods to determine the root cause and/or channel the necessary
resources to fix any issues.
Prevention Application users are required to submit their UTD Net ID, name, and create a
password in order to register and access the application. In some instances, the user may enter
the incorrect information in the first-time login screen. A validation control has been created to
ensure the user entered information matches the UTDs student database in order to ensure
accurate and secure application use.
Investigative Parking administrators routinely may validate the parking list data being
generated and sent to the user application. In order to ensure the integrity of the data being
generated, parking administrators will conduct spot checks routinely to ensure the application is
only providing accurate data to the users. If for instance inaccurate information is discovered
being passed to the user, the parking administrator will work with IT support to troubleshoot the
issue and/or manually update the parking system to reflect accurate information.

17

18

19

20

Testing
This section describes the various types and levels of testing involved to assure project security,
functionality and performance.
A safe and secure server and database are important for this system because personal
information of faculty and students is being collected (phone number, full name, net ID, email
address, vehicle id etc.) and it must remain secure and inaccessible to hackers. Since the
information is personal but not sensitive (such as social security, home address etc.) the
security measures do not need to be high level, but adequate enough to hide information from
unauthenticated sources. Security certificates will be added to database connection between
Galaxy and the U-Park connection both ways. There will be a trial authentication test to
security.
In order to test the functionality of the code unit testing will be performed. After
combining the code, integration testing will be performed in order to assure the application
functions well. Once created a few dummy accounts will be created and navigate through all
the features of the application to ensure the windows create the proper arguments.
For the performance testing of this system, load testing will be done. User satisfaction is
extremely important for this system because there will be a lot of users using the application
during peak hours and the system must be able to allow multiple users access. The application
must be quick, even when multiple users are online and so multiple speed tests will be
performed.

21

Project Management Documents

Roles and Responsibilities:
Name

Role

Position

Contact Information

Dr. Richard C.
Benson

Sponsor

UT Dallas, President

rcb123467@utdallas.edu

Carol Haines

Project Manager

UP-Solutions, Director of
IT

carolhaines@upsolutions.com

Safa Sadatyar

Team Member

UP-Solutions, Software
Developer

safasadatyar@upsolutions.com

Sara Irfan

Team Member

UP-Solutions, Software
Developer

sarairfan@upsolutions.com

Ramsey Robinson

Team Member

UP-Solutions, Application ramseyrobinson@upsolutions.c

Developer
om

Brian Sutton

Team Member

UP-Solutions, Application briansutton@upsolutions.com

Developer

Meeting Minutes:
Date
9/6/2016
11/9/2016
11/27/2016
11/28/2016

Attendees
Sara, Safa
Sara, Safa
Sara, Safa, Ramsey
Sara, Safa

Hours Spent
3
5
6
10

22

Work Breakdown Schedule (WBS)

Task Name
1.0 Analysis
1.1 Functional Requirements
1.2 Class Diagram
1.3 Process Model
1.4 Object Behavioral Model
2.0 Design
2.1 Controls - MA
2.2 Controls - AWA
2.3 Interface Design - MA
2.4 Interface Design - AWA
2.5 Software Design - MA
2.6 Software Design - AWA
2.7 Test Cases - MA
2.8 Test Cases - AWA
3.0 Implementation
3.1 Prototype
3.2 Architecture Diagram
3.3 Testing(sec,func,perf)
3.4 Design Documents
3.5 Final Report

Predecessor

1.2
1.3
1.0

2.1
2.2
2.1
2.2

Effort

Estimated
Start Date

Estimated End
Date

Assigned Resource(s)

7 Days
5 Days
3 Days
3 Days

9/7/2016
9/7/2016
9/19/2016
9/26/2016

9/16/2016
9/14/2016
9/23/2016
9/30/2016

Ramsey
Safa, Sara
Safa, Sara
Safa, Sara

2 Days
2 Days
5 Days
5 Days
7 Days
7 Days
2 Days
2 Days

10/3/2016
10/3/2016
10/6/2016
10/6/2016
10/17/2016
10/17/2016
10/31/2016
10/31/2016

10/5/2016
10/5/2016
10/14/2016
10/14/2016
10/28/2016
10/28/2016
11/2/2016
11/2/2016

Ramsey
Ramsey
Safa Sadatyar
Safa Sadatyar
Safa and Sara
Safa and Sara
Sara Irfan
Sara Irfan

2 Days
2 Days
1 Day
2 Days
2 Days

11/15/2016
11/15/2016
11/15/2016
11/15/2016
11/27/2016

11/27/2016
11/27/2016
11/27/2016
11/27/2016
11/28/2016

Safa
Safa
Sara
Sara and Safa
Sara and Safa

2.0

WBS Dictionary
Class Diagram:
Diagram will include information for interfaces for both mobile application and administrator
application
Process Model:
Describes relation between two models provided
Object Behavioral Model:
Will chart out how applications will be used by users
MA:
Mobile Application - Student/user side
AWA:
Administrator Web application - Administrator side

23

Lessons Learned
During the duration of this project I have encountered many successes, failures and have
learned a lot from both. Most of my time was spent in the planning phase of the project. We
created a very specific scope, but when we moved on to the next phases, of design, analysis and
implementation we faced a lot of difficulty because we lost sight of the scope and didnt really
focus on it. Due to this, we ended up having to recreate our class diagram a few times because
our classes ended up being out of scope. We created classes for the IT Support part of our project,
but when it came to creating methods and attributes, the diagram became really big and out of
scope. That when I realized that we will probably need to redo a few of our diagrams in order for
the entire system and program to even make sense. I wish that my group and I spent a little bit
more time researching a project/system idea because after realizing that a lot of other groups
were doing parking on campus as a project I just worried about there being 20 different groups
with the exact same tables, diagrams etc.
Choosing a good group is also really important because if the group isnt focused and on
the same page, the project can go downhill really quickly. For this project we had the option of
choosing our own groups, but in the real world we dont always have that luxury so getting along
with everyone, keeping everyone motivated and doing your part regardless of who else is in the
group is very important. One of our group members hasnt been present in class for a little while
and hasnt been responding to our messages and this burdened my group because we ended up
having to do a lot more than expected which became an issue when deadlines starting nearing. I
feel this affected the quality of the work we submitted because we had to change our focus from
getting our individual parts done to making sure the entire project is completed. I enjoyed going
through each process of the SDLC and creating the diagrams. I didnt realize how much work went
into even what seems the simplest apps and ideas. I am not a very patient person but that project
has taught me to be patient, detail oriented and careful at each and every step, these are all
important characteristics to have not only in a team but as a person.
-Sara Irfan

24

Throughout this project I learned a lot about working with others, time management and
problem solving. This, of course, was not the first time I have worked with a group during the
course of my collegiate career, but for some reason I always found myself very flustered every
time a milestone was due.
Working with others and having a strong group dynamic makes for a much better
experience when developing a project that is this rigorous and time intensive. I learned that
having a strong leader was an absolute must otherwise some people would just try and slide by
without doing anything. So at times I would have to take charge and tell my fellow group
members exactly what needed to be done for the milestone. At times, though, certain group
members were not available to work on what needed to be done so I felt that a lot of the work
would land on the rest of us who were responding to texts and coming to class. I know its
extremely important to pick a group you think you can rely on, but I think this was a good
experience because in a real job you will not always be able to pick who you work with and who
your supervisor is. So it is important to be able to adapt to situations that you are not
comfortable with.
Time management was also another skill that was crucial to the completion of the
project. I think in groups before my semester schedule was never as rigorous so it was a lot easier
to meet up and get started on group work earlier. So I learned that even though we could not
meet as much as we wanted too as a group splitting up the work and allocating a good amount
of time to my specific section was really important.
Problem solving was another crucial part of the project. It was really interesting
experience having to put our work and ideas into different diagrams. Sara and I would constantly
go back and forth on the structure of the diagram so having people to bounce ideas off of was
really helpful. I also learned that the planning phase and staying in the scope of the project was
really important so having the end result of what we wanted out of our project was really
important to staying on track.
-Safa Sadatyar

25

A projects success can be measured by the collaboration, teamwork, and communication

executed by the people involved. While working within my group, I learned the probability of a
group or team succeeding is deeply rooted in the teamwork, communication, and attitude of
each member on the team. Instructor assignments and deadlines can challenge a groups
perseverance and attitude and expose weaknesses within team members, but also reveal strong
attributes too. For example, many members on my team have very busy managing work and
school. Although our busy schedules sometimes made having project meetings or completing
assignments in a timely manner nearly impossible, we managed to complete every assignment
with high scores by our teamwork.
The system development life cycle (SDLC) is a framework defining each step in the
software development process. SDLC process is broken into phases that begin with planning,
analysis, design, and final implementation. During the development of the project it started to
become very obvious that the planning phase set the pace and foundation probability of the
projects success. Majority of my team and I time was spent investigating and determining solid,
concise, and clear business requirements for the project. The requirements were analyzed and
judge on the feasibility and clearness. Without the requirements being tested for feasibility and
clearness, I learned that the next phases would expose flaws and require our group to backtrack
into the planning phase. As I progressed in the project the design phase, I learned to specify the
hardware and system requirements that assist in defining overall system architecture. The
human computer interface (HCI) was developed in order to provide the main platform the user
uses to interact with the system. The platform was tested against the requirements set in the
planning phase, and the platform actually solves the needs that were addressed in the beginning.
Although the project ended in the design phase, I realize the project was thoroughly developed
through the SDLC methodology that the project had the potential to reach the implementation
phase with the necessary resources.
After completing this project and course, I will be applying this knowledge in my future
academic and professional career with confidence in the SDLC process. Additionally, I learned a
methodology such as SDLC is the one of the best approaches to completing a project that will
yield the highest chances of success. Lastly, this project improved my communication and
developed my teamwork and project management skills.
-Ramsey Robinson