Evaluacion y mejora para el desarrollo de software
IEEE
829
PARA ACCESORIOS BORCELLE
Made by:
Aguilera Perez Jesus Abraham
Alvarez Galindo Aldo Yamil
Mayo Ramos Angel David
Muñoz Reynoso Oscar Gael
What is it?
WHAT IS IEEE 829?
IEEE 829, also known as the Standard for Software Test Documentation, is a standard developed by the
Institute of Electrical and Electronics Engineers (IEEE) that defines a framework for documenting the
software testing process. This standard provides clear guidelines on how to structure and present the
various types of documents used during the software testing phases.
WHAT IS IT USED FOR?
The purpose of IEEE 829 is to ensure that the software testing process is clear, standardized, and well-
documented, achieving the following objectives: Establish Clear Communication, Improve the
Organization of the Testing Process, Ensure Traceability and Facilitate Auditing and Compliance.
How to use
IEEE 829? Unit testing
Integration testing
IEEE 829 is a flexible System testing
and adaptable standard
that can be applied to Acceptance testing
different types of
software testing Regression testing
Performance testing
Advantages
1 2 3
STANDARDIZATION QUALITY RISK
MANAGEMENT
mproves software quality
Makes it easier to compare by ensuring well-organized Risk Management: Helps
and understand documents testing. identify and mitigate
across teams and potential risks.
organizations.
Disadvantages
1 2 3
ADMINISTRATIVE RIGIDITY: ADDITIONAL
OVERHEAD: COSTS:
The structured approach
It can generate a significant may be too restrictive for Creating and maintaining
amount of documentation, agile or small projects, extensive documentation
increasing the time and effort where extensive can add to project costs,
required for management. documentation might not especially for teams with
be practical. limited resources.
Test Incident Report:
A document describing unexpected behavior or issues encountered during testing, including steps to reproduce and
potential impacts.
Structure
Test Summary Report:
A comprehensive summary of the testing process, results, and conclusions, highlighting whether objectives were met and
any unresolved issues.
Test Design Specification:
A document outlining the test conditions, test coverage, and detailed design for test cases to validate specific features or
functionality.
Test Case Specification:
A document that defines the inputs, expected results, and execution conditions for individual test cases.
Test Procedure Specification:
A step-by-step guide describing how to execute test cases, including setup, actions, and cleanup.
Test Item Transmittal Report:
A record used to track and confirm the delivery of test items (e.g., software, hardware) to the testing team.
Test Log:
A chronological record of test execution details, including events, outcomes, and any deviations from the planned
procedure.
Summary
IEEE 829 serves as a valuable framework for software testing documentation, promoting
consistency, clarity, and traceability throughout the testing lifecycle. By standardizing key
documents like test plans, test cases, and test reports, it helps ensure thorough and well-
organized testing practices. While it has been partially superseded by newer standards like
ISO/IEC/IEEE 29119, its principles remain highly relevant and continue to guide teams in
achieving high-quality software development.
Thanks
-CafCats Team.
