.NODE

Appendix K Problem/Change Report

Appendix K Problem Change Report

PROBLEM/CHANGE REPORT

(Type or Print)

1. Date

2. P/ CR No

3. Originator

4. Activity Code

5. Telephone/Ext.

6. Title

7. Category: (Circle)

Plans

Design

Test Info

Concept

Code

Manuals

Requirements

DB/ data file

8. Priority: (Circle)

Other _________________________

 

1

2

3

4

5

9. Problem/Change Description:


 

10. Corrective Action:


 

11. Actions Taken

Status

Date

   

12. QA Sign-Off


 
P/CR PREPARATION INSTRUCTIONS
  1. TITLE

    • Problem/Change Report
  1. DESCRIPTION/PURPOSE

    • 2.1 The Problem/Change Report (P/CR) shows essential data on each software problem/change detected . It also shows errors on omissions in documentation. Sufficient detail of the problem shall be reported to enable analysis and isolation or replication if necessary.
  1. APPLICATION INTERRELATIONSHIP

    • 3.1 P/CRs are used to record and report problems found throughout development. They are also used to report errors or omissions found in documentation. The P/CR is the basic input to the quality assurance program during the test and acceptance phase of the development effort. P/CRs on interfaces with other systems require joint resolution action.
  1. PREPARATION INSTRUCTIONS

    1. Date. The date form is prepared.
    2. P/CR Number. P/CR Number assigned for control purposes.
    3. Originator. Printed name of person originating the P/CR form.
    4. Activity Code. The activity and code name or number of individual originating the P/CR form.
    5. Telephone/Ext. Originator's office telephone number, and extension (if applicable ).
    6. Title. Name used to identify problem/change.
  1. Category. Circle appropriate category associated with problem/change being reported.

Categories:

  1. Plans - one of the plans developed for the project
  2. Concept - the operational concept
  3. Requirements - the system or software requirements
  4. Design - the design of the system or software
  5. Code - the software code
  6. Database/data file - a database or data file
  7. Test information - test plans, test descriptions, or test reports
  8. Manuals - the user , operator, or support manuals
  9. Other - other software products
  1. Priority. Circle appropriate priority code, 1 “ 5.

Priority Codes:

    1. Prevent the accomplishment of an operational or mission-essential capability
    2. Jeopardize safety, security, or other requirement designated "critical"
    1. Adversely affect the accomplishment of an operational or mission-essential capability and no work-around solution is known
    2. 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
    1. Adversely affect the accomplishment of an operational or mission-essential capability but a work-around solution is known
    2. 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
    1. Results in user/operator inconvenience or annoyance but does not affect a required operational or mission-essential capability
    2. Results in inconvenience or annoyance for development or support personnel, but does not prevent the accomplishment of those responsibilities
  1. Any other effect
  1. Problem/Change Description. Write a description of the problem/change. Develop a word picture of events leading up to the problem. Structure statements so that the programmer/test analyst can duplicate the situation. Cite equipment being used, unusual configuration, etc. Indicate consoles online, modes, etc., if applicable. If continuation sheets are required, fill in page _____of _______ at the top of the P/CR form.
  2. Corrective Action: A description, by the programmer/tester, of actions taken to resolve the reported problem or to complete the requested change.
  3. Actions Taken: Enter the status/disposition and date to indicate the current status. When the status changes, line out the old status and date and enter the appropriate new status and date.
  4. QA Sign-off. Signature by designated quality assurance (QA) organization member authorizing implementation of the corrective change(s) and certifying the correctness and completeness of the change(s).






Software Configuration Management
Software Configuration Management
ISBN: 0849319765
EAN: 2147483647
Year: 2006
Pages: 235
Authors: Jessica Keyes
Similar book on Amazon

Flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net