Priority defaults to 0 when an Issue is initiated.
The Cognizant engineer(s) assess the priority and assign a value ranging from 1-5, according to the table below,
when the Issue is in Open or Investigation State.
During HIT review of the Issue the priority may be changed.
Assessment of priority is from the perspective of the end user of a fielded product
(i.e. if the issue is not resolved prior to Software Baseline Verification Testing (SBVT)).
Priority |
Description |
0 |
Not Prioritized (default) |
1 |
Safety/Prevents Mission
- Prevent the accomplishment of an operational or mission essential capability or
- b. Jeopardize safety, security, or other requirement designated “critical”
|
2 |
Adverse effects/No work-around
- Adversely affect the accomplishment of an operational or mission essential capability and no work-around solution is known (i.e. the mission objective can be met but with a degraded outcome), or
- Adversely affect life cycle support of the system, and no work-around solution is known (i.e. the maintenance objective can be met but with a degraded outcome)
|
3 |
Adverse effects/Work-around
- Adversely affect the accomplishment of an operational or mission essential capability but a work-around solution is known (i.e. the mission objective can be met with a workaround action which was not originally planned), or
- Adversely affect life cycle support of the system, but a work-around solution is known (i.e. the maintenance objective can be met with a workaround action which was not originally planned)
|
4 |
Inconvenience/Annoyance
- Results in user/operator inconvenience or annoyance but does not affect a required operational or mission essential capability, or
- Results in inconvenience or annoyance for development or support personnel, but does not prevent the accomplishment of those responsibilities
|
5 |
Any other effect Document only changes |
6 |
N/A: automatically used if the issue was found in a development build (see Is Developmental selection for further information) |
Blank (not selectable) |
No priority (-1 is stored in the database and the Priority field is not displayed) for issues with a status of Potential Future Design Change. Note: Crew Impact selection is allowed for issues without a priority. |