Functional Specification
(GAS)
Gridlo ck Avoidance System
FUNCTIONAL DESIGN DOCUMENT
for
GRIDLOCK AVOIDANCE SYSTEM (GAS)
presented by
David Grant
Taylor Frith
Nhu Nguy
Chuck Askin
Carl Craft
Geoff Weller
David Graham
CS 410
Dennis Ray
Fall 1998
December 10, 1998
Functional Specification
(GAS)
Gridlo ck Avoidance System
1. SCOPE
1.1. Identification
This Functional Specifications document applies to the Gridlock Avoidance System,
GAS, presented by the fall 1998 CS 410 class at Old Dominion University (ODU).
1.2. System Overview
The purpose of the GAS is to develop a computer-based simulation model to mimic the
behavior of the Hampton Roads Interstate System south of the Mercury Boulevard
Interchange to the Battlefield Boulevard interchange.
Figure 1.2-1 Virginia Department of Transportation, Smart Travel Virginia, Dec. 8, 1998,
(http://www.vdot.state.va.us/roads/tunnel.html.)
Functional Specification
(GAS)
Gridlo ck Avoidance System
1.3. Document Overview
This Functional Specifications document describes the ODU CS 410 Team approach to
The functional specifications for the Gridlock Avoidance System and includes the
specific methods and procedures (technical and managerial) of the responsible
organizations that are to be employed during the course of the project. The processes
described herein reflect the requirements of the Software Engineering Institute's (SEI's)
Capability Maturity Model (CMM), Version 1.1, and the SEI's Method for Assessing the
Software Engineering Capability of Contractors (1987) at Level 2. The ODU CS 410
Team believes in rigorous, repeatable processes that promote efficiency, lower cost, and
Reduce risk. SEI compliance encourages the achievement of these goals and gives the
project the best possible chance of success. As a result, both project management and the
client are afforded earlier visibility into project progress and health. Better project
processes also promote higher efficiency and morale among project staff, as better
processes allow the project to operate from a position of control rather than
unmanageable schedule disruptions and delays, misspent money, excessive material
waste, and unacceptable overruns.
This document is organized into five sections and one appendix. The contents of these
sections are as follows:
Section 1 - Scope -- This section provides an introduction to the
document, including the identification of the system and applicable
CSCIs, a system overview, an overview of the contents of the Functional
Specifications document, and the relationship of the Functional
Specifications document to other program management documents.
Section 2 – Background/Objectives -- This section includes a description
of the planning activities associated with software development
management. This includes the GAS organization and resources, and the
overall project objectives.
Section 3 – Functional Specifications -- This section describes the
planning associated with software engineering activities requirements for
reaching the project objectives.
Section 4 – Schedule/Budget/Resources -- This section describes the
planning associated with the development process. This includes the GAS
organization and resources, schedule and milestones, risk management,
security, interface with associate contractors, interface with software
IV&V agents, subcontractor management, formal reviews, software
development library (which is part of the project repository), corrective
action process, and problem/change reporting.
Functional Specification
(GAS)
Gridlo ck Avoidance System
Section 5 - Conclusion -- This section summarizes the GAS project and
its importance in the preservation of the community infrastructure.
Appendix A is the Bibliography
1.4. Relationship to Other Plans
While this Functional Specifications document provides an overview of the CS 410 Team
approach to the development of software for the GAS project, its place in the context of
the whole program is better understood when it is utilized in conjunction with other plans
which form a part of the system document suite. This suite includes the following GAS
plans:
Program Management Plan. This plan describes the approach to program organization;
assignment of functions, duties, and responsibilities; management procedures and
policies; and reporting requirements of the GAS program.
Configuration Management Plan (CMP). This plan itemizes the approach to
configuration management for the design and development of the GAS project. It is
designed to ensure configuration management of the processes and the products that meet
the requirements of the GAS program
Software Quality Assurance Plan (SQAP). This plan describes the approach to
Software Quality Assurance for the GAS program. It is designed to ensure that quality is
built into the process of designing and developing software for the GAS program and that
the resulting products reflect this approach
1.5. Summary of Tailoring
TBD
<This is where the project's tailoring plan should be included. Include a description of all
tailoring of the software engineering process requirements called out in the ACP
Template, Studies and Systems Sector (SSS) software engineering procedures, Corporate
metrics spreadsheets, and SSS Process Quality Clause <if the project will employ
subcontractors and other teammates>. Note that tailoring is the modification of any
process requirements-managerial or technical. All tailoring must be reviewed and
approved by the responsible line manager--typically the Division Manager. Any removal
of a required activity or mechanism is considered a deviation and must be documented as
a waiver and reviewed and approved by Group and Sector management.
Functional Specification
(GAS)
Gridlo ck Avoidance System
2. BACKGROUND/OBJECTIVES
2.1. Background
David Grant (Project Manager) is a graduate of Tidewater Community College with an
AS degree in computer science and is currently senior at Old Dominion University
working on his Bachelor of Science in Computer Science degree with a minor in
Business Administration. He has also been employed by Science Applications
International Corporation (SAIC) as a Jr. Software Engineer for the past 16 months
concentrating mainly on System Level Testing and Software Testing activities.
Taylor Frith (Simulation and Data gathering) is currently a full-time student in the
Computer Science department at Old Dominion University. He will be graduating in May
1999 with a Bachelor of Science in Computer Science. He will be seeking a position in the
computer Science or computer engineering field with an emphasis on technical applications
and Visual C++ programming. His related experience is as a Research Assistant – Portsim
Software Development and Testing with the Virginia Modeling, Analysis and Simulation
Center (VMASC). Other experience includes the following.
- Naval Aviation Depot, Test Integration Facility, Chesapeake, Virginia
Electronics Engineer, Test and Evaluation and Production Support
Carl Craft (Simulation) is a retired navy aviation electronics technician and a graduate of
Tidewater Community College with an AS degree in computer science. He is currently a
Senior at Old Dominion University working on his Bachelor of Science in Computer
Science degree with a minor in Applied Mathematics. He has also completed classes in
Software Engineering and Computer Simulation
Nhu Nguy (Simulation and Web information) is a full-time student and senior at Old
Dominion University working on her Bachelor of Science in Computer Science degree with
a minor in Applied Mathematics.
Chuck Askin (Web Authoring) is a senior at Old Dominion University working on a
Bachelor of Science degree in Computer Science and has worked with the US navy for
16.5 years. His area of expertise in the Military was cryogenics. He is married with 3
girls. Attending CS 410 only.
Geoff Weller (Web Authoring) is a senior at Old Dominion University working on his
Bachelor of Science degree in Computer Science. He is also currently employed as a
Unix Systems Administrator for Computer Sciences Corp, contracted to NASA Langley.
Functional Specification
(GAS)
Gridlo ck Avoidance System
David Grant
Project Manager
Coordination of Resources
Administration
Carl Craft
Simulation
Research
Feasibility
Chuck Askin
Web Designer
Design
Training
Taylor Frith
Input/Output
Data Format
Data Migration
Nhu Nguy
Simulation Assistant
Research
Implementation
Geoff Weller
Information Specialist
Web Page Mainteneance
Information Repository
David Graham
Input Data
Data Resources
Data Format
Figure 2.1 Organizational Chart for CS 410 (GAS Project)
Functional Specification
(GAS)
Gridlo ck Avoidance System
2.2. Objectives

