The document outlines a program checklist (PCL) designed as a practical guide for developers and testers, with a focus on unit testing in a V-model development process. It details the purpose of PCL to ensure software quality by early defect detection and cost reduction in corrections, along with specific guidelines for creating and managing checklists. The document also includes criteria for unit test case classifications and the structure of various checklist sheets used in the testing process.

1. Program Check List (PCL) Author: Bui Ngoc Le Tester G9-D1

2. Introduction Duration: 1.5 hours Agenda: PCL: What and Who? PCL: Why and How? Purpose Practical Guide to PCL Target attends : Developer Tester

3. The Development V-Model

4. PCL – What and who PCL: P rogramming C heck L ist (UT Test case) PCL: Used in Unit Test Stage PCL: Done by Developers PCL: Used to check code following step by step

5. PCL - Why Ensure quality of software unit Detect defects and issues early Reduce the Quality Effort & Correction Cost Refer to evaluate Unit Test

6. PCL standard: 80 PCLs/1KLOC : 6.5 bugs/1KLOC Unit test case classification Normal (N) - <= 55%(+/- 5%) Abnormal (E) - <= 15%(+/- 5%) Limitation (L) - <= 10%(+/- 5%) Interface (I) - <= 20%(+/- 5%) PCL - How

7. Check list ID standard: Module ID + Base check list + No Module ID: Function name.. Base check list: S – Normal K – Common P - Pattern PCL - How

8. PCL structure: Summary sheet: Cover number of PCLs at each sheet and calculate total PCLs of file PCL sheet: The same as Table of contents Function check sheets: Describe detail about case to be checked PCL - How

9. PCL – How Purpose: Table of contents Master content of sheet System name, program name, programID, module name, moduleID, creator, approver, machine check, desk check Detail content of sheet No, ChecklistID, Check items, input condition, confirm contents, desk checked date, machine checked date PCL sheet

10. Purpose: Testing all activities of screen Master content of sheet Sheet Name, Style, Passed date, Note, System/Program Name, Section, Created, Confirmed, Approved, Sheet No Detail content of sheet Test condition, Check item Test case ID, Type (N, E, L, I), Test date PCL - How PCL – Function checklist sheets

11. Purpose: Testing all activities of screen Master content of sheet Sheet Name, Style, Passed date, Note, System/Program Name, Section, Created, Confirmed, Approved, Sheet No Detail content of sheet Test condition, Check item Test case ID, Type (N, E, L, I), Test date PCL - How

12. PCL – Checked contents Validation of date: Diversified input data Diversified Process condition Diversified Process object Manage table Work area Return error message/error code PCL - How

13. Questions and answers