Downloaded 158 times
Uploaded byنور شزننا
Software Quality Analyst and Software Quality Management
The document discusses software quality assurance (SQA) and software quality management (SQM), emphasizing their importance in ensuring that software products meet specified requirements and customer expectations. It outlines the roles and activities involved in SQA and SQM, highlighting the need for a quality culture within organizations and the systematic processes necessary for defect prevention. The document also compares quality assurance and quality control, detailing various quality models and standards such as ISO 9000 and ISO/IEC 9126.
More Related Content
Similar to Software Quality Analyst and Software Quality Management
Software Quality Analyst and Software Quality Management
- 1. Software Quality Assurance & SoftwareQuality Management Presenters: Nabila Sharudin (GS35566) Siti Hanisah Majid (GS35569) Nur Syazanna Jamaludin (GS36862)
- 2. SOFTWARE Intellectual product consisting of informationstored on a storage device (ISO/DIS 9000: 2000) QUALITY Conformance to specification and meeting customer needs Hoyer, R. W. and Hoyer, B. B. Y., "What is quality?", Quality Progress,2001 SOFTWARE QUALITY The degree to which a system, component, or process meets: • specified requirements • customer or user needs or expectations IEEE Definition
- 3. User Developer What Iwant Good specification Fast response Technically correct Control information Fits within system structure Easy to use help menus Easy to maintain Available as required Difficult for user to manage Exception data Fast development Reacts to business change Low maintenance Input data once Well documents Views of Quality
- 4. Software Quality Management Goals: Ensure that the required level of quality is achieved in software products, namely, that defined standards and procedures are followed Scope: • Particularly important for large, complex systems. The quality documentation is a record of progress and supports continuity of development as the development team changes • For smaller systems, quality management needs less documentation and should focus on establishing a quality culture
- 5. SQM Roles To ensurethat the required level of quality is achieved in a software product To encourage a company-wide "Quality Culture" where quality is viewed as everyone’s responsibility To reduce the learning curve and help with continuity in case team members change positions within the organization To enable in-process fault avoidance and fault prevention through proper development
- 6. While, Quality Managementshould be separate from Project Management to ensure independence of budget and schedule pressures as shown on the next diagram SQM Activities Quality Assurance Quality Planning Quality Control
- 7. Quality Management and SoftwareDevelopment
- 8. 1. A plannedand systematic pattern of all actions necessary to provide adequate confidence that an item or product conforms to established technical requirements IEEE 2. A set of activities designed to evaluate the process by which products are developed or manufactured IEEE Software Quality Assurance
- 9. Focused on providingconfidence that quality requirements will be fulfilled ISO9000 The goal of QA is to provide assurance that a product will meet the customer’s quality expectations. It consists of activities designed to ensure that quality will be built into the product. These activities usually precede development of the product and continue while the development is in progress It is a QA responsibility to develop and implement processes and standards to improve the development life cycle and to make sure that these procedures are followed. The focus of QA is defect prevention, processes and continual improvement of these processes
- 10. While QA isa proactive activity, QC is reactive Examples of QA activities include establishing standards and processes, quality audits, selection of tools and training The relationship between QA and QC is depicted in Figure 2 below.
- 11. SQP sources arederived from SQA components that are adopted as is or customized to the project's needs New procedures, standards and tools complementing missing or not-applicable SQA components that have been written in particular for the project, or imported from outside the organization Quality Planning
- 12. Focused on qualityrequirements ISO9000 Quality Control is a set of activities designed to evaluate whether a developed product (project document, developed system etc.) meets customer requirements It ensures that delivered products are checked for quality and determines how well it is built. Its focus is to find defects and to ensure that they are corrected QC is the responsibility of the project team Quality Control
- 13. Testing forms anintegral part of Quality Control, as displayed in Figure 1. However, not all QC activities are testing activities. Code inspections, technical reviews and stage gates are other examples of Quality Control activities.
- 14.
- 15. Software Quality Models McCall’sFactor Model Tree (1977)
- 16. Boehm’s Model (1978) UpgradeMcCall’s Model with the existence of device efficiency
- 17. F.U.R.P.S (Robert Grady- extendedby IBM Rational Software) Giving focus on IBM products
- 18. The Six QualityCharacteristics of A Software ISO/IEC 9126 The ISO 9126-1 quality model is the most useful one since it has been build based on an international consensus and agreement from all the country members of the ISO organization