Muutke küpsiste eelistusi

E-raamat: CENELEC 50128 and IEC 62279 Standards

  • Formaat: PDF+DRM
  • Ilmumisaeg: 23-Mar-2015
  • Kirjastus: ISTE Ltd and John Wiley & Sons Inc
  • Keel: eng
  • ISBN-13: 9781119122494
Teised raamatud teemal:
  • Formaat - PDF+DRM
  • Hind: 171,60 €*
  • * hind on lõplik, st. muud allahindlused enam ei rakendu
  • Lisa ostukorvi
  • Lisa soovinimekirja
  • See e-raamat on mõeldud ainult isiklikuks kasutamiseks. E-raamatuid ei saa tagastada.
  • Raamatukogudele
CENELEC 50128 and IEC 62279 StandardsSuurem pilt
  • Formaat: PDF+DRM
  • Ilmumisaeg: 23-Mar-2015
  • Kirjastus: ISTE Ltd and John Wiley & Sons Inc
  • Keel: eng
  • ISBN-13: 9781119122494
Teised raamatud teemal:

DRM piirangud

  • Kopeerimine (copy/paste):

    ei ole lubatud

  • Printimine:

    ei ole lubatud

  • Kasutamine:

    Digitaalõiguste kaitse (DRM)
    Kirjastus on väljastanud selle e-raamatu krüpteeritud kujul, mis tähendab, et selle lugemiseks peate installeerima spetsiaalse tarkvara. Samuti peate looma endale  Adobe ID Rohkem infot siin. E-raamatut saab lugeda 1 kasutaja ning alla laadida kuni 6'de seadmesse (kõik autoriseeritud sama Adobe ID-ga).

    Vajalik tarkvara
    Mobiilsetes seadmetes (telefon või tahvelarvuti) lugemiseks peate installeerima selle tasuta rakenduse: PocketBook Reader (iOS / Android)

    PC või Mac seadmes lugemiseks peate installima Adobe Digital Editionsi (Seeon tasuta rakendus spetsiaalselt e-raamatute lugemiseks. Seda ei tohi segamini ajada Adober Reader'iga, mis tõenäoliselt on juba teie arvutisse installeeritud )

    Seda e-raamatut ei saa lugeda Amazon Kindle's. 

CENELEC EN 50128 and IEC 62279 standards are applicable to the performance of software in the railway sector. The 2011 version of the 50128 standard firms up the techniques and methods to be implemented. This is a guide to its implementation, in order to understand the foundations of the standard and how it impacts on the activities to be undertaken, helping towards better a preparation for the independent evaluation phase, which is mandatory.

Introduction xiii
Chapter 1 From the System to the Software
1(12)
1.1 Introduction
1(1)
1.2 Command/control system
2(4)
1.3 System
6(2)
1.4 Software application
8(3)
1.4.1 What is software?
8(1)
1.4.2 Different types of software
9(1)
1.4.3 The software application in its proper context
10(1)
1.5 Conclusion
11(2)
Chapter 2 Railway Standards
13(18)
2.1 Introduction
13(1)
2.2 Generic standards
14(2)
2.2.1 Introduction
14(1)
2.2.2 Safety levels
15(1)
2.3 History between CENELEC and the 1EC
16(1)
2.4 CENELEC referential framework
17(6)
2.4.1 Introduction
17(1)
2.4.2 Description
18(3)
2.4.3 Implementation
21(1)
2.4.4 Software safety
22(1)
2.4.5 Safety versus availability
22(1)
2.5 EN 50155 standard
23(3)
2.6 CENELEC 50128
26(4)
2.6.1 Introduction
26(1)
2.6.2 SSIL management
26(2)
2.6.3 Comparison of 2001 and 2011 versions
28(2)
2.7 Conclusion
30(1)
Chapter 3 Risk and Safety Integrity Level
31(36)
3.1 Introduction
31(1)
3.2 Basic definitions
31(6)
3.3 Safety enforcement
37(24)
3.3.1 What is safety?
37(3)
3.3.2 Safety management
40(7)
3.3.3 Safety integrity
47(3)
3.3.4 Determination of the SIL
50(5)
3.3.5 SIL table
55(1)
3.3.6 Allocation of SILs
56(1)
3.3.7 SIL management
57(1)
3.3.8 Software SIL
58(1)
3.3.9 Iterative process
59(1)
3.3.10 Identification of safety requirements
60(1)
3.4 In IEC 61508 and IEC 61511
61(5)
3.4.1 Risk graph
62(2)
3.4.2 LOPA
64(2)
3.4.3 Overview
66(1)
3.5 Conclusion
66(1)
Chapter 4 Software Assurance
67(42)
4.1 Introduction
67(1)
4.2 Prerequisites
67(1)
4.3 Quality assurance
68(10)
4.3.1 Introduction
68(1)
4.3.2 Quality assurance management
69(4)
4.3.3 Realization of a software application
73(2)
4.3.4 Software quality assurance plan (SQAP)
75(3)
4.4 Organization
78(4)
4.4.1 Typical organization
78(2)
4.4.2 Skill management
80(2)
4.5 Configuration management
82(2)
4.6 Safety assurance management
84(2)
4.7 Verification and validation
86(18)
4.7.1 Introduction
86(1)
4.7.2 Verification
87(16)
4.7.3 Validation
103(1)
4.8 Independent assessment
104(1)
4.9 Tool qualification
104(1)
4.10 Conclusion
105(1)
4.11 Appendix A: List of quality documents to be produced
106(1)
4.12 Appendix B: structure of a software quality assurance plan
106(3)
Chapter 5 Requirements Management
109(46)
5.1 Introduction
109(1)
5.2 Requirements acquisition phase
110(19)
5.2.1 Introduction
110(1)
5.2.2 Requirements elicitation
111(8)
5.2.3 Process of analysis and documentation
119(7)
5.2.4 Verification and validation of the requirements
126(3)
5.3 Requirements specification
129(11)
5.3.1 Requirements characterization
129(6)
5.3.2 Characterization of requirements specification
135(1)
5.3.3 Expression of requirements
135(5)
5.3.4 Requirements validation
140(1)
5.4 Requirements realization
140(10)
5.4.1 Process
140(1)
5.4.2 Verification
141(2)
5.4.3 Traceability
143(3)
5.4.4 Change management
146(4)
5.5 Requirements management
150(4)
5.5.1 Activities
150(1)
5.5.2 Two approaches
151(1)
5.5.3 Implementation of tools
152(2)
5.6 Conclusion
154(1)
Chapter 6 Data Preparation
155(46)
6.1 Introduction
155(1)
6.2 Recap
156(1)
6.3 Issue
156(2)
6.4 Data-parameter-based system
158(7)
6.4.1 Introduction
158(3)
6.4.2 Characterization of data
161(1)
6.4.3 Service inhibition
162(2)
6.4.4 Overview
164(1)
6.5 From the system to the software
165(4)
6.5.1 Need
165(2)
6.5.2 What the CENELEC framework does not say
167(2)
6.6 Data preparation process
169(5)
6.6.1 Context
169(1)
6.6.2 Presentation of section 8 of the CENELEC 50128:2011 standard
170(4)
6.7 Data preparation process
174(25)
6.7.1 Management of the data preparation process
174(8)
6.7.2 Verification
182(1)
6.7.3 Specification phase
182(4)
6.7.4 Architecture phase
186(4)
6.7.5 Data production
190(6)
6.7.6 Integration of the application and acceptance of the tests
196(1)
6.7.7 Validation and evaluation of the application
197(1)
6.7.8 Procedure and tools for preparation of the application
197(1)
6.7.9 Development of generic software
198(1)
6.8 Conclusion
199(1)
6.9 Appendix: documentation to be produced
199(2)
Chapter 7 Generic Application
201(60)
7.1 Introduction
201(1)
7.2 Software application realization process
201(2)
7.3 Realization of a generic application
203(46)
7.3.1 Specification phase
203(10)
7.3.2 Architecture and component design phase
213(23)
7.3.3 Component design phase
236(6)
7.3.4 Coding phase
242(1)
7.3.5 Execution of component tests
243(3)
7.3.6 Software integration phase
246(1)
7.3.7 Overall software testing phase
247(2)
7.4 Some feedback on past experience
249(1)
7.5 Conclusion
250(1)
7.6 Appendix A: the programming language "Ada"
251(2)
7.7 Appendix B: the programming language "C"
253(2)
7.7.1 Introduction
253(1)
7.7.2 The difficulty with C
253(1)
7.7.3 MISRA-C
254(1)
7.7.4 Example of a rule
255(1)
7.8 Appendix C: introduction to object-oriented languages
255(3)
7.9 Appendix D: documentation needing to be produced
258(3)
Chapter 8 Modeling and Formalization
261(26)
8.1 Introduction
261(1)
8.2 Modeling
261(4)
8.2.1 Objectives
261(2)
8.2.2 Different types of modeling
263(1)
8.2.3 Model
264(1)
8.3 Use of formal techniques and formal methods
265(4)
8.3.1 Definitions
265(3)
8.3.2 UML
268(1)
8.4 Brief introduction to formal methods
269(10)
8.4.1 Recap
269(1)
8.4.2 Usage in the railway domain
270(6)
8.4.3 Summary
276(3)
8.5 Implementation of formal methods
279(5)
8.5.1 Conventional processes
279(1)
8.5.2 Process including formal methods
280(2)
8.5.3 Issues
282(2)
8.6 Maintenance of the software application
284(1)
8.7 Conclusion
285(2)
Chapter 9 Tool Qualification
287(22)
9.1 Introduction
287(1)
9.2 Concept of qualification
288(5)
9.2.1 Issue
288(1)
9.2.2 CENELEC 50128:2001
288(3)
9.2.3 DO-178
291(1)
9.2.4 IEC 61508
292(1)
9.2.5 ISO 26262
293(1)
9.3 CENELEC 50128:2011
293(12)
9.3.1 Introduction
293(1)
9.3.2 Qualification file
294(1)
9.3.3 Qualification process
295(2)
9.3.4 Implementation of the qualification process
297(8)
9.4 Fitness for purpose
305(1)
9.4.1 Design method
305(1)
9.4.2 In case of incompatibility
305(1)
9.4.3 Code generation
306(1)
9.5 Version management
306(1)
9.5.1 Identification of versions
306(1)
9.5.2 Bug/defect analysis
307(1)
9.5.3 Changing versions
307(1)
9.6 Qualification process
307(1)
9.6.1 Qualification file
307(1)
9.6.2 Ultimately
308(1)
9.6.3 Qualification of non-commercial tools
308(1)
9.7 Conclusion
308(1)
Chapter 10 Maintenance and Deployment
309(12)
10.1 Introduction
309(1)
10.2 Requirements
309(3)
10.2.1 Fault management
309(1)
10.2.2 Managing changes
310(2)
10.3 Deployment
312(3)
10.3.1 Issue
312(1)
10.3.2 Implementation
313(1)
10.3.3 In reality
314(1)
10.4 Software maintenance
315(1)
10.4.1 Issue
315(1)
10.4.2 Implementation
315(1)
10.5 Product line
316(2)
10.6 Conclusion
318(1)
10.7 Appendix: documentation needing to be produced
319(2)
Chapter 11 Assessment and Certification
321(8)
11.1 Introduction
321(1)
11.2 Evaluation
321(4)
11.2.1 Principles
321(3)
11.2.2 CENELEC 50128:2011
324(1)
11.3 Cross-acceptance
325(1)
11.4 Certification
326(2)
11.4.1 Product certification
326(1)
11.4.2 Software certification
327(1)
11.4.3 Evolution management
327(1)
11.5 Conclusion
328(1)
11.6 Appendix: documentation needing to be produced
328(1)
Conclusion 329(2)
Bibliography 331(12)
Glossary 343(8)
Index 351
Jean-Louis Boulanger is currently an Independent Safety Assessor (ISA) in the railway domain focusing on software elements. He is a specialist in the software engineering domain (requirement engineering, semi-formal and formal method, proof and model-checking). He also works as an expert for the French notified body CERTIFER in the field of certification of safety critical railway applications based on software (ERTMS, SCADA, automatic subway, etc.). His research interests include requirements, software verification and validation, traceability and RAMS with a special focus on SAFETY.
Lisainfo e-raamatute kohta Lisainfo e-raamatute kohta
Püsilink: https://www.kriso.ee/db/97811191224942e.html
Märksõnad: