The document discusses software quality management and configuration management. It defines quality management as establishing organizational processes and standards to ensure a product satisfies its specifications and customer satisfaction. Key quality management activities include quality assurance, planning, and control. Configuration management is defined as maintaining consistency of a product's attributes with requirements. It involves configuration management planning, change management, version and release management, and system building. Quality control checks that development procedures are followed as defined in the quality plan.

1. SOFTWARE QUALITY AND
CONFIGURATION MANAGEMENT
Presented by:
Souparnika Padaki Patil
3/11/2018
1
Software Quality and Configuration Management

2. SOFTWARE QUALITY MANAGEMENT
Quality means that a product satisfies the demands of its
specifications. It also means achieving a high level of customer
satisfaction with the product.
• At organizational level: Establishing a framework
of organizational processes and standards.
• At project level : have a check on planned
process and matching output with standards.
• Quality management at the project level is also
concerned with establishing a quality plan for a
project
SQM
Principles:
• Quality assurance and standards
• Quality planning
• Quality control
SQM
Activities:
3/11/2018
2
Software Quality and Configuration Management

3. QUALITY PLANNING
3/11/2018
3
 A quality plan sets out the desired product qualities and how
these are assessed and define the most significant quality
attributes.
 Structure of quality management:
 Product introduction
 Product plans
 Process descriptions
 Quality goals
 Risks and risk management
 Quality management attributes:
1.Safety 2.Understandability 3.Security
4.Reliability 5.Adaptability 6.Portability
7.Accessibility 8.Reusability etc..
Software Quality and Configuration Management

4. QUALITY CONTROL
• Checking the software development process (within a
particular project) to ensure that procedures and standards, as
defined in the quality plan, are being followed
• Two approaches to quality control
• (Manual) Quality reviews – main approach
• (Automated) Quality measurement
• Types of reviews:
• Design or program inspection. (part of software validation )
• Progress reviews. ( part of project)
• Quality reviews. ( part of quality management)
3/11/2018
4
Software Quality and Configuration Management

5. SOFTWARE CONFIGURATION
MANAGEMENT
Configuration management (CM) is a systems engineering process for
establishing and maintaining consistency of a product's performance,
functional, and physical attributes with its requirements, design, and
operational information.
What is the need of configuration management??
• Configuration management
planning
• Change management
• Version and release management
• System building
SCM activities:
CM Standards
3/11/2018
5
Software Quality and Configuration Management

6. CM Planning
 Starts during the early phases of the project
 All products of the software process may have
to be managed
• Specifications
• Designs
• Programs
• Test data
• User manuals
3/11/2018
6
Software Quality and Configuration Management

7. CHANGE MANAGEMENT
 Software systems are subject to continual change requests:
• From users
• From developers
• From market forces
 Change management is concerned with keeping track of
these changes and ensuring that they are implemented in
the most cost-effective way.
 Deciding factors for approval of change are:
 The consequences of not making the change
 The benefits of the change
 The number of users affected by the change
 The costs of making the change
3/11/2018
7
Software Quality and Configuration Management

8. VERSION AND RELEASE MANAGEMENT
Version management
• Version management (VM) is the process of keeping track of different
versions of software components or configuration items and the systems
in which these components are used.
• It also involves ensuring that changes made by different developers to
these versions do not interfere with each other.
• Feature of version management:
• Version and release identification
• Storage management
• Change history recording
• Independent development
• Project support
3/11/2018
8
Software Quality and Configuration Management

9. RELEASE MANAGEMENT
• Releases incorporate changes forced on the
system by errors discovered by users and by
hardware changes
• They also incorporate new system functionality
• Release planning is concerned with when to issue
a system version as a release
• System release’s : what it is and what does it
includes.
• Release problems.
• Release creation
3/11/2018
9
Software Quality and Configuration Management

10. 3/11/2018
10
Software Quality and Configuration Management