Problem List Certification - Final Review

Certification Gurus, We will take up Problem List Certification again tomorrow with a continuation of our Final Review. To speed up the process, I am including the final review checklist below so that you have a heads up as to what we will cover. Since we have been through most of this already, my plan will be to walk through quickly and ask for objections to passing a given step. Please come prepared with your objections. As a conveience, the OTJ article can be found at: http://hdl.handle.net/10909/35 and the backup material for the review can be found at: http://www.osehra.org/content/problem-list-refactoring-certification-final-review-materials I look forward to our meeting tomorrow. - Wes Product Build Checklist Low Medium High N/A Does the provided documentation adequately describe the intended behavior of the software? Attach a file... Add a comment... Low Medium High N/A Are the Use Cases documented? Attach a file... Add a comment... Low Medium High N/A Are external interfaces documented? Attach a file... Add a comment... Low Medium High N/A Are the components required for the build identified? Attach a file... Add a comment... Low Medium High N/A Do all components follow appropriate standards and conventions? Attach a file... Add a comment... Low Medium High N/A Are there sufficient unit and regression tests available to verify the submission? Attach a file... Add a comment... Low Medium High N/A Does the documentation describe how to install, test and run the code? Attach a file... Add a comment... Low Medium High N/A Are there functional tests available for this submission? Attach a file... Add a comment... Pre-Installation Low Medium High N/A Is test plan/problem duplication available, if applicable? Attach a file... Add a comment... Low Medium High N/A Do the unit and regression tests behave appropriately prior to product installation? Attach a file... Add a comment... Low Medium High N/A Do the functional tests behave appropriately prior to product installation? Attach a file... Add a comment... M-Code Patch Installation Only *- Save the patch description* No Yes 1. Perform editorial review Attach a file... Add a comment... No Yes 2. Ensure patch subject is clear Attach a file... Add a comment... No Yes 3. Ensure acronyms are defined in the first occurrence Attach a file... Add a comment... No Yes 4. Run spelling and grammar check Attach a file... Add a comment... No Yes 5. Ensure all required issue ticket numbers are listed (JIRA, Remedy, CA Service Desk, etc.) Attach a file... Add a comment... No Yes 6. Ensure patch priority is listed (Emergency or Routine via FORUM for VA patches) Attach a file... Add a comment... No Yes 7. Ensure patch category(s) are listed (patch for a patch, etc. via FORUM for VA patches) Attach a file... Add a comment... No Yes 8. Ensure instructions for disabling options/protocols are included if required Attach a file... Add a comment... No Yes 9. Confirm there is a statement regarding whether or not users can be on the system Attach a file... Add a comment... No Yes 10. Ensure time required to install patch is included Attach a file... Add a comment... No Yes 11. Question manual deletion of routines Attach a file... Add a comment... No Yes 12. Validate accuracy of patch name(s) found in the description Attach a file... Add a comment... No Yes 13. Ensure format is correct for files: FILE NAME (#number) Attach a file... Add a comment... No Yes 14. Ensure format is correct for fields: FIELD NAME (#number) Attach a file... Add a comment... No Yes 15. Ensure format is correct for options: Menu Text [INTERNAL OPTION NAME] Attach a file... Add a comment... No Yes 16. Ensure patch number list is in order of release Attach a file... Add a comment... No Yes 17. Ensure full name is used for other packages such as VA FileMan, TaskMan, MailMan, etc. Attach a file... Add a comment... No Yes 18. Ensure dependencies on other packages/patches listed Attach a file... Add a comment... No Yes 19. Ensure database changes are documented Attach a file... Add a comment... No Yes 20. Verify the patch description to the system description Attach a file... Add a comment... No Yes 21. Ensure estimate of disk space and journal file consumption is included, if applicable Attach a file... Add a comment... No Yes 22. Ensure reference is made to any documentation that will be sent out separately, if applicable Attach a file... Add a comment... No Yes 23. Compare the Installation Guide to the patch description's installation instructions, if applicable. Attach a file... Add a comment... *- Review file/global changes and save a "before" capture, if applicable* Low Medium High N/A 1. Check for use of privileged access (R, W, P/D) Attach a file... Add a comment... Low Medium High N/A 2. Check for current nodes Attach a file... Add a comment... *- Save a copy of the "before" components (other than routines), if applicable* Low Medium High N/A 1. Data Dictionary Attach a file... Add a comment... Low Medium High N/A 2. Data Values Attach a file... Add a comment... Low Medium High N/A 3. Protocols Attach a file... Add a comment... Low Medium High N/A 4. Options Attach a file... Add a comment... Low Medium High N/A 5. Duplicate problem and save the results, if applicable Attach a file... Add a comment... *- Installation* Low Medium High N/A 1. Load the patch Attach a file... Add a comment... Low Medium High N/A 2. Verify checksums in Transport Global Attach a file... Add a comment... *- Print Transport Global* Low Medium High N/A 1. Confirm Type ? Single Package Attach a file... Add a comment... Low Medium High N/A 2. Confirm presence of appropriate Required Builds Attach a file... Add a comment... Low Medium High N/A 3. Confirm all expected routines are included in the build (listed in the routine multiple) Attach a file... Add a comment... Low Medium High N/A 4. Confirm exported routine list is correctly namespaced Attach a file... Add a comment... Low Medium High N/A 5. Confirm alpha/beta testing is blank or set to ?no? Attach a file... Add a comment... Low Medium High N/A 6. Compare Transport Global to Current System Attach a file... Add a comment... Low Medium High N/A 7. Back a Transport Global Attach a file... Add a comment... Low Medium High N/A 8. Install Package(s) Attach a file... Add a comment... Low Medium High N/A 9. Compare time required to install with installation instructions Attach a file... Add a comment... Low Medium High N/A 10. Environment check, if applicable Attach a file... Add a comment... Post Installation Low Medium High N/A Do the unit and regression tests pass? Attach a file... Add a comment... Low Medium High N/A Do the functional tests pass? Attach a file... Add a comment... M-Code Patches Only Low Medium High N/A Verify the "after" patch installation checksums, if applicable Attach a file... Add a comment... Low Medium High N/A Perform ^%RCHECK on all patch routines and save results, if applicable Attach a file... Add a comment... *- Check first, second, and third routine lines adhere to M code SAC standards* Low Medium High N/A 1. First line Attach a file... Add a comment... Low Medium High N/A 2. Second line Attach a file... Add a comment... Low Medium High N/A 3. Third line Attach a file... Add a comment... Low Medium High N/A 4. Save copy of "after" components (other than routines), if applicable Attach a file... Add a comment... Low Medium High N/A 5. Ensure there are no variables, new with this patch, that were not explicitly killed. Attach a file... Add a comment... Low Medium High N/A 6. Ensure there are no warnings or errors listed Attach a file... Add a comment... Low Medium High N/A 7. Ensure exported protocols are properly attached to menus, if applicable Attach a file... Add a comment... Low Medium High N/A 8. Ensure exported options are properly attached to menus, if applicable Attach a file... Add a comment... *- Review file changes, if applicable* Low Medium High N/A 1. Save a copy of "after" components (other than routines), if applicable Attach a file... Add a comment... Low Medium High N/A 2. Confirm no erroneous nodes are exported Attach a file... Add a comment... Low Medium High N/A 3. If patch alters data, verify that new values adhere to data dictionaries Attach a file... Add a comment... Low Medium High N/A 4. Save copy of "after" components (other than routines), if applicable Attach a file... Add a comment... *- Do a routine search (^%RFIND) for the following items, if applicable* Low Medium High N/A 1. //// Attach a file... Add a comment... Low Medium High N/A 2. DIC(0) Attach a file... Add a comment... Low Medium High N/A 3. ^UTILITY Attach a file... Add a comment... Low Medium High N/A 4. ^TMP Attach a file... Add a comment... Low Medium High N/A 5. ^XTMP Attach a file... Add a comment... Low Medium High N/A 6. % Attach a file... Add a comment... Low Medium High N/A 7. $I Attach a file... Add a comment... Low Medium High N/A 8. U= Attach a file... Add a comment... Low Medium High N/A 9. K^10. ^( Attach a file... Add a comment... Low Medium High N/A Review sets and kills of IO variables Attach a file... Add a comment... Low Medium High N/A Confirm fields which contain executable code are write protected in the DD with ?@? or are defined as VA FileMan data type of ?M?, if applicable. Attach a file... Add a comment... Low Medium High N/A Test the patch to confirm that the patch has corrected the problem, if applicable Attach a file... Add a comment... Low Medium High N/A Check error log (D ^XTER) Attach a file... Add a comment... Low Medium High N/A Deliver report of findings to the developer and development manager Attach a file... Add a comment... Low Medium High N/A Ensure Patch Tracking Message (JIRA) has been delivered to appropriate staff, if applicable. Attach a file... Add a comment... Low Medium High N/A Perform user documentation review, if applicable Attach a file... Add a comment... Low Medium High N/A Ensure the documentation file names in the patch description match the actual file names, if applicable -- Wesley D. Turner, Ph.D. Kitware, Inc. Technical Leader 28 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4920
like0