Silver Bullet<Company Name>
Modernization of Relay Equivalence Drawing System
Risk List
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
Revision History
Date
Version
Description
Author
12/10/2004
0.1
Initial Revision
David Kerstanski
12/12/2004
1.0
First Revision to be reviewed
David Kerstanski
1/19/2005
1.1
Updated for status report
David Kerstanski
<Company Name>, 2017
Page 2 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
Table of Contents
1.
2.
Introduction
6
1.1
1.2
1.3
1.4
1.5
6
6
6
6
6
Purpose
Scope
Definitions, Acronyms, and Abbreviations
References
Overview
Risks
2.1
2.2
2.3
2.4
2.5
2.6
6
Meeting Time
2.1.1 Risk Magnitude or Ranking
2.1.2 Description
2.1.3 Impacts
2.1.4 Mitigation Strategy
2.1.5 Trigger
2.1.6 Contingency Plan
Clear Information
2.2.1 Risk Magnitude or Ranking
2.2.2 Description
2.2.3 Impacts
2.2.4 Mitigation Strategy
2.2.5 Trigger
2.2.6 Contingency Plan
Workflow Documentation
2.3.1 Risk Magnitude or Ranking
2.3.2 Description
2.3.3 Impacts
2.3.4 Mitigation Strategy
2.3.5 Trigger
2.3.6 Contingency Plan
Placement Algorithm Rework
2.4.1 Risk Magnitude or Ranking
2.4.2 Description
2.4.3 Impacts
2.4.4 Mitigation Strategy
2.4.5 Trigger
2.4.6 Contingency Plan
.dxf Understanding
2.5.1 Risk Magnitude or Ranking
2.5.2 Description
2.5.3 Impacts
2.5.4 Mitigation Strategy
2.5.5 Trigger
2.5.6 Contingency Plan
.dxf Testing
2.6.1 Risk Magnitude or Ranking
2.6.2 Description
2.6.3 Impacts
2.6.4 Mitigation Strategy
2.6.5 Trigger
2.6.6 Contingency Plan
<Company Name>, 2017
6
6
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
7
7
7
7
7
7
7
8
8
8
8
8
8
8
8
8
8
8
8
8
8
8
9
9
9
Page 3 of 15
<Project Name>
Risk List
2.7
2.8
2.9
2.10
2.11
2.12
2.13
2.14
Version:
1.1
Date: 1/19/05
Symbol Database Access
2.7.1 Risk Magnitude or Ranking
2.7.2 Description
2.7.3 Impacts
2.7.4 Mitigation Strategy
2.7.5 Trigger
2.7.6 Contingency Plan
.dxf Library Structures
2.8.1 Risk Magnitude or Ranking
2.8.2 Description
2.8.3 Impacts
2.8.4 Mitigation Strategy
2.8.5 Trigger
2.8.6 Contingency Plan
Border Implementation
2.9.1 Risk Magnitude or Ranking
2.9.2 Description
2.9.3 Impacts
2.9.4 Mitigation Strategy
2.9.5 Trigger
2.9.6 Contingency Plan
Input File Format
2.10.1 Risk Magnitude or Ranking
2.10.2 Description
2.10.3 Impacts
2.10.4 Mitigation Strategy
2.10.5 Trigger
2.10.6 Contingency Plan
CAAPE Integration
2.11.1 Risk Magnitude or Ranking
2.11.2 Description
2.11.3 Impacts
2.11.4 Mitigation Strategy
2.11.5 Trigger
2.11.6 Contingency Plan
.dxf Versions
2.12.1 Risk Magnitude or Ranking
2.12.2 Description
2.12.3 Impacts
2.12.4 Mitigation Strategy
2.12.5 Trigger
2.12.6 Contingency Plan
Implementation Language
2.13.1 Risk Magnitude or Ranking
2.13.2 Description
2.13.3 Impacts
2.13.4 Mitigation Strategy
2.13.5 Trigger
2.13.6 Contingency Plan
CAAPE Understanding
2.14.1 Risk Magnitude or Ranking
2.14.2 Description
2.14.3 Impacts
<Company Name>, 2017
9
9
9
9
9
9
9
9
9
9
9
9
9
10
10
10
10
10
10
10
10
10
10
10
10
10
10
11
11
11
11
11
11
11
11
11
11
11
11
11
11
11
12
12
12
12
12
12
12
12
12
12
12
Page 4 of 15
<Project Name>
Risk List
2.15
2.16
2.17
2.18
2.19
2.20
Version:
1.1
Date: 1/19/05
2.14.4 Mitigation Strategy
2.14.5 Trigger
2.14.6 Contingency Plan
Hardware/Software Cross References
2.15.1 Risk Magnitude or Ranking
2.15.2 Description
2.15.3 Impacts
2.15.4 Mitigation Strategy
2.15.5 Trigger
2.15.6 Contingency Plan
Hardware Requirements
2.16.1 Risk Magnitude or Ranking
2.16.2 Description
2.16.3 Impacts
2.16.4 Mitigation Strategy
2.16.5 Trigger
2.16.6 Contingency Plan
User Manual/Online Help
2.17.1 Risk Magnitude or Ranking
2.17.2 Description
2.17.3 Impacts
2.17.4 Mitigation Strategy
2.17.5 Trigger
2.17.6 Contingency Plan
Windows Printing
2.18.1 Risk Magnitude or Ranking
2.18.2 Description
2.18.3 Impacts
2.18.4 Mitigation Strategy
2.18.5 Trigger
2.18.6 Contingency Plan
Intermediate Representation of Input file
2.19.1 Risk Magnitude or Ranking
2.19.2 Description
2.19.3 Impacts
2.19.4 Mitigation Strategy
2.19.5 Trigger
Cell Rendering
2.20.1 Risk Magnitude or Ranking
2.20.2 Description
2.20.3 Impacts
2.20.4 Mitigation Strategy
2.20.5 Trigger
2.20.6 Contingency Plan
<Company Name>, 2017
12
12
12
12
12
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
13
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
14
15
15
15
15
15
15
15
Page 5 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
Risk List
1.
Introduction
1.1
Purpose
The purpose of this document is to list the current risks that the team needs to address. The risks are
described and strategies for dealing with the risks are also documented.
1.2
Scope
The risks that are listed are those that deal with any aspect of the project, either a risk internal to the
development team, or a risk that involves working with the project sponsor.
1.3
Definitions, Acronyms, and Abbreviations
CAAPE - The system that the Relay Drawing program receives its input from.
1.4
References
none
1.5
Overview
The Risk List is a compilation of all current risks that have been established by the team. The Magnitudes
of the risks range from 1 to 5 with 1 being the lowest risk and 5 being the highest risk.
2.
Risks
2.1
Meeting Time
2.1.1
Risk Magnitude or Ranking
1
2.1.2
Description
Given current class schedules it is hard to find meeting times for all team members.
2.1.3
Impacts
This risk may hinder the team’s ability to discuss important topics related to the project.
2.1.4
Mitigation Strategy
The team can have meetings with a few members and use the meeting minutes and other communication
channels to fill in the absent team members.
2.1.5
Trigger
The trigger will be if the team is not finding enough time to meet together.
2.1.6
Contingency Plan
The team will not meet as a whole and team members with topics to discuss can meet with a part of the
team.
2.2
Clear Information
2.2.1
Risk Magnitude or Ranking
3
<Company Name>, 2017
Page 6 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.2.2
Description
The initial requirements are not fully understood as it is early in the process, if one person elicits
requirements for an aspect of the system, that information must be conveyed correctly to the rest of the
team.
2.2.3
Impacts
Information regarding requirements or any other aspect of the system may be misunderstood and will cause
extra time and resources to be used to correct the misunderstandings
2.2.4
Mitigation Strategy
The team will need to use three way communication to ensure that all information is understood.
2.2.5
Trigger
The team members note that there is a lack of communication
2.2.6
Contingency Plan
The team leader will need to interfere and make sure communication lines stay open.
2.3
Workflow Documentation
2.3.1
Risk Magnitude or Ranking
3
2.3.2
Description
The information necessary to create a complete and correct Workflow Document is not fully understood
and has not been fully elicited. The document would be a representation of the current ALSTOM process.
This must be understood in order to create the new application.
2.3.3
Impacts
If the current workflow process is not understood it will be much more difficult to develop a system that
will be used within that process.
2.3.4
Mitigation Strategy
Create a workflow diagram that will be reviewed by the project sponsors. Revisions will be made to the
diagram, until a time at which the team has gained a solid understanding of the current workflow process.
2.3.5
Trigger
A misunderstanding of the flow is realized.
2.3.6
Contingency Plan
The team may try an alternate way of representing the workflow diagram, such as a textual representation,
to better understand the workflow steps.
2.4
Placement Algorithm Rework
2.4.1
Risk Magnitude or Ranking
4
2.4.2
Description
Knowledge of the current placement algorithm is not complete. The algorithm may need to be reworked
and must first be understood to determine if a new algorithm is necessary. Impacts
<Company Name>, 2017
Page 7 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.4.3
Impacts
In order to better utilize page space, as well as better integrate the placement algorithm into the new system
it will be necessary to rework the current algorithm.
2.4.4
Mitigation Strategy
Research on placement algorithms has been assigned. Research into the current algorithm must also be
done.
2.4.5
Trigger
The current algorithm can not be understood.
2.4.6
Contingency Plan
The team will need to assign more resources to algorithm rework.
2.5
.dxf Understanding
2.5.1
Risk Magnitude or Ranking
3
2.5.2
Description
The .dxf file format has not been used or worked with by any team members and must be researched to
gain a greater understanding of the file format. The output of new application will be .dxf and as such the
file format must be understood.
2.5.3
Impacts
The .dxf file format is the key output format and without a good understanding of the format the output
files can not be created correctly.
2.5.4
Mitigation Strategy
A team member has been assigned to research this topic.
2.5.5
Trigger
Misunderstanding of dxf files are limiting team project progression.
2.5.6
Contingency Plan
ALSTOM will be contacted to gain more knowledge on the .dxf topics.
2.6
.dxf Testing
2.6.1
Risk Magnitude or Ranking
5
2.6.2
Description
There may be difficulty in testing newly created .dxf files if a CAD system is necessary. The team maynot
always have access to such a system and must research alternatives for viewing .dxf files.
2.6.3
Impacts
An application that allows for viewing of .dxf files will need to be found and the best way to utilize the
application will need to be determined.
<Company Name>, 2017
Page 8 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.6.4
Mitigation Strategy
A team member has been assigned to research applications that can be used, and to determine if there are
any free applications that can be used to view the .dxf outputs that will be created.
2.6.5
Trigger
.dxf file testing is hindered by lack of ability to view .dxf files.
2.6.6
Contingency Plan
Ask the ALSTOM to purchase a non-expensive commercial package or loan a license to the team.
2.7
Symbol Database Access
2.7.1
Risk Magnitude or Ranking
4
2.7.2
Description
At the current time it is unclear what access the team will have to the current symbol databases and whether
the team will be able to use any part of the database as is.
2.7.3
Impacts
The symbol databases will need to be used in some manner, in order to better understand the creation of the
output drawings.
2.7.4
Mitigation Strategy
Research will need to be done to determine the team’s access level to the symbol database, as well as the
extent of reuse that will be available for the symbol database.
2.7.5
Trigger
The team has no access a dxf symbol library.
2.7.6
Contingency Plan
The team will need to create each of the symbols that will be used within the system.
2.8
.dxf Library Structures
2.8.1
Risk Magnitude or Ranking
3
2.8.2
Description
The .dxf library structure and creation mechanism are not understood by the team and research must be
done in order to determine the effectiveness of using such a library structure.
2.8.3
Impacts
The team will need to have knowledge in the library structure that can be used when creating .dxf files.
The team may need to use libraries to customize output files for specific customers.
2.8.4
Mitigation Strategy
A team member has been assigned to research .dxf related areas.
2.8.5
Trigger
Lack of understanding of the dxf library hinders team progress.
<Company Name>, 2017
Page 9 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.8.6
Contingency Plan
The team will need to ask ALSTOM to provide a better interface to the libraries that the team will need to
utilize.
2.9
Border Implementation
2.9.1
Risk Magnitude or Ranking
4
2.9.2
Description
The design of borders to be placed on the output drawings and their format is not fully understood and must
be researched.
2.9.3
Impacts
Borders will need to be placed around the output drawings and will need to have a mechanism to customize
their information.
2.9.4
Mitigation Strategy
Research must be done to determine the best implementation method for dealing with the borders.
2.9.5
Trigger
Implementation of the borders is not understood and becomes unclear.
2.9.6
Contingency Plan
The borders will be designed in the same manner that they are designed right now, with no modification to
the current process.
2.10
Input File Format
2.10.1 Risk Magnitude or Ranking
5
2.10.2 Description
The current input file descriptions and exactly which files will be used as inputs have not been defined.
The description and the definition of which files will be used is an important part of the application that
must be researched to continue with other aspects of the system. The team will also need to look into
parsing of the files and if there are toolkits that can be used when doing so.
2.10.3 Impacts
The input files are how the teams system will begin its interaction with the ALSTOM systems. The input
files may also become a factor when determining the amount of integration (if any) with the CAAPE
system.
2.10.4 Mitigation Strategy
A team member has been assigned to research file parsing toolkits, as well as researching the current file
formats and their definitions.
2.10.5 Trigger
It is determined that the input files are not being read correctly.
<Company Name>, 2017
Page 10 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.10.6 Contingency Plan
The team will ask ALSTOM to give the team a utility that allows the team to parse input files.
2.11
CAAPE Integration
2.11.1 Risk Magnitude or Ranking
1
2.11.2 Description
Integration with the CAAPE system (depth of integration, methods for integration, interfaces, APIs) are not
understood by the team at the current time and must be researched.
2.11.3 Impacts
The amount of integration with the CAAPE system will determine some requirements and can change the
team’s overall project plan.
2.11.4 Mitigation Strategy
Team member(s) will be assigned to research integration and interfaces with the CAAPE system.
2.11.5 Trigger
Integration is not being address.
2.11.6 Contingency Plan
There will be no integration with CAAPE and the team’s system will run separate from CAAPE.
2.12
.dxf Versions
2.12.1 Risk Magnitude or Ranking
4
2.12.2 Description
The .dxf output files must be saved into various formats, in order to be used in conjunction with a number
of different CAD versions or other .dxf viewing packages. The amount of support in regard to the number
of versions must be researched and documented.
2.12.3 Impacts
The amount of support in regard to the number of versions must be researched and documented. The
differences in the versions may need to be limited in regard to the input and output aspects of the system.
2.12.4 Mitigation Strategy
A team member has been assigned to research the aspects of .dxf files in regard to this project.
2.12.5 Trigger
The dxf files that are created are not created in correct or compatible versions.
2.12.6 Contingency Plan
The team will specify support for only a few versions of .dxf.
<Company Name>, 2017
Page 11 of 15
<Project Name>
Risk List
2.13
Version:
1.1
Date: 1/19/05
Implementation Language
2.13.1 Risk Magnitude or Ranking
2
2.13.2 Description
The team has not set an implementation language, and must elicit the language that will best suit this
system.
2.13.3 Impacts
The implementation language must be set at some point and must be approved by the project sponsors. The
usage of development software such as Microsoft’s Visual Studio must also be approved by project
sponsors.
2.13.4 Mitigation Strategy
The team must research implementation strategies as well as elicit implementation decisions from the
project sponsors.
2.13.5 Trigger
Language choice begins to hinder progress.
2.13.6 Contingency Plan
The team will use the implementation strategy suggested by ALSTOM.
2.14
CAAPE Understanding
2.14.1 Risk Magnitude or Ranking
4
2.14.2 Description
The team will need gain a working knowledge of the CAAPE system that is currently being used by
ALSTOM. This system is used to produce the input files that the team’s system will use.
2.14.3 Impacts
In order to better understand the input files and their format, a better understanding of the CAAPE system
is necessary.
2.14.4 Mitigation Strategy
Team members will be assigned to research the CAAPE system.
2.14.5 Trigger
The CAAPE system is not understood at a point when it is necessary to integrate with or use CAAPE.
2.14.6 Contingency Plan
Ask ALSTOM for more documentation on the CAAPE system and/or have more one on one’s with
ALSTOM to better learn CAAPE.
2.15
Hardware/Software Cross References
2.15.1 Risk Magnitude or Ranking
1
<Company Name>, 2017
Page 12 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.15.2 Description
The Hardware/Software Cross References are not fully understood and must be researched to determine the
extent that the new system will have to account for them and how they will integrate into the process.
2.15.3 Impacts
The team will need to determine if this risk is an issue and if it will have to be dealt with at all.
2.15.4 Mitigation Strategy
The team will need to talk with the project sponsor to determine what impact, if any, this risk will have.
2.15.5 Trigger
When this issues begins to hinder the project.
2.15.6 Contingency Plan
Begin research into the cross reference topic and talk with ALSTOM more regarding how to integrate it
into the system.
2.16
Hardware Requirements
2.16.1 Risk Magnitude or Ranking
2
2.16.2 Description
The team does not fully know all of the hardware requirements and what the full range of hardware
compatibility must be.
2.16.3 Impacts
Hardware requirements will need to be understood once implementation begins in order to be able to
support the necessary systems that ALSTOM will set.
2.16.4 Mitigation Strategy
Elicit and documents hardware requirements during the requirements gathering process.
2.16.5 Trigger
Trigger when the requirements become unclear.
2.16.6 Contingency Plan
Have ALSTOM set the hardware requirements for this project.
2.17
User Manual/Online Help
2.17.1 Risk Magnitude or Ranking
3
2.17.2 Description
The creation of user manuals and online help functionality may be resource intensive and will need to be
looked into.
2.17.3 Impacts
The project plan and schedule may need to be reevaluated based upon the amount of resources that are
needed for the creation of these artifacts.
<Company Name>, 2017
Page 13 of 15
<Project Name>
Risk List
Version:
1.1
Date: 1/19/05
2.17.4 Mitigation Strategy
The team will need to incorporate time into their project plans to deal with the creation of these artifacts as
well as beginning to think about information to place in these artifacts.
2.17.5 Trigger
When manual/Help file creation is not being done on schedule.
2.17.6 Contingency Plan
Adjust project plan to place more resources into creating the User Manual/Online Help portions of the
project.
2.18
Windows Printing
2.18.1 Risk Magnitude or Ranking
5
2.18.2 Description
The System must be able to print drawings by using windows native printing environment.
2.18.3 Impacts
One of the major requirements is printing and therefore this topic needs to be addressed at all iterations. If
printing can not be done then the project can not be completed.
2.18.4 Mitigation Strategy
A team member has been assigned to research the printing topic.
2.18.5 Trigger
Triggered when printing can not be done correctly within the confines of the project scope.
2.18.6 Contingency Plan
Add more resources to work on printing and integrating printing into the system.
2.19
Intermediate Representation of Input file
2.19.1 Risk Magnitude or Ranking
5
2.19.2 Description
The System must be able to accurately represent the data within the input files after it is parsed.
2.19.3 Impacts
The grid creation can not take place until there is an intermediate representation in place. The printing and
dxf creations will rely on the internal representation.
2.19.4 Mitigation Strategy
Two team members have been assigned to research this topic.
2.19.5 Trigger
This risk will be triggered if it begins to hinder progress.
<Company Name>, 2017
Page 14 of 15
<Project Name>
Risk List
2.20
Version:
1.1
Date: 1/19/05
Cell Rendering
2.20.1 Risk Magnitude or Ranking
4
2.20.2 Description
The cells that are read in from the dxf library must be rendered to be printed
2.20.3 Impacts
The cell rendering must take place in order to print the internal representations of the cells.
2.20.4 Mitigation Strategy
Three team members have been assigned to work on this area.
2.20.5 Trigger
Triggered when cells are not being rendered and it is causing progress to be halted or slowed.
2.20.6 Contingency Plan
Cell rendering will be worked on with more resources instead of lower risks area.
<Company Name>, 2017
Page 15 of 15