tailieunhanh - Lecture Software testing and analysis: Chapter 24 - Mauro Pezzè, Michal Young

Mature software processes include documentation standards for all the activities of the software process, including test and analysis activities. Documentation can be inspected to verify progress against schedule and quality goals and to identify problems, supporting process visibility, monitoring, and replicability. | Documenting Analysis and Test (c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 1 Learning objectives • Understand the purposes and importance of documentation • Identify some key quality documents and their relations • Understand the structure and content of key quality documents • Appreciate needs and opportunities for automatically generating and managing documentation (c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 2 Why Produce Quality Documentation? • Monitor and assess the process – For internal use (process visibility) – For external authorities (certification, auditing) • Improve the process – Maintain a body of knowledge reused across projects – Summarize and present data for process improvement • Increase reusability of test suites and other artifacts within and across projects (c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 3 Major categories of documents • Planning documents – describe the organization of the quality process – include organization strategies and project plans • Specification documents – describe test suites and test cases (as well as artifacts for other quality tasks) – test design specifications, test case specification, checklists, analysis procedure specifications • Reporting documents – Details and summary of analysis and test results (c) 2007 Mauro Pezzè & Michal Young Ch 24, slide 4 Metadata • Documents should include metadata to facilitate management – – – – – – Approval: persons responsible for the document History of the document Table of Contents Summary: relevance and possible uses of the document Goals: purpose of the document– Who should read it, and why? Required documents and references: reference to documents and artifacts needed for understanding and exploiting this document – Glossary: technical terms used in the document (c) 2007 Mauro Pezzè & Michal Young Ch 24, slide .