Software Quality Unit 6 SE

Software Quality
Software Quality Assurance Activities

Software Quality control
• Software quality control product is defined in

term of its fitness of purpose. That is, a quality
product does what the users want it to do. For
software products, the fitness of use is generally
explained in terms of satisfaction of the
requirements laid down in the SRS document.
Although "fitness of purpose" is a satisfactory
interpretation of quality for many devices such
as a car, a table fan, a grinding machine, etc.
view of a quality control associated with a software product several quality
methods such as the following:
• Portability: A software device is said to be portable, if it can be freely

made to work in various operating system environments, in multiple
machines, with other software products, etc.
• Usability: A software product has better usability if various categories of
users can easily invoke the functions of the product.
• Reusability: A software product has excellent reusability if different
modules of the product can quickly be reused to develop new products.
• Correctness: A software product is correct if various requirements as
specified in the SRS document have been correctly implemented.
• Maintainability: A software product is maintainable if bugs can be easily
corrected as and when they show up, new tasks can be easily added to the
product, and the functionalities of the product can be easily modified, etc.
Quality control System Activities: The quality system
activities encompass the following:
• Auditing of projects
• Review of the quality system
• Development of standards, methods, and guidelines, etc.
• Production of documents for the top management
summarizing the effectiveness of the quality system in
the organization.
Software Quality Assurance
• Software quality assurance is a planned and systematic plan of all actions
necessary to provide adequate confidence that an item or product
conforms to establish technical requirements.
• A set of activities designed to calculate the process by which the products
are developed or manufactured.
• A quality management approach
• Effective Software engineering technology (methods and tools)
• Formal technical reviews that are tested throughout the software process
• A multitier testing strategy
• Control of software documentation and the changes made to it.
• A procedure to ensure compliances with software development standards
• Measuring and reporting mechanisms.
Software Quality Assurance Activities
• Software quality assurance is composed of a variety of functions. SQA group
that has responsibility for quality assurance planning, record keeping,
analysis, and reporting.
Following activities are performed by an independent SQA group:
1. Prepares an SQA plan for a project
2. Participates in the development of the project's software process
description
3. Reviews software engineering activities to verify compliance with the
defined software process
4. Audits designated software work products to verify compliance with those
defined as a part of the software process
5. Ensures that deviations in software work and work products are
documented and handled according to a documented procedure
6. Records any noncompliance and reports to senior management
Quality Assurance v/s Quality control
Project Monitoring and Control
• Monitoring and Controlling are processes needed to track, review, and regulate
the progress and performance of the project. It also identifies any areas where
changes to the project management method are required and initiates the
required changes.
• The Monitoring & Controlling process group includes eleven processes, which
are:
• Monitor and control project work: The generic step under which all other
monitoring and controlling activities fall under.
• Perform integrated change control: The functions involved in making changes
to the project plan. When changes to the schedule, cost, or any other area of
the project management plan are necessary, the program is changed and re-
approved by the project sponsor.
• Control scope: Ensuring that the scope of the project does not change and
that unauthorized activities are not performed as part of the plan (scope
creep).
• Control schedule: The functions involved with ensuring the project work is
performed according to the schedule, and that project deadlines are met.
• Control costs: The tasks involved with ensuring the project costs stay
within the approved budget.
• Control quality: Ensuring that the quality of the project?s deliverables
is to the standard defined in the project management plan.
• Control communications: Providing for the communication needs of
each project stakeholder.
• Control Risks: Safeguarding the project from unexpected events that
negatively impact the project's budget, schedule, stakeholder needs, or
any other project success criteria.
• Control procurements: Ensuring the project's subcontractors and
vendors meet the project goals.
• Control stakeholder engagement: The tasks involved with ensuring that
all of the project's stakeholders are left satisfied with the project work.
Software Engineering Institute Capability Maturity
Model (SEICMM)
• The Capability Maturity Model (CMM) is a procedure used to develop and refine an
organization's software development process.
• The model defines a five-level evolutionary stage of increasingly organized and consistently
more mature processes.
• Level 1: Initial
• Ad hoc activities characterize a software development organization at this level. Very few
or no processes are described and followed. Since software production processes are not
limited, different engineers follow their process.
• Level 2: Repeatable
• At this level, the fundamental project management practices like tracking cost and
schedule are established. Size and cost estimation methods, like function point analysis,
COCOMO, etc. are used.
• Level 3: Defined
• At this level, the methods for both management and development activities are defined
and documented. There is a common organization-wide understanding of operations,
roles, and responsibilities. The ways through defined, the process and product qualities are
not measured. ISO 9000 goals at achieving this level.
• Level 4: Managed
• At this level, the focus is on software metrics. Two kinds of metrics are
composed.
• Product metrics measure the features of the product being developed,
such as its size, reliability, time complexity, understandability, etc.
• Process metrics follow the effectiveness of the process being used, such as
average defect correction time, productivity, the average number of
defects found per hour inspection, the average number of failures detected
during testing per LOC, etc. The software process and product quality are
measured, and quantitative quality requirements for the product are met.
• Level 5: Optimizing
• At this phase, process and product metrics are collected. Process and
product measurement data are evaluated for continuous process
improvement.

Software Quality Unit 6 SE

Uploaded by

Copyright:

Available Formats

Software Quality Unit 6 SE

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Software Quality Unit 6 SE

Uploaded by

Copyright:

Available Formats

Software Quality

Software Quality Assurance Activities

• Software quality control product is defined in

• Portability: A software device is said to be portable, if it can be freely

You might also like