Documents in the NTIS Technical Reports collection are the results of federally funded research. They are directly submitted to or collected by NTIS from Federal agencies for permanent accessibility to industry, academia and the public.  Before purchasing from NTIS, you may want to check for free access from (1) the issuing organization's website; (2) the U.S. Government Printing Office's Federal Digital System website; (3) the federal government Internet portal; or (4) a web search conducted using a commercial search engine such as
Accession Number ADA592418
Title Defect Prioritization Method Based on the Risk Priority Number: White Paper.
Publication Date Nov 2013
Media Count 12p
Personal Author J. Cohen R. Ferguson W. Hayes
Abstract Most software systems have some 'defects' that are identified by users. Some of these are truly defects in that the requirements were not properly implemented, some are caused by changes made to other systems, still others are requests for enhancements that would improve the users' experience. These 'defects' are generally stored in a database and are worked off in a series of incrementally delivered updates. For most systems, it is not financially feasible to fix all of the concerns in the near term, and indeed some issues may never be addressed. The government program office has an obligation to choose wisely among a set of competing defects to be corrected, especially in a financially constrained environment. Selecting the best set of fixes for the next incremental release is a difficult chore as there are many possible ways to prioritize the work. The release may be selected from defects that focus on the workflow of select system users. Since there may be distinct user groups, this method may generate conflict when a high-priority deficiency report is of great importance to one user community and fails to address the concerns of other user communities. Alternatively, an increment (or part of an increment) may address the full set of issues related to a specific function of the system. It also is possible to plan an increment to eliminate requirements for contractor field support, or some other existing work-around that is part of a complex workflow. A mathematical view of all the possible methods of selection quickly reveals there are hundreds of thousands (if not millions) of potential solutions to grouping, ordering, and packaging releases. This white paper provides a description of a generalized technique that could be used with any type of system to assist the program office in addressing and resolving the conflicting views and creating a better value system for defining releases. This technique was developed with the help of a DoD program office.
Keywords Composite measure of risk
Computer programs
Decision making
Defect correction
Defect prioritization method
Defect selection
Deficiency report prioritization
Failure occurrence
Failure severity
Failure sources prioritization
Operational impact
Rating scales
Risk analysis
Risk priority number
Software engineering
Software releases
Software system defects
Source lines of code

Source Agency Non Paid ADAS
NTIS Subject Category 62 - Computers, Control & Information Theory
62B - Computer Software
74G - Military Operations, Strategy, & Tactics
Corporate Author Carnegie-Mellon Univ., Pittsburgh, PA. Software Engineering Inst.
Document Type Technical report
Title Note White paper.
NTIS Issue Number 1412
Contract Number FA8721-05-C-0003

Science and Technology Highlights

See a sampling of the latest scientific, technical and engineering information from NTIS in the NTIS Technical Reports Newsletter

Acrobat Reader Mobile    Acrobat Reader