• Click to edit Master text styles

• Second level
• Third level
Introduction
• Fourth level
• Fifth level
[email protected]
 Measurement, Measures, Metrics
•Click to edit
If you can’t Master
measure textmanage
it, you can’t stylesit Tom DeMarco, 1982

• Second level
 Measurement
◦ is the act of obtaining a measure
• Third level
 Measure•
Fourth level
◦ provides a quantitative indication of the size of some product or process attribute,
• of errors
E.g., NumberFifth level
 Metric
◦ is a quantitative measure of the degree to which a system, component, or process
possesses a given attribute (IEEE Software Engineering Standards 1993): Software
Quality - E.g., Number of errors found per person-hours expended

06/08/2023 Software Metrics and Quality Assurance (SE717) -2-

 What to measure
•• Process
Click to edit Master text styles
• Second
Measure thelevel
efficacy of processes. What works, what doesn't.
• Third level
• Project • Fourth level
• Fifth level
Assess the status of projects. Track risk. Identify problem areas.
Adjust work flow.

• Product
Measure predefined product attributes
06/08/2023 Software Metrics and Quality Assurance (SE717) -3-
 What to measure
• Software
•• Click
Code quality
to edit Master text styles
• Maintainability
• Programmer
• Second level productivity • Usability
• Software
• Thirdengineer
level • And all other quality
productivity
• Fourth level factors
• Requirements,
• Fifth level • Management
• design, • Cost estimation
• testing • Schedule estimation,
• and all other tasks done by Duration, time
software engineers • Staffing

06/08/2023 Software Metrics and Quality Assurance (SE717) 4

 Process Metrics
••Process
Click tometrics
edit Master text styles
are measures of the software development
• Second
process, level
such as
• Third
• Overall level time
development
• Type of methodology
• Fourth levelused
• Process metrics are collected across all projects and over
• Fifth level
long periods of time.
• Their intent is to provide indicators that lead to long-term
software process improvement.

06/08/2023 Software Metrics and Quality Assurance (SE717) -5-

 Project Metrics
••Project
Click Metrics
to editare
Master text styles
the measures of Software Project and are
• Second
used level
to monitor and control the project. Project metrics usually
show• how
Thirdproject
level manager is able to estimate schedule and cost
• Fourth level
• They enable a software project manager to:
• Fifth level
 Minimize the development time by making the adjustments necessary
to avoid delays and potential problems and risks.
 Assess product cost on an ongoing basis & modify the technical
approach to improve cost estimation.

06/08/2023 Software Metrics and Quality Assurance (SE717) -6-

 Product metrics
••Product
Click tometrics
edit Master text styles
are measures of the software product at
• Second
any stage oflevel
its development, from requirements to the
• Third
installed system.
level Product metrics may measure:
• How•easy
Fourthis level
the software to use
• Fifth level
• How easy is the user to maintain
• The quality of software documentation
• And more ..

06/08/2023 Software Metrics and Quality Assurance (SE717) -7-

 Why do we measure?
• Click to edit Master text styles
• Second level
• Third level
• Fourth level
• Fifth level

06/08/2023 Software Metrics and Quality Assurance (SE717) -8-

 IEEE definitions of software quality metrics
• Click
(1) to edit Master
A quantitative text of
measure styles
the degree to which an item
possesses
• Secondalevel
given quality attribute.
(2) A •function
Third level whose inputs are software data and whose
output •isFourth
a single
level numerical value that can be interpreted
as the degree
• Fifthtolevel
which the software possesses a given
quality attribute.

06/08/2023 Software Metrics and Quality Assurance (SE717) -9-

 Main objectives of software quality metrics
1.• Click tomanagement
Facilitate edit Master textplanning
control, styles and managerial
intervention.
• Second level
Based on:
• Third level
        ·   Deviations of actual from planned performance.
• Fourth level
        ·   Deviations of actual
• Fifth level timetable and budget performance from
planned.
2. Identify situations for development or maintenance process
improvement (preventive or corrective actions). Based on:
        ·  Accumulation of metrics information regarding the performance of
teams, units, etc.

06/08/2023 Software Metrics and Quality Assurance (SE717) -10-

 Software size (volume) measures
••KLOC
Click to —edit Master
classic text
metric thatstyles
measures the size of
• Secondbylevel
software thousands of code lines.
• Thirdoflevel
• Number function points (NFP) — a measure of the
• Fourth level
development resources (human resources) required to
• Fifth level
develop a program, based on the functionality specified
for the software system.

06/08/2023 Software Metrics and Quality Assurance (SE717) -11-

 Process metrics categories
••Software
Click to edit quality
process Master text
metrics styles
•• Error density metrics
Second level
• Error severity metrics
• Third level
• Software process timetable metrics
• Fourth level
• Software process error removal effectiveness metrics
• Fifth level
• Software process productivity metrics

06/08/2023 Software Metrics and Quality Assurance (SE717) -12-

 Is KLOC enough ?
• Click to edit Master text styles
• Second level
• Third level
• Fourth level
• Fifth level

06/08/2023 Software Metrics and Quality Assurance (SE717) -13-

 Error density metrics
• Click
Code
toName
edit Master text styles Calculation formula
NCE
CED Code Error Density
• Second level CED = -----------
KLOC
NDE
DED Development Error Density
• Third level DED = -----------
KLOC
WCE
WCED Weighted Code Error Density WCDE = ---------
• Fourth level KLOC
WDED Weighted Development Error Density WDE
• Fifth level WDED = ---------
KLOC
WCEF Weighted Code Errors per Function Point WCE
WCEF = ----------
NFP
WDEF Weighted Development Errors per Function Point WDE
WDEF = ----------
NFP

NCE = The number of code errors detected by code inspections and testing.
NDE = total number of development (design and code) errors) detected in the development process.
WCE = weighted total code errors detected by code inspections and testing.
WDE = total weighted development (design and code) errors detected in the development process.

06/08/2023 Software Metrics and Quality Assurance (SE717) -14-

 Error severity metrics
• Click
Codeto edit Master text
Namestyles Calculation formula
•ASCE
Second level
Average Severity of Code Errors WCE
ASCE = -----------
NCE
• Third level
Average Severity of Development Errors WDE
ASDE ASDE = -----------
• Fourth level NDE

• Fifth level

NCE = The number of code errors detected by code inspections and testing.
NDE = total number of development (design and code) errors detected in the development process.
WCE = weighted total code errors detected by code inspections and testing.
WDE = total weighted development (design and code) errors detected in the development process.

06/08/2023 Software Metrics and Quality Assurance (SE717) -15-

 Software process timetable metrics
• Click to edit Master text styles
Code Name Calculation formula
• Second level
Time Table Observance MSOT
TTO TTO = -----------
• Third level MS
Average TCDAM
ADMC
• Fourth levelDelay of Milestone Completion ADMC = -----------
MS
• Fifth level

MSOT = Milestones completed on time.

MS = Total number of milestones.
TCDAM = Total Completion Delays (days, weeks, etc.) for all milestones.

06/08/2023 Software Metrics and Quality Assurance (SE717) -16-

 Time Table Metric Example
••TTO
Click to edit Master text styles
••Milestones
Second levelare Requirements, Analysis, Design, Implementation,
and• Third
Testinglevel
• E.g. Milestones completed in time are Requirements and analysis
• Fourth level
only then• TTO = 2/5
Fifth level
• ADMC
• Requirements (One week delay), Analysis (Three weeks delay),
Design (Two weeks delay), Implementation (Six weeks delay), and
Testing (Two weeks delay)
• Total Delay is 14 Weeks then ADMS = 14/5
06/08/2023 Software Metrics and Quality Assurance (SE717) -17-
 Error removal effectiveness metrics
• Click toName
Code edit Master text styles Calculation formula
Development Errors Removal NDE
DERE
• SecondEffectiveness
level DERE = ----------------
NDE + NYF
• ThirdDevelopment
DWERE level Weighted Errors WDE
DWERE = ------------------
Removal Effectiveness WDE+WYF
• Fourth level
• Fifthoflevel
NDE = total number development (design and code) errors) detected in the
development process.
WCE = weighted total code errors detected by code inspections and testing.
WDE = total weighted development (design and code) errors detected in
development process.
NYF = number software failures detected during a year of maintenance service.
WYF = weighted number of software failures detected during a year of maintenance
service.
06/08/2023 Software Metrics and Quality Assurance (SE717) -18-
 Error removal effectiveness metrics
••DERE
Click to edit Master text styles
••Number
Secondoflevel
errors detected at design and coding stages is 100
• Thirdof
• Number level
errors detected after one year of maintenance
• Fourth
service is 500level
• DERE=• 100/(100+500)
Fifth level

06/08/2023 Software Metrics and Quality Assurance (SE717) -19-

 Process productivity metrics
• Click toName
Code edit Master text styles Calculation formula
DevH
DevP
• Second Development Productivity
level DevP = ----------
KLOC
Function
FDevP• Third levelpoint Development Productivity DevH
FDevP = ----------
NFP
• Fourth level ReKLOC
CRe Code Reuse Cre = --------------
• Fifth level KLOC
ReDoc
DocRe Documentation Reuse DocRe = -----------
NDoc

DevH = Total working hours invested in the development of the software system.
ReKLOC = Number of thousands of reused lines of code.
ReDoc = Number of reused pages of documentation.
NDoc = Number of pages of documentation.
06/08/2023 Software Metrics and Quality Assurance (SE717) -20-
 Product metrics categories
*• Click to edit
Help Desk Master
(HD) quality text styles
metrics:
* HD calls density metrics - measured by the number of calls.
•*Second level
HD calls severity metrics - the severity of the HD issues raised.
* • HD
Third level
success metrics – the level of success in responding to HD calls.
* • Fourth level
HD productivity metrics.
* HD effectiveness metrics.
• Fifth level
* Corrective maintenance quality metrics.
* Software system failures density metrics
* Software system failures severity metrics
* Failures of maintenance services metrics
* Software system availability metrics
* Corrective maintenance productivity and effectiveness metrics.

06/08/2023 Software Metrics and Quality Assurance (SE717) -21-

 HD calls density metrics
• Click to edit Master
Code Nametext styles Calculation Formula
NHYC
HDD• Second
HD calls
leveldensity HDD = --------------
KLMC
WHDD • Third levelHD calls density
Weighted WHYC
WHYC = ------------
KLMC
• Weighted
Fourth level
HD calls per function point WHYC
WHDF WHDF = ------------
• Fifth level NMFP

NHYC = the number of HD calls during a year of service.

KLMC = Thousands of lines of maintained software code.
WHYC = weighted HD calls received during one year of service.
NMFP = number of function points to be maintained.

06/08/2023 Software Metrics and Quality Assurance (SE717) -22-

 Severity of HD calls and success metrics
• ClickCode
to edit
NameMaster text styles Calculation Formula
• Second
ASHC level
Average severity of HD calls WHYC
ASHC = --------------
NHYC
• Third level
NHYC = the number of HD calls during a year of service.
• Fourth level
WHYC = weighted HD calls received during one year of service.
• Fifth level
Code Name Calculation Formula
NHYOT
HDS HD service success HDS = --------------
NHYC

NHYNOT = Number of yearly HD calls completed on time during one year of service.
NHYC = the number of HD calls during a year of service.

06/08/2023 Software Metrics and Quality Assurance (SE717) -23-

 HD productivity and effectiveness metrics
• ClickCode
to edit Master text styles
Name Calculation Formula
• Second
HDP level
HD Productivity HDYH
HDP= --------------
KLNC
• Third level
Function Point HD Productivity HDYH
FHDP FHDP = ----------
• Fourth level NMFP
HDYH
HDE• Fifth
HDlevel
effectiveness HDE = --------------
NHYC

HDYH = Total yearly working hours invested in HD servicing of the software system.
KLMC = Thousands of lines of maintained software code.
NMFP = number of function points to be maintained.
NHYC = the number of HD calls during a year of service.

06/08/2023 Software Metrics and Quality Assurance (SE717) -24-

 Software system failures density metrics
• Click to edit Master
Code text styles
Name Calculation Formula
SSFD Software System Failure Density NYF
• Second level SSFD = --------------
KLMC

