SBIR
CS 410 Red Team
Old Dominion University
July 26, 2016
Abstract
Cell phone use while driving is dangerous regardless of how coordinated a driver may be. Research
shows that driving while using a cell phone significantly increases the risk of being in an accident.
Parents buy their teenagers a cell phone but currently have no control over its use by the child while
they are driving. Since all parents are concerned for their child’s safety, The Silencer will have a strong,
broad market. The Silencer uses Bluetooth technology to communicate to cell phones in the vehicle with
special software. This software legally disables incoming and outgoing calls from the phone while the
car’s engine is on. Other solutions on the market include blocking cell phone reception, which is illegal
by the FCC, and mobile transmission detection, which emits an even more distracting beep to annoy the
driver until he or she decides to cancel the call. Cell phone manufacturers already allow third-party
software on their phones, so The Silencer software can be loaded onto a child’s phone by a parent. With
this product, parents can be more at ease about their child’s safety in a society where cell phones are
becoming as ubiquitous as cars.
CS 410 Red
SILENCER
7/26/2016
Table of Contents (Brief)
Document
Pg. No.
Abstract ..............................................................................................................................................................1
Table of Contents (Brief) ...................................................................................................................................2
Table of Contents (Full) .....................................................................................................................................3
1
NSF Cover Sheet (Form 1207) ..................................................................................................................5
2
Project Summary (Brendan) ......................................................................................................................7
3
Project Scope (Dylan) ..............................................................................................................................14
4
Project Impact (Reda) ..............................................................................................................................19
5
Biographical Sketches (Reda) ..................................................................................................................21
6
Budget (Sam) ...........................................................................................................................................24
7
Facilities, Equipment, and Other Resources (Sam) .................................................................................28
8
Reference (Dylan) ....................................................................................................................................30
9
Appendices...............................................................................................................................................32
Page 2/84
CS 410 Red
SILENCER
7/26/2016
Table of Contents (Full)
Document
Pg. No.
Abstract ..............................................................................................................................................................1
Table of Contents (Brief) ...................................................................................................................................2
Table of Contents (Full) .....................................................................................................................................3
1
NSF Cover Sheet (Form 1207) ..................................................................................................................5
2
Project Summary (Brendan) ......................................................................................................................7
2.1
Car Crash Statistics in the United States (Brendan) ......................................................................... 7
2.2
Cell Phone Data for Car Crashes (Brendan) ..................................................................................... 8
2.3
Focus on Teenagers (Brendan).......................................................................................................... 9
2.4
Governments’ Response to Driving with Cell Phones (Sam) ......................................................... 10
2.5
Silencer Solution Introduction (Brendan) ....................................................................................... 12
3
Project Scope (Dylan) ..............................................................................................................................14
3.1
Target Customers ............................................................................................................................ 14
3.2
Competition .................................................................................................................................... 15
3.3
Innovation ....................................................................................................................................... 16
3.4
Evaluation Criteria .......................................................................................................................... 17
4
Project Impact (Reda) ..............................................................................................................................19
4.1
Customers’ Need for a Solution ...................................................................................................... 19
4.2
Benefits ........................................................................................................................................... 20
5
Biographical Sketches (Reda) ..................................................................................................................21
5.1
Senior Personnel ............................................................................................................................. 21
5.1.1
Brendan Geoghegan - Project Manager .................................................................................. 21
5.1.2
Donnie Goodson - Software and Web Design ........................................................................ 21
5.1.3
Duc Nguyen - Lead Software Developer ................................................................................ 22
5.1.4
Dylan Wheeler - Marketing and Documentation .................................................................... 22
5.1.5
Reda Elgourbi - Statistical Analyst ......................................................................................... 22
5.1.6
Samuel Shelor - Finance and Hardware ................................................................................. 22
Other Personnel – Consultants.................................................................................................................... 23
5.1.7
Dr. Stephan Olariu – Wireless Consultant .............................................................................. 23
5.1.8
Dr. Michele C. Weigle - Wireless Consultant ......................................................................... 23
5.1.9
Dr. Steven J. Zeil - Software Consultant ................................................................................ 24
6
Budget (Sam) ...........................................................................................................................................24
6.1
Summary Proposal Budget – NSF Form 1030 ............................................................................... 24
6.2
Salaries and Wages ......................................................................................................................... 27
6.3
Equipment ....................................................................................................................................... 27
7
Facilities, Equipment, and Other Resources (Sam) .................................................................................28
7.1
Facilities .......................................................................................................................................... 28
7.2
Location .......................................................................................................................................... 28
7.3
Software .......................................................................................................................................... 28
7.4
Hard Resource................................................................................................................................. 29
8
Reference (Dylan) ....................................................................................................................................30
9
Appendices...............................................................................................................................................32
9.1
Management Plan (Brendan) .......................................................................................................... 32
9.1.1
Program Identification ............................................................................................................ 32
9.1.2
Work Breakdown Structure..................................................................................................... 37
9.1.3
Program Planning ................................................................................................................... 37
9.1.4
Progress Performance Assessment.......................................................................................... 38
Page 3/84
CS 410 Red
SILENCER
7/26/2016
9.1.5
Reviews ................................................................................................................................... 41
9.2
Marketing Plan (Dylan) .................................................................................................................. 44
9.2.1
Market Analysis ...................................................................................................................... 44
9.2.2
Target Market .......................................................................................................................... 45
9.2.3
Sales Plan ................................................................................................................................ 46
9.2.4
Advertising Strategy ............................................................................................................... 46
9.3
Staffing Plan (Donnie) .................................................................................................................... 47
9.3.1
Phase 0 .................................................................................................................................... 47
9.3.2
Phase 1: Proof of Concept ...................................................................................................... 49
9.3.3
Phase 2: Critical Design .......................................................................................................... 52
9.3.4
Phase 3: Production and Out Years ......................................................................................... 56
9.4
Funding Plan (Sam) ........................................................................................................................ 60
9.5
Work Breakdown Structure (WBS) (Duc) ...................................................................................... 62
9.5.1
Phase 0 .................................................................................................................................... 62
9.5.2
Phase 1 .................................................................................................................................... 67
9.5.3
Phase 2 .................................................................................................................................... 70
9.5.4
Phase 3 .................................................................................................................................... 73
9.6
Risk Management Plan (Reda) ....................................................................................................... 76
9.7
Evaluation Plan (Duc) ..................................................................................................................... 78
9.7.1
Design Reviews ...................................................................................................................... 80
9.7.2
Code Reviews ......................................................................................................................... 80
9.7.3
Unit Testing ............................................................................................................................. 81
9.7.4
Integration Testing .................................................................................................................. 81
Page 4/84
CS 410 Red
SILENCER
7/26/2016
1 NSF Cover Sheet (Form 1207)
COVER SHEET FOR PROPOSAL TO THE NATIONAL SCIENCE FOUNDATION
PROGRAM ANNOUNCEMENT/SOLICITATION NO./CLOSING DATE/If not in response to a program announcement/solicitation enter NSF 00-2
FOR NSF USE ONLY
NSF PROPOSAL NUMBER
FOR CONSIDERATION BY NSF ORGANIZATIONAL UNIT(S) (Indicate the most specific unit known, i.e., program, division, etc.)
DATE RECEIVED
NUMBER OF COPIES
DIVISION ASSIGNED
EMPLOYER IDENTIFICATION NUMBER (EIN) OR
FUND CODE
DUNS # (Data Universal Numbering System)
SHOW PREVIOUS AWARD NO. IF THIS IS
FILE LOCATION
IS THIS PROPOSAL BEING SUBMITTED TO ANOTHER
FEDERAL
TAXPAYER IDENTIFICATION NUMBER (TIN)
A RENEWAL
000-00-0000
AN ACCOMPLISHMENT-BASED RENEWAL
AGENCY?
YES
NO
IF YES, LIST ACRONYM(S)
NAME OF ORGANIZATION TO WHICH AWARD SHOULD BE MADE
ADDRESS OF AWARDEE ORGANIZATION, INCLUDING 9 DIGIT ZIP CODE
Computer Productivity Initiative
E & CS Building
4700 Elkhorn Ave Suite 3300
Norfolk, VA 23529-0162
AWARDEE ORGANIZATION CODE (IF KNOWN)
NAME OF PERFORMING ORGANIZATION, IF DIFFERENT FROM ABOVE
ADDRESS OF PERFORMING ORGANIZATION, IF DIFFERENT, INCLUDING 9 DIGIT ZIP
CODE
PERFORMING ORGANIZATION CODE (IF KNOWN)
IS AWARDEE ORGANIZATION (Check All That Apply)
(See GPG II.D.1 For Definitions)
TITLE OF PROPOSED PROJECT
FOR-PROFIT ORGANIZATION
SMALL BUSINESS
MINORITY BUSINESS
WOMAN-OWNED BUSINESS
The Silencer
REQUESTED AMOUNT
PROPOSED DURATION (1-60 MONTHS)
REQUESTED STARTING DATE
6
December 19, 2007
SHOW RELATED PREPROPOSAL
NO.,
IF APPLICABLE
months
CHECK APPROPRIATE BOX(ES) IF THIS PROPOSAL INCLUDES ANY OF THE ITEMS LISTED BELOW
BEGINNING INVESTIGATOR (GPG I.A.3)
VERTEBRATE ANIMALS (GPG II.D.12) IACUC App. Date
DISCLOSURE OF LOBBYING ACTIVITIES (GPG II.D.1)
PROPRIETARY & PRIVILEGED INFORMATION (GPG I.B, II.D.7)
HUMAN SUBJECTS (GPG II.D.12)
Exemption Subsection
or IRB App. Date
NATIONAL ENVIRONMENTAL POLICY ACT (GPG II.D.10)
INTERNATIONAL COOPERATIVE ACTIVITIES: COUNTRY/COUNTRIES
HISTORIC PLACES (GPG II.D.10)
SMALL GRANT FOR EXPLOR. RESEARCH (SGER) (GPG II.D.12)
FACILITATION FOR SCIENTISTS/ENGINEERS WITH DISABILITIES (GPG
V.G.)RESEARCH OPPORTUNITY AWARD (GPG V.H)
PI/PD DEPARTMENT
PI/PD POSTAL ADDRESS
Computer Science
1234 Nokia Ave.
Norfolk, Va 23517
PI/PD FAX NUMBER
757-555-1234
NAMES (TYPED)
High Degree
Yr of Degree
Telephone Number
Electronic Mail Address
M.S.
1987
757-683-4832
blah@cs.odu.edu
PI/PD NAME
Brendan Geoghegan
CO-PI/PD
Page 5/84
CS 410 Red
SILENCER
7/26/2016
CERTIFICATION PAGE
Certification for Principal Investigators and Co-Principal Investigators
I certify to the best of my knowledge that:
(1) the statements herein (excluding scientific hypotheses and scientific opinions) are true and complete, and
(2) the text and graphics herein as well as any accompanying publications or other documents, unless otherwise indicated, are the original work of the
signatories or individuals working under their supervision. I agree to accept responsibility for the scientific conduct of the project and to provide the
required project reports if an award is made as a result of this proposal.
I understand that the willful provision of false information or concealing a material fact in this proposal or any other communication submitted to NSF is a
criminal offense (U.S.Code, Title 18, Section 1001).
Name (Typed)
PI/PD
Signature
Brendan Geoghegan
Social Security No.*
Date
000-00-0000
Co-PI/PD
000-00-0000
Certification for Authorized Organizational Representative or Individual Applicant
By signing and submitting this proposal, the individual applicant or the authorized official of the applicant institution is: (1) certifying that statements made herein
are true and complete to the best of his/her knowledge; and (2) agreeing to accept the obligation to comply with NSF award terms and conditions if an award is
made as a result of this application. Further, the applicant is hereby providing certifications regarding Federal debt status, debarment and suspension, drug-free
workplace, and lobbying activities (see below), as set forth in the Grant Proposal Guide (GPG), NSF 00-2. Willful provision of false information in this application
and its supporting documents or in reports required under an ensuing award is a criminal offense (U.S. Code, Title 18, Section 1001).
In addition, if the applicant institution employs more than fifty persons, the authorized official of the applicant institution is certifying that the institution has
implemented a written and enforced conflict of interest policy that is consistent with the provisions of Grant Policy Manual Section 510; that to the best of his/her
knowledge, all financial disclosures required by that conflict of interest policy have been made; and that all identified conflicts of interest will have been
satisfactorily managed, reduced or eliminated prior to the institution’s expenditure of any funds under the award, in accordance with the institution’s conflict of
interest policy. Conflicts that cannot be satisfactorily managed, reduced or eliminated must be disclosed to NSF.
Debt and Debarment Certifications
(If answer “yes” to either, please provide explanation.)
Is the organization delinquent on any Federal debt?
Is the organization or its principals presently debarred, suspended, proposed for debarment, declared ineligible,
or voluntarily excluded from covered transactions by any Federal Department or agency?
Yes
No
Yes
No
Certification Regarding Lobbying
This certification is required for an award of a Federal contract, grant or cooperative agreement exceeding $100,000 and for an award of a Federal loan or
a commitment providing for the United States to insure or guarantee a loan exceeding $150,000.
Certification for Contracts, Grants, Loans and Cooperative Agreements
The undersigned certifies, to the best of his or her knowledge and belief, that:
(1) No Federal appropriated funds have been paid or will be paid, by or on behalf of the undersigned, to any person for influencing or attempting to
influence an officer or employee of any agency, a Member of Congress, an officer or employee of Congress, or an employee of a Member of Congress in
connection with the awarding of any federal contract, the making of any Federal grant, the making of any Federal loan, the entering into of any cooperative
agreement, and the extension, continuation, renewal, amendment, or modification of any Federal contract, grant, loan, or cooperative agreement.
(2) If any funds other than Federal appropriated funds have been paid or will be paid to any person for influencing or attempting to influence an officer or
employee of any agency, a Member of Congress, and officer or employee of Congress, or an employee of a Member of Congress in connection with this
Federal contract, grant, loan, or cooperative agreement, the undersigned shall complete and submit Standard Form LLL, “Disclosure of Lobbying
Activities,” in accordance with its instructions.
(3) The undersigned shall require that the language of this certification be included in the award documents for all subawards at all tiers including
subcontracts, subgrants, and contracts under grants, loans, and cooperative agreements and that all subrecipients shall certify and disclose accordingly.
This certification is a material representation of fact upon which reliance was placed when this transaction was made or entered into. Submission of this
certification is a prerequisite for making or entering into this transaction imposed by Section 1352, Title 31, U.S. Code. Any person who fails to file the
required certification shall be subject to a civil penalty of not less than $10,000 and not more than $100,000 for each such failure.
AUTHORIZED ORGANIZATIONAL REPRESENTATIVE
NAME/TITLE (TYPED)
TELEPHONE NUMBER
SIGNATURE
ELECTRONIC MAIL ADDRESS
DATE
FAX NUMBER
*SUBMISSION OF SOCIAL SECURITY NUMBERS IS VOLUNTARY AND WILL NOT AFFECT THE ORGANIZATION’S ELIGIBILITY FOR AN AWARD. HOWEVER, THEY ARE AN
INTEGRAL PART OF THE NSF INFORMATION SYSTEM AND ASSIST IN PROCESSING THE PROPOSAL. SSN SOLICITED UNDER NSF ACT OF 1950, AS AMENDED.
Page 6/84
CS 410 Red
SILENCER
7/26/2016
2 Project Summary (Brendan)
Each year, 42,000 Americans die in automobile related accidents.1 Being distracted, while operating
one’s vehicle, is the number one cause in most of these accidents. Of all the drivers on the road, the
most inexperienced group is of course teenagers. This becomes quite an issue as surveys show that half
of these teenagers openly admit to texting or talking on cell phones while driving. The danger in this is
shown even more by the fact that the number one cause of death in teenagers is automobile accidents. 2
The government tries desperately to maintain a safe driving environment through traffic tickets and
new driving laws; however, the government can only do so much. In order to save lives effectively, it
should be the goal of the government to be preemptive but given America’s abundance of personal
freedoms it is a difficult task. The good news is that where the Government has failed, we will succeed.
Our product, the Silencer, will be the preemptive solution for the future.
2.1 Car Crash Statistics in the United States
(Brendan)
Car accidents are an everyday occurrence in this country and can occur anywhere. Highways, parking
1
http://www.nhtsa.dot.gov
2
http://www.statisticstop10.com/Causes_of_Death_Older_Teens.html
Page 7/84
CS 410 Red
SILENCER
7/26/2016
garages, side streets, and ever school parking lots are all susceptible to collisions. The following are just
some simple statistics to show the true scope of the problem we are dealing with.
 There were over 44,000 deaths related to auto accidents in 2006
– NHTSA
 78% of crashes involved a driver distracted within three seconds before an accident.
– NHTSA, 2006
 “If a driver's eyes are away from the roadway for two seconds or more in a six-second window,
