Quality Management and Quality Standard
- 1. Quality Assurance / Software Testing Training Quality Standard
- 2. Page 2Classification: Restricted Agenda • Quality Standard • SEI-CMMI • The CMM is organized into five maturity level • IEEE • Assignment 3
- 3. Page 3Classification: Restricted Quality Standard ISO (International Organization for Standardization) ISO is an independent, non-governmental membership organization and the world's largest developer of voluntary International Standards. ISO International Standards ensure that products and services are safe, reliable and of good quality. For business, they are strategic tools that reduce costs by minimizing waste and errors and increasing productivity. Popular standards ISO 9000 Quality management ISO 14000 Environmental management ISO 3166 Country codes ISO 26000 Social responsibility ISO 50001 Energy management ISO 31000 Risk management ISO 22000 Food safety management ISO 27001 Information security management ISO 20121 Sustainable events
- 4. Page 4Classification: Restricted SEI-CMMI Software Engineering Institute (SEI) developed Capability Maturity Model (CMM) CMM describes the prime elements - planning, engineering, managing software development and maintenance CMM can be used for Software process improvement Software process assessment Software capability evaluations
- 5. Page 5Classification: Restricted The CMM is organized into five maturity level Initial Level 1 Repeatable Level 2 Defined Level 3 Managed Level 4 Optimizing Level 5 Disciplined Process Standard Consistence Process Predictable Process Continuous Improvement Process
- 6. Page 6Classification: Restricted CMM – Level 1 – Initial Level Does not have an environment for developing and maintaining software. At the time of crises, projects usually stop using all planned procedures and revert to coding and testing. CMM – Level 2 – Repeatable level Effective management process having established which can be • Practiced • Documented • Enforced • Trained • Measured • Improvised
- 7. Page 7Classification: Restricted CMM – Level 3 – Defined level Standard defined software engineering and management process for developing and maintaining software. These processes are put together to make a coherent whole. CMM – Level 4 – Managed level Quantitative goals set for both software products and processes. The organizational measurement plan involves determining the productivity and quality for all important software process activities across all projects. CMM – Level 5 – Optimizing level •Process improvement •Tools to identify weaknesses existing in their processes •Make timely corrections
- 8. Page 8Classification: Restricted IEEE Institute of Electrical and Electronics Engineers designed an entire set of standards for software and to be followed by the testers. IEEE 488 Standard Digital Interface for Programmable Instrumentation, IEEE- 488-1978 (now 488.1). IEEE 802.1 Standards for LAN/MAN bridging and management and remote media access control (MAC) bridging. IEEE 802.7 Standards for broadband LAN cabling. IEEE 802.11 Wireless Networking – "WiFi". IEEE 802.15.1 Bluetooth
- 9. Page 9Classification: 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
- 10. Page 10Classification: 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
- 11. Page 11Classification: 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.
- 12. Page 12Classification: 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)
- 13. Page 13Classification: 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.
- 14. Page 14Classification: 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
- 15. Page 15Classification: 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.
- 16. Page 16Classification: Restricted Risk Management • Risk identification • Risk Analysis • Risk Planning • Risk Monitoring
- 17. Page 17Classification: 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.
- 18. Page 18Classification: 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.