Requirements Development

Requirements Management is the process of documenting, analyzing, tracing, prioritizing, and controlling changes to requirements. It’s a continuous process and is conducted throughout a system’s life cycle and confirmed at each technical review. Purpose of Requirements Management The purpose is to assure that the requirements continue to meet the needs and expectations of its customers

Derived Requirement are requirements that are not explicitly stated in the set of Stakeholder requirements, and yet is required to satisfy one or more of them. They also arise from constraints, consideration of issues implied but not explicitly stated in the requirements baseline, factors introduced by the selected architecture, Information Assurance (IA) requirements, and the

Note: Technical Requirements Document (TRD) is no longer in use and was replaced by the System Requirements Document (SRD) A Technical Requirements Document (TRD) was a requirements document that was put together by the government that addressed technical level requirements for a system. It accompanied a Request for Proposal (RFP) and provided a better technical

A Weapons Systems Specification (WSS) is a list of detailed requirements that are developed by the contractor during the development of a weapons system. It provides more detailed information about the weapon system than the government-provided Initial Capabilities Document (ICD) and Capabilities Development Document (CDD). The WSS is what’s actually used during the development, design,

The System Requirement Document (SRD) defines system-level functional and performance requirements for a system. The SRD is derived from the Capability Development Document (CDD), Concept of Operations (CONOPS), system-level performance metrics, mission threads/use cases, and usage environment and is developed by the program office.  It should include a system-level description of all software elements required

Standardization is the process of developing and implementing technical standards.  The process establishes a common agreement for engineering criteria, terms, principles, practices, materials, items, processes, and equipment parts, and components. An organization can benefit from standardization because it: [2,4] Enables mass production Enables customization Improves supplier coordination Improves quality Enables simplification Enables delayed differentiation Lowers

Requirements Tracing is one of the processes in Requirements Management; documenting, analyzing, tracing, prioritizing, and controlling. Tracing is conducted throughout a system’s life cycle and confirmed at each technical review for all new and old requirements. The purpose is to assure that the requirements continue to meet the needs and expectations of its customers and Stakeholders.

Figure: JCIDS Requirements Sequencing 1. The Initial Capabilities Document (ICD) is the most common starting point for new capability requirements. [1] Once validated, the ICD typically leads to an Analysis of Alternatives (AoA) and then the Capability Development Document (CDD) and Capability Production Document (CPD) for the development of a materiel capability solution. An ICD

One of the key assurance activities for any project is expert evaluation and assessment of the requirements. The requirements need to be evaluated by multiple people with varying expertise, in order to identify incorrect, ambiguous, and incomplete requirements. A System Requirements Review (SRR) is one way to accomplish this evaluation. A fundamental question for requirements

The process of developing product requirements is known as requirements development. Creating a thorough checklist to ensure the quality of the criteria you’ve written is an important aspect of the process. Below is a basic checklist that can be used to determine whether a requirement is acceptable, needs to be modified, or eliminated. Checklist: Requirements

A requirement is a statement that identifies a product or process operational, functional, or design characteristic or constraint. Users, System Engineers, and Program Managers will have to develop several different types of requirements for an acquisition program through its life cycle. These requirements range from very high-level concept-focused to very specific for a part. The four

Requirements Allocation is the act of decomposing higher-level requirements and assigning them to lower-level functions. All requirements of the top-level functions must be met by the aggregate of those for all lower-level functions. Step 3, Functional Analysis and Allocation, of the Systems Engineering Process is where requirements allocation occurs. Requirements allocation is often difficult to

  Modeling & Simulation (M&S) requirements specify the set of capabilities that a simulation needs in order to adequately serve all of its intended uses. Users rely on information from the three domains (Problem, User and Simulation) to develop a concise and consistent set of requirements for the simulation at hand. Users use this set

  The Mission Requirements Board (MRB) manages the national requirements process that reviews, validates, and approves national requirements for future intelligence capabilities and systems. It is the senior validation and approval authority for future intelligence systems funded within the National Foreign Intelligence Program (NFIP), and provides advice and counsel on future requirements funded outside that

Measures of Effectiveness (MOE) are designed to correspond to accomplishing mission/system objectives and achieving desired results. They quantify the results obtained by a system and may be expressed as probabilities that the system will perform as required. MOEs measure changes in a system’s capability, operational environment, or behavior related to achieving a goal, achieving an

Key Performance Parameters (KPP) are key system capabilities that must be met for a system to meet its operational goals set by the user/customer. These key capabilities form the foundation of any system and are deemed vital to its performance, function, design, and operations. Any changes to the KPP would significantly impact the system’s performance

A Key System Attribute (KSA) is a system capability considered crucial in support of achieving a balanced solution/approach to a Key Performance Parameter (KPP) or some other key performance attribute deemed necessary by the sponsor. KSAs are listed in the Capability Development Document (CDD) and Capability Production Document (CPD) with threshold and objective values.  They

The Joint Service Specification Guides (JSSG) establish a common framework to be used by Government-Industry Program Teams in the Aviation Sector for developing program unique requirements documents for Air Systems, Air Vehicles, and major Subsystems. Each JSSG contains a compilation of candidate references, generically stated requirements, verification criteria, and associated rationale, guidance, and lessons learned

The Initial Capabilities Document (ICD) documents the need for a materiel approach or an approach that is a combination of materiel and non-materiel, to a specific capability gap.  A capability gap is derived from an initial analysis of materiel approaches executed by the operational user and, as required, an independent analysis of materiel alternatives. It

The following table presents some good practices for managing requirements, an assessment of the costs to introduce and apply each practice, and the key benefits resulting from those practices. [1] AcqLinks and References: Sawyer, P., Sommerville, I. and S. Viller, “Capturing the Benefits of Requirements Engineering,” IEEE Software, March/April 1999, pp. 78-85  Updated: 7/27/2017

A Functional Needs Analysis (FNA) assesses current and future capabilities to meet the military objectives of the scenarios chosen in the Functional Area Analysis (FAA) and is an output of the Capabilities Based Assessment (CBA). Using military scenarios, the FNA assesses whether or not an inability to achieve a desired effect exists to determine if

Functional Analysis and Allocation is a top-down process of translating system level requirements into detailed functional and performance design criteria. The result of the process is a defined Functional Architecture with allocated system requirements that are traceable to each system function. SMC Systems Engineering Handbook – Figure15: Functional Analyss and Allocation The Functional Analysis and

The Functional Area Analysis (FAA) identifies the operational tasks, conditions, and standards needed to achieve military objectives. The FAA uses the national strategies (National Military Strategy, National Defense Strategy, National Security Strategy), the Family of Joint Future Concepts, and other assigned missions to arrive at a prioritized list of capabilities and tasks that must be

A feasibility assessment is a study to determine if the requirements of a project or a program can be met within the cost, schedule, and performance constraints of the project or program. Feasibility Assessment Goals The goal of the assessment is to determine if the requirements can be met with the anticipated technology. A secondary