Software Quality

1. Software Quality
By Dr. Anupama Sharma

7. It Focused on 2 basic Fundamentals
• 1. Quality of Design:-
Characteristics of items or tools used by designer.
• 2. Quality of Conformance:-
Degree to which design specifications are followed in
manufacturing the product or software

16. Software Quality Models
• Mc Calls Software Quality Model
• Boehm's Software Quality Model

37. SQA (via IEEE)
• “The Quality assurance process is a process for providing adequate assurance
that the software products and processes in the project life cycle conform to
their specified requirements and adhere to their established plans. “
• A planned and systematic pattern of all actions necessary to provide
adequate confidence that an item or product conforms to established
technical requirements.
• A set of activities designed to evaluate the process by which products are
developed or manufactured.

38. Software Quality Assurance
• IEEE 730 - Quality Assurance Plans
• “Quality Assurance - a planned and systematic pattern of all
actions necessary to provide adequate confidence that the time or
product conforms to established technical requirements.”
• Purpose of SQAP is to specify all the works products that need
to be produced during the project, activities that need to
performed for checking the quality of each of the work product
• It is interested in the quality of not only the final product but
also an intermediate product
• So it ensure that the delivered software is of good quality

39. SQA Life CYCLE or Framework of SQA
Design
Test
Deployment
Concept/ Requirements
Devel. & Coding
IV&V Risk Management
Metrics
Safety Reliability

40. Need of Quality Assurance Plan
• To ensure the final product produced is of high quality, some quality control
activities must be performed throughout the development
• If it is not done ,correcting errors in the final stage can be very expensive,
especially if they originated in the early phase.

41. Scope of quality management
• Quality management is 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.

42. Quality management activities
• Quality assurance
• Establish organisational procedures and standards for quality.
• Quality planning
• Select applicable procedures and standards for a particular project
and modify these as required.
• Quality control
• Ensure that procedures and standards are followed by the software
development team.
• Quality management should be separate from project management to
ensure independence.

43. Verification & Validation
• Verification:-is the process of determine whether or not product
of a given phase of software development full fill the
specification established during the previous phase.
• Validation:-is the process of evaluating software at the end of
software development to ensure compliance with the software
requirement. testing is common method of validation
• Software V&V is a systems engineering process employing
rigorous methodologies for evaluating the correctness and quality
of the software product throughout the software life cycle

44. Verification (Are we building the
product right?)
Validation (Are we building the right
product?)

45. V&V Activities
Requirements Phase
•System Reqts
Analysis
•S/W Reqts
Analysis
•Interface Analysis
•Process Analysis
•Technical Reviews
& Audits
Design Phase
•Design Analysis
•Interface Analysis
•Test Program
Analysis
•Supportability
Analysis
•Process Analysis
•Technical Reviews
& Audits
Code Phase
•Code Analysis
•Test Program
Analysis
•Supportability
Analysis
•Process Analysis
•Technical Reviews
& Audits
Test Phase
•Test Program
Analysis
•Independent Test
•Supportability
Analysis
•Technical Reviews
& Audits
Verify
Verify
Verify
Validate
Catastrophic/Critical/High Risk Functions List
Traceability Analysis
Issues Tracking
Metrics Assessment
Loading Analysis
Change Impact Analysis
Special Studies

46. SEI Capability Maturity Model (CMM)
• The CMM was developed by software engineering institute (SEI)
of carnegie-mellon university in 1986.
• CMM is not a SDLC model. instead it is a strategy for improving
the software process.
• CMM is used to judge the maturity of the software processes of
an organization and to identify the key practice that are required
to increase the maturity of these processes.

47. Objectives of the CMM
To increase customer satisfaction, by producing products according
to plan while simultaneously improving the organization’s capability
to produce better products
To increase software process maturity, the extent to which
processes are explicitly defined, managed, measured, controlled,
and effective, by:

48. Objectives of the CMM
• Establishing basic project management controls
• Standardizing the organization's software process activities
• Quantitatively analyzing processes and products for monitoring
and control
• Institutionalizing process improvement

