Requirements Development
- Overview:Requirements Develoment
- Requirement Development Steps
- Step 1: Gather & Develop Requirements
- Step 2: Write/Document Requirements
- Step 3: Check Completeness
- Step 4: Analyze, Refine & Decompose Requirements
- Step 5: Verify & Validate Requirements
- Step 6: Manage Requirements
 
- Capability Development Document
- Capability Development Tracking and Management (CDTM) tool
- Capability Production Document (CPD)
- Derived Requirements
- Deriving Electronic Requirements
- Design Synthesis
- EVMS Requirements
Establishing & Managing Requirements 
- Feasibility Assessment
- Functional Analysis and Allocation
- Functional Area Analysis (FAA)
- Functional Needs Analysis (FNA)
- Functional Solutions Analysis (FSA)
- Good Requirements Practices
- Guide to Specification Writing
- Initial Capabilities Document (ICD)
- Joint Capability Area Attributes
- Joint Service Specification Guides
- Key Performance Parameters (KPP)
- Key System Attributes (KSA)
- Measures of Effectiveness (MOE)
- Mission Requirements Board (MRB)
- M&S Requirements Development
- Operational Requirements
- Requirement Types
- Requirements Allocation
- Requirements Analysis
- Requirements Checklist
- Requirements Document Sequence
- Requirements Evaluation
- Requirements Tracing
- Requirements Training & Certification
- Software Requirements
- Standardization
- System Requirements Document (SRD)
- Technical Requirements Document
- Weapon System Speciifcation (WSS)
 
 
 
 
 
 
 
Requirements Development
Functional Analysis and Allocation


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 architecture with allocated system requirements that are traceable to each system function.

                        Functional Analysis and Allocation
                                            SMC Systems Engineering Handbook Figure15

The Functional Analysis and Allocation bridges the gap between the high level set of system requirements and constraints (from the Requirements Analysis) and the detailed set required (in Synthesis) to develop or purchase systems and implement programs. It is an integral part of both the Requirements Loop and the Design Loop. During this activity, an integrated Functional Architecture is defined in sufficient depth to support the synthesis of solutions in terms of people, products, and processes, and to allow identification and management of attendant risk. It is an iterative process, interacting and reacting to the ongoing activities in the both the Requirements and Design Loops. [1]

The initial step is to identify the lower-level functions required to perform the various system functions. As this is accomplished, the system requirements are allocated and functional architecture(s) are developed. These activities track and interact so that as details evolve, they are continually validated against each other. Should anomalies occur, alternate architectures and allocations may be carried through early stages of this activity until the optimum approach becomes apparent. The internal and external functional interfaces are defined as the architecture matures. The functional architecture(s) and their companion functional requirements are the input to the Synthesis activity. Completing the Design Loop, the detailed results of the Synthesis are compared to the candidate architecture(s) and allocated requirements to help zero in on the optimum approach and to assure that all proposed solutions meet established requirements. [1]  

Decomposition: to lower-level functions is the incoming interface for the Requirements Loop. The functions identified in the Requirements Analysis are analyzed to define successively lower-levels of functions that accomplish the higher-level functional requirements. Alternate lower-level functional solutions covering all anticipated operating modes are proposed and evaluated to determine which provides the best fit to the parent requirements and best balance between conflicting ones. The initial decomposition is the starting point for the development of the functional architecture and the allocation of requirements to the lower functional levels. Adjustments to the decomposition strategy may be necessary as details are developed. [1]  

Allocation: All requirements of the top-level functions must be allocated for all lower level functions. Traceability is an on-going record of the pedigree of requirements imposed on system and subsystem elements. Because requirements are derived or apportioned among several functions, they must be traceable across functional boundaries to parent and child requirement. Traceability allows the System Engineer to ascertain rapidly what effects any proposed changes in requirements may have on related requirements at any system level. The allocated requirements must be defined in measurable terms, contain applicable go/no go criteria, and be in sufficient detail to be used as design criteria in the subsequent Synthesis activity. [1]  

- Step 1: Requirements Analysis
- Step 2: System Analysis and Control
- Step 3: Functional Analysis Allocation
- Step 4: Design Synthesis

AcqTips:  


AcqLinks and References:
- [1] SMC Systems Engineering Handbook - Chapter 2, page 45
- Chapter 5 - Functional Analysis and Allocation
- Chapter 6 - Design Synthesis



Click Here!

Sponsors

Click Here!