CENELEC 50128 and IEC 62279 Standards

Name: CENELEC 50128 and IEC 62279 Standards
Brand: Wiley-ISTE
Price: 139.99 EUR
Availability: OnlineOnly

Jean-Louis Boulanger(Autor*in)

Wiley-ISTE (Verlag)

Erschienen am 23. März 2015

378 Seiten

E-Book

PDF mit Adobe-DRM

Systemvoraussetzungen

978-1-119-12249-4 (ISBN)

139,99 €inkl. 7% MwSt.

Systemvoraussetzungen

für PDF mit Adobe-DRM

E-Book Einzellizenz

Als Download verfügbar

Beschreibung

Weitere Details

Weitere Ausgaben

Inhalt

Cover
Title Page
Copyright
Contents
Introduction
I.1. Objective
I.2. Reminder
I.3. Overview
1: From the System to the Software
1.1. Introduction
1.2. Command/control system
1.3. System
1.4. Software application
1.4.1. What is software?
1.4.2. Different types of software
1.4.3. The software application in its proper context
1.5. Conclusion
2: Railway Standards
2.1. Introduction
2.2. Generic standards
2.2.1. Introduction
2.2.2. Safety levels
2.3. History between CENELEC and the IEC
2.4. CENELEC referential framework
2.4.1. Introduction
2.4.2. Description
2.4.3. Implementation
2.4.4. Software safety
2.4.5. Safety versus availability
2.5. EN 50155 standard
2.6. CENELEC 50128
2.6.1. Introduction
2.6.2. SSIL management
2.6.2.1. SSIL attribution
2.6.2.2. Choice of SSIL
2.6.3. Comparison of 2001 and 2011 versions
2.6.3.1. CENELEC 50128:2001
2.6.3.2. EN 50128:2011
2.7. Conclusion
3: Risk and Safety Integrity Level
3.1. Introduction
3.2. Basic definitions
3.3. Safety enforcement
3.3.1. What is safety?
3.3.2. Safety management
3.3.3. Safety integrity
3.3.4. Determination of the SIL
3.3.5. SIL table
3.3.6. Allocation of SILs
3.3.7. SIL management
3.3.8. Software SIL
3.3.9. Iterative process
3.3.10. Identification of safety requirements
3.4. In IEC 61508 and IEC 61511
3.4.1. Risk graph
3.4.2. LOPA
3.4.3. Overview
3.5. Conclusion
4: Software Assurance
4.1. Introduction
4.2. Prerequisites
4.3. Quality assurance
4.3.1. Introduction
4.3.2. Quality assurance management
4.3.2.1. Prescriptions of standard in force
4.3.2.2. ISO 9001:2008
4.3.2.3. Indicator
4.3.3. Realization of a software application
4.3.4. Software quality assurance plan (SQAP)
4.4. Organization
4.4.1. Typical organization
4.4.2. Skill management
4.5. Configuration management
4.6. Safety assurance management
4.7. Verification and validation
4.7.1. Introduction
4.7.2. Verification
4.7.2.1. Presentation
4.7.2.2. Activity of verification
4.7.2.3. Static analysis
4.7.2.4. Dynamic analysis
4.7.2.4.1. Test strategy
4.7.2.4.2. Coverage of tests
4.7.2.5. Summary
4.7.3. Validation
4.8. Independent assessment
4.9. Tool qualification
4.10. Conclusion
4.11. Appendix A: list of quality documents to be produced
4.12. Appendix B: structure of a software quality assurance plan
5: Requirements Management
5.1. Introduction
5.2. Requirements acquisition phase
5.2.1. Introduction
5.2.2. Requirements elicitation
5.2.2.1. Introduction
5.2.2.2. Identification of stakeholders
5.2.2.3. Identification of sources
5.2.3. Process of analysis and documentation
5.2.3.1. Subdivision of the process
5.2.3.2. Requirements analysis phase
5.2.3.2.1. Objectives
5.2.3.2.2. Elicitation techniques
5.2.3.2.3. Interview techniques
5.2.3.2.4. Prototyping and simulation techniques
5.2.3.3. Description production phase
5.2.4. Verification and validation of the requirements
5.2.4.1. Introduction
5.2.4.2. Verification
5.2.4.3. Validation
5.3. Requirements specification
5.3.1. Requirements characterization
5.3.1.1. Identification
5.3.1.2. A few important characteristics
5.3.1.3. Characterization of a set of requirements
5.3.1.4. Characterization of the process
5.3.1.5. Additional
5.3.2. Characterization of requirements specification
5.3.3. Expression of requirements
5.3.3.1. Natural language
5.3.3.2. Construction of a glossary
5.3.3.3. Formalization
5.3.3.4. Formulation by use of a template
5.3.3.5. Modeling
5.3.4. Requirements validation
5.4. Requirements realization
5.4.1. Process
5.4.2. Verification
5.4.2.1. Objective of verification
5.4.2.2. Documentary review
5.4.3. Traceability
5.4.4. Change management
5.4.4.1. Introduction
5.4.4.2. Nothing is perfect
5.4.4.3. Accepting change
5.4.4.4. Impact of change
5.5. Requirements management
5.5.1. Activities
5.5.2. Two approaches
5.5.2.1. Database-centered approach
5.5.2.2. Document-centered approach
5.5.3. Implementation of tools
5.6. Conclusion
6: Data Preparation
6.1. Introduction
6.2. Recap
6.3. Issue
6.4. Data-parameter-based system
6.4.1. Introduction
6.4.2. Characterization of data
6.4.3. Service inhibition
6.4.4. Overview
6.5. From the system to the software
6.5.1. Need
6.5.2. What the CENELEC framework does not say
6.6. Data preparation process
6.6.1. Context
6.6.1.1. Software assurance
6.6.1.2. Safety assurance management
6.6.2. Presentation of section 8 of the CENELEC 50128:2011 standard
6.6.2.1. Lifecycle
6.6.2.2. Problem of circularity
6.7. Data preparation process
6.7.1. Management of the data preparation process
6.7.1.1. Planning
6.7.1.2. Integration between the data and the generic software
6.7.1.3. Data production process
6.7.1.4. Inputs to the data preparation process
6.7.1.5. Study of safety of data process
6.7.1.6. Overview
6.7.2. Verification
6.7.3. Specification phase
6.7.3.1. Description of the step
6.7.3.2. Specification of application requirements
6.7.3.3. Complete data preparation tests
6.7.3.4. Verification
6.7.4. Architecture phase
6.7.4.1. Description of the architecture and the design
6.7.4.2. Integration tests
6.7.4.3. Verification report
6.7.5. Data production
6.7.5.1. Design of algorithms
6.7.5.2. Algorithm tests
6.7.5.3. Data verification
6.7.5.4. Activity of verification
6.7.5.5. Overview
6.7.6. Integration of the application and acceptance of the tests
6.7.6.1. Activities
6.7.6.2. Verification of the activity
6.7.6.3. Overview
6.7.7. Validation and evaluation of the application
6.7.8. Procedure and tools for preparation of the application
6.7.8.1. Boundary
6.7.8.2. Overview
6.7.9. Development of generic software
6.8. Conclusion
6.9. Appendix: documentation to be produced
7: Generic Application
7.1. Introduction
7.2. Software application realization process
7.3. Realization of a generic application
7.3.1. Specification phase
7.3.1.1. Description of the activity
7.3.1.2. Specification of software requirements
7.3.1.2.1. Principles
7.3.1.2.2. Use of formal methods
7.3.1.3. Specification of overall software tests
7.3.1.4. Verification report
7.3.2. Architecture and component design phase
7.3.2.1. Presentation of the phase
7.3.2.2. Interfaces
7.3.2.3. Components
7.3.2.4. Re-used components
7.3.2.4.1. Principles
7.3.2.4.2. Re-used components
7.3.2.4.3. COTS
7.3.2.4.4. Verification and validation
7.3.2.5. Architecture
7.3.2.6. Software design
7.3.2.6.1. Software design methods
7.3.2.6.2. Design specification
7.3.2.6.3. Choice of development language
7.3.2.6.4. Programming rules
7.3.2.6.5. Verification of programming rules
7.3.2.7. Specification of the integration tests
7.3.2.8. Verification report
7.3.3. Component design phase
7.3.3.1. Realization of the design
7.3.3.2. COTS and re-used components
7.3.3.3. Component tests
7.3.3.3.1. Methodology
7.3.3.3.2. Objective of coverage
7.3.3.4. Verification report
7.3.4. Coding phase
7.3.5. Execution of component tests
7.3.5.1. Activity
7.3.5.2. Verification report
7.3.6. Software integration phase
7.3.6.1. Activities
7.3.6.2. Verification report
7.3.7. Overall software testing phase
7.4. Some feedback on past experience
7.5. Conclusion
7.6. Appendix A: the programming language "Ada"
7.7. Appendix B: the programming language "C"
7.7.1. Introduction
7.7.2. The difficulty with C
7.7.3. MISRA-C
7.7.4. Example of a rule
7.8. Appendix C: introduction to object-oriented languages
7.9. Appendix D: documentation needing to be produced
8: Modeling and Formalization
8.1. Introduction
8.2. Modeling
8.2.1. Objectives
8.2.2. Different types of modeling
8.2.3. Model
8.3. Use of formal techniques and formal methods
8.3.1. Definitions
8.3.1.1. Semi-formal method
8.3.1.2. Formal method
8.3.1.3. Structured method
8.3.1.4. Computer-aided specification tools
8.3.2. UML
8.4. Brief introduction to formal methods
8.4.1. Recap
8.4.2. Usage in the railway domain
8.4.2.1. From Z to the B-method
8.4.2.2. From LUSTRE to SCADE
8.4.3. Summary
8.4.3.1. Model-checking
8.4.3.2. Establishment of formal methods
8.5. Implementation of formal methods
8.5.1. Conventional processes
8.5.2. Process including formal methods
8.5.3. Issues
8.6. Maintenance of the software application
8.7. Conclusion
9: Tool Qualification
9.1. Introduction
9.2. Concept of qualification
9.2.1. Issue
9.2.2. CENELEC 50128:2001
9.2.3. DO-178
9.2.3.1. Version B
9.2.3.2. Version C
9.2.4. IEC 61508
9.2.5. ISO 26262
9.3. CENELEC 50128:2011
9.3.1. Introduction
9.3.2. Qualification file
9.3.3. Qualification process
9.3.4. Implementation of the qualification process
9.3.4.1. Identification
9.3.4.2. Justification of class
9.3.4.2.1. Choice of Tx
9.3.4.2.2. Failure analysis
9.3.4.2.3. Compiler
9.3.4.3. Specification
9.3.4.4. Proof of conformity
9.3.4.4.1. Approach
9.3.4.4.2. Proof of proper operation
9.3.4.4.3. Certified product
9.3.4.4.4. Documented feedback
9.3.4.4.5. Validation
9.3.4.4.6. Other
9.4. Fitness for purpose
9.4.1. Design method
9.4.2. In case of incompatibility
9.4.3. Code generation
9.5. Version management
9.5.1. Identification of versions
9.5.2. Bug/defect analysis
9.5.3. Changing versions
9.6. Qualification process
9.6.1. Qualification file
9.6.2. Ultimately
9.6.3. Qualification of non-commercial tools
9.7. Conclusion
10: Maintenance and Deployment
10.1. Introduction
10.2. Requirements
10.2.1. Fault management
10.2.2. Managing changes
10.3. Deployment
10.3.1. Issue
10.3.2. Implementation
10.3.3. In reality
10.4. Software maintenance
10.4.1. Issue
10.4.2. Implementation
10.5. Product line
10.6. Conclusion
10.7. Appendix: documentation needing to be produced
11: Assessment and Certification
11.1. Introduction
11.2. Evaluation
11.2.1. Principles
11.2.2. CENELEC 50128:2011
11.3. Cross-acceptance
11.4. Certification
11.4.1. Product certification
11.4.2. Software certification
11.4.3. Evolution management
11.5. Conclusion
11.6. Appendix: documentation needing to be produced
Conclusion
C.1. Introduction
C.2. CENELEC and IEC
C.2.1. Compatibility between 50128:2001 and 50128:2011
C.2.2. Compatibility between CENELEC 50128 and IEC 62279
C.3. Changes to come
Bibliography
Glossary
Index

Systemvoraussetzungen

Als PDF speichern Als Link merken