• Third
WSSFD Weighted
level Software System Failure WYF
WFFFD = ---------
Density KLMC
• Fourth level
WSSFF Weighted Software System Failures WYF
WSSFF = ----------
• Fifth
per level point
Function NMFP

NYF = number of software failures detected during a year of maintenance service.

WYF = weighted number of yearly software failures detected during one year of maintenance service.
NMFP = number of function points designated for the maintained software.
KLMC = Thousands of lines of maintained software code.

06/08/2023 Software Metrics and Quality Assurance (SE717) -25-

 Failures of maintenance services metrics
• Click to edit Master text styles
Code
Name Calculation Formula
• Second level
MRepF Maintenance Repeated RepYF
MRepF = --------------
• repair Failure metric -
Third level NYF

• Fourth level
• Fifth level

        NYF = number of software failures detected during a year of maintenance service.
RepYF = Number of repeated software failure calls (service failures).

06/08/2023 Software Metrics and Quality Assurance (SE717) -26-

 Software system availability metrics
• ClickCode
to editName
Master text styles
Calculation Formula
NYSerH - NYFH
FA Full Availability
• Second level FA = -----------------------
NYSerH
NYSerH - NYVitFH
VitA level
• Third Vital Availability VitA = -----------------------------
NYSerH
• FourthTotal
TUA levelUnavailability NYTFH
TUA = ------------
• Fifth level NYSerH
 NYSerH = Number of hours software system is in service during one year.  
NYFH = Number of hours where at least one function is unavailable (failed) during one year, including total failure of the software
system.
 NYVitFH = Number of hours when at least one vital function is unavailable (failed) during one year, including total failure of the
software system.
 NYTFH = Number of hours of total failure (all system functions failed) during one year.
NYFH ≥ NYVitFH ≥ NYTFH. 1 – TUA ≥ VitA ≥FA

06/08/2023 Software Metrics and Quality Assurance (SE717) -27-

 The process of defining software quality metrics
• Click to edit Master text styles
• Second level
• Third level
• Fourth level
• Fifth level

06/08/2023 Software Metrics and Quality Assurance (SE717) -28-

 General limitations of quality metrics
• Click
 to constraints
Budget edit Master text styles
in allocating the necessary resources.
 •Human
Second factors
level , especially the opposition of employees to the
• Third of
evaluation level
their activities.
• Fourth level
 Validity Uncertainty regarding the data's, partial and biased
• Fifth level
reporting.

06/08/2023 Software Metrics and Quality Assurance (SE717) -29-

 Other Metrics
• Click to edit Master text styles
Understanding
 Learning time: Time for new user to gain basic understanding of features of the
•software
Second level
 Ease•ofThird level
learning
 Learning time: Time for new user to learn how to perform basic functions of the
• Fourth level
software
 Operability• Fifth level
 Operation time: Time required for a user to perform operation(s) of the software
 Usability
 Human factors: Number of negative comments from new users regarding
ergonomics, human factors, etc.

06/08/2023 Software Metrics and Quality Assurance (SE717) -30-

 Definition of software
• Click totoedit
According the Master
IEEE: text styles
• Second
• Software level programs, procedures, and possibly associated
is: Computer
documentation and data pertaining to the operation of a computer system.
• Third level
A ‘similar definition
• Fourth level comes from ISO:
• ISO definition (from
• Fifth ISO 9000-3) lists four components necessary to
level
assure the quality of the software development process and years of
maintenance:
• computer programs (code)
• procedures
• documentation
• data necessary for operating the software system.
06/08/2023 Software Metrics and Quality Assurance (SE717) -31-
 Basic Definitions
••Software
Click to edit– made
Error Master text styles
by programmer
• Syntax (grammatical) error
• Second level
• Logic error (multiply vice add two operands)
• Third
• Software Fault level
–
• Fourth
• All software level
errors may not cause software faults
• That part of •theFifth level
software may not be executed
• (An error is present but not encountered….)

• Software Failures – Here’s the interest.

• A software fault becomes a software failure when/if it is activated.
• Faults may be found in the software due to the way the software is executed or other constraints
on the software’s execution, such as execution options.
• Some runs result in failures; some not.
• Example: standard software running in different client shops.

06/08/2023 Software Metrics and Quality Assurance (SE717) -32-

 The Nine Causes of Software Errors
1.•FClick to edit Master
aulty requirements text
definition styles
• Second level
• Usually considered the root cause of software errors
• Incorrect requirement definitions
• Third level
• Simply stated, ‘wrong’ definitions (formulas, etc.)
• Fourth level
• Incomplete definitions
• Fifth level
• Unclear or implied requirements
• Missing requirements
• Just flat-out ‘missing.’ (e.g. Program Element Code)
• Inclusion of unneeded requirements
• (many projects have gone amuck for including far too many requirements that will never be used.
• Impacts budgets, complexity, development time, …

06/08/2023 Software Metrics and Quality Assurance (SE717) -33-

 The Nine Causes of Software Errors
• Click to edit Master
2.Client-developer text styles
communication failures
• •Misunderstanding
Second level of instructions in requirements documentation
• Third level of written changes during development.
• Misunderstanding
• Misunderstanding
• Fourth level
of oral changes during development.
• Fifth level
• Lack of attention
• to client messages by developers dealing with requirement changes and
• to client responses by clients to developer questions
• Very often, these very talented individuals come from different planets, it
seems.
• Clients represent the users; developers represent a different mindset entirely some times!

06/08/2023 Software Metrics and Quality Assurance (SE717) -34-

 The Nine Causes of Software Errors
• Click to edit
3.Deliberate Masterfrom
deviations textsoftware
styles requirements
••Developer
Secondreuses
levelprevious / similar work to save time.
• Often reused code needs modification which it may not get or contains
• Third level
unneeded / unusable extraneous code.
• Fourthdeveloper(s)
• Book suggests level may overtly omit functionality due to time /
• Fifth level
budget pressures.
• Another BAD choice; System testing will uncover these problems to everyone’s dismay!
• I have never seen this done intentionally!
• Developer inserting unapproved ‘enhancements’ (perfective coding; a slick
new sort / search….); may also ignore some seemingly minor features, which
sometimes are quite major.
• Have seen this and it too causes problems and embarrassment during reviews.

06/08/2023 Software Metrics and Quality Assurance (SE717) -35-

 The Nine Causes of Software Errors
• Click to edit Master
4. Logical design errors text styles
• Second that
• Definitions level
represent software requirements by means of erroneous
• Third level
algorithms.
• Fourth
• Yep! Wrong level
formulas; Wrong Decision Logic Tables; incorrect text; wrong operators / operands…

• Process definitions:
• Fifth level
procedures specified by systems analyst not accurate
reflection of the business process specified.
• Note: all errors are not necessarily software errors.
• This seems like a procedural error, and likely not a part of the software system…

• Erroneous Definition of Boundary Condition – a common source of errors

• The “absolutes” like ‘no more than’ “fewer than,” “n times or more;” “the first time,” etc.

06/08/2023 Software Metrics and Quality Assurance (SE717) -36-

 The Nine Causes of Software Errors
• Click
4. to edit
Logical Master
design text
errors styles
(continued)
••Omission
Second level
of required software system states
••IfThird level
rank is >= O1 and RPI is numeric, then….easy to miss action
• Fourth
based level
on the software system state.
• Omission • Fifth level
of definitions concerning reactions to illegal
operation of the software system.
• Including code to detect an illegal operation but failure to
design the computer software reaction to this:
• Gracefully terminate, sound alarm, etc.

06/08/2023 Software Metrics and Quality Assurance (SE717) -37-

 The Nine Causes of Software Errors
• Click
5. Codingtoerrors
edit Master text styles
••Too
Second
manylevel
to try to list.
••Syntax
Third level
errors (grammatical errors)
• Fourth
• Logic errorslevel
(program runs; results wrong)
• Fiftherrors
• Run-time level (crash during execution)

06/08/2023 Software Metrics and Quality Assurance (SE717) -38-

 The Nine Causes of Software Errors
6.• Click to edit w/documentation
Non-compliance Master text styles
& coding instructions
• Second level
• Non-compliance with published templates (structure)
• Non-compliance with coding standards (attribute names…)
• Third level
• (Standards and Integration Branch)
•
• Size ofFourth level
program;
• Fifth level
• Other programs must be able to run in environment!
• Data Elements and Codes: AFM 300-4;
• Required documentation manuals and operating instructions; AFDSDCM 300-8,
etc…
• SQA Team: testing not only execution software but coding standards; manuals,
messages displayed; resources needed; resources named (file names, program
names,…)
06/08/2023 Software Metrics and Quality Assurance (SE717) -39-
 The Nine Causes of Software Errors
••7.Click to edit Master
Shortcomings text styles
of the Testing Process
• •Likely
Second levelof the development process cut short most frequently!
the part
• Third level
• Incomplete test plans
• Parts of application
• Fourth level not tested or tested thoroughly!
• Failure to• document,
Fifth level report detected errors and faults
• So many levels of testing….we will cover.
• Failure to quickly correct detected faults due to unclear indications
that there ‘was’ a fault
• Failure to fix the errors due to time constraints
• Many philosophies here depending on severity of the error.

06/08/2023 Software Metrics and Quality Assurance (SE717) -40-

 The Nine Causes of Software Errors
8.• Click to editand
User interface Master texterrors
procedure styles
• Second level
9. Documentation
• Third levelerrors
• Errors in the design documents
• Fourth level
• Trouble for subsequent redesign and reuse
• Fifth level
• Errors in the documentation within the software for the User Manuals
• Errors in on-line help, if available.
• Listing of non-existing software functions
• Planned early but dropped; remain in documentation!
• Many error messages are totally meaningless

06/08/2023 Software Metrics and Quality Assurance (SE717) -41-

 The Nine Causes of Software Errors
• Click
The to editof Master
nine causes text styles
software errors are:
•aulty
1.F Second level definition
requirements
2.Client-developer communication failures
• Third level
3.Deliberate deviations from software requirements
• Fourth level
4.Logical design errors
• Fifth level
5.Coding errors
6.Non-compliance with documentation and coding instructions
7.Shortcomings of the testing process
8.User interface and procedure errors
9.Documentation errors
• You should be conversant with these
06/08/2023 Software Metrics and Quality Assurance (SE717) -42-
 What is Software Quality?
••As
Click to edit
you will see, Master text
there is no styles
commonly-agreed to definition.
• Second
• Software level is: 
quality
• Third
(1) The levelto which a system, component, or process
degree
• Fourth
meets level requirements.
specified
• Fifth level
by Philip Crosby
(2) The degree to which a system, component, or process
meets customer or user needs or expectations.
by Joseph M. Juran
• Now, more closely…
06/08/2023 Software Metrics and Quality Assurance (SE717) -43-
 What is Software Quality?
• Click toquality
Software edit Master text styles
is: (IEEE)
1.• Second level
The degree to which a system, component, or process meets
specified requirements.
• Third level
• Seems to emphasize
• Fourth level the specification, assuming the customer
has articulated all
• Fifth level that is needed in the specs AND that if the
specs are met, the customer will be satisfied.
• this is not necessarily the case, that, if fact, often ‘serious’ systems
are first deployed (errors discovered in specs sometimes very
serious);
• customers acquire to the deployment with understanding of a follow-on
deployment.
06/08/2023 Software Metrics and Quality Assurance (SE717) -44-
 What is Software Quality?
• Click toquality
Software edit Master text styles
is: (Joseph Juran)
• Second
2. levelto which a system, component, or process
The degree
• Thirdcustomer
meets level or user needs or expectations.
• Fourth
• Here, level is on a satisfied customer whatever it takes.
emphasis
• Fifth
Implies specs may need corrections
level
• But this seems to free the customer from ‘professional
responsibility’ for the accuracy and completeness of the specs!
• Assumption is that real needs can be articulated during
development. This may occur, but in fact major problems can
be discovered quite late. Not a happy customer!
06/08/2023 Software Metrics and Quality Assurance (SE717) -45-
 What is Software Quality?
• Click to
Software edit is:
quality Master
(Rogertext styles
Pressman)
4) •Conformance
Second levelto explicitly stated functional and performance
requirements,
• Third level (meets the specs)
• Discuss: ‘functional’
• Fourth level and ‘performance’ specs!!
• Explicitly documented
• Fifth level development standards, and seems to
imply a documented development process
• Implicit characteristics that are expected of all professionally
developed software further seems to imply quality as found
in reliability, maintainability, scalability, usability, and more

