Chapter 4

Software Engineering
College of Arts, Media and Technology ,CMU.
SE422 Software Quality Assurance

CH-4 Components of the SQA system
Kittitouch S.
1.2-26-11-12
Topics
 The SQA system
 Pre-project component
 Software project life cycle components
 Infrastructure components for error prevention and
improvement
 Management SQA components
 SQA standards, system certification, and
assessment components
 Organizing for SQA
 Considerations guiding construction of an
organization’s SQA system
The SQA system-an SQA architecture
 Software is…
▪ High complexity.
▪ Invisible product.
▪ Hard to search and fix defect(bug).
 SQA system components can be classified

into six classes:
The SQA system
1.Pre-Project components
resources required
•
2. Components of project life cycle
activities assessment.
–Reviews
–Expert opinions
–Software testing.
Operation
maintenance
3. Components of infrastructure error
prevention and improvement.
to eliminate or at least
reduce the rate of errors
4. Components of software quality
management.
prevent or minimize
schedule and
budget failures and their
outcomes.
5. Components of standardization,
certification, and SQA system assessment
The main objectives of (5.)
 Utilization of international professional
knowledge.
 improvement of coordination of the

organizational quality systems with other
organizations.
 assessment of the achievements of quality

systems according to a common scale.
Organizing for SQA – the human
components.
initiate and support
the implementation
of SQA
components, detect
deviations from SQA
procedures and
methodology, and
suggest
improvements.
The SQA system
Pre-project components
-Contract review
 Contract- the development unit is committed to an
agreed-upon functional specification, budget and schedule.
 examination of…
 the project proposal draft.
 the contract drafts.
Contract review activities(1/2)
 Clarification of the customer’s requirements
 Review of the project’s schedule and resource

requirement estimates
 Evaluation of the professional staff’s capacity

to carry out the proposed project
Contract review activities(2/2)
 Evaluation of the customer’s capacity to fulfill

his obligations
 Evaluation of development risks.

Pre-project components
-Development and quality plans
a plan is prepared of the project (“development
plan”) and its integrated quality assurance
activities (“quality plan”). These plans include
additional details and needed revisions based on
prior plans that provided the basis for the
current proposal and contract.
It is quite common for several months to pass

between the tender submission and the signing
of the contract.
The main issues treated in the project
development plan are:
 Schedules
 Required manpower and hardware resources
 Risk evaluations
 Organizational issues: team members,
subcontractors and partnerships
 Project methodology, development tools,
etc.
 Software reuse plans.
The main issues treated in the
project’s quality plan are:
 Quality goals, expressed in the appropriate
measurable terms
 Criteria for starting and ending each project

stage
 Lists of reviews, tests, and other scheduled

verification and validation activities.
Reading Assignment
 Read the examples of Project Plan and

Quality Plan in SQA. site.
The SQA system
Software project life cycle components
 Reviews
 Expert opinions
 Software testing
 Software maintenance
 Assurance of the quality of the subcontractors’

work and the customer supplied parts.
Reviews
 The design phase of the development

process produces a variety of documents.
The printed products include design reports,
software test documents, software installation
plans and software manuals, among others.
Reviews can be categorized as
 formal design reviews (DRs)
 peer reviews.
Formal design reviews (DRs)
 The committees are composed of senior

professionals, including the project leader
and, usually, the department manager, the
chief software engineer, and heads of other
related departments.
 The DR report itself includes a list of required

corrections (termed “action items”).
Formal design reviews (DRs)
 When a design review committee sits in order to decide
upon the continuation of the work completed so far, one of
the following options is usually open for consideration:
 Immediate approval of the DR document and continuation to the
next development phase.
 Approval to proceed to the next development phase after all the

action items have been completed and inspected by the
committee’s representative.
 An additional DR is required and scheduled to take place after all

the action items have been completed and inspected by the
committee’s representative.
Peer reviews
 Peer reviews (inspections and walkthroughs)

are directed at reviewing short documents,
chapters or parts of a report, a coded printout
of a software module.
 usually, the reviewers are all peers, not

superiors, who provide professional
assistance to colleagues.
Peer reviews
 The main objective of inspections and

walkthroughs is to detect as many design and
programming faults as possible.
 The output is a list of detected faults and, for

