IEEE 1633 2016:2017 Edition
$104.54
IEEE Recommended Practice on Software Reliability
Published By | Publication Date | Number of Pages |
IEEE | 2017 | 261 |
Revision Standard – Active. The methods for assessing and predicting the reliability of software, based on a life-cycle approach to software reliability engineering (SRE), are prescribed in this recommended practice. It provides information necessary for the application of software reliability (SR) measurement to a project, lays a foundation for building consistent methods, and establishes the basic principle for collecting the data needed to assess and predict the reliability of software. The recommended practice prescribes how any user can participate in SR assessments and predictions.
PDF Catalog
PDF Pages | PDF Title |
---|---|
1 | IEEE Std 1633-2016 Front cover |
2 | Title page |
4 | Important Notices and Disclaimers Concerning IEEE Standards Documents |
7 | Participants |
9 | Introduction |
11 | Copyrights and Permissions |
13 | Contents |
15 | 1. Overview 1.1 Scope 1.2 Purpose 2. Normative references |
16 | 3. Definitions, acronyms, and abbreviations 3.1 Definitions |
19 | 3.2 Acronyms and abbreviations |
22 | 4. Role, approach, and concepts 4.1 What is software reliability engineering? 4.2 Strategy |
24 | 4.3 Project-specific SRE tailoring |
31 | 4.4 Life-cycle considerations for SRE |
35 | 5. Software reliability procedure 5.1 Plan for software reliability |
57 | 5.2 Develop failure modes model |
68 | 5.3 Apply software reliability during development |
111 | 5.4 Apply software reliability during testing |
137 | 5.5 Support release decision |
143 | 5.6 Apply software reliability in operation |
149 | 6. Software reliability models 6.1 Overview |
150 | 6.2 Models that can be used before testing |
160 | 6.3 Models that can be used during and after testing |
169 | Annex A (informative) Software failure modes effects analysis templates A.1 Templates for preparing the software failure modes effects analysis (SFMEA) |
171 | A.2 Templates for analyzing the failure modes and root causes |
175 | A.3 Template for consequences |
176 | A.4 Template for mitigation |
177 | Annex B (informative) Methods for predicting software reliability during development B.1 Methods for predicting code size |
181 | B.2 Additional models for predicting defect density or defects |
187 | B.3 Factors that have been correlated to fielded defects |
190 | Annex C (informative) Additional information on software reliability models used during testing C.1 Models that can be used when the fault rate is peaking C.2 Models that can be used when the fault rate is decreasing |
195 | C.3 Models that can be used with increasing and then decreasing fault rate |
197 | C.4 Models that can be used regardless of the fault rate trend |
198 | C.5 Models that estimate remaining defects |
199 | C.6 Results of the IEEE survey |
201 | Annex D (informative) Estimated relative cost of SRE tasks |
204 | Annex E (informative) Software reliability engineering related tools |
206 | Annex F (informative) Examples F.1 Examples from 5.1 |
210 | F.2 Examples from 5.2 |
221 | F.3 Examples from 5.3 |
231 | F.4 Examples from 5.4 |
252 | F.5 Examples from 5.5 |
253 | F.6 Examples from 5.6 |
255 | Annex G (informative) Bibliography |