INCOSE Needs and Requirements Manual (eBook)

Needs, Requirements, Verification, Validation Across the Lifecycle

Tami Edner Katz, Michael J. Ryan, Louis S. Wheatcraft (Autoren)

eBook Download: EPUB

2024
1036 Seiten
Wiley (Verlag)
978-1-394-15276-6 (ISBN)

Infos

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:

• Defining the problem, opportunity, or threat and defining a mission statement, goals, objectives, and measures.
• Identifying external and internal stakeholders, eliciting stakeholder needs and requirements, defining drivers and constraints, and assessing risk.
• Performing lifecycle concept analysis and maturation and defining an integrated set of needs that represents the scope of the project.
• Transforming the integrated set of needs into well-formed design input requirements.
• Using attributes to manage needs and requirements across the lifecycle.
• Continuous integration, verification, and validation across the lifecycle.
• Moving between levels of the architecture, flow down and allocation of requirements, and budgeting performance, resource, and quality requirements.
• Defining the system verification and system validation success criteria, method, strategy, and responsible organizations.
• Planning and executing successful system verification and validation programs.
• Managing needs, requirements, verification, and validation across the lifecycle.
• Understanding the importance of an integrated, collaborative project team and effective communication between team members

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.

Textauszug

1
INTRODUCTION

1.1 PURPOSE

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.

1.2 SCOPE

To support PM and SE from an NRVV perspective, this Manual:

• Provides PM and SE practitioners with an understanding of the best practices for effective NRVV definition and management throughout the system lifecycle.
• Helps organizations understand that NRVV are key elements of SE activities.
• Provides guidance to the successful implementation of NRVV activities as part of PM and SE, in any domain.
• Reinforces the idea that adequate definition of lifecycle concepts and a well-formed set of needs is a prerequisite to the definition of a well-formed set of system design input requirements.
• Provides practical, cross-domain guidance to enable organizations to integrate best practices and concepts within their PM and SE processes, activities, WIs, and procedures.
• Provides a clear description of how the terms verification and validation are applied to the artifacts generated across the system lifecycle.
• Describes the importance of planning early for verification and validation activities across the lifecycle and the inclusion of verification and validation artifacts in system models.
• Provides thorough guidance to readers on planning, definition, execution, and reporting of verification and validation activities across the system lifecycle.
• Provides guidance and best practices that will help customers avoid accumulating technical debt and enable projects and suppliers to deliver a winning product.
• Presents a data-centric approach to NRVV definition and management.
• Provides guidance for organization- and enterprise-wide sharing of data and information associated with developing and managing an integrated set of needs, the resulting design input requirements, and design output specifications, as well as verification and validation artifacts throughout the system lifecycle.

1.3 AUDIENCE

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.

1.4 APPROACH

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.

Reader	Use Cases

Novice practitioners: those new to SE and NRVV

Learn and understand NRVV terminology, concepts, and best practices Access a structured, unambiguous, and comprehensive source of information and knowledge to help learn NRVV from a data-centric perspective Learn a consistent and unambiguous ontology (meta-model) for NRVV

Seasoned practitioners: those experienced in SE and NRVV but not from a data-centric perspective

Gain more in-depth understanding of NRVV from a data-centric perspective Reinforce, refresh, build upon, and renew their NRVV knowledge Tailor the concepts in the NRM to their organization’s product line, processes, and culture Adopt the NRVV best practices presented in this Manual Use this Manual to help mentor novice practitioners in the realm of NRVV

Course developers/educators/trainers: individuals or organizations that specialize in training practitioners and other stakeholders in NRVV processes and tools

Use a structured, unambiguous, and comprehensive source of information and knowledge to help teach NRVV from a data-centric perspective Suggest relevant NRVV topics to trainers for their course content Present a consistent and unambiguous ontology for NRVV. Lead SE curricula development and revision inside their own...

Produkt-Details

• Erscheint lt. Verlag: 18.10.2024
• Sprache: englisch
• Themenwelt: Mathematik / Informatik ► Informatik ► Datenbanken
• Themenwelt: Technik ► Elektrotechnik / Energietechnik
• Schlagworte: Business Analysis • elicitation • lifecycle concepts • Modeling • needs definition • Product Development • Project Management • requirements definition • requirements management • Software engineering • stakeholder needs • Stakeholders • Systems Engineering
• ISBN-10: 1-394-15276-0 / 1394152760
• ISBN-13: 978-1-394-15276-6 / 9781394152766