“…shall support…” Requirements
This type of requirement is used to flow an upper-tier (parent) requirement topic to a lower-tier (child) specification when the System Engineer either does not understand how the requirement can (or should) be portioned between the subordinate (child) CI’s, or is afraid to commit under contract. Requirements written in this form are essentially useless: either... read more
Acceptance Requirement
A design-specific type of technical requirement used to verify that an as-built built item is, in fact, a specimen of that design to within the tolerances established as part of that design. Often referred to as an “Acceptance Criterion”. Contrast with Qualification Requirement, which establishes
Allocable Requirement
A requirement where the measure(s) can (and should) be apportioned between the allocation target’s constituent parts. A non-allocable requirement must be passed to the subordinate parts in its entirety. This term disappeared somewhere in the late 1980’s, probably because it was too easily confused with the concept of “requirement allocation”. That was too bad, because... read more
Classification In the Compilation Context
Most material from which parameterizations are extracted were not written to make that task easy. The idea of extracting and classifying engineering data (e.g., requirements) from such source material is described along with a candidate framework. read more.
Design-to Requirement
A type of development requirement articulating a mandatory characteristic of a CI. Infrequently, referred to as “identification requirement” because the dingus isn’t considered to be the dingus if it doesn’t posses said characteristic correctly.
Development Requirement
A technical requirement used to guide (drive) the designers and verification planners during development of a CI. In a perfect world where nothing went wrong, synonymous with Qualification Requirement, except that the final Qualification Requirements might end up not matching the Development Requirements actually used to drive the design. The best ways to use this... read more
Environment
The circumstances, objects, or conditions by which an item is surrounded. read more.
Government Furnished Equipment (GFE)
Designs and/or articles that are provided by the Government acquisition customer as part of the system. The use of GFE can significantly complicate development, but sometimes there are no good alternatives to the practice. When GFE is itself not yet complete, it can take of the form of a directed design solution. The notion that... read more
Manufacturing Requirement
A type of requirement imposed on Manufacturing by Engineering. In most cases, a mandatory feature found on an identifying drawing.
Objective Requirement
Not, in fact, a requirement at all unless the customer explicitly identifies (in the SoW or T&C) some time, event, or circumstance at which it becomes mandatory, in which case they would more properly be represented by classification of the CI in question. Usually, just an indication of what the customer wishes they could have, if... read more
Operational Requirement
A requirement written with regard to what the End User intends to accomplish by the use of a CI or system of CI’s (which may, or may not, have been developed under a single contract with a single developer). The parameterization of an operational requirement need not be restricted to characteristics of the CI(s) or... read more
Performance Requirement
A requirement derived from a Function by identifying a Measure of Performance (MoP), supplying units and tolerance, and identifying the circumstances under which the MoP must obtain certain ranges of value.
Product Requirement
A requirement for the as-built condition of each S/N of a design which, when met, constitutes one element of justification for marking the item with a Part Number. Sometimes referred to as “Fabrication Requirement”. Contrast with Development Requirement. In legacy practice, Product Requirements were collected into Product/Fabrication Specifications.
Qualification Requirement
A technical requirement used as a criterion to determine whether development of a CI is competently complete (and that the developer should therefore be paid). In theory, synonymous with “development requirement” except that things don’t always end the way they started. The best way to use this term is in the past tense: “the Qualification... read more
Technical Requirement
A requirement with regard to what an Engineered item does for the End User. Contrast with Operational Requirement, which is what the End User accomplishes through the use of the item. read more.
Threshold Requirement
A requirement considered mandatory for successful completion of development. “Mandatory” could apply seperably to the topic or the measure of the requirement.
Verification Requirement
A type of technical requirement mandating some characteristic of a formal verification activity. A verification requirement can apply in either the development or production phases.