06/08/2023 Software Metrics and Quality Assurance (SE717) -46-

 What is Software Quality?
•• Click to Quality
Software edit Master text styles
Assurance is:
1. •A
Second
plannedlevel
and systematic pattern of all actions
• Third level
necessary to provide adequate confidence that an item
• Fourth level
or product conforms to established technical
• Fifth level
requirements.
2. A set of activities designed to evaluate the process by
which the products are developed or manufactured.
Contrast with: quality control.
•More closely:
06/08/2023 Software Metrics and Quality Assurance (SE717) -47-
 What is Software Quality?
• Click to edit Master text styles
• Says to plan and implement systematically! shows progress and instills confidence software is coming along

• Refers to a software development process a methodology; a way of doing things;

• Second level
•Refers to the specification of technical requirements must have these.
• Third level
• Note that SQA must include not only process for development but for
• Fourth level
• (hopefully) years of maintenance. So, we need to consider quality issues
• Fifth level
• affecting not only development but also maintenance into overall SQA concept.
• SQA activities must also include scheduling and budgeting.
• SQA must address issues that arise when time constraints are encountered
are features eliminated? Budget constraints may force compromise
when/if inadequate resources are allocated to development and/or maintenance.

06/08/2023 Software Metrics and Quality Assurance (SE717) -48-

 SQA - Expanded Definition
