| Description |
1 online resource (xii, 235 pages) : illustrations (some color) |
| Contents |
Intro; Preface; Acknowledgements; Contents; Chapter 1: Introduction; 1.1 Introduction; 1.1.1 Signalling Systems, ERTMS and CBTC; 1.1.1.1 Signalling Systems; 1.1.1.2 ERTMS; 1.1.1.3 Communications-Based Train Control; 1.1.2 EN 50129:2003; 1.1.3 Other Safety Systems than Railway Signalling Systems; 1.1.4 Structure of This Book; References and Further Reading; Chapter 2: Agile Development; 2.1 Introduction; 2.1.1 Introduction; 2.1.2 Trust; 2.1.3 The SafeScrum Process; 2.1.4 The Need for Documentation; 2.1.5 Agile Practices; 2.1.5.1 Relevant Agile Practices When Developing Signalling Systems |
|
2.1.5.2 Popular Practices Relevant for SCSW2.1.5.3 Extended Agile Safety Practices; 2.1.6 Reuse of Information and Documents and Templates; 2.1.6.1 Reuse Opportunities; 2.1.6.2 The Use of Templates; 2.1.7 Important Considerations When Applying Other Models than Waterfall/V-Model When Developing Signalling Systems; 2.1.7.1 Life Cycle; 2.1.7.2 Documentation; 2.1.7.3 Regression; 2.1.7.4 Configuration Management; 2.1.7.5 Change Impact Analysis, CIA; References and Further Reading; Chapter 3: Roles, Assessment and Authorisation; 3.1 Railway Roles, Assessment and Authorisation |
|
3.1.1 Railway, Safety and Agile Roles3.1.1.1 Introduction; 3.1.1.2 Railway Organisations and Roles; 3.1.1.3 Safety Roles; 3.1.1.4 Agile Roles; 3.1.2 Assessment and Authorisation; 3.1.2.1 Introduction; 3.1.2.2 Accreditation; 3.1.2.3 Notifications; 3.1.2.4 Independent Safety Assessment; What an ISA Does:; ISA Deliverables; What an ISA Is Not Doing, What Is Not Required by Safety Standards and Related Agile Approach; 3.1.2.5 Authorisation; References and Further Reading; Chapter 4: The Agile Safety Plan for Signalling Systems; 4.1 Introduction; 4.1.1 Safety and Agility |
|
4.1.2 The Safety Life Cycle4.1.3 High-Level Safety Plan, Release Plan and Document Flow; 4.1.4 Reuse Opportunities and Templates; 4.1.5 Tools; 4.1.6 The Agile Safety Plan; 4.1.7 Summary; References and Further Reading; Chapter 5: Safety Case Patterns, Notations and GSN; 5.1 Safety Case Patterns and Notations; 5.1.1 The Contents of a Safety Case; 5.1.2 Normal Prose Safety Case; 5.1.3 Structured Textual Pattern; 5.1.4 Writing a Safety Case; 5.1.5 Safety Case Diagrams; 5.1.5.1 Why Safety Case Diagrams; 5.1.5.2 Safety Case Diagram Patterns |
|
5.1.6 How GSN Supports Incremental Safety Case Development5.1.7 GSN Support for Agile Development; References and Further Reading; Chapter 6: The Safety Case: Introduction and Definition of the System; 6.1 General Introduction; 6.2 Introduction Part of the Safety Case; 6.2.1 Change History of the Safety Case; 6.2.2 Definition of System; References and Further Reading; Chapter 7: Safety Case: Quality Management Report; 7.1 Introduction; 7.2 Organisational Structure; 7.3 Quality Planning and Procedures; 7.4 Specification of Requirements; 7.5 Design Control; 7.6 Design Verification and Reviews |
| Summary |
The safety case (SC) is one of the railway industry's most important deliverables for creating confidence in their systems. This is the first book on how to write an SC, based on the standard EN 50129:2003. Experience has shown that preparing and understanding an SC is difficult and time consuming, and as such the book provides insights that enhance the training for writing an SC. The book discusses both "regular" safety cases and agile safety cases, which avoid too much documentation, improve communication between the stakeholders, allow quicker approval of the system, and which are important in the light of rapidly changing technology. In addition, it discusses the necessity of frequently updating software due to market requirements, changes in requirements and increased cyber-security threats. After a general introduction to SCs and agile thinking in chapter 1, chapter 2 describes the majority of the roles that are relevant when developing railway-signaling systems. Next, chapter 3 provides information related to the assessment of signaling systems, to certifications based on IEC 61508 and to the authorization of signaling systems. Chapter 4 then explains how an agile safety plan satisfying the requirements given in EN 50126-1:1999 can be developed, while chapter 5 provides a brief introduction to safety case patterns and notations. Lastly, chapter 6 combines all this and describes how an (agile) SC can be developed and what it should include. To ensure that infrastructure managers, suppliers, consultants and others can take full advantage of the agile mind-set, the book includes concrete examples and presents relevant agile practices. Although the scope of the book is limited to signaling systems, the basic foundations for (agile) SCs are clearly described so that they can also be applied in other cases |
| Bibliography |
Includes bibliographical references and index |
| Subject |
System safety.
|
|
Computer science.
|
|
Management information systems.
|
|
Software engineering.
|
|
Transportation engineering.
|
|
Traffic engineering.
|
|
Electronic data processing.
|
|
data processing.
|
|
computer science.
|
|
traffic engineering.
|
|
transportation engineering (civil engineering)
|
|
TECHNOLOGY & ENGINEERING -- Engineering (General)
|
|
TECHNOLOGY & ENGINEERING -- Reference.
|
|
Electronic data processing
|
|
Computer science
|
|
Management information systems
|
|
Software engineering
|
|
System safety
|
|
Traffic engineering
|
|
Transportation engineering
|
| Form |
Electronic book
|
| Author |
Stålhane, Tor, author
|
| ISBN |
9783319702650 |
|
3319702653 |
|
