\f(M Defect Tracking Log Instructions Description Defect Number Unigue identifier for the defect, ie., 1,2 eic. Date Created Date on which the defect was initialty reported and logged. Created By Mame of the person who reported the defect. Defect Description Description of the defect. State the subsystem, area, or other part of the preduct in which the defect occurs or which is affected by the defect. PM Process Choose the Project Management Process this defect was reported for: Opportunity Az=zessment, Initiating, Planning, Executing/Controlling and Clo=ing. Lifecycle Phase List the lifecycle this defect was reported for. The Software Development lifecycle is: Opportunity Assessment, Concept, Reguirements, Design, Development, Testing, Documentation and Training, Deployment and Post Deployment. N Priority The priority code indicates the impact of this defect on the project H = High (extremely important, the project cannot be successful without this defect being resolved} M = Medium {important to project success, but a work around existz) L = Low (desirable, but with little impact to project success if the defect iz not resobred) Mame of the persen who is responsible for fixing the defect Assigned Date Date on which the defect was assigned for resolution Estimated Time To Fix E=timated amount of time required to correct the defect. If applicable list in hours, not days. Status Current status of the defect: Mew, In Progress, Under Review and 7 Completed. 3 Description of the defect's rezolution. Resolution Date Date on which the defect is to be resolved (or is resolved depending upon g itz status). il Actual Time to Fix Actual time required to correct the defect. Root Cause Description |State the cause of the defect (for example, communication, oversight, | tranzcription, education, process, bad code.). (%] Fod | =&amp