Professional Documents
Culture Documents
Pugh Matrix Article 1 (146558375)
Pugh Matrix Article 1 (146558375)
Pugh Matrix Article 1 (146558375)
Team 1
Aaron Griggs
Christine Adelfio
Louis Lovas
Marvin Mondesir
Page 1 of 18
Page 2 of 18
Table of Contents
Table of Contents ............................................................................... 2
Need................................................................................................... 3
Stakeholders ...................................................................................... 3
Requirements ..................................................................................... 3
Drivers ..................................................................................... 3
Passengers ............................................................................... 3
Installers ................................................................................. 3
Maintainers .............................................................................. 4
Navigation System Manufacturers ............................................ 4
Fleet Managers ......................................................................... 4
Content Providers .................................................................... 4
Emergency Responders ............................................................ 4
Acceptance Criteria ............................................................................ 5
Concept Definition and Selection ........................................................ 5
Alternatives.............................................................................. 5
Pugh Matrix .............................................................................. 5
Selection and Rationale ............................................................ 5
Context Diagram (External Systems Diagram) ................................... 6
Use Case Scenarios ............................................................................ 7
Profile Management ................................................................. 7
Hazardous Weather .................................................................. 8
Traffic Jams.............................................................................. 9
Maintenance and Diagnostic................................................... 10
Installation ............................................................................ 11
Quality Function Deployment ........................................................... 12
Objective Hierarchy.......................................................................... 13
System Requirements ...................................................................... 14
Functional Requirements ....................................................... 14
Input Requirements .......................................................... 14
Output Requirements........................................................ 14
Interface Requirements..................................................... 15
System-wide Requirements.................................................... 15
Suitability Requirements ................................................... 15
Physical Requirements ...................................................... 15
Technology Requirements ................................................. 16
Cost Requirements ........................................................... 16
Standards and Protocols.................................................... 16
Schedule Requirements by Phase ....................................... 16
Supportability and Maintenance ......................................... 16
Functional Architecture .................................................................... 16
Risks ................................................................................................ 18
Page 2 of 18
Page 3 of 18
Need
People need to see and understand real-time traffic conditions. This opportunity provides drivers
with recommended routes to avoid unsafe road conditions, whether it is weather related or
congestion from an accident. The end result: a more efficient commute and an overall
happier, safer driver.
Stakeholders
The following table represents the active and passive stakeholders (bold are the customers):
Active Passive
Drivers Navigation System
Manufacturers
Installers Fleet Managers
Maintainers Emergency Responders
Content Providers*
* Providers of weather, road conditions, routes data
Requirements
This section contains the requirements for all the identified stakeholders.
To gather requirements, interviews were conducted with drives. The goal was to understand
how drivers cope with unsafe road conditions, the factors that affect getting to destinations
given some standard conditions and some of their feelings as they drive under these conditions.
Note in a real environment, many interviews would be conducted with drivers in person and via
the Internet and phone. Sample of people would be taken from automobile membership
organizations (i.e., AAA) or consumer panel survey participants.
Outcome is to determine whether the responses from interviewees justify the need for a real-
time traffic condition notification system.
Drivers
Want a safe commute
Want an efficient commute
Want to understand why traffic is backed up
Want alternative routes
Want timely, accurate information on road conditions
Want low (e.g. $20) monthly cost
Passengers
Want a safe commute
Want an efficient commute
Want to understand why traffic is backed up
Installers
Easy to install
Page 3 of 18
Page 4 of 18
Maintainers
Easy to repair
Fleet Managers
Want efficient use of fleet vehicles
Want to keep operators safe while on the road
Lower insurance costs
Content Providers
Want to reach a larger audience
Emergency Responders
Want to detour traffic during accidents or hazardous road conditions
Want timely, accurate information
Page 4 of 18
Page 5 of 18
Acceptance Criteria
The following criteria were defined to influence the implementation of the system:
Provide the driver with configurable, relevant up to date information.
Easy and safe to use while driving.
Reasonable monthly cost for basic service—$10 per month.
Alternatives
Four concepts were defined:
Radio – Broadcast through radio air waves.
Cell phone – Audio and text service that is delivered through cellular networks.
Traffic signs – Text based digital traffic signs.
Add-on service to existing navigation systems (e.g., Garmin, TomTom).
Pugh Matrix
Page 5 of 18
Page 6 of 18
Installers
Installation Alerts
Configurations
Log Updates
Modes
Profile Management Profile Management
Location Road Conditions
Real-time Traffic
Road Conditions Monitoring System Weather Conditions Content
Drivers
Alternative Route Traffic Conditions Providers
Service Requests Service Requests
Configurations
Service Alerts
Log Updates
Modes
Maintainers
Page 6 of 18
Page 7 of 18
Profile Management
The profile management use case is shown below. The system manages the content providers
and drivers’ preferences through profiles.
Page 7 of 18
Page 8 of 18
Hazardous Weather
The hazardous weather use case is shown below. The system receives weather and road
condition information from content providers. When road conditions affect the driver based on
the driver’s location, the driver is notified. The driver then requests an alternative route to
avoid the traffic jam.
Location Notification
Acknowledgement
Page 8 of 18
Page 9 of 18
Traffic Jams
The traffic jams use case is shown below. The system receives traffic information from content
providers. When traffic conditions affect the driver based on the driver’s location, the driver is
notified. The driver then requests an alternative route to avoid the traffic jam.
Location Notification
Acknowledgement
Page 9 of 18
Page 10 of 18
Service Request
Acknowledgement
Service Alert
Acknowledgement
Driver or
Maintainers Traffic Monitoring System Content Provider
Page 10 of 18
Page 11 of 18
Installation
The installation use case is shown below. The system receives an installation request from a
driver. The request is forwarded to the installers. The installers install and configure the
system in installation mode returning the system to normal operation after installation
completion.
Installation Request
Acknowledgement
Installation Alert
Acknowledgement
Driver or
Installers Traffic Monitoring System Content Provider
Page 11 of 18
Page 12 of 18
Amount of Information
Objectives (DDPs)
Information Update
Maintenance Time
Configuraiton Time
5 High, 1 Low
Responsive Time
Importance:
Installation Time
Number of user
Signal Strength
Size of device
Warning/Error
Subscription
Interpolation
Repair Time
Associated
Parts Cost
Amount of
Amount of
Displayed
screens
screen
Rate
WHATs - Stakeholder Requirements
Installation ++ ++ +++ ++ ++ ++ ++ ++ 3
Repair ++ ++ ++ +++ ++ - ++ ++ 3
Customizable ++ + 3
Efficienct commute ++ + + + + 4
Reduce congestion ++ ++ 2
Key
Strong Positive Correlation +++
Medium Positive Correlation ++
Weak Positive Correlation +
No correlation
Strong Negative Correlation -
Medium Negative Correlation --
Weak Negative Correlation ---
Page 12 of 18
Page 13 of 18
Objective Hierarchy
O perational O bjectives
Availability O bjectives
S tandards and P rotocols
MT B F 1 – 2 min
C ompliance with F C C
R egulations for W ireles s
D evices Maint. T ime < 30 min
between 2am and 3am
O peration within S ame S td. &
P rotocol of Nav S ys . R epair T ime < 30 min
(brand, model T B D )
Page 13 of 18
Page 14 of 18
System Requirements
The functional requirements in this section were derived from the use cases and QFD.
Functional Requirements
Input Requirements
The system shall accept an activation request from a driver.
The system shall accept an activation request from a content provider.
The system shall accept a profile modify request from a driver.
The system shall accept a profile modify request from a content provider.
The system shall accept a termination request from a driver.
The system shall accept a termination request from a content provider.
The system shall accept a location notification from a driver.
The system shall accept a weather alert notification from a content provider.
The system shall accept a road conditions notification from a content provider.
The system shall accept a weather hazard notification acknowledgement from a driver.
The system shall accept an alternative route request from a driver.
The system shall accept a traffic alert notification from a content provider.
The system shall accept a traffic conditions notification from a content provider.
The system shall accept a traffic jam notification acknowledgement from a driver.
The system shall accept a service request from a driver.
The system shall accept a service request from a content provider.
The system shall accept a service alert acknowledgement from a maintainer.
The system shall accept a diagnostics mode request from a maintainer.
The system shall accept a self-test request from a maintainer.
The system shall accept a self-test request from an installer.
The system shall accept a configuration change request from a maintainer.
The system shall accept a configuration change request from an installer.
The system shall accept a log update request from a maintainer.
The system shall accept a log update request from an installer.
The system shall accept a normal mode request from a maintainer.
The system shall accept a normal mode request from an installer.
The system shall accept a normal operation notification acknowledgement from a driver.
The system shall accept a normal operation notification acknowledgement from a content
provider.
The system shall accept an installation request from a driver.
The system shall accept an installation request from a content provider.
The system shall accept an installation alert acknowledgement from an installer.
The system shall accept an installation mode request from an installer.
Output Requirements
The system shall provide an activation response to a driver.
The system shall provide an activation response to a content provider.
The system shall provide a profile modify response to a driver.
The system shall provide a profile modify response to a content provider.
The system shall provide a termination response to a driver.
The system shall provide a termination response to a content provider.
The system shall provide a location acknowledgement to a driver.
The system shall provide a weather alert notification acknowledgement to a content
provider.
The system shall provide a road conditions notification acknowledgement to a content
provider.
The system shall provide a weather hazard notification to a driver.
Page 14 of 18
Page 15 of 18
The system shall provide an alternative route response to a driver.
The system shall provide a traffic alert notification acknowledgement to a content
provider.
The system shall provide a traffic conditions notification acknowledgement to a content
provider.
The system shall provide a traffic jam notification to a driver.
The system shall provide a service acknowledgement to a driver.
The system shall provide a service acknowledgement to a content provider.
The system shall provide a service alert to a maintainer.
The system shall provide a diagnostics mode response to a maintainer.
The system shall provide a self-test response to a maintainer.
The system shall provide a self-test response to an installer.
The system shall provide a configuration change response to a maintainer.
The system shall provide a configuration change response to an installer.
The system shall provide a log update acknowledgement to a maintainer.
The system shall provide a log update acknowledgement to an installer.
The system shall provide a normal mode response to a maintainer.
The system shall provide a normal mode response to an installer.
The system shall provide a normal operation notification to a driver.
The system shall provide a normal operation notification to a content provider.
The system shall provide an installation acknowledgement to a driver.
The system shall provide an installation acknowledgement to a content provider.
The system shall provide an installation alert to an installer.
The system shall provide an installation mode response to an installer.
Interface Requirements
The navigation system (specific brand and model TBD) shall provide the system external
interfaces.
The system shall integrate with the navigation system (specific brand and model TBD)
internal interfaces.
System-wide Requirements
Suitability Requirements
Accessing the required information shall take less than 30 seconds and less than 4 user
screens.
The number of items per screen shall be such that it takes the user less than 5 seconds
to see all of them.
The system shall be easily configured within 30 seconds for driver use.
The system shall have a MTBF of greater than 1 year. The design goal is 2 years.
Failure is defined to be a complete inability to provide traffic updates.
All system warnings or error messages shall fit within system screen.
Response time from button select to screen output shall be less than 3 seconds.
User set-up time shall take less than 10 minutes.
Maintenance on system shall occur between 2am and 3am daily and shall take less than
one-half hour.
Repair time of system unit is limited to 30 minutes before user is notified that repair time
must be extended.
Physical Requirements
The system shall operate within the physical specifications of the navigation system
(specific brand and model TBD).
Page 15 of 18
Page 16 of 18
Technology Requirements
The road, traffic, and weather conditions for the requested location shall be current as of
the previous 1 minute.
Cost Requirements
The system operational costs shall be $10 a month through a subscription plan.
Functional Architecture
Shown on the next page is the functional architecture using an IDEF0 A1 diagram
Page 16 of 18
Page 17 of 18
Page 17 of 18
Page 18 of 18
Risks
Primary
Item Severity Risk Description Impact Mitigation Plan
1 High Timeliness of content provider Performance Perform modeling and simulation
data of response times from content
provider systems. Prototype with
content providers.
2 Medium Development of common set of Maintanence Involve maintenance team in
diagnostic tools to maintain technical discussions with
system and co-operability with selected navigation system
content provider and selected makers and content provider.
navigation systems within
allocated time.
Page 18 of 18