|
|
| (36 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | ==Priorities for classifying problems==
| + | # [[OSEE/ATS/Users Guide/Intro|Getting Started]] |
| − | | + | # [[OSEE/ATS/Users Guide/Views|Views and Editors]] |
| − | {| class="wikitable" border="1"
| + | # [[OSEE/ATS/Users Guide/Usage|Using ATS]] |
| − | |-
| + | # [[OSEE/ATS/Users Guide/Tips|Tips and Tricks]] |
| − | ! Priority
| + | # [[OSEE/ATS/Users Guide/New|What's New]] |
| − | ! Description
| + | |
| − | ! MIL-STD-498 Description
| + | |
| − | |-
| + | |
| − | |1
| + | |
| − | |Prevents end users from performing an essential task that results in work stoppages. The impact to project cost/schedule requires an immediate resolution and a special release may be necessary.
| + | |
| − | |a.Prevent the accomplishment of an operational or mission essential capability | + | |
| − | b.Jeopardize safety, security, or other requirement designated "critical"
| + | |
| − | |-
| + | |
| − | |2
| + | |
| − | |Adversely affects end users from performing an essential task. Significant impact to project cost/schedule with resolution needed within 3 weeks.
| + | |
| − | |a. Adversely affect the accomplishment of an operational or mission essential capability and no work-around solution is known. | + | |
| − | b. Adversely affect technical, cost, or schedule risks to the project or to life cycle support of the system, and no work-around solution is known.
| + | |
| − | |-
| + | |
| − | |3
| + | |
| − | |Hinders end users from performing an essential task or a capability is behind schedule. Impact to project cost/schedule with resolution needed within 6 weeks.
| + | |
| − | |a. Adversely affect the accomplishment of an operational or mission essential capability but a work-around solution is known. | + | |
| − | b. Adversely affect technical, cost, or schedule risks to the project or to life cycle support of the system, but a work-around solution is known.
| + | |
| − | |-
| + | |
| − | |4
| + | |
| − | |Minor impact to end users or is a capability being developed per schedule. Can be resolved per normal release schedule.
| + | |
| − | |a. Result in user/operator inconvenience or annoyance but does not affect a required operational or mission essential capability.
| + | |
| − | b. Result in inconvenience or annoyance for development or support personnel, but does not prevent the accomplishment of those responsibilities.
| + | |
| − | |-
| + | |
| − | |5
| + | |
| − | |An inconvenience or annoyance. Can be resolved as schedule and budget permits. | + | |
| − | |Any other effect
| + | |
| − | |} | + | |
