How do you define Software Test Policy?

topic posted Mon, December 19, 2005 - 11:38 AM by  ۞ Karina
Here are a few suggestions:

1. Ensure that the software engineering tasks are defined, integrated, and consistently performed to produce the software.

2. Keep software work products consistent with each other.

3. Provide adequate resources and funding for performing the software engineering tasks.

4. Require training for the members of the software engineering technical staff in the performance of their technical assignments.

5. Orient members of the software engineering technical staff in related software engineering disciplines.

6. Orient the project manager and all software managers in the technical aspects of their software project.

7. Integrate the appropriate software engineering methods and tools into each project's defined software process.

8. Ensure that the software requirements are developed, maintained, documented, and verified by systematically analyzing the allocated requirements according to each project's defined software process.

9. Ensure that the software design is developed, maintained, documented, and verified, according to each project's defined software process, to accommodate the software requirements and to form the framework for coding.

10. Ensure that the software code is developed, maintained, documented, and verified, according to each project's defined software process, to implement the software requirements and software design.

11. Perform software testing according to each project's defined software process.

12. Plan and perform integration testing of the software according to each project's defined software process.

13. Plan and perform system and acceptance testing of the software to demonstrate that the software satisfies its requirements.

14. Develop and maintain the documentation that will be used to operate and maintain the software according to each project's defined software process.

15. Collect and analyze data on defects identified in peer reviews and testing according to each project's defined software process.

16. Maintain consistency across software work products, including the software plans, process descriptions, allocated requirements, software requirements, software design, code, test plans, and test procedures.

17. Make and use measurements to determine the functionality and quality of the software products.

18. Make and use measurements to determine the status of the software product engineering activities.

19. Review the activities for software product engineering with senior management on a periodic basis.

20. Review the activities for software product engineering with the project manager on both a periodic and event-driven basis.

21. Have the software quality assurance group conduct reviews or audits of the activities and work products for software product engineering and report the results.