| <html> | |
| <!-- | |
| Copyright (c) 2004, 2007 Boeing. | |
| All rights reserved. This program and the accompanying materials | |
| are made available under the terms of the Eclipse Public License v1.0 | |
| which accompanies this distribution, and is available at | |
| http://www.eclipse.org/legal/epl-v10.html | |
| Contributors: | |
| Boeing - initial API and implementation | |
| --> | |
| <head> | |
| <title>Priorities for classifying problems</title> | |
| <LINK rel="stylesheet" type="text/css" href="../../osee.help/html/style.css"> | |
| </head> | |
| <body> | |
| <h1>Priorities for classifying problems</h1> | |
| <Table border><TR><Th>Priority</Th><Th>Description</Th><Th>MIL-STD-498 Description</Th></TR> | |
| <TR> | |
| <TD align=center>1</TD> | |
| <TD>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.</TD> | |
| <TD>a. Prevent the accomplishment of an operational or mission essential capability<br>b. Jeopardize safety, security, or other requirement designated "critical"</TD> | |
| </TR> | |
| <TR> | |
| <TD align=center>2</TD> | |
| <TD>Adversely affects end users from performing an essential task. Significant impact to project cost/schedule with resolution needed within 3 weeks.</TD> | |
| <TD>a. Adversely affect the accomplishment of an operational or mission essential capability and no work-around solution is known.<br>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</TD> | |
| </TR> | |
| <TR> | |
| <TD align=center>3</TD> | |
| <TD>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.</TD> | |
| <TD>a. Adversely affect the accomplishment of an operational or mission essential capability but a work-around solution is known.<br>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</TD> | |
| </TR> | |
| <TR> | |
| <TD align=center>4</TD> | |
| <TD>Minor impact to end users or is a capability being developed per schedule. Can be resolved per normal release schedule.</TD> | |
| <TD>a. Result in user/operator inconvenience or annoyance but does not affect a required operational or mission essential capability.<br>b. Result in inconvenience or annoyance for development or support personnel, but does not prevent the accomplishment of those responsibilities.</TD></TR> | |
| <TR> | |
| <TD align=center>5</TD> | |
| <TD>An inconvenience or annoyance. Can be resolved as schedule and budget permits.</TD> | |
| <TD>Any other effect</TD> | |
| </TR> | |
| </Table> | |
| </body> | |
| </html> | |