Software Engineering

College of Arts, Media and Technology ,CMU.

Kittitouch S.
1.2-23-1-12
version Change detail Release date Author
1.0 - 5-1-12 Kittitouch
1.1 Add topics of
-Process Model:ETVX
9-1-12 Kittitouch
-Factors affecting intensity of
quality assurance activities in
the development process.
-Verification, validation and
qualification

1.2 Add topics of

-A model for SQA. defect
23-1-12 Kittitouch
removal effectiveness and cost.
 Classic and other software development
methodologies.
 Factors affecting intensity of quality
assurance activities in the development
process.
 Process Model:ETVX
 Verification, validation and qualification
 A model for SQA. defect removal
effectiveness and cost.
 The Software Development Life Cycle (SDLC)
model
 The prototyping model
 The spiral model
 The object-oriented model.
 Classic model.
 The model displays the major building blocks
for the entire development process.
 The most common illustration of the SDLC
model is the waterfall model
 Requirements definition.
 The customers must define their requirements. In
many cases the software system is part of a larger
system. Information about the other parts of the
expanded system helps establish cooperation
between the teams and develop component
interfaces.
 Analysis
 The main effort here is to analyze the
requirements’ implications to form the initial
software system model.
 Design.
 This stage involves the detailed definition of the
outputs, inputs and processing procedures,
including data structures and databases, software
structure
 Coding.
 The design is translated into a code.
 Coding involves quality assurance activities such
as inspection, unit tests and integration tests.
 System tests.
 The main goal of testing is to uncover as many
software errors as possible so as to achieve an
acceptable level of software quality once
corrections have been completed.
 Installation and conversion.
 The system is installed to serve as firmware, that is, as
part of the information system that represents a
major component of the expanded system.

 If the new information system is to replace an existing

system, a software conversion process has to be
initiated to make sure that the organization’s activities
continue uninterrupted during the conversion phase.
 Regular operation and maintenance.
 Throughout the regular operation period, which
usually lasts for several years or until a new
software generation appears on the scene,
maintenance is needed.
 Maintenance incorporates three types of services.
▪ Corrective – repairing software faults
▪ Adaptive – using the existing software features to fulfill
new requirements
▪ Perfective – adding new minor features to improve
software performance
The prototyping methodology makes use of..

 developments in information technology,

namely, advanced application generators
that allow for fast and easy development of
software prototypes.

 active participation in the development

process by customers and users capable of
examining and evaluating prototypes.
The prototyping model
 Prototyping as a software development
methodology has been found to be efficient
and effective mainly for small- to medium-
sized software development projects.
 Advantages of prototyping:
 Shorter development process.
 Substantial savings of development
resources(man-days).
 Better fit to customer requirements and reduced
risk of project failure.
 Easier and faster user comprehension of the new
system.
 Disadvantages of prototyping:
 Diminished flexibility and adaptability to changes
and additions.
 Reduced preparation for unexpected instances of
failure.
 The spiral model, as revised by Boehm (1988,
1998), offers an improved methodology for
overseeing large and more complex
development projects displaying higher
prospects for failure, typical of many projects
begun in the last two decades.
The spiral model
The advanced
spiral model
 The object-oriented model differs from the
other models by its intensive reuse of
software components.

 This methodology is characterized by its easy

integration of existing software modules
(called objects or components) into newly
developed software systems.
The object-oriented
model
 Economy – The cost of integrating a reusable software
component is much lower than the cost of developing
new components.

 Shorter development time – The integration of

reusable software components reduces scheduling
pressures.

 Improved quality – Used software components are

expected to contain considerably fewer defects than
newly developed software components due to
detection of faults by former users.
Quality assurance planners for a project are
required to determine:
 The list of quality assurance activities needed for
a project.
 For each quality assurance activity:
 Timing
 Type of quality assurance activity to be applied
 Who performs the activity and the resources required.
 Resources required for removal of defects and
introduction of changes.
 ETVX: Entry-Task-Validation-Exit
 Entry criteria define what inputs are required and
what quality these must be to achieve the exit
criteria. Entry criteria should be communicated to
supplier processes, to become their exit criteria. If
supplier processes are sufficiently well controlled,
then there is no need to check inputs.

 Task definitions specify the actions within the

process.
 Validation definitions identify test points within
the process and define the tests and criteria for
checking at these points. This enables problems
to be caught close to their cause, reducing
rework and scrap costs, and enabling problem
causes to be addressed.
 Exit criteria define what outputs are required
and what quality these must be to meet the
needs of customer processes. Exit criteria may
be derived from the entry criteria of customer
processes.
 Read Example 1-2; page 132-133
 “Verification – The process of evaluating a
system or component to determine whether
the products of a given development phase
satisfy the conditions imposed at the start of
that phase.”
 “Validation – The process of evaluating a
system or component during or at the end of
the development process to determine
whether it satisfies specified requirements.”
 “Qualification – The process used to
determine whether a system or component is
suitable for operational use.”
 The model deals with two quantitative
aspects of an SQA plan consisting of several
defect detection activities:

1. The plan’s total effectiveness in removing

project defects.
2. The total costs of removal of project defects
 Defect origin distribution
 Defect removal effectiveness
 Cost of defect removal
 Defect origins (the phase in which defects
were introduced) are distributed throughout
the development process, from the project’s
initiation to its completion
 It is assumed that any quality assurance activity
filters (screens) a certain percentage of existing
defects. It should be noted that in most cases,

 The percentage of removed defects is somewhat

lower than the percentage of detected defects as
some corrections are ineffective or inadequate.

 The remaining defects, those undetected and

uncorrected, are passed to successive development
phases.
 POD = Phase Originated Defects (from Table 7.3)
 PD = Passed Defects (from former phase or former quality assurance
activity)
FE

RD

CDR

TRC
 the model applies to a standard quality assurance plan that is composed
of six quality assurance activities as shown in Table 7.6.
Continue next slide
Continue next slide
 Chapter 7:Daniel Galin. SOFTWARE QUALITY ASSURANCE From
theory to implementation. Pearson Education Limited,2004.