Unit 1: Introduction to Testing-Content Continued

This section contains descriptions of the functional organization and roles required supporting the software test related responsibilities. The focus of the described organization is the efficient testing and development of quality software products. The responsibilities described may be combined or expanded based on the size or nature of a given project. The general software development project organization is shown in Figure 1. Specific responsibilities in the software test process are as follows:

Project Management. Responsible for cost, schedule and resources for Test Engineering; recognizing testing as a source of information (metrics) about the project and product, and as a tool for detecting, rather than correcting, problems, and approving test process.
Software Process Engineering. Responsible for using the test-related metrics for defining, tailoring, and maintaining the software development process. They become the advocate for process improvement.
System Engineering. Responsible for working with Test Engineering when system requirements are not testable; aiding Test Engineering in understanding external requirements. In some organizations, Test Engineering reports to System Engineering.
Software Engineering. Responsible for designing, implementing, and integrating the software being developed; performing testing starting with walkthroughs and ending with integration tests; reviewing test cases developed by Test Engineering; and providing consulting support during test design and execution.
Quality Assurance (QA). Responsible for ensuring that Test Engineering follows the process identified in master test planning documentation, testing has met the established standards, reviewing test documents, and witnessing tests (optional on many projects).
Configuration Management (CM). Responsible for identifying and controlling the software product baseline, producing formal builds, and delivering product baselines to Test Engineering.
Documentation and Data Management (DM). Responsible for delivering products, including test documentation, databases and software, and for maintaining.

Figure 2 shows an example of a software testing process reporting chain. Test Engineering is similar but independent of the Software Engineering reporting chain. The figure uses the team titles presented in Figure 1. This reporting structure is compliant with the Carnegie-Mellon Maturity Model (CMM) Software Engineering Institute's Level 3 model dated August 1991.

Figure 3 presents a disciplined approach to simultaneous development of products and their related processes across all functions such as engineering, production, testing, suppliers and the customer. The integrated product team promotes concurrent engineering practices, builds teamwork and a wide-based understanding of the software engineering process from requirements definition to customer acceptance. The integrated product team characteristics are: End-user oriented; Establishes Priorities (customer, product, process, constraints, and then the organization structure); Encompasses all phases of the life cycle.