Sie sind auf Seite 1von 2


Applications Lifecycle Cookbook

Phase 3: Quality Assurance and Testing 1 I1 1II

Step 17: Improve Unit Testing 17 18

Step 17: Improve Unit Testing

Objective Integrate testing early in the project lifecycle to discover potential defects before they are written into applications. Tool Wisconsin Department of Administration: Applications Performance Checklist (Tool T) Schneider National: Applications Performance Checklist (Tool U) How to Use the Tool Quality Assurance staff use the Testing Roles and Responsibilities Checklist (Tool T) to identify level of responsibility, mandatory deliverables, and prescribed actions at each stage of the project lifecycle. The checklist highlights mandatory deliverables to complete before the application progresses to subsequent phases of the software development process. In addition, the table includes examples deliverables that may be required depending on project scope and size. Depending on the complexity and the overall importance of the deliverable, the Quality Assurance team may act as a contributor, reviewer, lead, or a combination of any of the roles. Testing staff use the Applications Performance Checklist (Tool U) to identify key tasks and deliverables at each stage of the lifecycle. The tool also recommends time/effort levels for each stage of the project. Primary User(s) Project Manager Quality Assurance Staff


Phase Three: Quality Assurance and Testing


Phase 3: Quality Assurance and Testing 1 I1 1II

Step 18: Use Quality Metrics 17 18

Tool T
Testing Rules and Responsibilities Checklist
Testing Checklist Deliverable, Roles, and Actions by Phase
Project Deliverables and Role
Mandatory Deliverable
Project Plan Application Documentation Repository Requirements Documentation High-Level Business Function Diagram Selected Software Development Lifecycle Mode Implementation Plan

s/Responsibilities Matrix
QA Value

QA Role/ Responsibility Initiation Phase


Project risks (including legal issues), external deadlines, costs, schedule, and resource commitments are approved at a high level Adequate funding and resources are confirmed Application activities are planned and documented

Analysis Phase
Communication Plan Detailed Project Plan Identify Possible Reusable Objects Software and Hardware Requirements Test Plan Application Support Plan Project Change Request Issue Log C/R C/R R R R Application requirements are documented Initial design is validated and approved Adherence to standards and procedures is enforced Structured approach to scope and management is in place Consistent and ongoing management and customer awareness of project status Process for tracking and approving requirements changes in place

Design Phase
Updated Project Plan Physical Data Model Finalized Requirements, Software Environments, Development Tools, and Software and Hardware Requirements Design Review Approved Design Training Plan and Curriculum Detailed Test Plan C/R R C/R C/R R R Structured approach to documenting detailed application design and documenting test plans Overall application design is validated and approved Adherence to standards and procedures is enforced Consistent and ongoing management and customer awareness of project status

Construction Phase
Updated Project Plan Source Code Code Review Documented Test Results Technical Documentation Application Documentation Communication Deliverables C/R R R R C/R C/R R Rework is reduced with code reviews and unit test standards Quality Assurance checkpoints help manage project risks Consistent and ongoing management, team, and customer awareness of project status

Implementation Phase
Updated Project Plan Installed Application Project Closing Report Conduct User Training Customer Evaluation C/R R C/R Quality of production environment is validated after migration Consistent and ongoing management AGE and customer awareness of project status






Finalized Source Code and Documentation

Mandatory QA Role/ C/R Deliverable Responsibility Completion Phase


QA Value

Finalized Application Repository and Approved Completed Portfolio and Project Plan Completed Project Closing Report Project Lessons Learned Summary Customer Evaluation Project Team Evaluation

Ability to track application performance for integrity against benchmarks, analyze defects, and perform causal analysis Evaluate enhancement requests against original requirements Assessment of project by the customer Conduct project evaluations by the project team

Key C = Contributor R = Reviewer L = Lead

Source: Wisconsin Department of Administration; Applications Executive Council.