1. AOIT Introduction to Programming Unit 4, Lesson 11 Documenting Bugs and Fixes Copyright © 2009–2012 National Academy Foundation. All rights reserved.

2. How are bug/fix lists used in professional programming environments? As status information and an educational tool for internal purposes: As status information and an educational tool for external purposes: For each of these: - How similar is this to what you’ve done in this class? - What information would you include? - Where would you put the information? - Would you put the information in the program? # "internal" means inside the programming organization # "external" means for users or customers

3. Professional programmers are not likely to put bug/fix information in their programs There isn’t room: professional applications (even ones well tested) generate hundreds or thousands of bugs. Some programs are part of many products. Professional programming organizations take a “statistical” approach to their bugs and fixes: how many bugs, which chunks of code, how important, which release, which programmer, and who tested? Why would this data be important? What kind of software would you use to hold and report on this information?

4. Software companies keep internal and external bug/fix lists Typically bug/fix lists include the following types of data: Bug unique identifier or name Which release of the product has the bug Date the bug was reported Who reported the bug Who owns the bug (The person who will fix it) How important the bug is If the bug was fixed, when Would these items be part of an internal or external bug list (or both)?

5. Bug/fix lists are used for multiple purposes Bug/fix lists can be used for: Educational tools Status information for internal use Status information for external use You have used bug lists since the beginning of this course. For the culminating project, you will expand your bug/fix list format and focus.