their risk of being involved in a crash is two times higher than an alert driver,"
– Charlie Klauer, Virginia Tech Transportation Institute
2.2 Cell Phone Data for Car Crashes (Brendan)
Our project is focused on driving while using cell phones. For this reason it is important to have a
good understanding of just how dangerous and common cell phone usage while driving really is. We are
looking to deal with all aspects of phone usage from talking to texting and more. The overall summary
of what we have found relates that talking either on handset does not significantly reduce the danger of
cell phones. This is a good indicator that the conversation itself it’s a distraction rather than the device
being used. This is a little different from the danger of texting however, as the physical component of
typing on a phone is what becomes distracting.
 “85 percent of all cell phone customers talk on the phone while driving.”
Page 8/84
CS 410 Red
SILENCER
7/26/2016
– NTHSA
 “6 percent of auto accidents each year are caused by drivers talking on their phones.”
– Harvard Center for Risk Analysis
 “Talking on a cell phone while driving quadruples the chances of getting into a motor vehicle
accident.”
– New England Journal of Medicine
2.3 Focus on Teenagers (Brendan)
Teenagers have become our focus target for an array of reasons. Their inexperience in driving
combined with an increased likelihood to use phones while driving are just a couple of the reasons we
have chosen to target them. The fact is that teenagers can have things forced upon them by parents
more so than the government can force things on an average citizen. This leads to an array of
possibilities as our product would not normally be voluntarily used by the average person. The graph
below3 also gives a good idea as to why we are targeting teens.
3
http://www.statisticstop10.com/Causes_of_Death_Older_Teens.html
Page 9/84
CS 410 Red
SILENCER
7/26/2016
With nearly 40% of all teenage deaths being attributed to motor vehicle accidents it is obvious
something needs to be done.
2.4 Governments’ Response to Driving with
Cell Phones (Sam)
The government has begun responding to the danger of cell phone use while driving. Their
primary action has been imposing laws against using hand held phones while driving. In the following
diagram, states colored in red have already enacted laws making it illegal to use hand held cell phones
while driving. The states in yellow have partial bans, which can include many things. For example, a
partial ban could be only school bus drivers in that state. It could also mean there are laws that only
apply to novice drivers, such as drivers with a learner’s permit. The states in gray are considering a ban
on cell phone use but have not yet decided anything. Lastly, the states in blue have not yet formally
debated making hand held cell phone use illegal while driving.
Page 10/84
CS 410 Red
SILENCER
7/26/2016
The reason for these laws is justified by simply looking at the driver accident data that has been
collected in recent years. This data shows that cell phones are a major contributing factor towards
driver distraction, which is causing accidents. In fact, driver distraction is the leading cause of car
accidents. Unfortunately, these laws are not doing everything we need to stop the problem. This can be
seen clearly in Washington D.C., where there has been an increase in tickets given out each year for 3
years straight. The same rising trend in tickets given out for hand held cell phone use while driving also
exists in New York. A simple ticket is not going to stop this life-threatening problem.
There are going to be people that do not mind the extra expense of a ticket they got for driving while
using a hand held cell phone. There are also going to be people that are going to use it anyway when
they do not think there are any police officers around. However, the most dangerous group imaginable
Page 11/84
CS 410 Red
SILENCER
7/26/2016
is the drivers that are not only paying attention to their cell phone conversation more than the road, but
also looking all around for police officers. These people are going to be spending more time looking at
the cars behind them than the stopped car directly in front of them.
2.5 Silencer Solution Introduction (Brendan)
The Silencer will be designed to decrease the number of total
accidents related to cell phone usage while driving. The
Silencer will be unique when compared to any other
product out there because it will work directly with the cell
phones themselves. By utilizing the Bluetooth ability that
most phones come standard with, the Silencer will limit almost all functions of phones with the
designated software on them. With the exception of 911 calls, the Silencer will not allow any use of the
phone while in the vicinity of an included transmitter. Once in production, the Silencer will be the most
effective solution available on the market to this ever-growing problem.
Page 12/84
CS 410 Red
SILENCER
Page 13/84
7/26/2016
CS 410 Red
SILENCER
7/26/2016
3 Project Scope (Dylan)
This section will be about defining our customer and competition. By showing who we are selling to
and how we are better, this section will outline the general scope of the Silencer. The final part of this
section will be an overview of the WBS in defining how we want to progress as we build the Silencer.
3.1 Target Customers
The initial market of The Silencer will be the parents of teenagers who are just beginning to drive.
We initially plan to test the product by enrolling the help of some PTA’s, and even getting the schools
involved in order to test them on buses. However, our limited initial market does not prevent us from
expanding into other customer bases, such as businesses.
In 2005, the leading cause of worker death was auto accidents, and many large companies already
have at least a “hands-free” policy, such as General Motors’ policy that requires hands-free devices and
asks employees to avoid cell phone use in heavy traffic altogether. ExxonMobil and BP restrict cell
phone use while driving completely. Companies adopt these policies because plaintiffs have won cases
in the past against companies whose workers cause accidents while using the cell phone and driving.
Businesses are liable for employee negligence if there is no policy against that particular negligence. If
the company provides a cell phone, then the company can be held responsible even if the employee is
not officially on company business and involved in a cell phone related accident. Government agencies
have also adopted similar policies: the Washington Department of Labor and Industries prohibits the use
of electronic equipment and cell phones while driving on official state business.
Though our initial market is relatively small, specifically targeting parents of teenagers and high
schools, there is a large amount of room for growth into other markets. Our product can be used to help
enforce business policies for cell phone use. In a best-case scenario, states that have passed laws
regarding cell phone use in vehicles could require our product.
Page 14/84
CS 410 Red
SILENCER
7/26/2016
3.2 Competition
There are a few products that can be used to reduce the negative effects of cell phone use while
driving. Hands-free devices, such as Bluetooth earpieces, allow the driver to use the phone while still
being able to use both hands, however research has shown that the distraction of talking on the phone is
the cause of driver distraction and not the driver being unable to use their hands. Cell phone jammers
are an effective means of disabling cell phones, as they block outgoing and incoming calls and texts
without actively distracting the driver, however, these jammers are illegal in the United States and most
European countries.
A product called “Cell Coach” is designed specifically to target the use of cell phones by teens and
young adults while driving. This product does not disable or block incoming or outgoing calls, however.
Instead, it emits an “annoying sounds, similar to safety alerts given to aircraft pilots” whenever a cell
phone call is made or received in the car. The idea behind this product is that the sound will be so
annoying to the drivers that they will hang up the phone themselves. This product does nothing about
text messages being received, and the sound can possibly distract the driver and cause an accident.
There is no product currently on the market the actively prevents driver distraction without blocking
cell phone reception itself, which is illegal. Hands-free Bluetooth earpieces do not have a noticeable
improvement in driver performance over normal cell phone use. Cell phone jammers, while solving
some problems of driver distraction, are illegal. The Cell Coach does not actively block any functionality
of the phone, and could possibly cause additional driver distraction and agitation.
Page 15/84
CS 410 Red
SILENCER
7/26/2016
3.3 Innovation
Our product, The Silencer, is designed to send incoming calls and texts straight to voicemail, or the
inbox in the case of texts. The Silencer will be placed in the car and whenever a Bluetooth enabled
phone enters the car, The Silencer software will be put on the phone. Once a phone has the software,
The Silencer disables any activity on the phone, except an outgoing 911 call, whenever the car is turned
on. Though this may sound similar to jammers, The Silencer is a legal device because it does not prevent
any functionality or block calls from being received and instead simulates a phone that has been turned
off. Anything that is sent to the phone will be received but will be held in voicemail or the messages
inbox until the phone is reactivated by The Silencer. Our product does not cause any active distraction to
the driver, and at the same time prevents any cell phone from doing the same.
The Silencer is innovative for a number of reasons. In the future, all cell phones produced by major
cell phone companies such as Nokia will be Bluetooth enabled. This allows The Silencer to remain a
valid product for future phone products without having to change the format of the emitted signal.
Bluetooth also allows The Silencer to transmit the disabling software without having to depend on the
customer going to a website to download it. Each brand of cell phone does have a specific SDK for their
Page 16/84
CS 410 Red
SILENCER
7/26/2016
cell phone programs, however, with the ever-increasing size of memory becoming available in a smaller
physical size storing a number of different Silencer programs tailored to specific phone brands would not
be difficult to accomplish.
3.4 Evaluation Criteria
Development of the Silencer will be divided into four separate easily definable phases. Phase 0, the
first phase, is oriented around the project inception and planning. Phase 1’s goal is development of a
prototype of the product and refining the product. Phase 2 involves testing the prototype in real world
situations, alpha and beta testing, and finally organizing a manufacturing plan. Phase 3 is the out years
of the product, involving mass production, marketing, and maintenance of the product.
For Phase 0, the end goal is to receive SBIR funding to move on to the next phase. During this phase,
a number of different plans and documents are created in order to better explain our product and define
the need for our product in the current market.
In Phase 1, a working prototype is the end goal. More documents are creating during this phase and
deliverables are made, such as different milestones for the prototype. An example milestone for the
prototype would be for a Bluetooth connection to be established between two workstations, which can
be two computers or even a computer and a cell phone.
In Phase 2, testing the product in real world situations is goal. Alpha testing would most likely
involve in house testing of the product to make sure that it is in a workable state before moving on to
Beta. During Beta testing is when we would present the product to different schools and PTAs in order
to get a wide testing base. This phase would conclude once we have tested each of our test cases and
created a working product.
Phase 3, being the out years of the product, does not have a defined end. During this phase, mass
production of the production would occur, and success would be measured by the amount of profit
Page 17/84
CS 410 Red
SILENCER
made by marketing and selling the product.
Page 18/84
7/26/2016
CS 410 Red
SILENCER
7/26/2016
4 Project Impact (Reda)
This section summarizes the need to prevent and/or reduce teenager cell phone use while driving by
introducing The Silencer. In addition, it will highlight the different alternatives that are currently
available in the market and how The Silencer differs from them. Also, it will show the benefits offered by
The Silencer.
4.1 Customers’ Need for a Solution
Car crashes are the leading cause of teenage death in the United States. One of the main causes of
car crashes is driver distraction, and cell phone use while driving is nowadays one of the most
dangerous, if not the most dangerous kind, of driver distraction. The exact number of accidents caused
directly by hand-held cell phone use while driving is unknown because state troopers and city police did
not track and report it directly on accident reports, since people involved in accidents rarely confess that
they were using a handheld cell phone in the very few moments before the crash.
Many surveys show that teenagers do not mind talking on the phone and driving at the same time.
In addition, and even more dangerous, is the fact that they love text-messaging. They can read incoming
text messages and even reply to the received ones while driving, which is, in my personal point of view, a
lot more dangerous and scary than talking on their hand held cell phones. Moreover, their lack of driving
experience makes them even more likely to get into a crash if distracted while driving.
The government’s efforts to reduce cell phone use while driving has definitely failed; the laws
governing it were proven to be ineffective. The National Highway Traffic Safety Administration reported
that the number of traffic tickets issued for driving while operating a cell phone rose steadily in New
York and Rochester, for instance, since the ban in 2001. All in all, we need a better and more effective
solution, and our product: the Silencer, can make the difference, and keep drivers, especially teenagers,
safer.
Page 19/84
CS 410 Red
SILENCER
7/26/2016
4.2 Benefits
Our main goal and the best benefit of our product is the fact that it is going to make us safer and help
decrease the number of car accidents caused by cell phone use while driving, especially among
teenagers. While the car is running, only a call to 911 can be made in case of emergency, that is also a
benefit since this product is not only going to keep the driver safe by not allowing them to talk to their
cell phone while driving, but in the meantime, it allow them to communicate with 911 whenever they
have to. In addition the Silencer will provide peace of mind to parents because their teenage kids are not
being distracted while driving. When a parent calls their teenage son or daughter in order to check on
their safety, they can actually be putting their safety at risk. With the Silencer, there is no more need to
do that. The risk that a car crash can happen due to talking on their hand held cell phone, or due to text
messaging, is going to be reduced significantly.
Page 20/84
CS 410 Red
SILENCER
7/26/2016
5 Biographical Sketches (Reda)
This section will give a biography and general information about each of the members on our team
as well as the consultants we have asked to help and assist us in developing our product (the Silencer),
who are mainly part of the Old Dominion University Staff and faculty.
5.1 Senior Personnel
Senior Personnel consists of the six members of our team. We work together in phase 0 and 1 to develop
the prototype of the Silencer. Here you can find their biographies and some general information about each one
of us.
5.1.1
Brendan Geoghegan - Project Manager
Brendan is a senior at ODU going for a degree in Computer Science. He spent his first two years of
college at VMI where he won a NCAA conference title for diving. He is a midshipman in the United States
Navy and has had the privilege to travel to both Japan and Sweden within the past two years on military
orders. Once Brendan graduates he plans to commission as a Naval Flight Officer.
5.1.2 Donnie Goodson - Software and Web
Design
Donnie is an undergraduate Computer Science student at ODU with a minor in Business
Administration. He plans to graduate Fall 2008. Donnie transferred from Virginia Highlands Community
College where he earned an Associates degree in General Studies in 2006 and two Certificates in IT from
completing a FastTrack workforce training program in 2007. Donnie enjoys programming in Java and C++
and is also interested in Web Development. He has been a percussionist since middle school and enjoys
playing drums, marimbas, and other instruments when he has spare time.
Page 21/84
CS 410 Red
5.1.3
SILENCER
7/26/2016
Duc Nguyen - Lead Software Developer
Duc is an international student from Vietnam and has been in the US since 2003. He is a senior with a
major in Computer Science and a minor in Applied Math. He will graduate in December 2008. He is
currently working as a research assistant for Dr. Pothen where his primary task is to help develop
COLPACK, a graph coloring library to facilitate computation of vertex coloring for general and bipartite
graphs. Also, he has worked for System Group (2006) and did a summer internship in 2007 at Argonne
National Lab (IL). Duc likes to play chess and computer games during his leisure time. He won the Chess
District Champion 4 times when he was in school.
5.1.4 Dylan Wheeler - Marketing and
Documentation
Dylan is an undergraduate at Old Dominion University with a major in Computer Science and a minor
in Modeling and Simulation, with plans to graduate in the Spring of 2009. He has worked at a number of
companies involved in work related to his major, including a government contractor specializing in M &
S, and a web development business. His hobbies include martial arts (he is currently a Black Belt in
Hapkido and Taekwondo), playing guitar, reading, and sports.
5.1.5
Reda Elgourbi - Statistical Analyst
Reda is a senior undergraduate at ODU majoring in Computer science anticipating graduation in
spring 2009. He is originally from Morocco. He spent the first two years at Tidewater Community College
and got an associate degree in science-Computer science. Reda also used to play soccer professionally in
Morocco with RAJA Casablanca, one of the two best teams over there. He still plays here although not
professionally.
5.1.6
Samuel Shelor - Finance and Hardware
Samuel is a senior at Old Dominion University. He is majoring in Computer Science and minoring in
Page 22/84
CS 410 Red
SILENCER
7/26/2016
Computer Engineering. He plans to graduate in December 2008. In his free time, which is almost
nonexistent, he plays video/computer games.
Other Personnel – Consultants
Each one of our three consultants is a part of the Old Dominion University staff and faculty. We tried to get
their help, advices, and insight in developing the Silencer. Here you can find general information about each one
of them.
5.1.7
Dr. Stephan Olariu – Wireless Consultant
Dr Stephen Olariu is a world renown technologist in the areas of wireless networks, mobile
multimedia systems, parallel and distributed architectures, and networks. Much of his experience has
been with the design and implementation of robust protocols for wireless networks and in particular
sensor networks and their applications. Dr. Olariu received his PhD in computer science in 1986 from
McGill University, Montreal. He has been to more than 120 universities and research institutes around
the world lecturing on topics ranging from wireless networks and mobile computing to biology-inspired
algorithms and applications, to telemedicine, to wireless location systems, and security. Dr. Olariu is
currently the director of the Sensor Networks Research Group at Old Dominion University.
5.1.8
Dr. Michele C. Weigle - Wireless Consultant
Dr Michele C. Weigle's home town is St. Francisville, Louisiana, a beautiful small town on the banks
of the mighty Mississippi River. She received her PhD in computer science from the University of North
Carolina in August 2003 and has been an Assistant Professor at Old Dominion University since July 2006.
The courses she teaches here at ODU include CS 312-Internet Concepts, CS 455/555-Intro to Networks,
and CS 795/895-Vehicular Networks.
Page 23/84
CS 410 Red
SILENCER
5.1.9
7/26/2016
Dr. Steven J. Zeil - Software Consultant
Dr Steven Zeil is a key professor here at Old Dominion University’s department of Computer Science.
His research interests in the past have focused on testing and reliability measurement. More recently, he
has been focusing on issues in distance learning, especially web-delivery of course content.
6 Budget (Sam)
This section will encompass all financial plans and expenditures throughout the project phases.
6.1 Summary Proposal Budget – NSF Form
1030
FOR NSF USE ONLY
54
ORGANIZATION
SUMMARY PROPOSAL BUDGET
PROPOSAL NO.
DURATION (MONTHS)
Computer Productivity Initiative
Proposed
PRINCIPAL INVESTIGATOR/PROJECT DIRECTOR
Granted
AWARD NO.
Janet Brunelle
A. SENIOR PERSONNEL: PI/PD, Co-PIs, Faculty and Other Senior Associates
List each separately with name and title. (A.7. Show number in brackets)
NSF-Funded
Person-months
CAL ACAD SUMR
Funds
Funds
Requested By
Granted by NSF
Proposer
1.
2.
3.
4.
5.
6. (
) OTHERS (LIST INDIVIDUALLY ON BUDGET EXPLANATION PAGE)
7. (
) TOTAL SENIOR PERSONNEL (1-6)
B. OTHER PERSONNEL (SHOW NUMBERS IN BRACKETS)
1. (
) POSTDOCTORAL ASSOCIATES
2. (
) OTHER PROFESSIONALS (TECHNICIAN, PROGRAMMER, ETC.)
3. (
) GRADUATE STUDENTS
4. (
) UNDERGRADUATE STUDENTS
5. (
) SECRETARIAL - CLERICAL (IF CHARGED DIRECTLY)
6. (
) OTHER
TOTAL SALARIES AND WAGES (A + B)
C. FRINGE BENEFITS (IF CHARGED AS DIRECT COSTS)
TOTAL SALARIES, WAGES AND FRINGE BENEFITS (A + B + C)
D. EQUIPMENT (LIST ITEM AND DOLLAR AMOUNT FOR EACH ITEM EXCEEDING $5,000.)
$
TOTAL EQUIPMENT
E. TRAVEL
1. DOMESTIC (INCL. CANADA, MEXICO AND U.S. POSSESSIONS)
9,394
2. FOREIGN
F. PARTICIPANT SUPPORT
1. STIPENDS
$
2. TRAVEL
Page 24/84
(If Different)
$
70,110
70,110
70,110
CS 410 Red
SILENCER
7/26/2016
3. SUBSISTENCE
4. OTHER
TOTAL NUMBER OF PARTICIPANTS (
)
G. OTHER DIRECT COSTS
1. MATERIALS AND SUPPLIES
2. PUBLICATION/DOCUMENTATION/DISSEMINATION
3. CONSULTANT SERVICES
4. COMPUTER SERVICES
5. SUBAWARDS
TOTAL PARTICIPANT COSTS
6. OTHER
TOTAL OTHER DIRECT COSTS
H. TOTAL DIRECT COSTS (A THROUGH G)
I. INDIRECT COSTS (F&A) (SPECIFY RATE AND BASE)
79,504
TOTAL INDIRECT COSTS (F&A)
J. TOTAL DIRECT AND INDIRECT COSTS (H + I)
K. RESIDUAL FUNDS (IF FOR FURTHER SUPPORT OF CURRENT PROJECT SEE GPG II.D.7.j.)
L. AMOUNT OF THIS REQUEST (J) OR (J MINUS K)
79,504
$79,504
$
M. COST SHARING: PROPOSED LEVEL $
PI/PD TYPED NAME AND SIGNATURE*
AGREED LEVEL IF DIFFERENT: $
FOR NSF USE ONLY
DATE
ORG. REP. TYPED NAME & SIGNATURE*
DATE
NSF Form 1030 (10/99) Supersedes All Previous Editions
*SIGNATURES REQUIRED ONLY FOR REVISED BUDGET (GPG III.C)
INDIRECT COST RATE VERIFICATION
Date Checked Date of Rate Sheet
Initials-ORG
INSTRUCTIONS FOR USE OF SUMMARY PROPOSAL BUDGET
(NSF FORM 1030)
1. General
a. Each grant proposal, including requests for supplemental funding, must contain a Budget in this format unless a pertinent
program announcement/solicitation specifically provides otherwise. A Budget need not be submitted for incremental funding unless
the original grant letter did not indicate specific incremental funding or if adjustments to the planned increment exceeding the
greater of 10% or $10,000 are being requested.
b. Copies of NSF Form 1030 and instructions may be reproduced locally.
c. A separate form should be completed for each year of support requested. An additional form showing the cumulative budget
for the full term requested should be completed for proposals requesting more than one year's support. Identify each year's
request (e.g., "First year," or "Cumulative Budget," etc.) in the margin at the top right of the form.
d. Completion of this summary does not eliminate the need to document and justify the amounts requested in each category.
Such documentation should be provided on additional page(s) immediately following the budget in the proposal and should be
identified by line item. The documentation page(s) should be titled "Budget Justification."
e. If a revised budget is required by NSF, it must be signed and dated by the Authorized Organizational Representative and
Principal Investigator and submitted in at least the original and two copies.
2. Budget Line Items
A full discussion of the budget and the allowability of selected items of cost is contained in the Grant Proposal Guide (GPG), NSF
Grant Policy Manual (GPM) (NSF 95-26, periodically revised), and other NSF program announcements/solicitations. The following
is a brief outline of budget documentation requirements by line item. (NOTE: All documentation or justification required on the line
items below should be provided on the Budget Justification page(s).)
A., B., and C. Salaries, Wages and Fringe Benefits (GPM 611). See definitions in GPG Appendix C. List individually, all senior
personnel who were grouped under Part A, the requested person-months to be funded, and rates of pay.
D. Equipment (GPM 612). Items exceeding $5,000 and 1 year's useful life are defined as permanent equipment (unless lower
thresholds are established by the organization). List item and dollar amount for each item. Justify.
E. Travel (GPM 614 and GPM 760). Address the type and extent of travel and its relation to the project. Itemize by destination
and cost and justify travel outside the United States and its possessions, Puerto Rico, Canada and Mexico. Include dates of
foreign visits or meetings. Air fares are limited to round trip, jet-economy rates.
F. Participant Support (GPM 618). Normally, participant support costs only may be requested for grants supporting
conferences, workshops, symposia or training activities. Show number of participants in brackets. Consult GPG or specific
program announcement/solicitation for additional information.
Page 25/84
CS 410 Red
G.
SILENCER
7/26/2016
Other Direct Costs.
1. Materials and Supplies (GPM 613). Indicate types required and estimate costs.
2. Publication, Documentation and Dissemination (GPM 617). Estimate costs of documenting, preparing, publishing,
disseminating, and sharing research findings.
3.
Consultant Services (GPM 616). Indicate name, daily compensation (limited to individual's normal rate or daily rate paid
for Level IV of the Executive Schedule, whichever is less), and estimated days of service, and justify. Include travel costs,
if any.
4.
Computer Services (GPM 615). Include justification based on estimated computer service rates at the proposing
institution. Purchase of equipment should be included under D.
Sub awards (GPM 313). Also include a complete signed budget NSF Form 1030 for each subaward and justify details.
Other. Itemize and justify. Include computer equipment leasing and tuition remission. (GPG II.D.7.f and II.D.7.a.ii)
5.
6.
I. Indirect Costs (GPM 630) (Also known as Facilities and Administrative Costs for colleges and universities). Specify current
rate(s) and base(s). Use current rate(s) negotiated with the cognizant Federal negotiating agency. See GPM for special policy
regarding grants to individuals, travel grants, equipment grants, doctoral dissertation grants and grants involving participant support
costs (GPM, Chapter VI).
K. Residual Funds (GPG II.D.7.j). This line is used only for budgets for incremental funding requests on continuing grants.
Grantees should provide a rationale for residual funds in excess of 20% as part of the project report. (See GPG VII.G)
L. Amount of Request. Line L will be the same as Line J unless the Foundation disapproves the carryover of funds. If
disapproved, Line L will equal J minus K.
M. Cost Sharing (GPM 330). Include any specific cost sharing amounts in excess of the minimum one percent required under
unsolicited research proposals. Include the estimated value of any in-kind contributions. Discuss the source, nature, amount and
availability of any proposed cost sharing on the Budget Justification page. If a proposal budget includes a specific cost sharing
level, the identified cost sharing level is expected to be included as a requirement in the award.
PROPOSERS MUST NOT ALTER OR REARRANGE THE COST CATEGORIES AS THEY APPEAR ON THIS FORM, WHICH
HAS BEEN DESIGNED FOR COMPATIBILITY WITH DATA CAPTURE BY NSF'S MANAGEMENT INFORMATION SYSTEM.
IMPROPER COMPLETION OF THIS FORM MAY RESULT IN RETURN OF PROPOSAL.
Page 26/84
CS 410 Red
SILENCER
7/26/2016
6.2 Salaries and Wages
The employees we will need and how long we will need them has been determined by the Work
Breakdown Structure. The salaries we are using for estimates have come from information gathered
from the Bureau of Labor Statistics. The 40% overhead cost we are adding to each employee is an
estimate based on typical overhead for an employee. This overhead includes additional expenses like
health insurance, vacation time, sick time, workmen’s comp, and pension plans.
Personnel
Job Title
Qty
1
1
2
Yearly
Salary
$65,190
$48,849
$75,340
Yearly w/
Overhead
$91,266
$68,389
$105,476
Hourly
Salary
$43.88
$32.88
$50.71
Duration
(days)
91
24
30
Technical Writer
Web Designer
Software
Developer
Computer
Hardware
Engineer
Total
Cost
$31,944.60
$6,312.60
$24,340.80
1
$93,010
$130,214
$62.60
15
$7,512.00
$70,110
6.3 Equipment
The hardware we will need during phase 1 consists primarily of computers for the initial staff to
do their work on. In addition to these workstations, we will also need test phones for each of the
mobile application developers. These phones need to be Nokia cell phones because Nokia is the most
common brand of cell phone on the market currently.
Hardware
Item
Nokia 6085
Dell XPS M1530
Total
Qty
2
6
Page 27/84
Cost
$400
$9,000
$9,400
CS 410 Red
SILENCER
7/26/2016
7 Facilities, Equipment, and Other Resources
(Sam)
This section will outline the things we will need to have and acquire in this project. This includes
Office space, SDKs, Bluetooth sensors and more.
7.1 Facilities
Since most of our team is located at Old Dominion University in Norfolk, VA, this is where our
meetings will be held. However, more specifically, we will be meeting in one of the conference rooms
on the 3rd floor of the Engineering and Computational Sciences building. These rooms have a great deal
of helpful technical equipment. For our team member not located in Norfolk, VA, we will set up a live
bidirectional video/audio feed to assist with the communication process.
Two more facilities our team will be taking advantage of at ODU are the computer labs, which are
available to students taking Computer Science courses. The computers in these labs have most of the
software we will be using for this project, as well as a fast Internet connection.
7.2 Location
Department Of Computer Science
Engineering & Computational Science Bldg,
4700 Elkhorn Ave, Suite 3300,
Norfolk, VA 23529-0162
7.3 Software
A lot of the software we will need is available with the lab computers at ODU. For example,
Microsoft Word for the documentation. For our prototype we will be using 2 Bluetooth enabled laptops.
Page 28/84
CS 410 Red
SILENCER
7/26/2016
These 2 laptops will be coded with interacting software using a familiar coding language, such as C++.
We can write this C++ code using a free compiler or a compiler on the lab computers. As far as the
actual development, we will eventually need the cell phone SDK, and possibility some way of writing
native code for the cell phone. We may also need some Windows software to emulate the phone for
quick testing.
7.4 Hard Resource
During the prototyping phase, our hardware will be one laptop acting as the Silencer and another
laptop acting as the cell phone with Silencer software. After this initial prototype we will need
additional hardware to continue the development of our product. We will need a Nokia cell phone to
load our software onto. We will also need a Bluetooth transmitter; this must be integrated with a circuit
with storage for software to transmit to the cell phone.
Page 29/84
CS 410 Red
SILENCER
7/26/2016
8 Reference (Dylan)
 AT&T. February 1, 2008. <http://www.att.com/>.
 Autozone . February 1, 2008. <http://www.autozone.com/>.
 BestBuy. February 1, 2008. <http://www.bestbuy.com/>.
 "Bluetooth 2005 Future Trends and Opportunities in the Worldwide Market." Context World.
