J-STD-Of 6-1 9 9 5

Page 199

Annex M
Category and priority classifications for problem reporting

(normative)

M.1 Scope

This annex contains requirements for a category and priority classification scheme t o be
applied to each problem submitted t o the corrective action system. This annex is normative
(that is, binding), subject t o the following conditions: 1) these requirements may be tailored,
and 2 ) the developer may use alternate category and priority schemes if approved by the
acquirer.

M.2 Classification by category

The developer shall:

a) Assign each problem in software products t o one or more of the categories in figure 12.
b) Assign each problem in activities to one or more of the activities in figure 1 (shown at
the stan of clause 5).

M-3 Classification by priority

The developer shall assign each problem in software products or activities t o one of the
priorities in figure 13.
 J-STD-0 1 6-1 995
Page 200

Figure 12-Categories t o be used for classifying problems in software products

11 1
Applies if a problem could:

/ a) Prevent the accomplishment of an essential capability

I1
I1 I b) Jeopardize safety, security, or other requirement designated 'critical" A
a) Adversely affect the accomplishment of an essential capability and no work-
around solution is known
b) Adversely affect technical, cost, or schedule risks t o the project or t o life cycle I
1 3 1 a ) Adversely affem the accomplishment of an essential cawbiliry but a work- 1
11 I around solution is known

I b) Adversely affect technical, cost, or schedule risks t o the project or t o life cycle

a] Result in user/operator inconvenience or annoyance but does not affect 3

required operational or mission essential capability