We intend to provide city planners and transportation professionals with results that
describe their system’s operations at current and modified vehicle flow rates in two
formats: statistical and graphical.

Provide a tool that is necessary to support the interstate highway system in Hampton
Roads, which is a critical element to the infrastructure of society in the area.

Demonstrate a simulation for a small segment of the Hampton Roads interstate
system for project validation and verification.

Market the project on a consultant basis with adaptability to different markets and
systems (what ifs).

Complete the project by the end of the calendar year 2001.

Ensure that software and hardware are both Y2K compliant.
Functional Specification
(GAS)
Gridlo ck Avoidance System
3. FUNCTIONAL SPECIFICATIONS
3.1. Affirmative Specifications
This section provides the following intended, achievable specifications of the GAS
project:











A proper depiction of the present Hampton Roads Interstate Highway system traffic
flow (the standard).
Long-term lane closures (construction/repairs).
Short-term lane closures (breakdowns/collisions).
Addition of lanes/interchanges to current system.
Addition of alternative routes to current system.
Introduction of weather phenomena on system (bright sun at eye level during AM and
PM hours).
Introduction of weather changes on system. (snow, heavy rain, etc.).
System reaction to emergency evacuation situations (hurricanes, etc.).
System reaction to changes in vehicle mix (percentage of cars/trucks/commercial
vehicles).
Reaction of system to speed limit changes.
Introduction of seasonal phenomena to system (tourists, vacationers, etc.).
3.2. Negative Specifications
This section provides the following non-achievable specifications of the GAS project:





Is not a real-time system.
Does not include surface road traffic patterns.
Does not include driver lane change tendencies.
Does not include driver related attribute tendencies.
Does not include individual vehicle related tendencies regarding entering and exiting
at certain predetermined points.
Functional Specification
(GAS)
Gridlo ck Avoidance System
4. SCHEDULE/BUDGET/RESOURCES
This section provides a working schedule for the three time periods involved and an overall
budget for the GAS Project. Included as well is an outline for any required resources.
4.1. Schedule
Fall 1998
Project Feasibility Presentation
Organizational Diagram
Cost/Resource Plan
Proposed Schedule
Milestones Presentation
Detailed Map of Hampton Roads Interstate Highway System
Functional Specifications Document delivered
Initial Data gathered
Project Scope Determined
Approval Proofs of Concept Presentation
11/98
11/98
11/98
11/98
11/98
12/98
12/98
12/98
12/98
12/98









Spring 1998
Final Data for Demo gathered
Select Demo highway segment
Subcontract work for CS 300u and CS 250
Preliminary Project Prototype Specifications
Project Home Page Demo
Project Prototype Demo
Grant Proposal Document delivered
1/98
1/98
1/98
2/98
3/98
4/98
4/98
15%
Research, Development, and Implementation
Lease office space and begin operations
Format and prepare data for simulator migration
Unit Testing
Unit Regression Testing
System Testing
System Regression Testing
Project Delivery
80%
50%
40%
10%
75%
5%
5%
6/98
6/98 - 6/99
6/99 - 6/00
6/00 - 1/01
1/01 - 9/01
9/01 - 12/01
12/01
Functional Specification
(GAS)
Gridlo ck Avoidance System
4.2. Resources
CS 300u
Conduct survey of real-life traffic patterns
Marketing research to determine funding sources
CS 250
Collect and format data for Statistical Analysis
Collect and format data for Simulator migration
4.3. Budget
Personnel
ODU Faculty Advisor (annual cost $46,000)
ODU Graduate Student workers (12 - 15 working
20 hours per week at $15 per hour)
Total Personnel Costs
Office
Office Space (annual cost $18,000)
Office Furniture (annual cost $6,000)
Office Supplies (annual cost $7200)
Total Office Costs
$
115,000
450,000
565,000
45,000
15,000
18,000
78,000
Equipment Purchases
Six Gateway E-5200 computers
15,600
One AlphaServer 8200 5/625, UNIX, 2 CPU, 4 GB, 4.3 GB KFTHA
Note: Media and doc required for first system on site
178,000
One EISA Bridge
2,000
Two PCI 3 port RAID controller w/4 MB cache
Note: If using 9 GB drives refer to SOC for significant restrictions 6,400
Twenty-three 4.3 GB 7200 RPM Storage Works Ultra Wide Disk
27,000
Three Storage Wide Shelf for 8299 (SE, Single BUS)
4,300
One PS/2 style Keyboard – North American/English
100
One VT510, White, Low-emissions, US/Canada/Mexico
400
One Power cord for 8200
100
One Bulkhead assembly kit for KZPSC-BA
100
Four .0 meter VHDCI male to VHCDI male cable
600
Lexmark OPTRA 3455 network printer
2,600
Hewlett-Packard OfficeJet Pro 1175C all-in-one printer
1,000
Statistical software package
200
Hewlett-Packard DeskJet 2500C Plotter
9,400
IBM Fast Ethernet LAN switch 1100
1,900
Evaluation Simulator Engines
4,300
Functional Specification
(GAS)
Gridlo ck Avoidance System
Total Equipment Costs
ODU Research Foundation Cost
Total Project Expenditures
254,000
$
403,000
1,300,000
Functional Specification
(GAS)
Gridlo ck Avoidance System
5. CONCLUSION
The Gridlock Avoidance System is a necessary tool to insure the stability of the infrastructure of
the Hampton Roads area. The risks of not proceeding with the project far outweigh the risks of
proceeding on schedule. The risk of gridlock capturing and holding for ransom not only
Hampton Roads but also many other cities throughout the United States is a real threat. In order
to avoid this threat in the future we must act decisively and quickly. A weapon in our arsenal
such as the GAS project could quell any uprising of this sort in the area. It will not only preserve
our current lifestyle but work to better it in the future. The biggest hurdle to overcome is a
correct depiction of the current highway system. Through the development of our prototype, the
extensive unit and system level testing, and the research data collected from organizations such
as the Virginia Department of Transportation, (VDOT), we can deliver a reliable an effective tool
to be used in the fight to overcome and eventually defeat ‘Highway Gridlock’ in the Hampton
Roads area.
Thank you for the opportunity to present our project to you and remember that your vote today
can either make you a hero or a zero in the eyes of future generations.
Functional Specification
(GAS)
Gridlo ck Avoidance System
BIBLIOGRAPHY
Dr. Leathrum (Old Dominion University - ECE)
Dr. Overstreet (Old Dominion University - CS)
Mr. Dennis Watson (VDOT)