October 2004. February 1, 2008.
<http://www.contextworld.com/SpecialReportsBluetooth.html>.
 “Leading causes of death in the United States - older teenagers.” Statistics Top 10 – Death
Statistics. March 7, 2005. February 1, 2008.
<http://www.statisticstop10.com/Causes_of_Death_Older_Teens.html>.
 Circuit City. February 1, 2008. <http://www.circuitcity.com/>.
 GoDaddy. Economy Plan. February 1, 2008. <http://www.godaddy.com/>.
 “IDC Finds Slower Growth in the Mobile Phone Market in 2007”. IDC. 25 Jan. 2008.
<http://www.idc.com/>.
 Lowes. February 1, 2008. <http://www.lowes.com/>.
 Laura Bruno. “Stop text messaging, drivers urged.” USA Today. February 1, 2008.
<http://www.usatoday.com/news/nation/2007-06-11-dwt_N.htm>.
 National Highway Traffic Safety Administration (NHTSA). February 1, 2008.
<http://www.nhtsa.dot.gov/>.
 "Nokia Predicts Increase in Sales of Bluetooth Cell Phones." Telecommunications Industry News.
5 Jan. 2006. February 1, 2008. <http://www.teleclick.ca/>.
 Office Depot. February 1, 2008. <http://www.officedepot.com/>.
Page 30/84
CS 410 Red
SILENCER
 Top 10 Hosting List. 4 March 2008. <http://www.top10hostinglist.com/>.
Page 31/84
7/26/2016
CS 410 Red
SILENCER
7/26/2016
9 Appendices
9.1 Management Plan (Brendan)
9.1.1
Program Identification
This Program Management Plan (PMP) is for the Silencer system for ensuring that no teenager causes
an accident because of cell phone usage. The program will deliver the Silencer software, hardware, and
documentation for both. The Silencer Project Team (SPT) is responsible for the integration, acceptance
testing and training of the Total Computing Environment.
9.1.1.1
Program Management Overview
Execution of the Program will be performed in accordance with the procedures defined by the set of
planning documents. These documents include Program Management Plan*, Development Plan,
Evaluation Plan, Marketing Plan, Staffing Plan, Financial Plan, Resource Plan, and Risk Management Plan
(RMP) (see Figure 1). The responsibilities of the Program Team, the capabilities of the system, and the
Program deliverables are detailed under the contractual provisions, as well as SPT’s technical,
management, and cost proposals.
* This Program Management Plan shall be deemed to meet the contractual requirement of a Project
Management Plan.
Page 32/84
CS 410 Red
SILENCER
7/26/2016
Management
Plan
Marketing Plan
Staffing Plan
Funding Plan
Work Breakdown
Structure
Risk Management Plan
Evaluation Plan
Figure 1. Program Management
This Program Management Plan describes the management philosophy, program organization,
schedule, and major milestones that serve as the guide for execution of the Program. The PMP also
provides the customer and the quality team with the information they need to monitor and evaluate the
progress of the effort. This plan provides the following pertinent information:
 Corporate Organization
 Program Team Organization With Areas of Responsibility
 Work Breakdown Structure
 Program Planning
o Progress Reporting and Team Management
o Detailed Program Schedule and Milestones
o Program Reviews
The Program Management Plan provides guidance for the content and execution of the following
plans:

Risk Management
Page 33/84
CS 410 Red
SILENCER

Financial

Evaluation

Development
9.1.1.2
7/26/2016
Corporate Structure
The entirety of Computer Productivity Initiative supports the Silencer Project Team. In 1995, Old
Dominion University started the Computer Productivity Initiative from a grant by the National Science
Foundation to give Computer Science students the opportunity to develop solutions to real world
problems. The Silencer Project Team formed in the spring semester of 2008. The team will either be
directly involved in the development process of Silencer service or outsource responsibilities on a
contract basis. The following is the SPT’s organizational structure:
 Consultant – Janet Brunelle, Old Dominion University
 Project Manager – Brendan Geoghegan
 Silencer Program Office – The Silencer Program Office will execute the program and
provide day-to-day senior management supervision, management, engineering, and
administrative resources necessary to manage and administer the Silencer service.
9.1.1.3
Management Approach
The Silencer’s management goal is to work closely with the customer to fully understand the system
requirements and field a system that meets those requirements. The management approach to
executing contracts at Silencer is based on the philosophy that successful Programs are delivered by
goal-oriented teams. A Program Manager (PM) will lead the SPT. The PM is responsible for all planning,
programmatic, technical, and financial aspects of the Program. The PM is the primary Point of Contact
(POC) for the customer. The primary duties include supervision of all planning, scheduling, financial, and
technical activities, and customer liaison. The PM is responsible for all Program-related decisions and
Page 34/84
CS 410 Red
SILENCER
7/26/2016
commitments with approval, as required, from the Corporate Management Team.
A key element of the Silencer’s program management approach is customer involvement. The
Silencer group desires the customer to retain an active role in monitoring the progress of all aspects of
the program. The customer is encouraged to discuss technical details directly with members of the
Program team, provide planning and schedule recommendations, and assist in resolution of technical
and programmatic issues. In order to facilitate customer involvement, the SPT will provide access to
program information including, but not limited to:

Program Plans and Schedules

Program Status

Formal Review Material

Action Items

System Drawings and Documentation
9.1.1.4
Program Team
The Program Team is committed to provide the best value by delivering COTS, open architecture, and
low-risk systems at the lowest cost. This commitment is attainable because it is based on the re-use of
existing technology that is field-proven. Through strategic teaming and an extensive system selection
process, Computer Productivity Initiative has assembled a cohesive Program Team that is experienced
with the implementation of each component that will comprise the Silencer system.
Program Manager. Overall management responsibility for the Silencer is assigned to a Program
Manager who is responsible for planning and coordination of the day-to-day technical, contractual, and
financial aspects of the program. He is responsible for the generation and management of all program
schedules, for the coordination of program staff assignments and for coordinating all program activities.
His principal assistants are:
Page 35/84
CS 410 Red
SILENCER
7/26/2016
 Hardware Specialist. The HS is responsible for system-level activities to ensure system
hardware meets the specification requirements. The HS is also responsible for the development of
system specifications, system design documents, interface documents, test plans, and procedures.
 Software Specialist. The SS is responsible for the development of system software
functions as defined in the system specifications. The SS is also responsible for integration of all
system components to meet the performance requirements of the system.
 Documentation Specialist. The DS provides overall documentation direction for the
Program Team. The DS will ensure that everyone on the team has met the required documentation
specifications, and that each person is aware of the tasks he/she has been assigned. The DS will also
provide documentation of each meeting in which an overview of tasks assigned is given.
 Financial Manager. The FM works in coordination with the rest of the team to devise a
specific and schedule based budget plan, that will be reviewed by each of the team members and
approved by both the PM and the customer. The FM will also determine the best agency to pursue
to get funding for the project.
 Marketing Director. The MD is responsible for developing a marketing plan that includes
the specification of an initial target market. The MS is responsible for the development of an indepth plan on how to advertise and sell the Silencer to the specified target market. The MD must
also determine the various risks involved and the best way to mitigate them.
 Web Developer. The WD is responsible for the creation and maintenance of a product
website which will include the display of all relevant documents and presentations. The WD will
update the website as needed.
 Statistical Analyst. The SA is responsible for researching the problem area, project risks,
major competitors, and societal effects of solution integration.
Page 36/84
CS 410 Red
SILENCER
9.1.1.5
7/26/2016
Program Duration
The Silencer is a 3-year project that will culminate in the rollout of a reliable product that will save
lives. Although an initial prerelease is planned to get a read on the market, full production is planned for
the summer of 2011.
9.1.2
Work Breakdown Structure
The program Work Breakdown Structure (WBS) reflects the budgeted cost versus resources required
to complete each task. The WBS phase numbers are integrated as part of the master program schedule.
Assuming SBIR funding, the budget will be carefully planned out against the set deadlines set by SBIR
guidelines. The budget will be carefully planned out against the set deadlines set by SBIR guidelines. The
budgets are created by the Financial Manager, reviewed by the Silencer Project Team, and set by the
Program Manager. The WBS will be used to mark the different milestones throughout the phases and to
make sure that the team in on time and on budget. The WBS management tool that the Silencer Project
Team will use is Microsoft Project 2003.
9.1.3
Program Planning
The Silencer Project Team office will maintain the program master schedule. The master schedule
contains a line item for each WBS element and will be used to track the progress of each element. All
deviations from the master schedule must be coordinated with the program office. It is the responsibility
of each team member to call attention to possible schedule deviations at the earliest opportunity. The
program office will coordinate the program schedule with Computer Productivity Initiative. The program
will be developed in phases; within each phase, formal reviews will play an integral part in monitoring
program progress. All formal reviews will be announced four weeks in advance of the starting date. The
SPT will take a “top down approach” to the Program Schedule, meaning that we will pace our workload
to fit the overall Program requirements. Particular attention will be given to timely milestone
Page 37/84
CS 410 Red
SILENCER
7/26/2016
completions. It is recognized that the schedule is particularly tight, containing critical program
milestones during the first year, and adequate personnel will be available in order to keep the program
moving forward.
9.1.4
Progress Performance Assessment
All SPT members will participate in progress reporting and team management. The Silencer will track
technical and financial progress of the program. Reviews will be held monthly or as mutually agreeable
between Computer Productivity Initiative and the Silencer Project Team.
 Report on progress to date
 Present work to be performed during the next month
 Present status of all deliverables and review planned delivery dates
 Plan and coordinate activities, including the new review date.
 Discuss technical or programmatic issues as necessary.
In preparation for the meetings, the Program Manager will collect the status data on relevant ongoing activities, progress against schedule and budget, and planned activity for the next reporting
period. Quality reviews of all program documentation and procedures will be held periodically. In
particular, the quality program will be involved with program deliveries and milestones and will work off
the master program schedule to plan program audits. Technical, financial, and quality progress and
status reporting will be conducted according to the following general guidelines.
9.1.4.1
Technical Progress and Reporting
The schedule for the program is established during the planning phase and monitored throughout
the performance period. The schedule contains an entry for each WBS element. The percentage of
completion for each WBS element is determined as necessary to manage program progress and is
Page 38/84
CS 410 Red
SILENCER
7/26/2016
reviewed at least quarterly during the General Manager’s review.
9.1.4.2
Financial Management and Reporting
The financial profile for the Program is established during the planning phase and monitored
throughout the performance period. This profile is generated by assigning accounting phase numbers to
every Program activity that has been identified as a scheduled event. A budget representing labor costs,
materials purchase, and other expenditures (such as travel expenses) is then prepared for every phase.
The schedule and budgets are then integrated to provide a spending profile for the phase. The Program
spending profile represents a summary of phase spending profiles.
The PM is provided an information package that identifies the phase numbers assigned to each
activity, the corresponding budgets and schedules, the overall spending profile for the program, and a
synopsis of all major deliverables and milestones specified in the contract. The PM uses this information,
combined with an on-line financial summary of the Program to track its financial status on a weekly
basis. An updated spending profile is provided automatically by the Contracts Administrator on a
monthly basis, or upon request from the PM. The PM uses the financial summary in conjunction with his
assessments of technical progress to track the overall status of the efforts (please see the Financial Plan
for more information).
9.1.4.3
Earned Value
Earned Value Ratios will be reported as required. At a minimum, the SPT will determine earned value
quarterly at the overall Program level and will report at the second level of WBS indenture in order to
provide additional information. The SPT will use Microsoft Project Program Manager Software in order
to calculate the ratios. Please refer to the Financial Appendix for more information.
Page 39/84
CS 410 Red
SILENCER
9.1.4.4
7/26/2016
Quality Process and Reporting
Quality management on the program will be a team effort. The Project Manager will coordinate
conduct, quality reviews, and audits. The PM is ultimately responsible for the development and
implementation of the System Quality Program Plan. The SQPP is an umbrella plan that incorporates the
quality programs of the program team members. The SQPP describes a team quality concept, including
Process Coordination and Quality Evaluators. Team members are responsible for performing the
processes required to complete Program tasks. Quality Evaluators are responsible for verifying that the
development, production, and handling of all documentation, software, and hardware are performed in
accordance with the SQPP and its component processes. The team is also responsible for conducting
periodic reviews and evaluations of work in process attending in house test events and supporting in
house Program reviews. All planned quality program activities and quality evaluations (internal audits)
are submitted to the PM for review. See the Evaluation Plan for more details.
9.1.4.5
Monthly Progress Report
The SPT will submit monthly progress reports. The report shall cover, at a minimum, the following:

Progress Summary;

The variance statement;

Critical Path Analysis;

Milestone Deliverables, planned actual and forecast;

Earned Value Schedule and Cost Performance Indices;

Dependencies: a ‘critical items list’ of all items, whether or not the Contractor’s
direct responsibility, which could jeopardize timely completion of the work or any
significant parts of the program;

Risk Status: update of risk register;
Page 40/84
CS 410 Red
SILENCER

Look Ahead (Future action and Forecast);

Resource Profile;

Work Package/Activities planned, actual & forecast status;

Milestone/Deliverables planned, actual & forecast status;

Configuration Change Control issues;
9.1.5
7/26/2016
Reviews
Reviews will play an integral part in the management and monitoring of all phases of the SPT.
Informal reviews with the program team members will be held at all levels on a weekly basis to ensure
that the program stays on track. Formal technical reviews will be held to ensure that the program is
proceeding as planned. The types of reviews, their purpose, and presented information are addressed in
the following paragraphs.
9.1.5.1
Program Management Reviews
Program Management Reviews (PMRs) will be conducted with SPT and subcontract representatives.
The first PMR will be conducted in August 2008; thereafter PMRs will be conducted approximately twice
weekly. The PMRs are scheduled to discuss programmatic issues related to the development and
implementation of the project. The reviews will provide the opportunity to review the progress of the
effort; as well as to conduct milestone reviews of deliverables, and identifies and resolves any issues that
may arise during the execution of the tasking. The PM will ensure that all program related information
required to meet the objectives of the review are prepared and delivered no later than the night prior to
the scheduled review date. The PM will also be responsible for identifying the SPT personnel who will
attend the review. The PM will attend all Program Management Reviews. The following information will
be prepared in support of each PMR. Recorded during the review and delivered before the completion of
the review.
Page 41/84
CS 410 Red
SILENCER
9.1.5.2
7/26/2016
Technical Reviews
Formal technical reviews will be conducted on the dates specified in the master schedule. The
reviews will be held jointly with the Silencer Project Team, Program Team members, and sub-suppliers as
necessary. An agenda and review material will be submitted to SPT two weeks prior to the scheduled
meeting. Review meeting minutes will be delivered before the completion of the review. The objectives
for each review are outlined below (please see the Technical Plan for more information).
Reviews will be held to validate the direction taken for the design, development, and test of the
system. The System Requirements Review (SRR), Preliminary Design Review (PDR), and Critical Design
Review (CDR) will be formal reviews held at SPT’s facility. The Test Readiness Reviews (TRR) will be
formal reviews completed before completion of each phase.
System Requirements Review is conducted to ensure that the Program team fully
understands the system performance requirements specified in the System/Segment Specification. A
detailed review of requirements for the system and each subsystem will be reviewed. The
System/Segment Specification (Technical Specification) will be used in the review.
System Design Review is conducted to present and review the system design. System
requirement allocation to each system component will be discussed. The general approach to be taken
for the integration of each system component will be presented. The documents listed below will be
used in the review. This will be an informal review. The data will be included in the PDR.
 System/Segment Design Document
 System Interface Design Document
Software Requirements Review is conducted to review the software specification and
interface requirement specifications. This review will be conducted as part of the PDR.
Preliminary Design Review is conducted to present the preliminary design of the Program
Page 42/84
CS 410 Red
SILENCER
7/26/2016
System. The functional requirements of each subsystem will be discussed in detail. The following
documents will be used in the review:
Critical Design Review is conducted to review system integration issues. In particular, the
review will focus on system interfaces in preparation for Subsystem FAT.
Test Readiness Review is held to determine if the system is ready to proceed to the next
level of test. Test configurations and results from the previous test efforts will be presented. The test
report from the previous test will be used in the review.
9.1.5.3
Quality Reviews
The PM supported by the Project Manager (PM) will establish the time and identify attendees for all
formal reviews. He will also coordinate with the appropriate managers to conduct quality reviews at key
program milestones, and in preparation for formal reviews with the customer. Informal peer review and
engineering planning meetings will also be held at the discretion of each subsystem manager to discuss
technical issues, conduct internal comment reviews, and provide technical guidance to members of the
Program team (please see the Evaluation Plan for more information). As part of the quality activities for
the program, the quality team will conduct informal reviews to:
 Evaluate the processes used by the Program team members to program tasks;
 Evaluate deliverable products for compliance with contract requirements;
 Evaluate work-in-process during engineering reviews;
 Document results of each evaluation; and recommend corrective and preventive actions if necessary.
