IEC PAS 62814:2012
(Main)Dependability of software products containing reusable components - Guidance for functionality and tests
Dependability of software products containing reusable components - Guidance for functionality and tests
IEC/PAS 62814:2012(E) introduces the concept of assuring reused components and their usage within new products. It provides information and criteria about the tests and analysis required for products containing such reused parts. The objective is to support the engineering requirements for functionality and tests of reusable software components and composite systems containing such components in evaluating and assuring reuse dependability. Keywords: reused software components, dependability
General Information
Standards Content (Sample)
IEC/PAS 62814 ®
Edition 1.0 2012-12
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
Dependability of software products containing reusable components – Guidance
for functionality and tests
IEC/PAS 62814:2012(E)
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.
IEC Central Office Tel.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
Useful links:
IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org
The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and
by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and
committee,…). definitions in English and French, with equivalent terms in
It also gives information on projects, replaced and additional languages. Also known as the International
withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.
IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc
Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication
details all new publications released. Available on-line and or need further assistance, please contact the
also once a month by email. Customer Service Centre: csc@iec.ch.
IEC/PAS 62814 ®
Edition 1.0 2012-12
PUBLICLY AVAILABLE
SPECIFICATION
PRE-STANDARD
Dependability of software products containing reusable components – Guidance
for functionality and tests
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XA
ICS 03.120.01 ISBN 978-2-83220-501-3
– 2 – PAS 62814 © IEC:2012(E)
CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviations . 8
3.1 Terms related to software engineering . 8
3.2 Terms related to software dependability . 9
3.3 Terms related to software reuse . 10
3.4 General terms . 13
3.5 Abbreviations . 13
4 Dependability of software reuse methodology – Reusability-driven software
development . 13
4.1 General . 13
4.2 Dependability methods for reuse . 15
4.3 Dependability-related objectives of software reuse . 16
4.4 Ingredients of software reuse and hypotheses for reuse dependability . 17
5 Software reuse dependability methodology applications . 18
5.1 Application aspects and organization of dependable software reuse . 18
5.1.1 General . 18
5.1.2 Pre-store characteristics of reusability . 19
5.1.3 Pre-use characteristics of reusability . 20
5.1.4 Build-for-reuse . 20
5.1.5 Build-by-reuse . 21
5.1.6 Coupling “build-for-reuse” and “build-by-reuse” . 22
5.2 Validation, re-validation and reliability of software reuse . 25
5.3 Naïve assumptions and rules for improving software reuse dependability . 26
5.4 Dependability and reuse aspects of software/hardware interaction . 26
5.4.1 General . 26
5.4.2 Reuse of software with an upgrade / remanufactured hardware . 26
5.4.3 Limitations of hardware . 27
5.4.4 Limitations due to incompatibilities . 27
5.4.5 Dependability, energy consumption and ecology. 27
6 Software reuse assurance . 27
6.1 General . 27
6.2 Build for reuse – Validation and qualification of components to be reused . 28
6.2.1 General . 28
6.2.2 Validation and qualification . 28
6.2.3 Assessment of quantifiable quality targets . 28
6.3 Build by reuse – Validation and qualification of the receiving system . 28
6.3.1 General . 28
6.3.2 Validation and qualification . 28
6.3.3 Assessment of quantifiable quality targets . 29
7 Warranty and documentation . 29
7.1 General . 29
7.2 Life cycle, contextual criticality, warranty period . 29
7.3 Product documentation . 29
PAS 62814 © IEC:2012(E) – 3 –
7.4 Product safety and control . 29
7.5 Legal aspects . 29
7.5.1 General . 29
7.5.2 Contractual issues . 29
7.5.3 Product liability . 30
Annex A (informative) General remarks on software reuse . 31
Annex B (informative) Qualification and integration of reusable software components . 33
Annex C (informative) Testing and integration of reusable software components –
Issues for industrial best practice . 37
Annex D (informative) Example of software pre-use . 46
Annex E (informative) Influence of reused software to hardware components and
products . 50
Bibliography . 52
Figure 1 – Approaches to software reuse and its elements . 15
Figure 2 – Elements of the reuse process . 17
Figure 3 – Integration of the reusable component . 17
Figure 4 – Characteristics of reusability . 19
Figure 5 – Build-for-reuse framework . 21
Figure 6 – Build-by-reuse framework . 22
Figure 7 – Combining “build-for-reuse” and “build-by-reuse” . 24
Figure A.1 – Service-oriented architecture . 31
Figure C.1 – A test process in vendor-oriented component testing [30] . 38
Figure C.2 – A validation process for completely reused components [30] . 40
Figure C.3 – A Validation process for adapted and customized components . 41
Figure C.4 – Maturity levels for a component testing process . 43
Figure D.1 – Example of a supervision task . 49
Table 1 – Summary of reuse classification . 14
Table C.1 – Testing issues of reusable software components . 43
Table D.1 – Operating experience, monolithic view . 47
Table D.2 – Operating experience, use of the individual paths . 47
Table D.3 – Production demands, use of the individual paths; the values of p did not
i
change. 48
– 4 – PAS 62814 © IEC:2012(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DEPENDABILITY OF SOFTWARE PRODUCTS
CONTAINING REUSABLE COMPONENTS –
GUIDANCE FOR FUNCTIONALITY AND TESTS
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
memb
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.