Possible
Risk:
|
Mitigating Action:
|
|
1
|
Component of project not delivered
by group member.
|
Regular meetings to check progress.
Management of deadlines.
|
2
|
Extended learning curve with
on-board network.
|
Simplify the network.
|
3
|
Loss/damage of borrowed equipment
from USM (car, ECU, sensors etc.).
|
Simulate data outputs.
|
4
|
Car unavailable to test system
components.
|
Simulate testing environment e.g.
using a road car.
|
5
|
Wireless communication not feasible.
|
Use on-car storage to transfer data
to off-board systems
|
6
|
Wireless range not high enough to
cover track.
|
Multiple base stations/burst
transmission every lap.
|
7
|
Customer requirements change during
the course of the project.
|
Formal specification agreed upon at
start of project. All changes discussed with customer and approved before
implementation.
|
8
|
Loss of software code.
|
SVN repositories used and adhered to
throughout project.
|
9
|
Loss of documentation (reports
etc.).
|
Make sure everything is saved to
cloud storage.
|
10
|
Damage/loss to equipment (soldering
etc.).
|
Where possible, multiple components
to be bought within same order. Alternative equipment to be identified.
|
11
|
Budget constraints.
|
Research alternative components or
discuss other sources of funding (i.e. USM).
|
12
|
Lead times.
|
Project management to take into
account deadlines for orders, alternative suppliers to be used if required.
|
13
|
PCB complexity too high to be
manufactured in house.
|
Outsource manufacture, taking into
account extended lead times.
|
14
|
Lab space becomes inaccessible due
to fire/flood etc.
|
Re-evaluate project objectives in
discussions with mentor and customer. Video/photos/logbooks to be taken
throughout to show progress.
|
15
|
Off-board software implementation
too complex to develop within timescales.
|
Simplify software objectives.
|
16
|
Complexity of project under or over
estimated.
|
Revise objectives.
|
Sunday, 27 October 2013
Technical Risks
Below is a table that lists all the technical risks associated with the project proposal. Risk in this context is taken to mean any event or action (or inaction) that would jeopardise any project outcomes or significantly impede project progress. Along with the risk, actions have been provided that would be taken to mitigate the effects of the risk.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment