Atjaunināt sīkdatņu piekrišanu

Requirements Engineering for Safety-Critical Systems [Hardback]

Edited by (Federal University of Sćo Paulo, Brazil), Edited by (Blekinge Institute of Technology, Sweden)
Citas grāmatas par šo tēmu:
  • Hardback
  • Cena: 122,33 €
  • Grāmatu piegādes laiks ir 3-4 nedēļas, ja grāmata ir uz vietas izdevniecības noliktavā. Ja izdevējam nepieciešams publicēt jaunu tirāžu, grāmatas piegāde var aizkavēties.
  • Daudzums:
  • Ielikt grozā
  • Piegādes laiks - 4-6 nedēļas
  • Pievienot vēlmju sarakstam
Requirements Engineering for Safety-Critical SystemsPalielināt
Citas grāmatas par šo tēmu:
Permanent link: https://www.kriso.lv/db/9788770224277.html
Keywords:
Safety-Critical Systems (SCS) are increasingly present in people's daily activities. In the means of transport, in medical treatments, in industrial processes, in the control of air, land, maritime traffic, and many other situations, we use and depend on SCS. The requirements engineering of any system is crucial for the proper development of the same, and it becomes even more relevant for the development of SCS. Requirements Engineering is a discipline that focuses on the development of techniques, methods, processes, and tools that assist in the design of software and systems, covering the activities of elicitation, analysis, modeling and specification, validation, and management of requirements. The complete specification of system requirements establishes the basis for its architectural design. It offers a description of the functional and quality aspects that should guide the implementation and system evolution. In this book, we discuss essential elements of requirements engineering applied to SCS, such as the relationship between safety/hazard analysis and requirements specification, a balance between conservative and agile methodologies during SCS development, the role of requirements engineering in safety cases, and requirements engineering maturity model for SCS. This book provides relevant insights for professionals, students, and researchers interested in improving the quality of the SCS development process, making system requirements a solid foundation for improving the safety and security of future systems.
Preface xi
Acknowledgments xiii
List of Figures xv
List of Tables xix
List of Abbreviations xxi
1 Introduction 1(4)
2 The Role of the Safety and Hazard Analysis 5(18)
Jessyka Vilela
2.1 Introduction
5(1)
2.2 Foundations of Safety Engineering
6(3)
2.2.1 The Threats: Faults, Errors, and Failures
6(1)
2.2.2 Safety Concepts
7(2)
2.3 A Method for Safety and Hazard Analysis
9(5)
2.3.1 Step 1: Hazards Identification
9(1)
2.3.2 Fault-Tree Analysis (FTA)
10(2)
2.3.3 HAZOP
12(1)
2.3.4 STAMP/STPA
13(1)
2.4 Step 2: Hazards Evaluation
14(2)
2.4.1 Step 3: Risk Analysis
15(1)
2.5 Safety-related Requirements Specification
16(4)
2.5.1 The Means to Obtain Safety
17(1)
2.5.2 Model-driven Approaches
18(1)
2.5.3 Textual-driven Approaches
18(1)
2.5.4 Model-driven Approaches Combined with Natural Language Specification
19(1)
2.5.5 Ontological Approach to Elicit Safety Requirements
19(1)
2.6 Conclusions
20(3)
3 Integrating New and Traditional Approaches of Safety Analysis 23(14)
L.E.G. Martins
3.1 Introduction
23(1)
3.2 Background and Related Work
24(2)
3.2.1 Background
24(1)
3.2.2 Related Work
25(1)
3.3 Traditional Approaches
26(3)
3.3.1 FMEA: Failure Mode and Effect Analysis
26(2)
3.3.2 FTA: Fault Tree Analysis
28(1)
3.4 New Approaches
29(3)
3.4.1 STAMP
29(1)
3.4.2 STPA
30(2)
3.5 Integration Between New and Traditional Approaches
32(2)
3.6 Conclusion
34(3)
4 Agile Requirements Engineering 37(18)
Jessyka Vilela
4.1 Introduction
37(2)
4.2 Agile Methods
39(3)
4.2.1 Scrum
40(1)
4.2.2 XP
41(1)
4.3 Agile Requirements Engineering in SCS
42(5)
4.3.1 Requirements Elicitation
42(1)
4.3.2 Requirements Analysis & Negotiation
43(1)
4.3.3 Requirements Specification
44(1)
4.3.4 Requirements Validation
45(1)
4.3.5 Requirements Management
46(1)
4.4 Traditional x Agile Requirements Engineering
47(2)
4.5 Case Studies
49(1)
4.5.1 Pharmaceutical Company
49(1)
4.5.2 Avionics Company
50(1)
4.6 Conclusions
50(5)
5 A Comparative Study of Requirements-Based Testing Approaches 55(30)
J. Santos
L.E.G. Martins
5.1 Introduction
56(1)
5.2 Background and Related Work
56(3)
5.3 Experiment Design
59(7)
5.4 Results and Discussion
66(14)
5.5 Conclusions
80(1)
5.6 Future Work
81(4)
6 Requirements Engineering in Aircraft Systems, Hardware, Software, and Database Development 85(24)
J.C. Marques
S.H.M. Yelisetty
L.M.S. Barros
6.1 Introduction
85(1)
6.2 Aviation Standards
86(8)
6.2.1 SAE ARP 4754A
87(1)
6.2.2 RTCA DO-297
87(2)
6.2.3 RTCA DO-178C
89(2)
6.2.4 RTCA DO-254
91(1)
6.2.5 RTCA DO-200B
92(2)
6.3 Requirements Engineering in Aviation
94(4)
6.3.1 Certification Requirements
95(1)
6.3.2 Aircraft and System Requirements
96(2)
6.4 Software Requirements
98(4)
6.4.1 Model-Based Software Requirements
99(1)
6.4.2 Software Requirements Using Object-Oriented Technology
100(1)
6.4.3 Software Requirements Using Formal Methods
101(1)
6.5 Hardware Requirements
102(3)
6.5.1 Onboard Database Requirements
103(1)
6.5.2 Parameter Data Items
103(1)
6.5.3 Aeronautical Databases
104(1)
6.6 Conclusion
105(4)
7 Generating Safety Requirements for Medical Equipment 109(16)
A. Martinazzo
L.E.G. Martins
T.S. Cunha
7.1 Introduction
110(1)
7.2 Related Works
111(1)
7.3 Framework for Integration of Risk Management Process
112(10)
7.3.1 Risk Management Process According to ISO 14971
112(1)
7.3.2 Framework Description.
113(13)
7.3.2.1 Equipment Functions
114(1)
7.3.2.2 Hazardous Situations Level 1
114(3)
7.3.2.3 Equipment Architecture
117(1)
7.3.2.4 Risk Evaluation and Control Level 1
117(3)
7.3.2.5 Development of Components
120(1)
7.3.2.6 Hazardous Situations Level 2 Evaluation and Risk Control
120(2)
7.4 Conclusion
122(3)
8 Meta-Requirements for Space Systems 125(20)
C.H.N. Lahoz
8.1 Introduction
125(1)
8.2 Requirements Engineering in Space Systems
126(3)
8.2.1 Requirements in Space Systems
126(1)
8.2.2 Meta-Requirements in Space Systems
127(1)
8.2.3 Requirement Engineering Process in Space Systems
128(1)
8.3 Meta-requirements Selected to Space Systems
129(12)
8.3.1 Accuracy
130(1)
8.3.2 Availability
130(1)
8.3.3 Completeness
131(1)
8.3.4 Consistency
131(1)
8.3.5 Correctness
132(1)
8.3.6 Efficiency
132(1)
8.3.7 Failure Tolerance
133(1)
8.3.8 Maintainability
134(1)
8.3.9 Modularity
135(1)
8.3.10 Portability
135(1)
8.3.11 Reliability
135(1)
8.3.12 Recoverability
136(1)
8.3.13 Robustness
137(1)
8.3.14 Safety
137(1)
8.3.15 Security
138(1)
8.3.16 Self-description
139(1)
8.3.17 Simplicity
139(1)
8.3.18 Stability
139(1)
8.3.19 Survivability
140(1)
8.3.20 Testability
140(1)
8.3.21 Traceability
141(1)
8.4 Conclusion
141(4)
9 The Role of Requirements Engineering in Safety Cases 145(22)
Camilo Almendra
Carla Silva
9.1 Introduction
145(1)
9.2 Safety Cases
146(5)
9.2.1 Definition
146(1)
9.2.2 Example
147(2)
9.2.3 Development
149(2)
9.3 Requirements Artefacts and Safety Cases
151(10)
9.3.1 Safety Requirements
151(6)
9.3.2 Argumentation patterns
157(4)
9.4 Safety Case Development and Requirements Processes
161(2)
9.4.1 Joint development
161(1)
9.4.2 Traceability
162(1)
9.5 Conclusions
163(4)
10 Safety and Security Requirements Working Together 167(16)
C. Santos
10.1 Introduction
167(1)
10.2 Approaching Safety and Security Requirements
168(11)
10.2.1 Understanding the Stuxnet
168(1)
10.2.2 May Stuxnet Similar Case Also Happen in Aircraft?
169(1)
10.2.3 But are the authorities doing something in this new scenario?
169(1)
10.2.4 Understanding the DO-326A/ED-202A Airworthiness Security Process Specification
170(1)
10.2.5 Why Do We Need Specific Guidelines for Security Requirements?
171(1)
10.2.6 A Practical Example of a Possible Back Door for an Attacker
171(2)
10.2.7 Considering Security Aspects During the Aircraft Development Lifecycle
173(2)
10.2.8 Defining Security Treat Conditions
175(1)
10.2.9 Security Measures
176(1)
10.2.10 Developing Security Requirements
177(2)
10.3 Conclusion
179(4)
11 Requirements Engineering Maturity Model for Safety-Critical Systems 183(16)
Jessyka Vilela
11.1 Introduction
184(2)
11.2 A Maturity Model for Safety-Critical Systems
186(5)
11.2.1 Process Area View
187(1)
11.2.2 Maturity Level View
188(3)
11.3 Evaluating the safety processes
191(5)
11.3.1 Assessment Instrument and Tool
191(1)
11.3.2 Results of a Safety Maturity Assessment
192(4)
11.4 Conclusions
196(3)
Index 199(2)
About Editors and Authors 201
Luiz Eduardo G. Martins has a PhD in electrical engineering from State University of Campinas (UNICAMP), in Brazil. Dr. Martins is an associate professor of software engineering and embedded systems at Federal University of Sćo Paulo, where he works as a research leader in collaboration with industrial partners in safety-critical systems domain. Dr. Martins has developed several projects in medical devices and aerospace domains. His research interests include requirements engineering, software quality process, model-driven software development, IoT and technological innovation in medical systems.













Tony Gorschek is a Professor of Software Engineering at Blekinge Institute of Technology - where he works as a research leader and scientist in close collaboration with industrial partners. Dr. Gorschek has over fifteen years of industrial experience as a CTO, senior executive consultant, and engineer. At present, he works as a research leader and in several research projects developing scalable, efficient, and effective solutions when it comes to software-intensive product and service development. Dr. Gorschek leads the SERT profile (Software Engineering ReThought) Swedens largest software engineering research initiative.