inspections, also a defect summary and
statistics to be used as a database for
reviewing and improving development
methods.
Expert opinions
 Expert opinions support quality assessment

efforts by introducing additional external
capabilities into the organization’s in-house
development process. Turning to outside
experts may be particularly useful in the
following situations: bna5od r2y el5obra2
Expert opinions (more in page 62)
 Insufficient in-house professional capabilities

in a given area.
 In small organizations in many cases it is

difficult to find enough suitable candidates to
participate in the design review teams.
 In cases of major disagreement among the

organization’s
Software testing
 Software tests are formal SQA components

that are targeted toward review of the actual
running of the software. The tests are based
on a prepared list of test cases that represent
a variety of expected scenarios.
 The test report will include a detailed list of

the faults detected and recommendations.
Software maintenance components
 Software maintenance services vary in range

and are provided for extensive periods, often
several years. These services fall into the
following categories:
 Corrective maintenance – User’s support

services and correction of soft-ware code and
documentation failures
Software maintenance components
 Adaptive maintenance – Adaptation of

current software to new circumstances and
customers without changing the basic
software product.
 Functionality improvement maintenance –

The functional and performance related
improvement of existing software, carried
out with respect to limited issues.
Assurance of the quality of the
external participant’s work
 Subcontractors and customers frequently
join the directly contracted developers (the
“supplier”) in carrying out software
development projects. The larger and more
complex the project, the greater the
likelihood that external participants will be
required, and the larger the proportion of
work trans-mitted to them
The SQA system
Infrastructure components for error
prevention and improvement
 Procedures and work instructions
 Templates and checklists
 Staff training, retraining, and certification
 Preventive and corrective actions
 Configuration management
 Documentation control.
Management SQA components
Management SQA components
 Project progress control (including

maintenance contract control)
 Software quality metrics
 Software quality costs.

SQA standards, system certification, and
SQA standards, system certification, and
 Quality management
 SEI CMM assessment standard
 ISO 9001 and ISO 9000-3 standards.
 Project process standards

 IEEE 1012 standard
 ISO/IEC 12207 standard.
 ISO/IEC 29110 standard
Organizing for SQA
– the human components
Organizing for SQA
 Management’s role in SQA

 The responsibilities of top management
 The SQA unit

 This unit and software testers are the only parts of
the SQA organizational base that devote
themselves full-time to SQA matters.
Organizing for SQA
 SQA trustees, committees and forums
 SQA trustees are members of development and
maintenance teams who have a special interest in
software quality and are prepared to devote part
of their time to these issues.
Referrence
 Chapter 4:Daniel Galin. SOFTWARE QUALITY ASSURANCE From

theory to implementation. Pearson Education Limited,2004.

Chapter 4

Uploaded by

Copyright:

Available Formats

Chapter 4

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

Chapter 4

Uploaded by

Copyright:

Available Formats

Software Engineering

College of Arts, Media and Technology ,CMU.

SE422 Software Quality Assurance

 SQA system components can be classified

 improvement of coordination of the

 assessment of the achievements of quality

 Clarification of the customer’s requirements

 Review of the project’s schedule and resource

 Evaluation of the professional staff’s capacity

 Evaluation of the customer’s capacity to fulfill

 Evaluation of development risks.

It is quite common for several months to pass

 Criteria for starting and ending each project

 Lists of reviews, tests, and other scheduled

 Read the examples of Project Plan and

 Assurance of the quality of the subcontractors’

 The design phase of the development

 The committees are composed of senior

 The DR report itself includes a list of required

 Approval to proceed to the next development phase after all the

 An additional DR is required and scheduled to take place after all

 Peer reviews (inspections and walkthroughs)

 usually, the reviewers are all peers, not

 The main objective of inspections and

 The output is a list of detected faults and, for

 Expert opinions support quality assessment

 Insufficient in-house professional capabilities

 In small organizations in many cases it is

 In cases of major disagreement among the

 Software tests are formal SQA components

 The test report will include a detailed list of

 Software maintenance services vary in range

 Corrective maintenance – User’s support

 Adaptive maintenance – Adaptation of

 Functionality improvement maintenance –

 Project progress control (including

 Software quality metrics

 Software quality costs.

 Project process standards

 Management’s role in SQA

 The SQA unit

 Chapter 4:Daniel Galin. SOFTWARE QUALITY ASSURANCE From

You might also like

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.