118,99 €
Mehr erfahren.
- Herausgeber: John Wiley & Sons
- Kategorie: Wissenschaft und neue Technologien
- Serie: Wiley Series in Systems Engineering and Management
- Sprache: Englisch
Focuses on the core systems engineering tasks of writing, managing, and tracking requirements for reliability, maintainability, and supportability that are most likely to satisfy customers and lead to success for suppliers
This book helps systems engineers lead the development of systems and services whose reliability, maintainability, and supportability meet and exceed the expectations of their customers and promote success and profit for their suppliers. This book is organized into three major parts: reliability, maintainability, and supportability engineering. Within each part, there is material on requirements development, quantitative modelling, statistical analysis, and best practices in each of these areas. Heavy emphasis is placed on correct use of language. The author discusses the use of various sustainability engineering methods and techniques in crafting requirements that are focused on the customers’ needs, unambiguous, easily understood by the requirements’ stakeholders, and verifiable. Part of each major division of the book is devoted to statistical analyses needed to determine when requirements are being met by systems operating in customer environments. To further support systems engineers in writing, analyzing, and interpreting sustainability requirements, this book also
- Contains “Language Tips” to help systems engineers learn the different languages spoken by specialists and non-specialists in the sustainability disciplines
- Provides exercises in each chapter, allowing the reader to try out some of the ideas and procedures presented in the chapter
- Delivers end-of-chapter summaries of the current reliability, maintainability, and supportability engineering best practices for systems engineers
Reliability, Maintainability, and Supportability is a reference for systems engineers and graduate students hoping to learn how to effectively determine and develop appropriate requirements so that designers may fulfil the intent of the customer.
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 903
Veröffentlichungsjahr: 2015
Ähnliche
CONTENTS
Cover
Title page
Foreword
PURPOSE AND RATIONALE
GOALS
ORGANIZATION OF THIS BOOK
Acknowledgments
Part I: Reliability Engineering
1 Systems Engineering and the Sustainability Disciplines
1.1 PURPOSE OF THIS BOOK
1.2 GOALS
1.3 SCOPE
1.4 AUDIENCE
1.5 GETTING STARTED
1.6 KEY SUCCESS FACTORS FOR SYSTEMS ENGINEERS IN RELIABILITY, MAINTAINABILITY, AND SUPPORTABILITY ENGINEERING
1.7 ORGANIZING A COURSE USING THIS BOOK
1.8 CHAPTER SUMMARY
REFERENCES
2 Reliability Requirements
2.1 WHAT TO EXPECT FROM THIS CHAPTER
2.2 RELIABILITY FOR SYSTEMS ENGINEERS
2.3 RELIABILITY, MAINTAINABILITY, AND SUPPORTABILITY ARE MUTUALLY REINFORCING
2.4 THE STRUCTURE OF RELIABILITY REQUIREMENTS
2.5 EXAMPLES OF RELIABILITY REQUIREMENTS
2.6 INTERPRETATION OF RELIABILITY REQUIREMENTS
2.7 SOME ADDITIONAL FIGURES OF MERIT
2.8 CURRENT BEST PRACTICES IN DEVELOPING RELIABILITY REQUIREMENTS
2.9 CHAPTER SUMMARY
2.10 EXERCISES
REFERENCES
3 Reliability Modeling for Systems Engineers
3.1 WHAT TO EXPECT FROM THIS CHAPTER
3.2 INTRODUCTION
3.3 RELIABILITY EFFECTIVENESS CRITERIA AND FIGURES OF MERIT FOR NONMAINTAINED UNITS
3.4 ENSEMBLES OF NONMAINTAINED COMPONENTS
3.5 RELIABILITY MODELING BEST PRACTICES FOR SYSTEMS ENGINEERS
3.6 CHAPTER SUMMARY
3.7 EXERCISES
REFERENCES
4 Reliability Modeling for Systems Engineers
4.1 WHAT TO EXPECT FROM THIS CHAPTER
4.2 INTRODUCTION
4.3 RELIABILITY EFFECTIVENESS CRITERIA AND FIGURES OF MERIT FOR MAINTAINED SYSTEMS
4.4 MAINTAINED SYSTEM RELIABILITY MODELS
4.5 STABILITY OF RELIABILITY MODELS
4.6 SOFTWARE RESOURCES
4.7 RELIABILITY MODELING BEST PRACTICES FOR SYSTEMS ENGINEERS
4.8 CHAPTER SUMMARY
4.9 EXERCISES
REFERENCES
5 Comparing Predicted and Realized Reliability with Requirements
5.1 WHAT TO EXPECT FROM THIS CHAPTER
5.2 INTRODUCTION
5.3 EFFECTIVENESS CRITERIA, FIGURES OF MERIT, METRICS, AND PREDICTIONS
5.4 STATISTICAL COMPARISON OVERVIEW
5.5 STATISTICAL COMPARISON TECHNIQUES
5.6 FAILURE REPORTING AND CORRECTIVE ACTION SYSTEM
5.7 RELIABILITY TESTING
5.8 BEST PRACTICES IN RELIABILITY REQUIREMENTS COMPARISONS
5.9 CHAPTER SUMMARY
5.10 EXERCISES
REFERENCES
6 Design for Reliability
6.1 WHAT TO EXPECT FROM THIS CHAPTER
6.2 INTRODUCTION
6.3 TECHNIQUES FOR RELIABILITY ASSESSMENT
6.4 THE DESIGN FOR RELIABILITY PROCESS
6.5 HARDWARE DESIGN FOR RELIABILITY
6.6 QUALITATIVE DESIGN FOR RELIABILITY TECHNIQUES
6.7 DESIGN FOR RELIABILITY FOR SOFTWARE PRODUCTS
6.8 ROBUST DESIGN
6.9 DESIGN FOR RELIABILITY BEST PRACTICES FOR SYSTEMS ENGINEERS
6.10 SOFTWARE RESOURCES
6.11 CHAPTER SUMMARY
6.12 EXERCISES
REFERENCES
7 Reliability Engineering for High-Consequence Systems
7.1 WHAT TO EXPECT FROM THIS CHAPTER
7.2 DEFINITION AND EXAMPLES OF HIGH-CONSEQUENCE SYSTEMS
7.3 RELIABILITY REQUIREMENTS FOR HIGH-CONSEQUENCE SYSTEMS
7.4 STRATEGIES FOR MEETING RELIABILITY REQUIREMENTS IN HIGH-CONSEQUENCE SYSTEMS
7.5 CURRENT BEST PRACTICES IN RELIABILITY ENGINEERING FOR HIGH-CONSEQUENCE SYSTEMS
7.6 CHAPTER SUMMARY
7.7 EXERCISES
REFERENCES
8 Reliability Engineering for Services
8.1 WHAT TO EXPECT FROM THIS CHAPTER
8.2 INTRODUCTION
8.3 SERVICE FUNCTIONAL DECOMPOSITION
8.4 SERVICE FAILURE MODES AND FAILURE MECHANISMS
8.5 SERVICE RELIABILITY REQUIREMENTS
8.6 SERVICE-LEVEL AGREEMENTS
8.7 SDI RELIABILITY REQUIREMENTS
8.8 DESIGN FOR RELIABILITY TECHNIQUES FOR SERVICES
8.9 CURRENT BEST PRACTICES IN SERVICE RELIABILITY ENGINEERING
8.10 CHAPTER SUMMARY
8.11 EXERCISES
REFERENCES
9 Reliability Engineering for the Software Component of Systems and Services
9.1 WHAT TO EXPECT FROM THIS CHAPTER
9.2 INTRODUCTION
9.3 RELIABILITY REQUIREMENTS FOR THE SOFTWARE COMPONENT OF SYSTEMS AND SERVICES
9.4 RELIABILITY MODELING FOR SOFTWARE
9.5 SOFTWARE FAILURE MODES AND FAILURE MECHANISMS
9.6 DESIGN FOR RELIABILITY IN SOFTWARE
9.7 CURRENT BEST PRACTICES IN RELIABILITY ENGINEERING FOR SOFTWARE
9.8 CHAPTER SUMMARY
9.9 EXERCISES
REFERENCES
Part II: Maintainability Engineering
10 Maintainability Requirements
10.1 WHAT TO EXPECT FROM THIS CHAPTER
10.2 MAINTAINABILITY FOR SYSTEMS ENGINEERS
10.3 MAINTAINABILITY EFFECTIVENESS CRITERIA AND FIGURES OF MERIT
10.4 EXAMPLES OF MAINTAINABILITY REQUIREMENTS
10.5 MAINTAINABILITY MODELING
10.6 INTERPRETING AND VERIFYING MAINTAINABILITY REQUIREMENTS
10.7 MAINTAINABILITY ENGINEERING FOR HIGH-CONSEQUENCE SYSTEMS
10.8 CURRENT BEST PRACTICES IN MAINTAINABILITY REQUIREMENTS DEVELOPMENT
10.9 CHAPTER SUMMARY
10.10 EXERCISES
REFERENCES
11 Design for Maintainability
11.1 WHAT TO EXPECT FROM THIS CHAPTER
11.2 SYSTEM OR SERVICE MAINTENANCE CONCEPT
11.3 MAINTAINABILITY ASSESSMENT
11.4 DESIGN FOR MAINTAINABILITY TECHNIQUES
11.5 CURRENT BEST PRACTICES IN DESIGN FOR MAINTAINABILITY
11.6 CHAPTER SUMMARY
11.7 EXERCISES
REFERENCES
Part III: Supportability Engineering
12 Support Requirements
12.1 WHAT TO EXPECT FROM THIS CHAPTER
12.2 SUPPORTABILITY FOR SYSTEMS ENGINEERS
12.3 SYSTEM OR SERVICE SUPPORT CONCEPT
12.4 SUPPORT EFFECTIVENESS CRITERIA AND FIGURES OF MERIT
12.5 EXAMPLES OF SUPPORT REQUIREMENTS
12.6 INTERPRETING AND VERIFYING SUPPORT REQUIREMENTS
12.7 SUPPORTABILITY ENGINEERING FOR HIGH-CONSEQUENCE SYSTEMS
12.8 CURRENT BEST PRACTICES IN SUPPORT REQUIREMENTS DEVELOPMENT
12.9 CHAPTER SUMMARY
12.10 EXERCISES
REFERENCES
13 Design for Supportability
13.1 WHAT TO EXPECT FROM THIS CHAPTER
13.2 SUPPORTABILITY ASSESSMENT
13.3 IMPLEMENTATION OF FACTORS PROMOTING SUPPORTABILITY
13.4 QUANTITATIVE DESIGN FOR SUPPORTABILITY TECHNIQUES
13.5 CURRENT BEST PRACTICES IN DESIGN FOR SUPPORTABILITY
13.6 CHAPTER SUMMARY
13.7 EXERCISES
REFERENCES
Index
Wiley Series in Systems Engineering and Management
End User License Agreement
List of Tables
Chapter 02
Table 2.1 Example Failure-Free Intervals
Table 2.2 Example Refrigerator Outage Times
Table 2.3 Confidence Coefficients Based on the Normal Distribution
Table 2.4 Component Survival Probabilities
Chapter 03
Table 3.1 Weibull Distribution Hazard Rate
Table 3.2 Gamma Distribution Hazard Rate
Table 3.3 Strong Accelerated Life Model
Table 3.4 Confidence Coefficients for UCL Computations
Chapter 04
Table 4.1 Server Rack Example
Chapter 05
Table 5.1 Example Subassembly Component Reliability Parameters
Table 5.2 Data Analysis Decision Tree
Table 5.3 Sample Times between Unscheduled Outages Data
Table 5.4 Normal Confidence Coefficients
Table 5.5 Marine Diesel Engine Failure Counts
Table 5.6 Marine Diesel Engine Failures
Chapter 06
Table 6.1 Components and Stresses
Table 6.2 Concept FMEA Table
Table 6.3 Design FMEA Example
Table 6.4 Example of a FME(C)A Probability Scale
Table 6.5 Example of a Severity Scale
Table 6.6 Sample Scale for Probability of Affecting Users
Chapter 07
Table 7.1 Qualification Decision Errors
Table 7.2 Certification Decision Errors
Chapter 10
Table 10.1 P{Requirement Not Met}
Table 10.2 Downtimes Included in Availability
Chapter 11
Table 11.1 Unit A LoRA Spreadsheet
Table 11.2 Unit B LoRA Spreadsheet
Chapter 12
Table 12.1 Supportability Tracking Variables
List of Illustrations
Chapter 02
Figure 2.1 History diagram illustrating failure and outage.
Figure 2.2 Logistics network example.
Chapter 03
Figure 3.1 Generic life distribution.
Figure 3.2 A generic density function.
Figure 3.3 Stress–strength relationship in a population.
Figure 3.4 Force of mortality for human populations.
Figure 3.5 Specification limits and process output.
Figure 3.6 UAC-UAS call flow.
Figure 3.7 An ensemble of five single-point-of-failure components.
Figure 3.8 A parallel redundant system of four units.
Figure 3.9 Two-unit hot standby ensemble with switch.
Figure 3.10 Bridge network.
Figure 3.11 Example of a system reliability block diagram.
Chapter 04
Figure 4.1 System history diagram.
Figure 4.2 Server rack example reliability block diagram.
Figure 4.3 Server rack example—number of failures.
Figure 4.4 Server rack example—availability.
Figure 4.5 Server rack example—downtime.
Figure 4.6 Generic superposition of point processes.
Figure 4.7 State diagram for three-unit hot-standby redundant system.
Chapter 05
Figure 5.1 Example of a FRACAS flow diagram.
Chapter 06
Figure 6.1 Design for reliability process tree.
Figure 6.2 Example of a printed wiring board (a) top view (b) bottom view. Photo courtesy of A. G. Blum.
Figure 6.3 Design for reliability procedure for PWBs.
Figure 6.4 Beginning a fault tree for passenger elevator example.
Figure 6.5 Sub fault tree for “system does not hold car” event.
Figure 6.6 Sub fault tree for “no power to motor” event.
Figure 6.7 Fault tree illustration with a repeated event.
Figure 6.8 Home alarm system functional decomposition.
Figure 6.9 Normal density of resistor values in new population.
Chapter 07
Figure 7.1 Regenerator section system functional decomposition.
Chapter 08
Figure 8.1 Cloud backup service functional decomposition.
Chapter 10
Figure 10.1 Extract from a system history diagram.
Chapter 13
Figure 13.1 A maintenance facility flow network.
Figure 13.2 Example routing matrix.
Guide
Cover
Table of Contents
Begin Reading
Pages
ii
iii
iv
v
xviii
xix
xx
xxi
xxii
xxiii
1
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
98
99
100
101
102
103
104
105
106
107
108
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
129
130
131
132
133
134
135
137
139
140
141
142
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
377
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
WILEY SERIES IN SYSTEMS ENGINEERING AND MANAGEMENT
Andrew P. Sage, Editor
A complete list of the titles in this series appears at the end of this volume.
Reliability, Maintainability, and Supportability
Best Practices for Systems Engineers
Michael Tortorella
Copyright © 2015 by John Wiley & Sons, Inc. All rights reserved
Published by John Wiley & Sons, Inc., Hoboken, New JerseyPublished simultaneously in Canada
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning, or otherwise, except as permitted under Section 107 or 108 of the 1976 United States Copyright Act, without either the prior written permission of the Publisher, or authorization through payment of the appropriate per-copy fee to the Copyright Clearance Center, Inc., 222 Rosewood Drive, Danvers, MA 01923, (978) 750-8400, fax (978) 750-4470, or on the web at www.copyright.com. Requests to the Publisher for permission should be addressed to the Permissions Department, John Wiley & Sons, Inc., 111 River Street, Hoboken, NJ 07030, (201) 748-6011, fax (201) 748-6008, or online at http://www.wiley.com/go/permissions.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. No warranty may be created or extended by sales representatives or written sales materials. The advice and strategies contained herein may not be suitable for your situation. You should consult with a professional where appropriate. Neither the publisher nor author shall be liable for any loss of profit or any other commercial damages, including but not limited to special, incidental, consequential, or other damages.
For general information on our other products and services or for technical support, please contact our Customer Care Department within the United States at (800) 762-2974, outside the United States at (317) 572-3993 or fax (317) 572-4002.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic formats. For more information about Wiley products, visit our web site at www.wiley.com.
Library of Congress Cataloging-in-Publication Data:
Tortorella, Michael, 1947– Reliability, maintainability, and supportability : best practices for systems engineers / Michael Tortorella. pages cm. – (Wiley series in systems engineering and management) Includes bibliographical references and index.
ISBN 978-1-118-85888-2 (hardback)1. Reliability (Engineering) I. Title. TA169.T676 2015 620′.00452–dc23
2014049531
For Matthew
1982–1999
Lux æterna
Foreword
PURPOSE AND RATIONALE
Students and professionals have many choices of text and reference books for the sustainability engineering disciplines: reliability, maintainability, and supportability. Available books range from theoretical treatises on the mathematical theory of reliability, applied maintainability and logistics modeling, studies in reliability physics, and books devoted to systems management. But there’s still something missing: there is a need for an exposition of the sustainability engineering activities that systems engineers need to carry out, which explains the purposes and benefits of the activities without necessarily explaining how to do them all in detail. This book fills that need.
Several decades of experience in sustainability engineering and management in the telecommunications industry and additional experience in research and teaching have led me to these relevant observations.
Few publications in the sustainability disciplines focus on the core systems engineering tasks of creating, managing, and tracking requirements for these disciplines specifically.
The small number of degree-granting programs in sustainability engineering means that many systems engineers have no exposure to these ideas until they are assigned to deal with them in the work environment.
The gap between what is known and available in the research literature and what is routinely practiced in day-to-day sustainability engineering is large and growing. Many sustainability engineers use oversimplified models and tools to deal with sustainability engineering tasks and consequently miss opportunities to develop more thorough and informative product management and improvement plans at lower cost.
Systems engineers, in particular, because of the broad scope of their responsibilities, need support from those with specialized expertise to write good sustainability requirements, understand the results provided to them by sustainability engineering specialists, and track compliance with stated sustainability requirements. Consequently, they need enough background knowledge in these areas to be good suppliers and customers for the specialist teams.
Many software tools essential for executing complex sustainability engineering tasks often (silently) incorporate simplifying assumptions, rely on the user to discern when results are reasonable or not, and do not give the user good insight into what to expect from the tool and what not to expect from the tool.
Sustainability engineering and management is not an obscure, arcane branch of knowledge. It is a human endeavor that can readily be carried out systematically and on the basis of a manageable number of principles. The purpose of this book is to provide that basis for systems engineers in particular. Certainly, few have as much influence on a product’s design as do systems engineers. The creation of appropriate sustainability requirements is a key step to developing a system whose realized reliability, maintainability, and supportability meet the needs and desires of the system’s customers while promoting success and profit to the vendor. Conversely, incomplete, unfocused, or inappropriate requirements lead to customer dissatisfaction with the system they purchase and use and cost the vendor more in warranty costs, maintenance of an extensive repair business, and lost goodwill. Our purpose here is to provide systems engineers with the principles and tools needed to craft sustainability requirements that make the product or system successful in satisfying the customers’ needs and desires for reliability, maintainability, and supportability while keeping costs manageable. Our purpose is also to provide methods and tools systems engineers can use to determine whether sustainability requirements are being met satisfactorily by understanding and analysis of data from field installations. Finally, the book discusses enough quantitative modeling for reliability, maintainability, and supportability to support systems engineers in their engineering, management, validation, and communication tasks.
It is important to note that this book is not intended as a textbook in the mathematical theory of reliability (or the mathematical underpinnings of maintainability or supportability). Rather, our intention is to provide systems engineers with knowledge about the results of these theories so that, while they may sometimes construct needed reliability, maintainability, and supportability models on their own, it is more important that they be able to successfully acquire and use information provided to them by specialist engineers in these disciplines. The customer–supplier model provides a useful context for this interaction:
Systems engineers act as suppliers in providing specialist engineers with clear and effective reliability, maintainability, and supportability requirements for the product.
Systems engineers act as customers for the reliability, maintainability, and supportability models, data analysis, and so on, provided by specialist engineering teams during development.
Therefore, systems engineers need a good grasp of the language and concepts used in these areas, while not necessarily needing to be able to carry out extensive modeling or data analysis themselves. While this book is careful to describe the necessary language and concepts correctly and in appropriate contexts, it makes no attempt to provide mathematical proofs for the results cited. References are provided for those interested in pursuing details of the mathematical theory of reliability, but those details are not within the scope or purpose of this book.
GOALS
I hope this book will enable systems engineers to lead the development of systems (which we will interpret broadly in this book as encompassing products and services) whose reliability, maintainability, and supportability meet and exceed the expectations of their customers and provide success and profit to their employers. My intention is that systems engineers will themselves be able to employ, and encourage their sustainability engineering specialists to employ, the best practices discussed here in an orderly, systematic fashion guided by customer needs. I recognize that systems engineers have a very broad range of responsibilities, and it may not be possible for them to deal with every responsibility at equal depth. Therefore, it is important that their sustainability engineering and management responsibilities be supported by as straightforward and systematic a program as possible. I emphasize the thought processes underlying all the activities a systems engineer may have to undertake to ensure successful product or system sustainability. To avoid losing sight of the forest for the trees, we repeatedly return to the basic questions and first principles of the field in all the applications we cover, including hardware products, software-intensive systems, services, and high-consequence systems. My intention in doing this is to help systems engineers choose appropriate methods and tools to accomplish their purposes, and thereby create the most suitable sustainability requirements consistent with fulfilling customer needs and expectations and supplier success.
ORGANIZATION OF THIS BOOK
Every author likes to think that he brings to the reader a uniquely formative experience through the superior organization of topics and methods in his book. If only it were that simple. Success in learning depends primarily on student commitment. I can only try to make that job easier. I hope that the devices I use in this book will fulfill that wish.
The book is organized into three major divisions, one corresponding to each of reliability, maintainability, and supportability engineering. Within each division, there is material on
Requirements development,
Quantitative modeling sufficient for understanding, developing, and interpreting requirements,
Statistical analysis for checking whether systems in operation meet or do not meet requirements, and
Best practices in each of these areas.
I place a lot of emphasis on correct use of language. As discussed at length in
Chapter 1
, the language we use in the formal system that constitutes sustainability engineering contains many of the same words we use in ordinary discourse. It is vital to keep in mind which context you are operating in at all times. To help you do this in places where I think there is more than the usual possibility for confusion, I will point out in the text information you need to dispel that confusion. These instances are introduced by the header “Language tip” and they appear in many places in the text.
This book is primarily for systems engineers whose main concern is the determination and development of appropriate requirements so that designers may fulfill the intent of the customer. Accordingly, the book emphasizes the use of various sustainability engineering methods and techniques in crafting requirements that are
Focused on the customers’ needs,
Unambiguous,
Easily understood by the requirements’ stakeholders (customers, designers, and management), and
Verifiable through collection and analysis of data from system operation.
The device employed in the book to promote this goal is the frequent interjection of “Requirements tips” that appear when needed and of most benefit.
An equally important concern of systems engineers is determining when requirements are being met by systems operating in customer environments. Accordingly, a chapter or section in each of the major divisions of the book is devoted to the statistical analyses needed to accomplish this task.
The title of the book emphasizes “Best Practices.” Each chapter concludes with a section summarizing the current best practices for systems engineers concerning the material covered in the chapter.
Finally, I believe that everything we do is a process, whether we call it that or not. In particular, we should all be mindful that everything we do can be improved. Requirements development and verification are no exception (indeed, this book is no exception, and I welcome suggestions from readers to help make the next version better).
Acknowledgments
I have had the good fortune to work with many talented and caring people who have shared their knowledge and helped shape my thinking in this area. First and foremost, I want to thank the late Norman A. Marlow who gave me the freedom to pursue interesting and important problems in network and service reliability and guided my early career at Bell Laboratories. Elsayed A. Elsayed and Endre Boros promoted my pleasant and fruitful relationship with Rutgers University. Many other colleagues and friends contributed their time and expertise to help me learn more about reliability engineering. These include Susan Albin, Sigmund J. Amster, Lawrence A. Baxter, Michele Boulanger, Chun Kin Chan, Ramon V. Leon, Michael LuValle, and William Q. Meeker. José Ramirez-Marquez helped me pass the torch. Working with Bill Frakes on the SUPER project was an education and a pleasure. A. Blanton Godfrey, Jeffrey H. Hooper, and William V. Robinson provided invaluable management support, and Jon Bankert and Jack Sipress gave me an opportunity to work with the Bell Labs Undersea Cable Laboratory where I learned a great deal of practical reliability engineering. I am grateful to Stevens Institute of Technology for employing me to teach a course in the Systems Engineering program based on these ideas. I am deeply grateful to Chun Kin Chan, Bill Frakes, and D. A. Hoeflin for carefully reading the manuscript and offering excellent suggestions. I have also benefitted from conversations with David Coit, Elsayed Elsayed, Shirish Kher, Mohcene Mezhoudi, Himanshu Pant, William V. Robinson, and Terry Welsher. Outside my immediate circle of colleagues, I thank Harry Ascher, Alessandro Birolini, Ilya Gertsbakh, and William A. Thompson. Learning from their clear and well-constructed books helped me be a better reliability engineer. Laura Madison helped clean up my sometimes too-convoluted prose; her patience in taking on a bigger job than she anticipated is much appreciated. Finally, my thanks to Andrea for her patience with my frequent and extended disappearances into the authorial vortex. To all these and many more too numerous to mention, thank you for helping shape this book. I have tried to learn from your suggestions, but people tell me I am sometimes a stubborn cuss, so there may remain errors in the book, and if so, they are mine alone.
Part IReliability Engineering
1Systems Engineering and the Sustainability Disciplines
1.1 PURPOSE OF THIS BOOK
1.1.1 Systems Engineers Create and Monitor Requirements
The textbook marketplace offers many high-quality books that provide the student, professional, and researcher with many points of view on the sustainability disciplines of reliability engineering, maintainability engineering, and supportability engineering. The point of view we advance here, though, is different from that of other books. This book focuses intently on the roles and responsibilities of the systems engineer in creating and monitoring the requirements for reliability, maintainability, and supportability that will guide development of products and services that are most likely to satisfy their customers and lead to success for their suppliers. Systems engineers play a pivotal role in this process. Get the requirements wrong and the likelihood of a successful product or service is almost nil. That, coupled with the importance of acting as early as possible in the development process to build in quality and reliability, compels a new emphasis on preparing systems engineers to understand how the sustainability disciplines contribute to product and service success and to enlarge their toolkit to incorporate generation and validation of sustainability requirements that promote greater product and service success. The first major purpose of this book is to provide systems engineers with the knowledge they need to craft clear, concise, and effective sustainability requirements so that they may fulfill their role of key leader in successful product and service development.
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
Lesen Sie weiter in der vollständigen Ausgabe!
