Schweitzer Fachinformationen
Wenn es um professionelles Wissen geht, ist Schweitzer Fachinformationen wegweisend. Kunden aus Recht und Beratung sowie Unternehmen, öffentliche Verwaltungen und Bibliotheken erhalten komplette Lösungen zum Beschaffen, Verwalten und Nutzen von digitalen und gedruckten Medien.
Complete and comprehensive manual for eliciting, defining, and managing needs and requirements, integration, verification, and validation across the lifecycle
The INCOSE Needs and Requirements Manual presents product development and systems engineering practices, activities, and artifacts from the perspective of needs, requirements, verification, and validation across the system lifecycle. Composed of 16 chapters, this book provides practical guidance to help organizations understand the importance of lifecycle concepts, needs, requirements, verification, and validation activities, enabling them to successfully and effectively implement these activities during product development, systems engineering, and project management.
The parent handbook published by Wiley, INCOSE Systems Engineering Handbook, divides the system lifecycle into a series of processes, with each process described in terms of a series of activities. This Manual provides more detail needed by practitioners to successfully implement these activities, with guidance and lessons learned from hundreds of years of collective experience of the authors, contributors, and reviewers. For example, while the Handbook mentions the need to define the problem statement, mission, goals, and objectives for a system, the Manual provides detailed guidance on doing so.
Sample topics covered in the INCOSE Needs and Requirements Manual include:
The INCOSE Needs and Requirements Manual is an essential accompanying reference to the INCOSE Systems Engineering Handbook for novice and seasoned system engineers, software engineers, project managers, product developers, tool vendors, course developers, educators, trainers, customers, suppliers, non-SE stakeholders , as well as researchers and students studying systems engineering and systems design.
Louis S. Wheatcraft is a Senior Consultant and Managing Member of Wheatland Consulting, LLC and is a long time member of INCOSE and is the current Chair of the INCOSE Requirements Working Group.
Michael J. Ryan is the Director of Capability Associates Pty Ltd. Dr. Ryan recently retired as a Professor at the University of New South Wales and is an INCOSE Fellow.
Tami Edner Katz is a Staff Consultant at BAE Systems, Inc. working as a chief engineer on various space mission projects. Dr. Katz also teaches courses on MBSE and Requirements at the University of Colorado at Boulder.
List of Tables
Preface
Glossary
Section 1: INTRODUCTION
Section 2: DEFINITIONS AND CONCEPTS
Section 3: INFORMATION-BASED NEEDS AND REQUIREMENT DEVELOPMENT AND MANAGEMENT
Section 4: LIFECYCLE CONCEPTS AND NEEDS DEFINITION
Section 5: NEED VERIFICATION AND NEED VALIDATION
Section 6: DESIGN INPUT REQUIREMENTS DEFINITION
Section 7: REQUIREMENT VERIFICATION AND VALIDATION
Section 8: DESIGN VERIFICATION AND DESIGN VALIDATION
Section 9: PRODUCTION VERIFICATION
Section 10: SYSTEM VERIFICATION AND VALIDATION COMMON PRINCIPLES
Section 11: SYSTEM VERIFICATION AND VALIDATION PROCESSES
Section 12: THE USE OF OTS SYSTEM ELEMENTS
Section 13: SUPPLIER DEVELOPED SOI
Section 14: NEEDS, REQUIREMENTS, VERIFICATION, AND VALIDATION MANAGEMENT
Section 15: ATTRIBUTES FOR NEEDS AND REQUIREMENTS
Section 16: DESIRABLE FEATURES OF AN SE TOOLSET
APPENDIX A: REFERENCES
APPENDIX B: ACRONYMS AND ABBREVIATIONS
APPENDIX C: GLOSSARY
APPENDIX D: COMMENT FORM
This Needs and Requirements Manual (NRM) presents systems engineering (SE) from the perspective of the definition and management across the system lifecycle of needs, requirements, verification, and validation (NRVV). NRVV are common threads that tie together all lifecycle activities and processes.
As presented in this Manual, for acceptance, certification, and qualification, the system or product being developed is verified against design input requirements and validated against its integrated set of needs. To successfully complete system verification and system validation, the needs and requirements of the system as well as the system verification and validation artifacts must be managed throughout the entire system lifecycle. This Manual provides practical guidance on the concepts and activities required to achieve those outcomes.
As shown in Figure 1.1, this Manual supplements and elaborates the INCOSE Systems Engineering Handbook (SE HB) [1] and the Systems Engineering Body of Knowledge (SEBoK) [2], providing more detailed guidance on the "what," "how," and "why" concerning NRVV across the system lifecycle. The NRM also addresses ambiguity and inconsistencies in NRVV terminology and ontology.
Figure 1.1 shows this Manual is further elaborated by several supporting guides. The Guide to Needs and Requirements (GtNR) [3] and the Guide to Verification and Validation (GtVV) [4] focus further on the "what" and "how" of the specific processes being implemented within an organization. The level of detail is similar in content to an organization's Work Instructions (WIs) or Standard Operating Procedures (SOPs). These guides reference this Manual for specific guidance on the "why" and underlying concepts, maintaining consistency in approach and ontology defined in this Manual.
FIGURE 1.1 Relationships Between INCOSE Requirements Working Group (RWG) Products and the INCOSE SE HB and SEBoK.
Although this Manual addresses the activities and underlying analysis associated with defining individual and sets of needs and design input requirements, the actual writing of the need and requirement statements is covered in the INCOSE Guide to Writing Requirements (GtWR) [5]. The GtWR includes a list of key characteristics of well-formed needs and requirements and sets of needs and requirements, as well as a set of rules that can help achieve those characteristics. Throughout this Manual, when the activities being discussed contribute to a given characteristic defined in the GtWR, a trace to that characteristic is included.
Figure 1.1 also shows that this Manual and the associated guides advocate a data-centric approach to Project Management (PM) and SE as defined in the INCOSE RWG Whitepaper Integrated Data as a Foundation of Systems Engineering [6], as discussed in Chapter 3 of this Manual.
To support PM and SE from an NRVV perspective, this Manual:
This Manual is intended for those whose role is to perform NRVV activities throughout the system lifecycle. This includes those who verify that the design and realized System of Interest (SOI) meet the requirements and those who validate that the requirements, design, and realized SOI meet the needs in the intended operational environment when used by the intended users and mitigate risk of any misuse of the SOI and losses because of misuse.
This Manual is addressed to practitioners of all levels of experience. Someone new to PM and SE should find the specific guidance useful, and those more experienced should be able to find new insights concerning NRVV across all stages of the system lifecycle, which is often absent from other texts, guides, or standards, particularly in terms of a data-centric perspective.
Major user groups who will benefit from the use of this Manual include systems engineers, requirements engineers, business analysts, product developers, system architects, configuration managers, designers, testers, verifiers, validators, manufacturers, coders, operators, users, disposers, course developers, trainers, tool vendors, project managers, acquisition personnel, lawyers, regulators, and standards organizations. Specific use cases for various classes of readers are shown in Table 1.1.
While this Manual addresses the specific application of the activities and concepts associated with NRVV, the specifics of "how" this information is applied are not prescribed. For example, while the use of models and a data-centric approach is advocated, the specifics concerning how to implement these concepts within the project's toolset are not addressed; while the use of Requirement Management Tools (RMTs) is advocated, the specifics concerning any particular RMT are not discussed. In this regard, this Manual is structured to enable other INCOSE Working Groups (WGs) and tool vendors to develop domain or tool-specific guides that tailor these contents to best fit the needs of the organization.
There are many use cases for how organizations practice SE to develop systems and products. This Manual presents a generic set of concepts and activities that can be applied. It is not intended that organizations adopt all the activities presented, but rather use the best practices presented to tailor their product development activities and processes appropriate to their domain, product line, workforce, and culture in such a way that provides the most value. For additional guidance concerning tailoring, refer to Chapter 4 of the INCOSE SE HB [1].
TABLE 1.1 NRVV Use Cases.
Dateiformat: ePUBKopierschutz: Adobe-DRM (Digital Rights Management)
Systemvoraussetzungen:
Das Dateiformat ePUB ist sehr gut für Romane und Sachbücher geeignet – also für „fließenden” Text ohne komplexes Layout. Bei E-Readern oder Smartphones passt sich der Zeilen- und Seitenumbruch automatisch den kleinen Displays an. Mit Adobe-DRM wird hier ein „harter” Kopierschutz verwendet. Wenn die notwendigen Voraussetzungen nicht vorliegen, können Sie das E-Book leider nicht öffnen. Daher müssen Sie bereits vor dem Download Ihre Lese-Hardware vorbereiten.Bitte beachten Sie: Wir empfehlen Ihnen unbedingt nach Installation der Lese-Software diese mit Ihrer persönlichen Adobe-ID zu autorisieren!
Weitere Informationen finden Sie in unserer E-Book Hilfe.