49. Capability Maturity Model (CMM)
It is a strategy for improving the software process, irrespective
of the actual life cycle model used.

50. Key process area of CMM

51. Key process area of CMM

52. CMM Building Blocks: the Maturity Levels
Institutionalize
process improvement
Quantitative analysis of processes
and products for monitoring and
control
Standardize the software
process activities for all
the organization’s projects
Establish basic project
management controls

53. ISO 9000 certification
• ISO (International Standards Organization) is a consortium of 63
countries established to formulate and foster standardization ISO
published its 9000 series of standards in 1987.
• ISO certification serves as a reference for contract between
independent parties
• ISO 9000 standard specifies the guidelines for maintaining a
quality system.

54. ISO 9000 certification
• Quality standards and procedures should be
documented in an organisational quality manual.
• An external body may certify that an organisation’s
quality manual conforms to ISO 9000 standards.
• Some customers require suppliers to be ISO 9000
certified although the need for flexibility here is
increasingly recognised.

55. ISO 9000 certification
• An international set of standards for quality management.
• Applicable to a range of organisations from manufacturing to service
industries.
• ISO 9001 applicable to organisations which design, develop and maintain
products.
• ISO 9001 is a generic model of the quality process that must be instantiated
for each organisation using the standard.

56. How to get an ISO 9000 Certification
• Application
• Pre-assessment
• Document review and adequacy of audit
• Compliance audit
• Registration
• Continued surveillance

57. Types of ISO 9000 quality standards
• ISO 9001 applies to the organizations engaged in design, development, production,
and servicing of goods. This is the standard that is applicable to most software
development organizations
• ISO 9002 applies to those organizations which do not design products but are only
involved in production. Examples of these category industries include steel and car
manufacturing industries that buy the product and plant designs from external
sources and are involved in only manufacturing those products.
• Therefore, ISO 9002 is not applicable to software development organizations.
• ISO 9003 applies to organizations that are involved only in installation and testing
of the products.

58. Need for obtaining ISO 9000 certification
• Confidence of customers in an organization increases when organization qualifies
for ISO certification. software organizations involved in software export to obtain
ISO 9000certification.
• ISO 9000 requires a well-documented software production process to be in place. A
well-documented software production process contributes to repeatable and higher
quality of the developed software.
• ISO 9000 makes the development process focused, efficient, and cost effective.
• ISO 9000 certification points out the weak points of an organization and
recommends remedial action.
• ISO 9000 sets the basic framework for the development of an optimal process and
Total Quality Management (TQM).

59. EXPECTED
QUALITY
by the Customer
PLANNED
QUALITY
by the Company
PRODUCED
QUALITY
by the Company
PERCEIVED
QUALITY
by the Customer
Measurement of the
Performance of the Company
Measurement of the
Client’s satisfaction
The ISO 9000:2000 requirements

60. ISO certification is awarded by an
international standard body and can
be quoted as an official document
Deals primarily for manufacturing
industry and provisioning of services
It aims at level 3 of CMM
Has Customer Focus as primary aim
and follows procedural controls
SEI CMM assessment is purely for
Internal use
CMM was developed specially for
Software industry and therefore ad
dresses software issues
Goes beyond Quality Assurance and
lead to TQM
Provide a list of Key Process Areas
to proceed from lower CMM level to
higher level to provide gradual
Quality improvements
ISO CMM
Differences Between

61. Shortcomings of ISO 9000 certification
• ISO 9000 requires a software production process to be adhered to but does
not guarantee the process to be of high quality.
• It also does not give any guideline for defining an appropriate process.
• ISO 9000 certification process is not fool-proof and no international
accreditation agency exists. Therefore it is likely that variations in the norms
of awarding certificates can exist among the different accreditation agencies
and also among the registrars.
• ISO 9000 does not automatically lead to continuous process improvement,
i.e. does not automatically lead to TQM.

62. Thank You