Software Testing Management
- 1. Quality Assurance / Software Testing Training Requirement Management Configuration Management Project Management Risk Management
- 2. Page 2Classification: Restricted Agenda • Requirement Management • Configuration Management • Project Management • Risk Management
- 3. Page 3Classification: Restricted Requirements, CM, Strategy & DLC • Requirement Management • Configuration Management • Project Management • Risk Management • Test Strategy and Planning • Overview of Test Strategy • Test Planning (Pre->Test->Post Activities) • Risk Analysis • Estimations • Typical Test issues
- 4. Page 4Classification: Restricted Requirement Management Testing Cycle starts with the study of client’s requirements. Understanding of the requirements is very essential for testing the product. Requirements management is the process of documenting, analyzing, tracing, prioritizing and agreeing on requirements and then controlling change and communicating to relevant stakeholders. It is a continuous process throughout a project. A requirement is a capability to which a project outcome (product or service) should conform
- 5. Page 5Classification: Restricted Configuration Management PC version Initial system DEC version VMS version Unix version Mainfram e version Workstatio n version Sun version CM should be based on a set of standards, which are applied within an organization.
- 6. Page 6Classification: Restricted CM Planning • Documents, required for future system maintenance, should be identified and included as managed documents. • It defines the types of documents to be managed and a document naming scheme. Change Management • Keeping and managing the changes and ensuring that they are implemented in the most cost-effective way. Change Request form A part of the CM planning process Records change required Change suggested by Reason why change was suggested Urgency of change Records change evaluation Impact analysis Change cost Recommendations(system maintenance staff)
- 7. Page 7Classification: Restricted VERSION AND RELEASE MANAGEMENT Invent identification scheme for system versions and plan when new system version is to be produced. Ensure that version management procedures and tools are properly applied and to plan and distribute new system releases. Versions/Releases Versions - An instance of a system, which is functionally distinct in some way from other system instances. Release -An instance of a system, which is distributed to users outside of the development team.
- 8. Page 8Classification: Restricted Project Management Project Staffing Project budget may not allow to utilize highly – paid staff. Staff with the appropriate experience may not be available. Project Scheduling Bar charts and Activity Networks Scheduling problems
- 9. Page 9Classification: Restricted Project Planning Plan Description Quality plan Describes the quality procedures and standards used in a project. Validation plan Describes the approach, resources and schedule used for system validation. Configuration management plan Describes the configuration management procedures and structures to be used. Maintenance plan Predicts the maintenance requirements of the system/ maintenance costs and efforts required. Staff development plan Describes how the skills and experience of the project team members will be developed.
- 10. Page 10Classification: Restricted Risk Management • Risk identification • Risk Analysis • Risk Planning • Risk Monitoring
- 11. Page 11Classification: Restricted Risk Risk type Description Staff turnover Project Experienced staff will leave the project before it is finished. Management change Project There will be a change of organizational management with different priorities. Hardware unavailability Project Hardware which is essential for the project will not be delivered on schedule. Requiremens change Project & Product There will be a larger number of changes to the requirements than anticipated.
- 12. Page 12Classification: Restricted Risk Risk type Description Specification delays Project & Product Specifications of essential interfaces are not available on schedule. Size under estimate Project & Product The size of the system has been under estimated. CASE tool under performance Product CASE tools which support the project do not perform as anticipated. Technology change Business The underlying technology on which the system is built is superseded by new technology. Product competition Business A competitive product is marketed before the system is completed.