缺陷记录日志.docVIP

Assignment Kit #8 Assignment description Using the Defect Recording Log in Table 12.2 in the textbook, record every defect you find in the programs you write. Identify the program where the defect was found, list each defect on a separate entry, and completely describe each defect. Summarize the defect data in the Project Plan Summary for each program. Also, submit a copy of any Time Recording Log and Job Number Log pages and Weekly Activity Summaries that you have not previously submitted and turn in a completed planning form and Defect Recording Log for each newly developed program. Make multiple copies of the Defect Recording Log since you will use it for every program you write for the rest of the course. Also read the textbook Chapters 13 and 14. There will be a quiz on this material in the next lecture. Comments on the assignment With this assignment, we start to address the issue of program quality. Your principal objective in addressing program quality is to manage the defects in your programs. To do this, you need to understand those defects. When starting to gather defect data, your initial objective is to obtain data you can later use for defect analysis and planning. Keep copies of all the forms and data you submit. Table 12.1 Defect Type Standard DEFECT TYPES: Type Number Type Name Description 10 Documentation comments, messages 20 Syntax spelling, punctuation, typos, instruction formats 30 Build, Package change management, library, version control 40 Assignment declaration, duplicate names, scope, limits 50 Interface procedure calls and references, I/O, user formats 60 Checking error messages, inadequate checks 70 Data structure, content 80 Function logic, pointers, loops, recursion, computation, function defects 90 System configuration, timing, memory 100 Environment design, compile, test, or other support system problems Table 12.2 Defect Recording Log Defect Types 10 Documentation 60 Checking 20 Syntax 70 Data 30 Build