••Software
Click to edit
qualityMaster text styles
assurance is:
••ASecond level
systematic, planned set of actions necessary to provide
adequate
• Third confidence
level that the software development process or
the maintenance
• Fourth levelprocess of a software system product conforms
to established
• Fifth functional
level technical requirements as well as with
the managerial requirements of keeping the schedule and
operating within the budgetary confines.
• This SQA definition supports the concept of the ISE 9000
standards regarding SQA, and corresponds to main outlines of
the Capability Maturity Model (CMM) for software.
06/08/2023 Software Metrics and Quality Assurance (SE717) -49-
 Software Quality Assurance vs. Software Quality Control
different objectives.
••Quality
Click Control
to editisMaster
defined astext styles
a designed to evaluate the quality of a set of
activities
• Second developed
level or manufactured product
• We have QC inspections during development and before deployment
• QC• activities
Third levelare only a part of the total range of QA activities.
• Fourth level
• Quality Assurance’s objective is to minimize the cost of guaranteeing
quality by a• variety
Fifth level
of activities performed throughout the
development / manufacturing processes / stages.
• Activities prevent causes of errors; detect and correct them early in the
development process
• QA substantially reduces the rate of products that do not qualify for shipment
and/at the same time, reduce the costs of guaranteeing quality in most cases.

06/08/2023 Software Metrics and Quality Assurance (SE717) -50-

 The objectives of SQA activities
• Click
In to edit
Software Master text
Development styles
(Process-oriented)
• Second
(1) Assuring level
an acceptable level of confidence that the software
•will conform
Third level to functional technical requirements.
• Fourthan
(2) Assuring acceptable level of confidence that the software
level
will conform to managerial scheduling and budgetary
• Fifth level
requirements.
(3) Initiation and management of activities for the
improvement and greater efficiency of software
development and SQA activities.

06/08/2023 Software Metrics and Quality Assurance (SE717) -51-

 The objectives of SQA activities
• Click
In to edit
Software Master text
Maintenance styles
(Product-oriented)
• Second
(1) level
Assuring an acceptable level of confidence that the
• Third level
software maintenance activities will conform to the
functional technical requirements.
• Fourth level
• Fifth
(2) Assuring anlevel
acceptable level of confidence that the
software maintenance activities will conform to
managerial scheduling and budgetary requirements.
(3) Initiate and manage activities to improve and increase the
efficiency of software maintenance and SQA activities.

06/08/2023 Software Metrics and Quality Assurance (SE717) -52-

• Click to edit Master text styles
• Second level
• Third level

Question?
• Fourth level
• Fifth level