IEEE 829 defines a systematic approach for software testing, which result in effective testing (test plans, test design, test cases, test procedures, better coverage), effective follow-up to track and minimize rework, Reuse documented test cases/procedures by other personal, and proof that testing was conducted to reach a quality level.

 

Inputs to IEEE 829 software testing test documents include: preliminary hazard analysis report (IEEE 1228 std for software safety plan), Software Requirement Specification (IEEE Std. 830 std recommended practice for Software Requirement), and Software Design Description (IEEE 1016 recommended practice for software design description).

The IEEE 829 standard takes a modular approach for defining the specification, as a result, its outcome can be multiple documents, which include:

• test plan (scope,. approach, resources, schedule)
• Test design specification (details of test approach for software features)
• Test case specification (test inputs, expected outputs, and execution conditions for a test item)
• est procedure specification (sequence of execution steps)
• Test item transmittal report (identify test items, locations and status)
• Test log (details about the execution test)
• Test incident report (exceptions that require investigation)
• Test summary report (summary of test activities, result, and evaluation of corresponding test).

The IEEE 829 document is very descriptive document, which makes it easier to comprehend and implement in comparison to some of the other IEEE documents.  
I recently looked into IEEE 1016 Software Design Description (SDD), which acts as an input artifact to IEEE 829.  The benefit of SDD is that it helps to insure adequete design, facilitates design verification, simplifies coding, accommodates for software testing, improves maintainability.  As I sought to implement this standard, I was unable to find a MS word template, an example, or a similar artifact that would aid in expediting the implementation efforts (the Annex section was not very helpful).  I sent an email to a few professors at CSU Fullerton requesting some guidance.  In absence of their response, I can only assume that they were not aware of any such templates either.  Thus, I was faced with attempting to create a template myself (which is no easy task for a first time reader).  In contrast to IEEE 1016, the IEEE 829 Annex provides much more detailed example of implementing the standard.

---

[1] Schmidt, Michael. Implementing the IEEE Software Engineering Standards. Indianapolis, Ind: Sams, 2000. Print.

[2] "IEEE Standard for Software Test Documentation." IEEE Std 829-1998. Software Engineering Technical Committee of the IEEE Computer Society. Web.