How do you define Software Test Policy?

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.

Test Policy

Test Policy

Hi Like I said, we will be moving ahead with our next step of learning. So, today i will try to give you a brief Idea about Test Policy and its related area.

So, what is test Policy?

Test Policy is a high level company document and will be developed by management. This document defines “Testing Objective” specific to that organization. Relatively static document (Changes when organization’s focus changes).Test policy is the base that is used by an organization at the time of signing the contract with the clients or Vendor.

The following is an example of how a test policy document exists in a small scale IT company:

Small-scale company test policy would look similar to the following:

1. Testing Definition: Verification + Validation --> The V&V Model
2. Design Testing Process: Proper planning before starting of testing phase
3. Testing Standard: Defect per 280 LOC (Lines of Code) / Defect per 10 functional points.
4. Testing Measurements: QAM(Quality Assurance Management), TTM (Test Team management), PCM (Process Capability Measurement).

Gearing Up Again - CTAL Test Manager Exam

Hi All,

This is the new beginning of this blog as I am going to try CTAL Test Manager Exam Soon.

during this cycle I will be a part of learning that how to break this spell of success. So I invite all of you to come and join me in this run.

Wot I am going to do is that, I will try to provide an alternate learning experience besides books and by using great power of net and off-course god gifted brain.

So Learning Objectives or Level of Knowledge are defined into four categories and during the span of our learning we will going to give emphasis in these four areas.

Remember (K1)

Understand (K2)

Apply (K3)

Analyze (K4)

Now in simpler way:

K1: By REMEMBER it means à Remember, recall, recognize, and know.

K2: By UNDERSTAND it means à Summarize, classify, compare, map, contrast, exemplify, interpret, translate, represent, infer, conclude, categorize.

K3: By APPLY it means à Implement, execute, use, follow a procedure, apply a procedure.

K4: By ANALYZE it means à Analyse, differentiate, select, structure,, focus , attribute, deconstruct, evaluate, judge, monitor, coordinate, create, synthesize, generate, hypothesis, plan, design, construct, produce.

I hope you got some ideas about different areas we will going to discuss in Future.

Chao,

Johnson Stephen