Page 43/84
CS 410 Red
SILENCER
7/26/2016
9.2 Marketing Plan (Dylan)
This section will outline the marketing plan for The Silencer. The target market, initial audience for the
prototype, and potential future markets will be discussed, as well as methods that can be used to get our
product out to the public.
9.2.1
Market Analysis
Car crashes are the leading cause of death for people aged 15 to 20, and younger drivers are three
times more likely to die in a crash as those 25 and older. In fact, the younger the driver, the more likely
an accident can occur: the crash rate for 16 year olds per million miles is three times as high as 19 year
olds, and nearly six times as high as 20 to 24 year olds. To go along with these frightening statistics, a
2007 survey by Nationwide Mutual Insurance found that 73% of people talk on cell phones while driving,
and that cell phone use was highest among younger drivers. The same survey also showed that 19% of
motorists say they send and receive text messages while driving. Cell phone use while driving
quadruples the risk of a serious crash, and slows reaction time by 20%.
There are a few products that can be used to reduce the negative effects of cell phone use while
driving. Hands-free devices, such as Bluetooth earpieces, allow the driver to use the phone while still
being able to use both hands, however research has shown that the distraction of talking on the phone is
the cause of driver distraction, not the driver being unable to use their hands. Cell phone jammers are
an effective means of disabling cell phones, as they block outgoing and incoming calls and texts without
actively distracting the driver, however these jammers are illegal in the United States and most European
countries.
A product called “Cell Coach” is designed specifically to target the use of cell phones by teens and
young adults while driving. This product, however, does not disable or block incoming or outgoing calls.
Instead it emits an “annoying sound, similar to safety alerts given to aircraft pilots” whenever a cell
Page 44/84
CS 410 Red
SILENCER
7/26/2016
phone call is made or received in the car. The idea behind this product is that the sound will be so
annoying to drivers that they will hang up the phone themselves.
Our product, The Silencer, is designed to send incoming calls and texts straight to voicemail, or the
inbox in the case of texts. The Silencer will be placed in the car and whenever a Bluetooth enabled
phone enters the car, The Silencer software will be put on the phone. Once a phone has the software,
The Silencer disables any activity on the phone, except an outgoing 911 call, whenever the car is turned
on. Though this may sound similar to jammers, The Silencer is a legal device because it does not prevent
any functionality, it instead simulates a phone that has been turned off. Anything that is sent to the
phone will be received, but will be held in voicemail or the messages inbox until the phone is reactivated
by The Silencer. Our product does not cause any active distraction to the driver, and at the same time
prevents any cell phone use from doing the same.
9.2.2
Target Market
The initial market of The Silencer will be the parents of teenagers who are just beginning to drive.
We initially plan to test the product by enrolling the help of some PTA’s, and even getting the schools
involved in order to test them on buses. However, our limited initial market does not prevent us from
expanding into other customer bases, such as businesses.
In 2005, the leading cause of worker death was auto accidents, and many large companies already
have at least a “hands-free” policy, such as General Motors’ policy that requires hands-free devices and
asks employees to avoid cell phone use in heavy traffic altogether. In fact, ExxonMobil and BP restrict
cell phone use while driving completely. Companies adopt these policies because plaintiffs have won
cases in the past against companies whose workers cause accidents while using the cell phone and
driving, since companies are liable for employee negligence is there is no policy against that particular
negligence. If the company provides a cell phone, then the company can be held responsible even if the
Page 45/84
CS 410 Red
SILENCER
7/26/2016
employee is not officially on company business and involved in an accident. Government agencies have
also adopted similar polices: the Washington Department of Labor and Industries prohibits the use of
electronic equipment and cell phones while driving on official state business.
9.2.3
Sales Plan
Since The Silencer has such a large potential customer base, there are a number of options for selling
the product. Because of the way The Silencer has to be installed, it can be sold in a store such as Best
Buy and installed by the store’s staff, in a similar manner to a car radio. However, since it will be
possible for mechanically proficient people to install it themselves, we can also offer the product
through a website with an extra cost of shipping and handling.
During the testing phase of the product, we will be able to give test products to schools in order to
distribute them to parents during PTA meetings, and we could convince the school to test them in their
buses as well. We could also have applications for test products on our website.
9.2.4
Advertising Strategy
Our product can be advertised through schools, similar to our testing phase. Once testing is finished,
we would be able to sell the product through the school or directly to parents. Since cell phone use
while driving is becoming a more prominent threat to safety while driving, local news agencies may
want to run stories about the product in order to inform their viewers about possible ways to improve
safety in vehicles. Business may also want to adopt this product as a way to enforce their cell phone use
policies in company cars.
Page 46/84
CS 410 Red
SILENCER
7/26/2016
9.3 Staffing Plan (Donnie)
This document defines the staffing requirements for each phase. This document describes the titles
and roles of the staff that will be needed. A detailed list of all tasks per team member is available in the
Appendix.
9.3.1
Phase 0
During this phase, the product team will consist of six students in the Computer Science department
at Old Dominion University. The students will also seek outside sources as needed to assist in the
research and idea development. These consultants and the students will not be paid for their work.
Diagram – Phase 0 Staffing Plan
9.3.1.1
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate team
member communications. The project manager also must assist in the development of the WBS, assign
resources, prioritize tasks, and define task dependencies.
9.3.1.2
Software Specialist
The responsibilities include identifying the software needed for the Silencer service, estimating costs,
Page 47/84
CS 410 Red
SILENCER
7/26/2016
and determining the best methods for developing or attaining the components.
9.3.1.3
Web Design Specialist
The responsibilities include creating and maintaining the team and product websites, as well as
managing additional web developers in future phases.
9.3.1.4
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects of
the project. The marketing specialist will determine the overall marketing plan.
9.3.1.5
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
9.3.1.6
Finance Specialist
The responsibilities include receiving funding, creating the budget, and determining the product cost.
The financial specialist is responsible for the financial and funding plans.
9.3.1.7
Hardware Specialist
The responsibilities include identifying the hardware needed for the Silencer system, estimating
costs, and determining the best methods for developing or attaining the components.
9.3.1.8
Statistical Analyst
The responsibilities include researching the problem area, project risks, major competitors, and
societal effects of solution integration.
Page 48/84
CS 410 Red
SILENCER
9.3.2
7/26/2016
Phase 1: Proof of Concept
In this phase a lab prototype will be developed and the SBIR Phase 2 proposal will be developed.
Success will be measured by the successful completion of those two deliverables.
The following staff will be needed in Phase 1 of this project:
Diagram – Phase 1 Staffing Plan
9.3.2.1
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate team
member communications. The project manager also must assist in the development of the WBS, assign
resources, prioritize tasks, and define task dependencies.
9.3.2.2
Software Specialist
The responsibilities include identifying the software needed for the Silencer service, estimating costs,
and determining the best methods for developing or attaining the components.
Page 49/84
CS 410 Red
SILENCER
9.3.2.3
7/26/2016
Web Design Specialist
The responsibilities include creating and maintaining the team and product websites, as well as
managing additional web developers in future phases.
9.3.2.4
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects of
the project. The marketing specialist will determine the overall marketing plan.
9.3.2.5
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
9.3.2.6
Finance Specialist
The responsibilities include receiving funding, creating the budget, and determining the product cost.
The financial specialist is responsible for the financial and funding plans.
9.3.2.7
Hardware Specialist
The responsibilities include identifying the hardware needed for the Silencer system, estimating
costs, and determining the best methods for developing or attaining the components.
9.3.2.8
Statistical Analyst
The responsibilities include researching the problem area, project risks, major competitors, and
societal effects of solution integration.
9.3.2.9
Software Design Expert
The responsibilities include providing professional opinions on how best to solve problems
encountered in the development and testing of the software behind the Silencer system.
Page 50/84
CS 410 Red
SILENCER
9.3.2.10
7/26/2016
Wireless Expert
The responsibilities include providing expert opinions on purchasing wireless hardware, as well as on
how best to solve problems encountered in the testing of all hardware, both individually and as a
complete system.
Phase 1 Staffing Budget
Job Title
Technical
Writer
Web Designer
Software
Developer
Computer
Hardware
Engineer
Total
Qty Yearly
Salary
1
$65,190
Yearly w/
Overhead
$91,266
Hourly Duration
Salary (days)
$43.88 91
Cost
1
2
$48,849
$75,340
$68,389
$105,476
$32.88
$50.71
24
30
$6,312.60
$24,340.80
1
$93,010
$130,214
$62.60
15
$7,512.00
$31,944.64
$70,110.04
Page 51/84
CS 410 Red
SILENCER
9.3.3
7/26/2016
Phase 2: Critical Design
In this phase, the actual prototype of the product will be developed.
The following staff will be needed in Phase 2 of this project:
Diagram – Phase 2 Staffing Plan
9.3.3.1
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate team
member communications. The project manager also must assist in the development of the WBS, assign
resources, prioritize tasks, and define task dependencies.
9.3.3.2
Software Specialist
The responsibilities include identifying the software needed for the Silencer service, estimating costs,
and determining the best methods for developing or attaining the components.
9.3.3.3
Web Design Specialist
The responsibilities include creating and maintaining the team and product websites, as well as
Page 52/84
CS 410 Red
SILENCER
7/26/2016
managing additional web developers in future phases.
9.3.3.4
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects of
the project. The marketing specialist will determine the overall marketing plan.
9.3.3.5
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
9.3.3.6
Finance Specialist
The responsibilities include receiving funding, creating the budget, and determining the product cost.
The financial specialist is responsible for the financial and funding plans.
9.3.3.7
Hardware Specialist
The responsibilities include identifying the hardware needed for the Silencer system, estimating
costs, and determining the best methods for developing or attaining the components.
9.3.3.8
Statistical Analyst
The responsibilities include researching the problem area, project risks, major competitors, and
societal effects of solution integration.
9.3.3.9
Web Developer
The responsibilities include creating, modifying, and maintaining the project web site as directed by
the Web Design Specialist.
9.3.3.10
Software Tester
The responsibilities include testing Silencer software in both a prototype simulation environment as
well as final host product environments.
Page 53/84
CS 410 Red
SILENCER
9.3.3.11
7/26/2016
Website Tester
The responsibilities include verifying all areas of the project web site work as expected and produce
accurate data.
9.3.3.12
Software Consultant
The responsibilities include providing professional opinions on how best to solve problems
encountered in the development and testing of the software behind the Silencer system.
9.3.3.13
Software Engineer
The responsibilities include coding product software as directed by the Software Specialist.
9.3.3.14
Bluetooth Expert
The responsibilities include overseeing the integration of Bluetooth technology with Silencer
software and will solve problems encountered in the testing of all Bluetooth components, both
individually and as a complete system.
9.3.3.15
Budget and Financial Consultant
The responsibilities include overseeing accounting practices, monitoring the budget, and giving
professional financial advice.
9.3.3.16
Hardware Tester
The responsibilities include prototype and integration testing of all hardware components assuring
that all electrical and interface specifications are met.
9.3.3.17
HR Representative
The responsibilities include managing team payroll and interpersonal conflicts.
9.3.3.18
Technical Writer
The responsibilities include preparing formal documents for software and hardware components of
Page 54/84
CS 410 Red
SILENCER
7/26/2016
the Silencer as directed by the Documentation Specialist.
9.3.3.19
Research Assistant
The responsibilities include assisting the Statistical Analyst through product related research and
verifying and updating all previously recorded statistics.
Phase 2 Staffing Budget
Job Title
Software Engineer
Web Developer
HR Representative
Technical Writer
Financial Analyst
Computer Hardware
Engineer
Total Cost
40% Overhead Cost
Total Cost Including
Overhead
Qty
2
1
1
1
1
1
Salary
$85,810
$40,409
$108,920
$65,190
$77,270
$93,010
Cost
$171,620
$40,410
$108,920
$65,190
$77,270
$93,010
$556,420
$222,570
$778,990
Sources:
Salaries - http://www.bls.gov/oes/current/oes_va.htm
http://www.salary.com/
Page 55/84
CS 410 Red
SILENCER
9.3.4
7/26/2016
Phase 3: Production and Out Years
The phase is the main rollout of the product. In this phase, the Bluetooth hardware and Silencer
software are working for a certain number of cell phone manufacturers and actual production begins.
The marketing campaign also begins in this phase.
The following staff will be needed in Phase 3 of this project:
Diagram – Phase 3 Staffing Plan
9.3.4.1
Project Manager
The responsibilities include making sure that all tasks are assigned and are performed with high
quality. The project manager must also resolve difference between team members and facilitate team
member communications. The project manager also must assist in the development of the WBS, assign
resources, prioritize tasks, and define task dependencies.
Page 56/84
CS 410 Red
SILENCER
9.3.4.2
7/26/2016
Software Specialist
The responsibilities include identifying the software needed for the Silencer service, estimating costs,
and determining the best methods for developing or attaining the components.
9.3.4.3
Web Design Specialist
The responsibilities include creating and maintaining the team and product websites, as well as
managing additional web developers in future phases.
9.3.4.4
Marketing Specialist
The responsibilities include determining the target market and supporting the marketing aspects of
the project. The marketing specialist will determine the overall marketing plan.
9.3.4.5
Documentation Specialist
The responsibilities include creating and maintaining documents required to fulfill deliverable
requirements during development.
9.3.4.6
Finance Specialist
The responsibilities include receiving funding, creating the budget, and determining the product cost.
The financial specialist is responsible for the financial and funding plans.
9.3.4.7
Hardware Specialist
The responsibilities include identifying the hardware needed for the Silencer system, estimating
costs, and determining the best methods for developing or attaining the components.
9.3.4.8
Statistical Analyst
The responsibilities include researching the problem area, project risks, major competitors, and
societal effects of solution integration.
Page 57/84
CS 410 Red
SILENCER
9.3.4.9
7/26/2016
Software Engineer
The responsibilities include coding product software as directed by the Software Specialist.
9.3.4.10
Budget and Financial Consultant
The responsibilities include overseeing accounting practices, monitoring the budget, and giving
professional financial advice.
9.3.4.11
Web Developer
The responsibilities include creating, modifying, and maintaining the project web site as directed by
the Web Design Specialist.
9.3.4.12
HR Representative
The responsibilities include managing team payroll and interpersonal conflicts.
9.3.4.13
Marketing Expert
The responsibilities include implementing marketing strategies decided with the Marketing
Specialist.
9.3.4.14
Advertising Expert
The responsibilities include designing and implementing advertising campaigns for the product.
9.3.4.15
Product Pricing Expert
The responsibilities include calculating a final product price based on the budget and economic
conditions.
9.3.4.16
Payroll Manager
The responsibilities include validating and distributing all payments to paid employees of the product
team.
Page 58/84
CS 410 Red
SILENCER
9.3.4.17
7/26/2016
Tax Expert
The responsibilities include verifying all tax documents and payments are made correctly and
submitted by federal deadlines.
9.3.4.18
Research Assistant
The responsibilities include assisting the Statistical Analyst through product related research and
verifying and updating all previously recorded statistics.
9.3.4.19
Market Researcher
The responsibilities include assisting the Statistical Analyst in researching market areas and strategies
for increasing sales volume.
9.3.4.20
Corporate Lawyer
The responsibilities include assuring all documentation clearly explains that the team is not
responsible for any damages caused by using the product. All such explanations will meet legal
standards for such disclaimers.
Phase 3 Staffing Budget
Job Title
Software Engineer
Web Developer
HR Representative
Advertising Expert
Pricing Expert
Financial Analyst
Payroll
Tax Expert
Market Researcher
Lawyer
Total Cost
40% Overhead Cost
Total Cost Including
Overhead
Qty
2
1
1
1
1
1
1
1
1
1
Salary
$85,810
$40,409
$108,920
$82,120
$74,080
$77,270
$34,660
$28,890
$75,980
$115,080
Cost
$171,620
$40,409
$108,920
$82,120
$74,080
$77,270
$34,660
$28,890
$75,980
$115,080
$809,029
$323,612
$1,132,641
Page 59/84
CS 410 Red
SILENCER
7/26/2016
9.4 Funding Plan (Sam)
Funding for the development of the Silencer will be requested from the National Science Foundation.
More specifically, we will be applying for the grants they have in the area of mobile application
development. The estimated expenses for phase 1 of the development process come to $79,500. This
cost estimate includes pay for the developers as well as equipment for the developers to use. This initial
$79,500 will be used for creating an early prototype of what we want to create. This $79,500 falls below
the maximum provided for phase I by the SBIR, which is $100,000.
After successfully making a working prototype in phase I we will be requesting an additional
$750,000 for phase II. Our phase II budget comes to $778,990, which falls slightly above the maximum
provided by NSF for phase II. For the remaining $28,990 we plan to take out a small business loan.
During this phase we will be working on prototypes for additional phones and we will become ready to
enter the production phase.
Next we will begin marketing as well as production. For phase III we will require $1,616,940
between the expenses for company salaries as well as any supplies and workspaces we will need. This
will also include the cost for initial production of our product. To fund phase III we plan to seek support
from outside investors. If our investor support is not sufficient, we will request more small business
loans.
In the out years we will be requiring fewer funds to simply maintain support and continue
manufacturing. We will still need someone to develop for newer phones. We will also need a customer
support line. In addition, we will need someone to maintain and update our website. The estimated
cost during the out years is $229,870 per year. Early in the out years we will begin making enough
money off our sold products to pay off any debt we have acquired. We will also begin making enough
Page 60/84
CS 410 Red
SILENCER
7/26/2016
money to pay for our out years expenses.
The due date for the NSF funding request is June 10th 2008. Our topic area will be “Software and
Services”; the subtopic area is “Mobile Applications”. We will need to create a 200-word project
summary covering many topics listed on their website.
Page 61/84
CS 410 Red
SILENCER
7/26/2016
9.5 Work Breakdown Structure (WBS) (Duc)
WBS has a crucial role in helping the team manage the project. Not only does it break big tasks into
subtasks and manage deadline, it also helps to assign and manage resources for each task and calculate
the total cost. We have used Microsoft Project to generate and manage WBS. Our project consists of four
phases:
9.5.1
Phase 0
This is the first phase of our project. We will dedicate the whole Spring 2008 semester for this phase.
In this phase, finding a feasible problem and create a solution for it is our major task. We spent a lot of
time making sure that our solution does solve the problem and that it contains all the basic features that
are needed. During the summer, each team member will do independent research to improve our
Silencer.
WBS
Task Name
Duration
Start
1.1
Phase 0
104 days
1/15/2008 8:00
6/6/2008 17:00
1.1.1
Presentation I - Project Concept
41 days
1/15/2008 8:00
3/11/2008 17:00
1.1.1.1
Develop Project Team
22 days
1/15/2008 8:00
2/13/2008 17:00
1.1.1.1.1
Determine Team Members
3 days
1/15/2008 8:00
1/17/2008 17:00
1.1.1.1.2
Team Contact List
3 days
1/27/2008 8:00
2/1/2008 17:00
1.1.1.1.3
Create Classroom Web Site
3 days
2/3/2008 8:00
2/7/2008 17:00
1.1.1.1.4
Identify Product List
2 days
2/4/2008 8:00
2/5/2008 17:00
1.1.1.1.5
Team Website
6 days
2/6/2008 8:00
2/13/2008 17:00
1.1.1.1.5.1
Research
6 days
2/6/2008 8:00
2/13/2008 17:00
1.1.1.1.5.2
Layout
6 days
2/6/2008 8:00
2/13/2008 17:00
1.1.1.1.6
Define Group Meeting Times
1 day
2/9/2008 8:00
2/11/2008 17:00
1.1.1.2
Define Project
5 days
2/11/2008 8:00
2/15/2008 17:00
1.1.1.2.1
Define Problem
1 day
2/11/2008 8:00
2/11/2008 17:00
1.1.1.2.2
Develop solution
1 day
2/11/2008 8:00
2/11/2008 17:00
1.1.1.2.3
Define Objectives/ Goals
1 day
2/11/2008 8:00
2/11/2008 17:00
1.1.1.2.4
Team Website
4 days
2/12/2008 8:00
2/15/2008 17:00
1.1.1.2.4.1
Research
4 days
2/12/2008 8:00
2/15/2008 17:00
1.1.1.2.4.2
Layout
4 days
2/12/2008 8:00
2/15/2008 17:00
1.1.1.3
Conduct Project Research
3 days
2/13/2008 8:00
2/15/2008 17:00
1.1.1.3.1
Conduct Survey
3 days
2/13/2008 8:00
2/15/2008 17:00
1.1.1.3.2
Competition Matrix
1 day
2/15/2008 8:00
2/15/2008 17:00
1.1.1.3.3
Update Website
1 day
2/15/2008 8:00
2/15/2008 17:00
1.1.1.4
Determine Initial Solution
18 days
2/15/2008 8:00
3/11/2008 17:00
1.1.1.4.1
Technology Research
1 day
2/15/2008 8:00
2/15/2008 17:00
Page 62/84
Finish
CS 410 Red
SILENCER
7/26/2016
1.1.1.4.2
Determine Experts Needed
7 days
2/15/2008 8:00
2/25/2008 17:00
1.1.1.4.2.1
Identify Experts
1 day
2/15/2008 8:00
2/15/2008 17:00
1.1.1.4.2.2
Meet with Experts
6 days
2/16/2008 8:00
2/25/2008 17:00
1.1.1.4.3
Team Meeting
1 day
2/17/2008 8:00
2/18/2008 17:00
1.1.1.4.4
Cost Research
3 days
2/17/2008 8:00
2/20/2008 17:00
1.1.1.4.5
Flow Chart for different Scenarios
1 day
2/20/2008 8:00
2/20/2008 17:00
1.1.1.4.6
Silencer Research
6 days
2/23/2008 8:00
3/11/2008 17:00
1.1.1.4.7
Team Meeting
1 day
2/24/2008 8:00
2/25/2008 17:00
1.1.1.4.8
Create Risk Matrix and Risk Mitigation Plan
2 days
2/25/2008 8:00
2/26/2008 17:00
1.1.1.4.9
Determine Solution Characteristics
2 days
3/4/2008 8:00
3/5/2008 17:00
1.1.2
Presentation II - Feasibility
8 days
3/1/2008 8:00
3/12/2008 17:00
1.1.2.1
Requirements Analysis
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1
Assign Team Roles
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.1
Determine Project Manager
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.2
Determine Hardware Specialist
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.3
Determine Documentation Specialist
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.4
Determine Webmaster
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.5
Determine Marketing Specialist
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.6
Determine Software Specialist
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.1.7
Determine Finance Specialist
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.2
Design
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.2.1
Determine Initial Features the Silencer Must Have
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.2.2
What's in the Box
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.2.3
What's NOT in the Box
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.2.4
Marketing
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.3
Financial
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.3.1
Determine Cost of Solution
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.4
Technical
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.4.1
Determine Hardware Needed
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.1.4.2
Determine Hardware Costs
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.2.2
Presentation
8 days
3/1/2008 8:00
3/12/2008 17:00
1.1.2.2.1
Feasibility Presentation Script
6 days
3/1/2008 8:00
3/10/2008 17:00
1.1.2.2.2
Create Slides for Presentation
4 days
3/7/2008 8:00
3/12/2008 17:00
1.1.2.2.2.1
Organizational Chart Slide
1 day
3/7/2008 8:00
3/7/2008 17:00
1.1.2.2.2.2
Problem Statement Slide
3 days
3/9/2008 8:00
3/12/2008 17:00
1.1.2.2.2.3
Problem Analysis Slide
3 days
3/9/2008 8:00
3/12/2008 17:00
1.1.2.2.2.4
Fingerprints Slide
3 days
3/9/2008 8:00
3/12/2008 17:00
1.1.2.2.2.5
Solution Slide
1 day
3/10/2008 8:00
3/10/2008 17:00
1.1.2.2.2.6
What’s in the Box? Slide
1 day
3/10/2008 8:00
3/10/2008 17:00
1.1.2.2.2.7
Installation Slides
1 day
3/10/2008 8:00
3/10/2008 17:00
1.1.2.2.2.8
MFCD Slide
1 day
3/11/2008 8:00
3/11/2008 17:00
1.1.2.2.2.9
Scenario Slides
1 day
3/11/2008 8:00
3/11/2008 17:00
1.1.2.2.2.10
Survey Slide
1 day
3/11/2008 8:00
3/11/2008 17:00
1.1.2.2.2.11
What We Don’t Do Slide
1 day
3/11/2008 8:00
3/11/2008 17:00
1.1.2.2.2.12
Initial Manufacturer Support Slide
1 day
3/11/2008 8:00
3/11/2008 17:00
1.1.2.2.2.13
Organization Chart
1 day
3/12/2008 8:00
3/12/2008 17:00
1.1.2.2.2.14
Costs Slide
1 day
3/12/2008 8:00
3/12/2008 17:00
1.1.2.2.2.15
Risk Matrix Slide
1 day
3/12/2008 8:00
3/12/2008 17:00
1.1.2.2.2.16
Competition Slide
1 day
3/12/2008 8:00
3/12/2008 17:00
1.1.2.2.2.17
References
1 day
3/12/2008 8:00
3/12/2008 17:00
1.1.2.2.3
Create Handouts
1 day
3/5/2008 8:00
3/5/2008 17:00
Page 63/84
CS 410 Red
SILENCER
7/26/2016
1.1.2.2.4
Final Team Website
3 days
3/2/2008 8:00
3/5/2008 17:00
1.1.2.2.4.1
Design
3 days
3/2/2008 8:00
3/5/2008 17:00
1.1.2.2.4.2
Content
3 days
3/2/2008 8:00
3/5/2008 17:00
1.1.2.2.5
Feasibility Presentation
1 day
3/6/2008 8:00
3/6/2008 17:00
1.1.3
Presentation III - Milestone Planning
10 days
3/28/2008 8:00
4/10/2008 17:00
1.1.3.1
Milestone Planning and Preparation
10 days
3/28/2008 8:00
4/10/2008 17:00
1.1.3.1.1
Update Script from Feasibility Presentation
4 days
3/28/2008 8:00
4/2/2008 17:00
1.1.3.1.2
Planning
7 days
3/29/2008 8:00
4/8/2008 17:00
1.1.3.1.2.1
Create WBS
7 days
3/29/2008 8:00
4/8/2008 17:00
1.1.3.1.2.1.1
Phase 0
7 days
3/29/2008 8:00
4/8/2008 17:00
1.1.3.1.2.1.1.1
Determine Tasks
2 days
3/29/2008 8:00
4/8/2008 17:00
1.1.3.1.2.1.1.2
Determine and Assign Resources
1 day
3/30/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.1.3
Determine Task Dependencies
4 days
3/31/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.1.4
Update Project Hours
5.13 days
3/31/2008 8:00
4/7/2008 9:00
1.1.3.1.2.1.1.5
Submit Project Hours
2 days
3/31/2008 8:00
4/1/2008 17:00
1.1.3.1.2.1.1.6
Level Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.2
Phase 1
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.2.1
Determine Tasks
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.2.2
Determine and Assign Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.2.3
Determine Task Dependencies
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.2.4
Update Project Hours
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.2.5
Level Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.3
Phase 2
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.3.1
Determine Tasks
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.3.2
Determine and Assign Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.3.3
Determine Task Dependencies
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.3.4
Update Project Hours
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.3.5
Level Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.4
Phase 3
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.4.1
Determine Tasks
2 days
4/3/2008 8:00
4/4/2008 17:00
1.1.3.1.2.1.4.2
Determine and Assign Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.4.3
Determine Task Dependencies
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.4.4
Update Project Hours
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.1.4.5
Level Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.2.2
Determine Non-Development Human Resources
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.3
Technical
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4
Financial Plan
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.1
Funding Agency
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.1.1
Determine Funding Agency
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.1.2
Get Required Docs for SBIR from Funding Agency
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.2
Determine Product Costs
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.3
Determine Human Resource Costs
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.4
Determine Technical Center Costs
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.5
Determine Overhead Equipment Costs
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.6
Determine Non-Development Human Resources Costs
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.7
Perform Cash Flow Analysis
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.8
Determine Break Even
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.4.9
Assess Financial Feasibility
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5
Marketing
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.1
Determine Target Markets
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.1.1
Determine Rollout Market
1 day
4/3/2008 8:00
4/3/2008 17:00
Page 64/84
CS 410 Red
SILENCER
7/26/2016
1.1.3.1.5.1.2
Determine Step 2 Rollout Markets
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2
Determine Marketing Plan
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2.1
Define Advertising Plan for Rollout
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2.2
Define Advertising Resources for Rollout
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2.3
Determine Advertising Costs for Rollout
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2.4
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.5.2.5
Determine Estimated Advertising Costs for Step 2 Rollout
Determine Estimated Advertising Costs for Nationwide
Rollout
1 day
4/3/2008 8:00
4/3/2008 17:00
1.1.3.1.6
Communication
9 days
3/29/2008 8:00
4/10/2008 17:00
1.1.3.1.6.1
Team Website
9 days
3/29/2008 8:00
4/10/2008 17:00
1.1.3.1.6.1.1
Design
2 days
3/29/2008 8:00
4/10/2008 17:00
1.1.3.1.6.1.2
Content
2 days
4/7/2008 8:00
4/8/2008 17:00
1.1.3.1.6.1.3
Peer Review/Test Links
1 day
4/7/2008 8:00
4/7/2008 17:00
1.1.3.1.7
SBIR
3 days
4/5/2008 8:00
4/9/2008 17:00
1.1.3.1.7.1
Determine Requirements
2 days
4/5/2008 8:00
4/8/2008 17:00
1.1.3.1.7.2
Assign SBIR Team Responsibilities
1 day
4/9/2008 8:00
4/9/2008 17:00
1.1.3.2
Presentation
7 days
4/2/2008 8:00
4/10/2008 17:00
1.1.3.2.1
Create Slides
7 days
4/2/2008 8:00
4/10/2008 17:00
1.1.3.2.1.1
Create Story Slide
2 days
4/2/2008 8:00
4/3/2008 17:00
1.1.3.2.1.2
Phase 0 Gantt Chart
1 day
4/7/2008 8:00
4/7/2008 17:00
1.1.3.2.1.3
Phase 1 Gantt Chart
1 day
4/8/2008 8:00
4/8/2008 17:00
1.1.3.2.1.4
Features
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.1.5
Marketing
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.1.6
Financial
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.1.7
Technical
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.1.8
Risks
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2
Documentation
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2.1
Create Overview and Abstract
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2.2
Create Funding Plan
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2.3
Create Marketing Plan
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2.4
Create Risk Mitigation Plan
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.2.5
Create Technical Plan
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.3.2.3
Create Script
1 day
4/2/2008 8:00
4/2/2008 17:00
1.1.3.2.4
Create Handouts
1 day
4/2/2008 8:00
4/2/2008 17:00
1.1.3.2.5
Milestone Presentation
1 day
4/10/2008 8:00
4/10/2008 17:00
1.1.4
Presentation IV - Project Approval
19 days
4/11/2008 8:00
5/7/2008 17:00
1.1.4.1
Planning and Preparation
8.5 days
4/11/2008 8:00
4/23/2008 12:00
1.1.4.1.1
Improve Milestone Presentation
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.2
Improve WBS
2.5 days
4/20/2008 8:00
4/23/2008 12:00
1.1.4.1.3
Improve Financial Plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.4
Improve Marketing Plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.5
Improve Risk Mitigation Plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.6
Improve Technical Plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7
Create SBIR
7 days
4/11/2008 8:00
4/21/2008 17:00
1.1.4.1.7.1
Cover Sheet
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.2
Project Summary
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.3
Table of Contents
2 days
4/11/2008 8:00
4/14/2008 17:00
1.1.4.1.7.4
Project Description
4 days
4/11/2008 8:00
4/16/2008 17:00
1.1.4.1.7.5
References Cited
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.6
Biographical Sketch(es)
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.7
Budget
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.8
Facilities, Equipment and Other Resources
1 day
4/11/2008 8:00
4/11/2008 17:00
Page 65/84
CS 410 Red
SILENCER
7/26/2016
1.1.4.1.7.9
Special Information and Supplementary Documentation
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.10
Marketing Plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.11
Competition
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.12
Industry Analysis
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.13
Managment and organization plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.14
Development, milestones and exit plan
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.15
Funding plan
4 days
4/11/2008 8:00
4/16/2008 17:00
1.1.4.1.7.16
Evaluation plan
1 day
4/17/2008 8:00
4/17/2008 17:00
1.1.4.1.7.17
WBS - Gantt charts
1 day
4/18/2008 8:00
4/18/2008 17:00
1.1.4.1.7.18
Contracts
1 day
4/21/2008 8:00
4/21/2008 17:00
1.1.4.1.7.19
Glossary
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.7.20
Risk assessment
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.8
Create Project Website
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.8.1
Determine Website Structure
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.8.2
Determine Website Hardware
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.8.3
Create Look and Feel
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.1.8.4
Move Documents to Website
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2
Presentation
18 days
4/11/2008 8:00
5/6/2008 17:00
1.1.4.2.1
Create Slides
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.1.1
Features
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.1.2
Marketing
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.1.3
Financial
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.1.4
Technical
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.1.5
Risks
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.2
Create Handouts
1 day
4/11/2008 8:00
4/11/2008 17:00
1.1.4.2.3
Approval Presentation
1 day
5/6/2008 8:00
5/6/2008 17:00
1.1.4.3
Postmortem
1 day
5/7/2008 8:00
5/7/2008 17:00
1.1.4.3.1
Fillout Postmortem Questionaire
1 day
5/7/2008 8:00
5/7/2008 17:00
1.1.4.3.2
Hold Postmortem Meeting
1 day
5/7/2008 8:00
5/7/2008 17:00
1.1.4.3.3
Project Report / Lessons Learned
1 day
5/7/2008 8:00
5/7/2008 17:00
1.1.5
SBIR I Grant Proposal
22 days
5/8/2008 8:00
6/6/2008 17:00
1.1.5.1
Create SBIR Phase 1 Proposal
21 days
5/8/2008 8:00
6/5/2008 17:00
1.1.5.2
SBIR Phase 1 Approval
1 day
6/6/2008 8:00
6/6/2008 17:00
1.2
Summer Research
65 days
6/9/2008 8:00
9/5/2008 17:00
Page 66/84
CS 410 Red
SILENCER
9.5.2
7/26/2016
Phase 1
This is the second phase of our project. We will dedicate the whole Fall 2008 semester for this phase.
In this phase, developing a working prototype and the documentation for it are our major tasks. We
want to show that our idea is technically feasible and that even a normal person can read our
instructions and from there, understand the features of our product.
WBS
Task Name
Duration
Start
Finish
1.3
Phase 1
94 days
9/8/2008 8:00
1/15/2009 17:00
1.3.1
Team Development
7 days
9/8/2008 8:00
9/16/2008 17:00
1.3.1.1
Identify New Team Members
6 days
9/8/2008 8:00
9/15/2008 17:00
1.3.1.2
Reassign Responsibilties as Needed
1 day
9/16/2008 8:00
9/16/2008 17:00
1.3.1.3
Get New Members to Sign Project Charter
1 day
9/16/2008 8:00
9/16/2008 17:00
1.3.2
Phase 0 Outcome Review
2 days
9/8/2008 8:00
9/9/2008 17:00
1.3.2.1
Update Project from Approval Presentation Phase 0
2 days
9/8/2008 8:00
9/9/2008 17:00
1.3.3
Documentations
92 days
9/10/2008 8:00
1/15/2009 17:00
1.3.3.1
21 days
9/10/2008 8:00
10/8/2008 17:00
1.3.3.2
Product Description Paper (Writing - Lab I)
Development Environment Requirements for Prototype
(Writing - Requirements List)
7 days
10/9/2008 8:00
10/17/2008 17:00
1.3.3.3
Prototype Product Specification (Writing - Lab II)
14 days
10/9/2008 8:00
10/28/2008 17:00
1.3.3.4
Prototype Test Plan/Procedures (Writing - Lab III)
21 days
10/29/2008 8:00
11/26/2008 17:00
1.3.3.5
Product/Prototype User's Manuals (Writing - Lab IV)
14 days
11/27/2008 8:00
12/16/2008 17:00
1.3.3.6
SBIR II Grant Proposal (Writing - Lab V)
22 days
12/17/2008 8:00
1/15/2009 17:00
1.3.3.6.1
SBIR Grant Proposal
21 days
12/17/2008 8:00
1/14/2009 17:00
1.3.3.6.2
SBIR Phase 2 Approval
1 day
1/15/2009 8:00
1/15/2009 17:00
1.3.4
Prototype Development
77 days
9/10/2008 8:00
12/25/2008 17:00
1.3.4.1
Prototype Planning
6 days
9/10/2008 8:00
9/17/2008 17:00
1.3.4.1.1
Define Approach
2 days
9/10/2008 8:00
9/11/2008 17:00
1.3.4.1.1.1
Define Group Meeting Times
1 day
9/10/2008 8:00
9/10/2008 17:00
1.3.4.1.1.2
Determine Communication Methods
1 day
9/11/2008 8:00
9/11/2008 17:00
1.3.4.1.2
Determine Development Platform
6 days
9/10/2008 8:00
9/17/2008 17:00
1.3.4.2
Prototype Requirements
6 days
9/18/2008 8:00
9/25/2008 17:00
1.3.4.2.1
Define Functional Level Requirements
6 days
9/18/2008 8:00
9/25/2008 17:00
1.3.4.2.1.1
Define Functional Level Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.1.2
Functional Requirements Document
5 days
9/19/2008 8:00
9/25/2008 17:00
1.3.4.2.2
Car - LEGO Mindstorm
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.2.1
Define Car's Prototype Hardware Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.2.2
Define Car's Software Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.3
The Silencer
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.3.1
Define The Silencer's Prototype Hardware Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.3.2
Define The Silencer's Software Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.3.2.1
Define Interface Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.3.2.2
Define Features to be implemented
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.4
Cell phone
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.4.1
Determine the cell phone's brand to be used
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.4.2
Define Software Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.4.2.1
Define Interface Requirements
1 day
9/18/2008 8:00
9/18/2008 17:00
Page 67/84
CS 410 Red
SILENCER
7/26/2016
1.3.4.2.4.2.2
Define Features to be implemented
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5
Create Requirements Doc
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.1
Hardware
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.1.1
Create Requirements Doc for Car
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.1.2
Create Requirements Doc for The Silencer
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.2
Software
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.2.1
Create Requirements Doc for Car
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.2.2
Create Requirements Doc for The Silencer
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.2.5.2.3
Create Requirements Doc for Cell phone
1 day
9/18/2008 8:00
9/18/2008 17:00
1.3.4.3
Hardware Procurement
10 days
9/26/2008 8:00
10/9/2008 17:00
1.3.4.4
Software Development
30 days
10/10/2008 8:00
11/20/2008 17:00
1.3.4.4.1
Software Design
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.1
Car
8 days
10/10/2008 8:00
10/21/2008 17:00
1.3.4.4.1.1.1
Design Signal-Sending Algorithm
8 days
10/10/2008 8:00
10/21/2008 17:00
1.3.4.4.1.2
The Silencer
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.2.1
Design Gui Interface
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.2.2
Design Signal-Sending Algorithm
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.3
Cell phone
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.3.1
Design Gui Interface
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.3.2
Design Signal-Handling Algorithm
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.3.3
Design Call-Blocking Algorithm
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.1.3.4
Specify exception numbers
10 days
10/10/2008 8:00
10/23/2008 17:00
1.3.4.4.2
Software Development
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.1
Car
8 days
10/24/2008 8:00
11/4/2008 17:00
1.3.4.4.2.1.1
Develop Signal-Sending Algorithm
8 days
10/24/2008 8:00
11/4/2008 17:00
1.3.4.4.2.2
The Silencer
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.2.1
Develop Gui Interface
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.2.2
Develop Signal-Sending Algorithm
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.3
Cell phone
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.3.1
Develop Gui Interface
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.3.2
Develop Signal-Handling Algorithm
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.2.3.3
Develop Call-Blocking Algorithm
10 days
10/24/2008 8:00
11/6/2008 17:00
1.3.4.4.3
Software Testing
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.1
Car
8 days
11/7/2008 8:00
11/18/2008 17:00
1.3.4.4.3.1.1
Test Signal-Sending Algorithm
8 days
11/7/2008 8:00
11/18/2008 17:00
1.3.4.4.3.2
The Silencer
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.2.1
Test Gui Interface
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.2.2
Test Signal-Sending Algorithm
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.3
Cell phone
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.3.1
Test Gui Interface
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.3.2
Test Signal-Handling Algorithm
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.4.3.3.3
Test Call-Blocking Algorithm
10 days
11/7/2008 8:00
11/20/2008 17:00
1.3.4.5
Prototype Implementation
4.89 days
11/21/2008 8:00
11/27/2008 16:08
1.3.4.5.1
Setup Prototype for Demo
3.26 days
11/21/2008 8:00
11/26/2008 10:05
1.3.4.5.2
Production Readiness Test
1.63 days
11/26/2008 10:05
11/27/2008 16:08
1.3.4.6
Prototype Demonstration
11 days
12/11/2008 8:00
12/25/2008 17:00
1.3.4.6.1
Prototype Presentation I
1 day
12/11/2008 8:00
12/11/2008 17:00
1.3.4.6.2
Final Prototype Demonstration
1 day
12/25/2008 8:00
12/25/2008 17:00
1.3.5
Project Web Page
24 days
11/3/2008 8:00
12/4/2008 17:00
1.3.5.1
Design Project Web Page
8 days
11/3/2008 8:00
11/12/2008 17:00
1.3.5.2
Develop Project Web Page
8 days
11/13/2008 8:00
11/24/2008 17:00
Page 68/84
CS 410 Red
1.3.5.3
SILENCER
Test Project Web Page
7/26/2016
8 days
Page 69/84
11/25/2008 8:00
12/4/2008 17:00
CS 410 Red
SILENCER
9.5.3
7/26/2016
Phase 2
This is the third phase of our project. It will last for seven months. In this phase, we want to develop
a complete prototype and do Beta testing. We will also create a complete documentation and user
guide. We will make sure that an average parent can read and understand how to use our product. We
will hire more staff in this phase so that we can achieve our goal in a timely manner.
WBS
Task Name
Duration
Start
Finish
1.4
Phase 2
156 days
1/16/2009 8:00
8/21/2009 17:00
1.4.1
Team Development
23 days
1/16/2009 8:00
2/17/2009 17:00
1.4.1.1
Personnel
23 days
1/16/2009 8:00
2/17/2009 17:00
1.4.1.1.1
Identify New Team Members
1 day
1/16/2009 8:00
1/16/2009 17:00
1.4.1.1.2
Hire New Management Resources
21 days
1/16/2009 8:00
2/13/2009 17:00
1.4.1.1.3
Get New Team Members to Sign Project Charter
1 day
2/16/2009 8:00
2/16/2009 17:00
1.4.1.1.4
Reassign Responsibilties as Needed
1 day
2/17/2009 8:00
2/17/2009 17:00
1.4.2
Phase 1 Outcome Review
2 days
2/18/2009 8:00
2/19/2009 17:00
1.4.3
Planning
49 days
2/20/2009 8:00
4/29/2009 17:00
1.4.3.1
Define Approach
2 days
2/20/2009 8:00
2/23/2009 17:00
1.4.3.1.1
Determine Communication Methods
1 day
2/20/2009 8:00
2/20/2009 17:00
1.4.3.1.2
Determine Development Approach
1 day
2/23/2009 8:00
2/23/2009 17:00
1.4.3.2
Define Functional Level Requirements
10 days
2/24/2009 8:00
3/9/2009 17:00
1.4.3.2.1
5 days
2/24/2009 8:00
3/2/2009 17:00
5 days
2/24/2009 8:00
3/2/2009 17:00
1.4.3.2.1.2
Define Functional Level Requirements
Define The Silencer's Software Functional Level
Requirements
Define The Silencer's Hardware Functional Level
Requirements
3 days
2/24/2009 8:00
2/26/2009 17:00
1.4.3.2.1.3
Define Cell Phone Software Fuctional Level Requirements
1 day
2/24/2009 8:00
2/24/2009 17:00
1.4.3.2.2
Functional Requirements Document
5 days
3/3/2009 8:00
3/9/2009 17:00
1.4.3.3
Hardware Vendors
49 days
2/20/2009 8:00
4/29/2009 17:00
1.4.3.3.1
Procurement Planning
10 days
2/20/2009 8:00
3/5/2009 17:00
1.4.3.3.1.1
Determine Requirements
5 days
2/20/2009 8:00
2/26/2009 17:00
1.4.3.3.1.2
Create Statement of Work
5 days
2/27/2009 8:00
3/5/2009 17:00
1.4.3.3.2
Solicitation Planning
9 days
3/6/2009 8:00
3/18/2009 17:00
1.4.3.3.2.1
Identify Potential Vendors
5 days
3/6/2009 8:00
3/12/2009 17:00
1.4.3.3.2.2
Develop Evaluation Criteria
1 day
3/13/2009 8:00
3/13/2009 17:00
1.4.3.3.2.3
Create RFP (Request for Proposal)
3 days
3/16/2009 8:00
3/18/2009 17:00
1.4.3.3.3
Solicitation
16 days
3/19/2009 8:00
4/9/2009 17:00
1.4.3.3.3.1
Send RFP to Vendors
1 day
3/19/2009 8:00
3/19/2009 17:00
1.4.3.3.3.2
Proposals Received
1 day
4/9/2009 8:00
4/9/2009 17:00
1.4.3.3.4
Solicitation Selection
3 days
4/10/2009 8:00
4/14/2009 17:00
1.4.3.3.4.1
Select Vendor based on Criteria
3 days
4/10/2009 8:00
4/14/2009 17:00
1.4.3.3.5
Contract Admin
4 days
4/15/2009 8:00
4/20/2009 17:00
1.4.3.3.5.1
Create Formal Contract
3 days
4/15/2009 8:00
4/17/2009 17:00
1.4.3.3.5.2
Send Contract to Vendor
1 day
4/20/2009 8:00
4/20/2009 17:00
1.4.3.3.6
Contract Closeout
7 days
4/21/2009 8:00
4/29/2009 17:00
1.4.3.3.6.1
Evaluate Products Received
5 days
4/21/2009 8:00
4/27/2009 17:00
1.4.3.3.6.2
Evaluate Contract Terms Being Met
1 day
4/28/2009 8:00
4/28/2009 17:00
1.4.3.3.6.3
Formal Acceptance
1 day
4/29/2009 8:00
4/29/2009 17:00
1.4.3.2.1.1
Page 70/84
CS 410 Red
SILENCER
7/26/2016
1.4.3.3.7
Advertising
11 days
3/13/2009 8:00
3/27/2009 17:00
1.4.3.3.7.1
Select Advertising Agency
5 days
3/13/2009 8:00
3/19/2009 17:00
1.4.3.3.7.2
Product Name and Logo Selection
6 days
3/20/2009 8:00
3/27/2009 17:00
1.4.4
Requirements
4 days
4/30/2009 8:00
5/5/2009 17:00
1.4.4.1
Car
1 day
4/30/2009 8:00
4/30/2009 17:00
1.4.4.1.1
Define Prototype Hardware Requirements
1 day
4/30/2009 8:00
4/30/2009 17:00
1.4.4.1.2
Define Software Requirements
1 day
4/30/2009 8:00
4/30/2009 17:00
1.4.4.2
The Silencer
1 day
5/1/2009 8:00
5/1/2009 17:00
1.4.4.2.1
Define Prototype Hardware Requirements
1 day
5/1/2009 8:00
5/1/2009 17:00
1.4.4.2.2
Define Software Requirements
1 day
5/1/2009 8:00
5/1/2009 17:00
1.4.4.3
Cell Phone
1 day
5/4/2009 8:00
5/4/2009 17:00
1.4.4.3.1
Define Hardware Requirements
1 day
5/4/2009 8:00
5/4/2009 17:00
1.4.4.3.2
Define Software Requirements
1 day
5/4/2009 8:00
5/4/2009 17:00
1.4.4.4
Create Requirements Doc
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.1
Hardware
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.1.1
Create Requirements Doc for Car
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.1.2
Create Requirements Doc for The Silencer
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.1.3
Create Requirements Doc for Cell Phone
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.2
Software
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.2.1
Create Requirements Doc for Car
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.2.2
Create Requirements Doc for The Silencer
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.4.4.2.3
Create Requirements Doc for Cell Phone
1 day
5/5/2009 8:00
5/5/2009 17:00
1.4.5
Development Environment Setup
4 days
5/6/2009 8:00
5/11/2009 17:00
1.4.5.1
Car
4 days
5/6/2009 8:00
5/11/2009 17:00
1.4.5.2
The Silencer
4 days
5/6/2009 8:00
5/11/2009 17:00
1.4.5.3
Cell Phone
3 days
5/6/2009 8:00
5/8/2009 17:00
1.4.6
Software Development
30 days
5/12/2009 8:00
6/22/2009 17:00
1.4.6.1
Software Design
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.1
Car
8 days
5/12/2009 8:00
5/21/2009 17:00
1.4.6.1.1.1
Design Signal-Sending Algorithm
8 days
5/12/2009 8:00
5/21/2009 17:00
1.4.6.1.2
The Silencer
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.2.1
Design GUI Interface
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.2.2
Design Signal-Sending Algorithm
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.3
Cell phone
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.3.1
Design GUI Interface
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.3.2
Design Signal-Handling Algorithm
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.3.3
Design Call-Blocking Algorithm
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.1.3.4
Specify exception numbers
10 days
5/12/2009 8:00
5/25/2009 17:00
1.4.6.2
Software Development
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.1
Car
8 days
5/26/2009 8:00
6/4/2009 17:00
1.4.6.2.1.1
Develop Signal-Sending Algorithm
8 days
5/26/2009 8:00
6/4/2009 17:00
1.4.6.2.2
The Silencer
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.2.1
Develop GUI Interface
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.2.2
Develop Signal-Sending Algorithm
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.3
Cell phone
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.3.1
Develop GUI Interface
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.3.2
Develop Signal-Handling Algorithm
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.2.3.3
Develop Call-Blocking Algorithm
10 days
5/26/2009 8:00
6/8/2009 17:00
1.4.6.3
Software Testing
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.1
Car
8 days
6/9/2009 8:00
6/18/2009 17:00
1.4.6.3.1.1
Test Signal-Sending Algorithm
8 days
6/9/2009 8:00
6/18/2009 17:00
Page 71/84
CS 410 Red
SILENCER
7/26/2016
1.4.6.3.2
The Silencer
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.2.1
Test GUI Interface
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.2.2
Test Signal-Sending Algorithm
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.3
Cell phone
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.3.1
Test GUI Interface
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.3.2
Test Signal-Handling Algorithm
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.6.3.3.3
Test Call-Blocking Algorithm
10 days
6/9/2009 8:00
6/22/2009 17:00
1.4.7
User Documentation
30 days
6/23/2009 8:00
8/3/2009 17:00
1.4.7.1
Installation Guide
20 days
6/23/2009 8:00
7/20/2009 17:00
1.4.7.2
User Manual
30 days
6/23/2009 8:00
8/3/2009 17:00
1.4.8
Implementation
14 days
8/4/2009 8:00
8/21/2009 17:00
1.4.8.1
Setup Prototype for Demo
2 days
8/4/2009 8:00
8/5/2009 17:00
1.4.8.2
Production Readiness Test
12 days
8/6/2009 8:00
8/21/2009 17:00
Page 72/84
CS 410 Red
SILENCER
9.5.4
7/26/2016
Phase 3
This is the last phase of our project. In this phase, we will mass-produce our Silencer and market it.
We will continuously improve our product so that we can compete with other products and occupy a
major share of the market.
WBS
Task Name
Duration
Start
Finish
1.5
Phase 3
293 days
8/24/2009 8:00
10/6/2010 17:00
1.5.1
Team Development
2 days
8/24/2009 8:00
8/25/2009 17:00
1.5.1.1
Identify New Team Members
1 day
8/24/2009 8:00
8/24/2009 17:00
1.5.1.2
Reassign Responsibilties as Needed
1 day
8/25/2009 8:00
8/25/2009 17:00
1.5.2
Phase 2 Outcome Review
2 days
8/26/2009 8:00
8/27/2009 17:00
1.5.3
Production - The Silencer
208 days
8/28/2009 8:00
6/15/2010 17:00
1.5.3.1
Hardware Vendors
34 days
8/28/2009 8:00
10/14/2009 17:00
1.5.3.1.1
Procurement Planning
10 days
8/28/2009 8:00
9/10/2009 17:00
1.5.3.1.1.1
Determine Requirements
5 days
8/28/2009 8:00
9/3/2009 17:00
1.5.3.1.1.2
Create Statement of Work
5 days
9/4/2009 8:00
9/10/2009 17:00
1.5.3.1.2
Solitation Planning
9 days
9/11/2009 8:00
9/23/2009 17:00
1.5.3.1.2.1
Identify Potential Vendors
5 days
9/11/2009 8:00
9/17/2009 17:00
1.5.3.1.2.2
Develop Evaluation Criteria
1 day
9/18/2009 8:00
9/18/2009 17:00
1.5.3.1.2.3
Create RFP (Request for Proposal)
3 days
9/21/2009 8:00
9/23/2009 17:00
1.5.3.1.3
Solitication
2 days
9/24/2009 8:00
9/25/2009 17:00
1.5.3.1.3.1
Send RFP to Vendors
1 day
9/24/2009 8:00
9/24/2009 17:00
1.5.3.1.3.2
Proposals Received
1 day
9/25/2009 8:00
9/25/2009 17:00
1.5.3.1.4
Solicitation Selection
3 days
9/28/2009 8:00
9/30/2009 17:00
1.5.3.1.4.1
Select Vendor based on Criteria
3 days
9/28/2009 8:00
9/30/2009 17:00
1.5.3.1.5
Contract Admin
4 days
10/1/2009 8:00
10/6/2009 17:00
1.5.3.1.5.1
Create Formal Contract
3 days
10/1/2009 8:00
10/5/2009 17:00
1.5.3.1.5.2
Send Contract to Vendor
1 day
10/6/2009 8:00
10/6/2009 17:00
1.5.3.1.6
Hardware
4 days
10/7/2009 8:00
10/12/2009 17:00
1.5.3.1.6.1
Receive Hardware from Vendor
1 day
10/7/2009 8:00
10/7/2009 17:00
1.5.3.1.6.2
Evaluate Hardware Received
3 days
10/8/2009 8:00
10/12/2009 17:00
1.5.3.1.7
Contract Closeout
2 days
10/13/2009 8:00
10/14/2009 17:00
1.5.3.1.7.1
Evaluate Contract Terms Being Met
1 day
10/13/2009 8:00
10/13/2009 17:00
1.5.3.1.7.2
Formal Acceptance
1 day
10/14/2009 8:00
10/14/2009 17:00
1.5.3.2
Office
36 days
8/28/2009 8:00
10/16/2009 17:00
1.5.3.2.1
Hire Office Staff
15 days
8/28/2009 8:00
9/17/2009 17:00
1.5.3.2.2
Set up Phones
2 days
8/28/2009 8:00
8/31/2009 17:00
1.5.3.2.3
Order Office PCs
5 days
8/28/2009 8:00
9/3/2009 17:00
1.5.3.2.4
Receive PCs
1 day
9/4/2009 8:00
9/4/2009 17:00
1.5.3.2.5
Set up Computers
2 days
9/7/2009 8:00
9/8/2009 17:00
1.5.3.2.6
Train Office Staff
30 days
9/7/2009 8:00
10/16/2009 17:00
1.5.3.3
Technical Support
38 days
8/28/2009 8:00
10/20/2009 17:00
1.5.3.3.1
Hire Customer Support Staff
15 days
8/28/2009 8:00
9/17/2009 17:00
1.5.3.3.2
Set up Phones
2 days
8/31/2009 8:00
9/1/2009 17:00
1.5.3.3.3
Order Office PCs
5 days
8/28/2009 8:00
9/3/2009 17:00
1.5.3.3.4
Receive PCs
1 day
9/4/2009 8:00
9/4/2009 17:00
1.5.3.3.5
Set up Computers
2 days
9/7/2009 8:00
9/8/2009 17:00
Page 73/84
CS 410 Red
SILENCER
7/26/2016
1.5.3.3.6
Train Customer Support Staff
30 days
9/9/2009 8:00
10/20/2009 17:00
1.5.3.4
Financial
31 days
8/28/2009 8:00
10/9/2009 17:00
1.5.3.4.1
Retain Venture Captial from CIT
30 days
8/28/2009 8:00
10/8/2009 17:00
1.5.3.4.2
CIT Grant Approval
1 day
10/9/2009 8:00
10/9/2009 17:00
1.5.3.5
Website
180 days
8/28/2009 8:00
5/6/2010 17:00
1.5.3.5.1
Create Customer Facing Website
180 days
8/28/2009 8:00
5/6/2010 17:00
1.5.3.6
Marketing
208 days
8/28/2009 8:00
6/15/2010 17:00
1.5.3.6.1
Beta Test
66 days
8/28/2009 8:00
11/27/2009 17:00
1.5.3.6.1.1
Select Beta Test Market
1 day
8/28/2009 8:00
8/28/2009 17:00
1.5.3.6.1.2
Choose 6 Test Locations
10 days
8/31/2009 8:00
9/11/2009 17:00
1.5.3.6.1.3
Perform Beta Test
40 days
9/14/2009 8:00
11/6/2009 17:00
1.5.3.6.1.4
Get Test Feedback
10 days
11/9/2009 8:00
11/20/2009 17:00
1.5.3.6.1.5
Create Beta Test Results Report
5 days
11/23/2009 8:00
11/27/2009 17:00
1.5.3.6.2
Initial Rollout
36 days
12/21/2009 8:00
2/8/2010 17:00
1.5.3.6.2.1
Advertising
36 days
12/21/2009 8:00
2/8/2010 17:00
1.5.3.6.2.1.1
Determine Advertising Agency
5 days
12/21/2009 8:00
12/25/2009 17:00
1.5.3.6.2.1.2
Prepare Advertising Materials
30 days
12/28/2009 8:00
2/5/2010 17:00
1.5.3.6.2.1.3
Launch Marketing Campaign
1 day
2/8/2010 8:00
2/8/2010 17:00
1.5.3.6.3
Step 2 Rollout
91 days
2/9/2010 8:00
6/15/2010 17:00
1.5.3.6.3.1
Advertising
31 days
2/9/2010 8:00
3/23/2010 17:00
1.5.3.6.3.1.1
Prepare Advertising Materials
30 days
2/9/2010 8:00
3/22/2010 17:00
1.5.3.6.3.1.2
Launch Marketing Campaign
1 day
3/23/2010 8:00
3/23/2010 17:00
1.5.3.6.3.2
Nationwide Rollout
31 days
5/4/2010 8:00
6/15/2010 17:00
1.5.3.6.3.2.1
Advertising
31 days
5/4/2010 8:00
6/15/2010 17:00
1.5.3.6.3.2.1.1
Prepare Advertising Materials
30 days
5/4/2010 8:00
6/14/2010 17:00
1.5.3.6.3.2.1.2
Launch Marketing Campaign
1 day
6/15/2010 8:00
6/15/2010 17:00
1.5.4
Post Production Improvements
81 days
6/16/2010 8:00
10/6/2010 17:00
1.5.4.1
Requirements
7 days
6/16/2010 8:00
6/24/2010 17:00
1.5.4.1.1
Define Functional Level Requirements
7 days
6/16/2010 8:00
6/24/2010 17:00
1.5.4.1.1.1
Define Functional Level Requirements
2 days
6/16/2010 8:00
6/17/2010 17:00
1.5.4.1.1.2
Functional Requirements Document
5 days
6/18/2010 8:00
6/24/2010 17:00
1.5.4.1.2
The Silencer
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.2.1
Define Hardware Requirements
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.2.2
Define Software Requirements
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.3
Cell Phone
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.3.1
Define Hardware Requirements
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.3.2
Define SoftwareRequirements
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.4
Create Requirements Doc
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.4.1
The Silencer Software
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.1.4.2
Cell phone Software
1 day
6/16/2010 8:00
6/16/2010 17:00
1.5.4.2
Software
30 days
6/25/2010 8:00
8/5/2010 17:00
1.5.4.2.1
Software Design
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.1
The Silencer
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.1.1
Design GUI Interface
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.1.2
Design Signal-Sending Algorithm
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.2
Cell phone
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.2.1
Design GUI Interface
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.2.2
Design Signal-Handling Algorithm
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.2.3
Design Call-Blocking Algorithm
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.1.2.4
Specify exception numbers
10 days
6/25/2010 8:00
7/8/2010 17:00
1.5.4.2.2
Software Development
10 days
7/9/2010 8:00
7/22/2010 17:00
Page 74/84
CS 410 Red
SILENCER
7/26/2016
1.5.4.2.2.1
The Silencer
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.1.1
Develop GUI Interface
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.1.2
Develop Signal-Sending Algorithm
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.2
Cell phone
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.2.1
Develop GUI Interface
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.2.2
Develop Signal-Handling Algorithm
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.2.2.3
Develop Call-Blocking Algorithm
10 days
7/9/2010 8:00
7/22/2010 17:00
1.5.4.2.3
Software Testing
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.1
The Silencer
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.1.1
Test GUI Interface
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.1.2
Test Signal-Sending Algorithm
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.2
Cell phone
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.2.1
Test GUI Interface
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.2.2
Test Signal-Handling Algorithm
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.2.3.2.3
Test Call-Blocking Algorithm
10 days
7/23/2010 8:00
8/5/2010 17:00
1.5.4.3
User Documentation
30 days
8/6/2010 8:00
9/16/2010 17:00
1.5.4.3.1
Installation Guide
20 days
8/6/2010 8:00
9/2/2010 17:00
1.5.4.3.2
User Manual
30 days
8/6/2010 8:00
9/16/2010 17:00
1.5.4.4
Implementation
14 days
9/17/2010 8:00
10/6/2010 17:00
1.5.4.4.1
Setup Prototype for Demo
2 days
9/17/2010 8:00
9/20/2010 17:00
1.5.4.4.2
Production Readiness Test
12 days
9/21/2010 8:00
10/6/2010 17:00
Page 75/84
CS 410 Red
SILENCER
7/26/2016
9.6 Risk Management Plan (Reda)
Our biggest risk in this project is the “workarounds”, or the fact that teenagers will try to get into the
box installed under the driver seat and trying disabling our system. They can try to steal the key and
make a copy for instance, that way whenever they use the car, it is going to be easy to open the box,
disable Bluetooth transmitter or unplug the power wire, and therefore have full control over their cell
phone while driving.
Another scenario is the fact that teenagers can just break the lock in order to get to the box, but this
is going to be extremely hard since the box we are going to provide is going to be very secure and be
very hard to break into. Moreover, in addition to the key, the box is going to require a password to open
it. Of course, if a teenager watches one of their parents open it, they can just get the password also, so
the parents have to be careful and make sure they do not do that in their children’s presence.
Our moderate risks include the fact that competition is solving the problem first. “The cell coach” is
Page 76/84
CS 410 Red
SILENCER
7/26/2016
out most direct competitor. It consists of a device installed in the car that starts beeping louder and
louder when the driver starts talking on their cell phone, to the point where it becomes so loud that the
driver will just have to hang up and not use their phone. This device though, does not prevent text
messaging. Our product is going to be much better since the only outgoing call it is going to enable is
911. The receipt and sending of text messages is simply not going to be allowed. Therefore “the Silencer”
is going to be much more efficient, sophisticated and harder to disable than “the cell coach”.
Security problems with Bluetooth are also an issue, but nowadays almost every single cell phone is
Bluetooth enabled. So the fact that the Silencer uses Bluetooth is not going to be a special case of
Bluetooth security to worry much about.
Another risk is the fact that customers might be hesitating to buy the Silencer because they do not
want to install the secured box under their seat. That is why our team will provide installation manuals
describing easy installation steps. Phones numbers of installation professionals in different areas are
going to be provided, and since the installation is far from complicated, it won’t be costly.
As you can see on the risk matrix, one of the other risks we have to take into consideration is the fact
that not a lot of customers might be attracted to our product. Thus we are going to have to use an
effective marketing campaign on the internet and on the media (television, radio …). Our statistics on car
crashes and distractions that might cause them, especially the cell phone related ones, should help us in
attracting customers and getting parents to act wiser and protect their teenage children by buying our
product.
Finally, dependency on cell phone companies will be a significant risk. However, our team is going to
work on this with the largest cell phone manufacturers in the market, and the fact that a lot of phones
are very popular and come free or at discounted prices with different plans, should make our task easier.
Therefore our team will develop the software tailored towards the most popular cell phone brands.
Page 77/84
CS 410 Red
SILENCER
7/26/2016
9.7 Evaluation Plan (Duc)
The four phases of the project will have to be evaluated constantly. Without this constant evaluation
our project will never reach its goal. We will be evaluating based on our milestones. There will need to
be weekly meetings in order to evaluate the success of our project. These meetings will allow the group
to discuss the progress, success and failures of the project. For phases 0 and 1 the meeting will be based
on the opinions of the group. The group receives assistance from Mrs. Brunelle (CS 410 & 411 instructor),
Dr. Olariu (wireless expert), Dr. Weigle (wireless expert), and Dr. Zeil (software design consultant). They
will help our group make sure that we stay on track. The team will go over the success of the project to
date. The same applies to weekly evaluation intervals. The phase 2 and phase 3 mid-phase evaluations
will be determined from WBS, and evaluation will be scheduled at a weekly meeting just as with the
phase 0. Before entering a given phase, the evaluation plan will be examined and updated as needed to
reflect any changes caused by previous phases.
During our project life cycle we will be constantly evaluating ourselves to make sure we meet the
deadline for all of the deliverables. The team will also be monitoring to make sure that we are under our
budget for the project’s life.
Page 78/84
CS 410 Red
SILENCER
7/26/2016
Phase Chart
The following chart shows the deliverables that will be evaluated at the beginning of the phase,
during the phase, and the end of the phase.
Phase 0
Phase Begin
Evaluation
Presentation I
Project Concept
SBIR I
Phase 1
Phase 2
Prototype
Final Production
Specifications
Product Description
Paper
Management plan
Prototype Product
Specification
Phase 3
Production Plan
Personnel plan
Marketing plan
Organization
Chart
Competition
Matrix
Risk Matrix
Phase Mid
Evaluation
Presentation II
Feasibility
WBS
MFCD
Presentation III
Milestone
Planning
Financial Plan
Phase End
Evaluation
Prototype
Development
Environment
Requirements
User Manual
Completed Budget
Prototype Test
Plan/Procedures
Marketing Plan
Test Plan
Online Support
1st Prototype
Demonstration
Final Prototype
Demonstration
Presentation IV
Project Approval
User's Manuals
Positive feedback
Project Webpage
Project Webpage
SBIR I
SBIR II
Figure 1
Working Product
Model
Phase Chart
Page 79/84
Return on
Investment
CS 410 Red
SILENCER
7/26/2016
Here are things that we will do to evaluate each phase of the project:
 Design Reviews
 Code Reviews
 Unit Testing
 Integration Testing
9.7.1
Design Reviews
This is the primary evaluation activity of Phase 0. The purpose of review is to carefully understand
and analyze design. We don’t want any important design features to be forgotten. We want to make sure
that the Silencer will actually help the teenage driver safer. We will make sure that no distractions will
be created by the cell phone while the teenager is driving. We want to make sure that there are no
loopholes that the driver can take advantage of, i.e. finding a way to get around the software and talk
while driving.
The design will be reviewed weekly by the team member. There are many important scenarios that
the users could experience while using our Silencer. The team members will discuss and try to find those
scenarios and make sure that our product will work well under those scenarios. The preparation of the
review will be send well in advance by email to the group reviewer so that no time is wasted during the
meeting. The group members will make sure that they have well understood the whole development
before the review session. This will help us to make most efficient use of our time.
9.7.2
Code Reviews
Code reviews will be pertaining to software requirements. The code reviews will occur at various
stages throughout the implementation stage of the project. Similar to the design reviews, code reviews
will be a group wide review of the code being used by all parties involved in the milestone/deliverable as
well as any additional parties that may be of use. Following the code review, any errors and/or flaws will
Page 80/84
CS 410 Red
SILENCER
7/26/2016
be corrected and a follow-up code review will be conducted if deemed necessary.
Code review is mainly done for the following purposes:
 If someone else looks at our code or design, they are likely to find mistakes we missed.
 Each team member will be looking at each other’s code so that fewer mistakes are found at testing
time, which will save time.
 We will make sure there is an accurate and up-to-date documentation.
 Team members will learn by reading each other’s code.
 It can be a means of establishing quality metrics, so one can measure the effectiveness of different
quality processes.
 The process of explaining our software to someone else can help us actually review our own
program, rather than just looking at and seeing what we expect or want to see.
 With right code and design reviews we will save time and improve quality over the entire project life
cycle.
9.7.3
Unit Testing
Each functionality of the Bluetooth transceiver and the cell phone software will be tested to make
sure that they do what they suppose to. The developer of functionality will have a responsibility to
create test cases and use them to test that functionality. That functionality will also be double-checked
by another member of the team for quality assurance.
9.7.4
Integration Testing
In the integration testing, we want to make sure that the cell phone software will work with the
Bluetooth transceiver, i.e., the cell phone software is able to receive the signal sent from the Bluetooth
transceiver and switch to silent mode in a timely manner. This is an important test because, even though
each piece works well individually, when we put them together problems may arise.
Page 81/84
CS 410 Red
SILENCER
7/26/2016
Regression testing: We want to make sure that once the cell phone software or the Bluetooth
transceiver is updated, it is still be able to work with the other pieces.
Recovery testing: The Bluetooth transceiver may lose power from the car. We want to make
sure that no matter how many times the power source is lost, the transceiver is still able to boot up and
work correctly once the power source comes back.
Security testing: Because Bluetooth is used as a means of communication between the cell
phone and the transceiver, we want to make sure that our software is secured, that no intruder will be
able to hack into the phone via Bluetooth connection.
Performance testing: This is where the performance requirements are checked. These may
include the size of the software when installed, the amount of main memory it requires, and the
response time. Because the cell phone has limited battery power, we also need to make sure that the
software will not consume too much power.
Alpha and Beta testing: This is where the software is released to the actual end users. The
initial alpha release will be done at ODU by our team members. Once the application has passed through
the alpha phase, a beta release, possibly incorporating changes necessitated by the alpha phase, can be
made to larger more representative stores before the final release is made to all stores. We will ask the
members of the local Parent-Teacher Association (PTA) to test our Beta product because we feel they are
already predisposed to caring significantly about their children’s lives. .
Page 82/84
CS 410 Red
SILENCER
7/26/2016
From these tests and polls, we will evaluate the usability and effectiveness of our product. The
testing will also identify aspects of our product that can be improved. The member of the PTA will gain
an appreciation for the benefits our product will provide and they will also help us to market the
Silencer to other parents who did not join the PTA.
Beta testing plan:
The following will be tested:
 Product’s functionality
 Product’s user-friendliness
 User documentation
Each beta tester will receive the following:
 Bluetooth transceiver
 Cell phone software
 User Manual
 Basic instructions
Product functionality
 While the teen is driving, his/her cell phone will be switched to either silent or vibrate mode
depending on the parent’s choice.
 All calls will be forwarded to voice mail
 The software will be secured so that hackers cannot use the Bluetooth connection to intrude onto
the cell phone.
Page 83/84
CS 410 Red
SILENCER
7/26/2016
Product’s user-friendliness
 Due to the limitation of the cell phone, power consumption and performance issue, we will use Text
user interface (TUI) in stead of Graphical user interface (GUI). However, we will make sure that our
TUI is easy to used
 It will have a user friendly help menu
User documentation will contain:
 An instruction on how to install the Bluetooth transceiver and the software on the cell phone
 An instruction on how to use the software
 An instruction on how to configure the Bluetooth transceiver remotely by using the cell phone
 Common problems and troubleshooting
 Guaranty information.
Page 84/84