Escolar Documentos
Profissional Documentos
Cultura Documentos
2.
3.
Software products:
SW products
Complexity
Visibility
Nature of
development and
production
process
Important Conclusion
SQA environment
The main characteristics of this environment :
1.
2.
3.
4.
5.
6.
7.
Contractual conditions
Subjection to customer-supplier relationship
Required teamwork
Cooperation and coordination with other SW teams
Interfaces with other SW systems
The need to continue carrying out a project despite
team member changes.
The need to continue out SW maintenance for
extended period.
8
Contractual conditions
the activities of SW development & maintenance need to
cope with :
10
Required teamwork
requirements
The need of variety
The wish to benefit from professional
mutual support & review for
enhancement of project quality
11
12
Input interfaces
Output interfaces
I/O interfaces to the machines control board,
as in medical and lab. Control systems
13
14
( Modification )
15
Chapter 2
16
What is Software ?
IEEE Definition:
Software Is :
Computer programs, procedures, and possibly
associated documentation and data pertaining
to the operation of a computer system.
17
18
TO sum up:
Software quality assurance always
includes :
Code quality
The quality of the documentation
And the quality of the necessary SW
data
19
20
21
error
Documentation error
SW data error
22
23
1.
2.
3.
4.
24
In written forms
Orally
Responses to the design problems
others
25
26
Erroneous algorithms
Process definitions that contain sequencing
errors
Erroneous definition of boundary conditions
Omission of required SW system states
Omission of definitions concerning reactions to
illegal operations
27
Coding errors
28
Such as
Procedure errors
31
Documentation errors
of software functions.
Errors in the explanations and instructions
Listing of non-existing software functions
32
2.
33
34
1.
2.
SQA is :
A planned and systematic pattern of all actions
necessary to provide adequate confidence that
an item or product conforms to established
technical requirements.
A set of activities designed to evaluate the
process by which the products are developed
or manufactured. Contrast with quality control.
35
37
38
Chapter 3
Software Quality Factors
40
SQ. Factors
41
42
43
46
Integrity:
48
49
50
Testability :
Deal with the testing of an IS as well as with its operation.
Providing predefined intermediate results and log files.
Automatic diagnostics performed by the SW system prior
starting the system, to find out whether all components of
SW system are in working order.
Obtain a report about detected faults.
51
Different HW
Different OS
Example : SW designed to work under windows 2000 env. Is
required to allow low-cost transfer to Linux.
-
52
Reusability :
Deals with the use of SW modules originally designed
for one project in a new SW project currently begin
developed.
The reuse of SW is expected to save resources., shorten
the project period, and provide higher quality modules.
These benefits of higher quality are based on the
assumption that most SW faults have already been
detected by SQA activities performed previously on it.
53
54
Reusability
Verifiability
Porotability
Chapter 4
The Components Of the SQA system- Overview
58
components
Components of project life cycle activities assessment
Components of infrastructure error prevention and
improvement.
Components of SQ management
Components of standardization, certification, and SQA
system assessment
Organizing for SQA- the human components
59
Pre-project Components :
To assure that :
1. The project commitments have been
adequately defined considering the resources
required, the schedule and budget.
2. The development and quality plans have been
correctly determined.
60
62
63
64
Part II
Pre-project SQ components
Chapter 5
Contract Review
66
Contract Review
Is the software quality element that reduces the
probability of undesirable situation. See page
78
Contract review is a requirement by the ISO 9001
and ISO 9000-3 guidelines.
67
in a tender
Submission of a proposal according to the
customers RFP.
Receipt of an order from a companys customer
Receipt of an internal request or order from
another department in the organization
68
Contract review :
is
If
69
70
71
72
73
74
75
Time pressures
Proper contract review requires substantial professional work
The potential contract review team members are very busy.
76
77
78
79
Chapter 6
Development and quality plans
80
2.
3.
4.
5.
81
Project products
Project interfaces
Project methodology and development tools
SW development standards and procedures
The mapping of the development process.( proj. mgt. Gantt )
Project milestones ( documents , code , report )
Project staff organization ( org. stru., prof. req., no of team
mem., names of team leaders )
Development facilities ( SW, HW tools, space, period req. for
each use )
Development risks ( see next slide )
Control methods
Project cost estimation
82
Development risks
1.
2.
3.
83
3.
The type
Who responsible
84
5.
Purchased SW
Subcontractor SW
Customer supplied SW
85
86
Chapter 7
Integrating Quality activities in the project life
cycle
SDLC ( Req. def. , Analysis, Design, Coding, sys. Tests, install and
conversion, op. and maintenance )
87
88
89
Spiral Model
Planning
Risk analysis and resolution
Engineering activities
Customer evaluation, comment, changes, etc
90
91
Economy
Improve quality
Shorter development time
92
93
Timing
Who perform & the resources required
Team members, external body for QA
94
Project factors
Team factors
97
98
2.
99
100
101
The Model
103
104
105
106
Chapter 8
Reviews
107
Reviews Objectives
( Direct Objectives )
109
110
The participants
The prior preparations
The DR session
The recommended post-DR activities
113
The participants in a DR
114
115
Preparation for a DR
Preparation for a DR
Preparation for a DR
118
The DR session
4.
Decisions forms :
120
121
122
123
124
Peer Reviews
two review methods ( Inspection and Walkthrough )
125
126
127
A review leader
The author
Specialized professional
For inspections:
A designer
A coder or implementer
A tester
For walkthrough:
A standards enforcer
A maintenance expert
A user representative.
128
Team assignments
The presenter
The Scribe
129
Leader preparation
Teams preparation
130
Session Documentation
by the scribe
by the leader
131
133
Comparisons
134
in-house proff.
Temporary lack in-house proff.
Disagreements
135
Chapter 9
Software testing - Strategies
Testing Definition :
IEEEdefinition:
1.
2.
136
Direct objectives:
To
Indirect objectives
To
Bottom-Up
141
142
144
145
Main disadv.
The lateness at which the prog. As whole can be observed ( at the stage
following testing of the last module )
Main disadv.
The relative difficulty of preparing the required stubs, with often require
very complicated programming.
146
White
148
149
150
Example (1/4)
Imperial Taxi Services (ITS) serves one-time passengers and regular clients
(identified by a taxi card). The ITS taxi fares for one-time passengers are
calculated as follows:
(1) Minimal fare: $2. This fare covers the distance traveled up to 1000 yards and
waiting time (stopping for traffic lights or traffic jams, etc.) of up to 3 minutes.
(2) For every additional 250 yards or part of it: 25 cents.
(3) For every additional 2 minutes of stopping or waiting or part thereof: 20 cents.
(4) One suitcase: no charge; each additional suitcase: $1.
(5) Night supplement: 25%, effective for journeys between 21.00 and 06.00. 191
9.4 White box testing
(6) Regular clients are entitled to a 10% discount and are not charged the night
supplement.
Example (2/4)
Example (3/4)
Example (4/4)
158
A set of input variable values that produce the same output results
or that are processed identically.
Its boundaries are defined by
159
160
Example
Example
Example
Documentation tests
164
Reliability tests
165
Stress tests
load
tests
166
Stress tests
Durability tests
They are typically required for real-time
firmware
These test include
167
168
Maintainability tests
Concerned by:
System structure compliance to the
standards and development procedures
Programmers manual
Internal documentation
169
Portability tests
Interoperability test
170
Advantages
Disadvantages
171
Chapter 10
Software testing
Implementation
172
174
Unit tests
Deal
Integration tests
Deal
System tests
Refer
175
What to test?
So we must decide
Which
Factor
178
179
180
Should we use
Synthetic test case
Real-life test cases
181
182
System tests
183
184
185
186
Test design
Composed of
Detailed design and procedures for each test
The software test procedure document
Test case database/file
187
Test implementation
In general it consists of
A
series of tests
Corrections of detected errors
Re-tests (regression tests)
Test implementation
Automated testing
planning
Test design
Test case preparation
Test performance
Test log and report preparation
Re-testing after correction of detected
errors (regression tests)
Final test log and report preparation
including comparison reports
190
Automated testing
191
Automated testing
Coverage
monitoring
192
Automated testing
193
Automated testing
Automated testing
195
Automated testing
196
197
Advantages
Identification of unexpected errors
A wider population in search of errors
Low costs
Disadvantages
A lack of systematic testing
Low quality error reports
Difficult to reproduce the test environment
Much effort is required to examine reports
199
Chapter 11
Assuring the quality of software
maintenance components
200
Corrective maintenance
Adaptive maintenance
customer requirements,
Functionality improvement maintenance
perfective maintenance of new functions added to the
software so as to enhance performance,
preventive maintenance activities that improve
reliability and system infrastructure for easier
and more efficient future maintainability
201
Code failure
software
Documentation failure
users
failure
202
203
Maintenance policy
204
Maintenance policy
205
Maintenance policy
version policy
206
Maintenance policy
version policy
Software package can evolve into a multiversion package, a tree with several main
branches and numerous secondary
branches, each branch representing a
version with specialized revisions
More difficult and time-consuming
Some organizations apply a limited tree
version policy
See example P260
207
Maintenance policy
Change policy
Refers to the method of examining
each change request and the
criteria used for its approval
Permissive policy contributes to an
often-unjustified increase in the
change task load
208
Maintenance policy
Change policy
A balanced policy is preferred
209
210
211
212
213
214
215
the CAB
216
Configuration management
Failure repair
Software system version installed at the customers site
A copy of the current code and its documentation
Group
replacement
217
Chapter 12
218
Subcontractors outsourcing
Undertake to carry out parts of a project
Advantages : staff availability, special expertise or
low prices.
Advantages:
reduce time and cost
increase quality: since these components have already
been tested and corrected by the developers and
previous customers
219
why?
Apply the customers special expertise,
respond to commercial or other security
needs
Keep internal development staff occupied,
prevent future maintenance problems
Disadvantages:
220
221
222
2.
3.
4.
223
6.
of information
Systematic evaluation of the suppliers
224
Collection of information
Internal
Auditing
225
Chapter 17
226
Corrective actions:
A
Preventive actions:
A
Information collection
Analysis of information
Development of solutions and
improved methods
Implementation of improved methods
Follow-up.
229
230
Information collection
231
Information collection
232
Generating feedback
233
3.
4.
5.
234
Follow-up of activities
1.
2.
3.
235
Can be
members
CAPA records
Screening the collected information
Nominating entire ad hoc CAPA
teams
Promoting implementation of CAPA
Following up
237
Chapter 21
238
Quality metrics
IEEE definition
A quantitative measure of the degree
to which an item possesses a given
quality attribute
239
Deviations of actual
240
241
Classification
Process
Product
metrics
metrics
242
Measures
Function Point
A method used to provide pre-project
estimates of project size, stated in terms of
required development resources
It measures project size by functionality,
indicated in the customers or tender
requirement specification
244
245
on detailed requirements
specifications or software system
specifications, which are not always
available at the preproject stage
Requires an experienced function point
team
Cannot be universally applied
246
Process metrics
1.
density metrics
Error severity metrics.
2.
3.
4.
247
Process metrics
measures:
Software volume
Errors counted
Relate to the number of errors or to the weighted number
of errors (severity of the errors)
Application of weighted measures can lead to decisions
different than those arrived at with simple (unweighted)
metrics
weighted measures are assumed to be better indicators of
adverse situations
248
Process metrics
249
Process metrics
250
Process metrics
251
Process metrics
2.
252
Process metrics
2.
253
Process metrics
3.
The
254
Process metrics
3.
255
Process metrics
4.
256
Process metrics
4.
257
Product metric
Corrective
maintenance services
258
Product metric
HD quality metrics
HD productivity and effectiveness metrics
Corrective maintenance quality metrics
Corrective maintenance productivity and
effectiveness metrics
259
Product metric
1.
260
Product metric
2.
metrics
E.g. HD Productivity:
KLMC = thousands of lines of maintained software code
HDYH = total yearly working hours invested in HD servicing
of the software system
Effectiveness
metrics
261
Product metric
3.
Software
Product metric
4.
263
4.
CAB committees
Project team
264
CHAPTER 22
266
of control
Prevention costs
Appraisal costs
Costs
of failure of control
270
271
1) Prevention costs
272
1) Prevention costs
273
2) Appraisal costs
Costs
of software testing:
Costs
275
276
277
278
279
280
281
282
Updating
283
284
285
286
288
This
289
Chapter 23
SQA Standards
290
291
292
Customer focus
Leadership
Involvement of people
Process approach
System approach to management
Continual improvement
Factual approach to decision making
Mutually supportive supplier relationships
293
294
Development
295
296
297
298
299
enhancement of software
development is composed of five-level
maturity model
300
301
302
CMMI motivation
303
CMMI structure
304
CMMI structure
305
CMMI structure
Capability level:
Maturity level
306
CMMI structure
1:
2:
3:
4:
5:
Initial
Managed
Defined
Quantitatively managed
Optimizing
307
309
311
312
313