결함 등록 및 처리 과정 일반

등록/검증 과정(Verification Process)

Activity: This is the actual activity that was being performed at the time the defect was discovered. For example, during function test phase, you might decide to do a code inspection. The phase would be function test but the activity is code inspection.

Trigger: The environment or condition that had to exist for the defect to surface. What is needed to reproduce the defect? During Review and Inspection activities, choose the selection which best describes what you were thinking about when you discovered the defect. For other defects, match the description with the environment or condition which was the catalyst for the failure.

Impact: For in-process defects, select the impact which you judge the defect would have had upon the customer if it had escaped to the field. For field reported defects, select the impact the failure had on the customer.

문제 등록 관련 섹션 (Opener Section - Verification Process)
문제점 발견 활동 (Defect Removal Activities)	문제 발생 환경/조건 (Triggers)	문제가 고객에게 끼칠 영향 (Impact)
Design Review Code Inspection Unit Test Function Test System Test	Design Conformance Logic/ Flow Backward Compatibility Lateral Compatibility Concurrency Internal Document Language Dependency Side Effect Rare Situations Simple Path Complex Path Coverage Variation Sequencing Interaction Workload/Stress Recovery/Exception Startup/Restart Hardware Configuration Software Configuration Blocked Test (previously Normal Mode)	Installability Serviceability Standards Integrity/Security Migration Reliability Performance Documentation Requirements Maintenance Usability Accessibility Capability

 http://www.research.ibm.com/softeng/ODC/DETODC.HTM

처리/개발 과정(Development Process)

Target: Represents the high level identity of the entity that was fixed.
Defect Type: Represents the nature of the actual correction that was made.
Qualifier (applies to the Defect Type): Captures the element of either a nonexistent or wrong or irrelevant implementation.
Source: Identifies the origin of the Target ( i.e. Design/Code, ID, etc.)which had the defect.
Age: Identifies the history of the Target ( i.e. Design/Code, ID, etc.) which had the defect.  

문제 처리 관련 섹션 (Closer Section - Development Process)
문제 처리 타겟 상위 (Target)	문제 처리 유형 (Defect Type)	처리 유형 세부 (Qualifer)	원천 도입 후 내력 (Age)	원천 도입처 (Source)
Design Code	Assign/Init Checking Alg/Method Func/Class/Object Timing/Serial Interface/O-O Messages Relationship	Missing Incorrect Extraneous	Base New Rewritten ReFixed	Developed In-House Reused From Library Outsourced Ported