MIL-HDBK-520 (USAF)

作者:标准资料网 时间:2024-05-15 02:01:34  浏览:9741   来源:标准资料网

MIL-HDBK-520 (USAF), DEPARTMENT OF DEFENSE HANDBOOK: SYSTEMS REQUIREMENTS DOCUMENT GUIDANCE (05 MAR 2010)., A guidance document/handbook or template for developing a System/Subsystem Requirements Document never existed. It was Department of Defense (DoD) best practice to use the System/Subsystem Specification DID and MIL-STD-961 as a reference point for establishing a SRD and subsequent system and subsystem specifications. After development of the Joint Services Specification Guides (JSSGs), under now defunct Joint Aeronautical Commander?s Group (JACG), it served as a convenient template for a SRD at the system or subsystem level. Data Item Description (DID) DI-IPSC-81431A, System/Subsystem Specification; and MIL-STD-961, Department of Defense Standard Practice Defense and Program-Unique Specifications Format and Content, coupled with several different Systems Engineering (SE) guides, formed the framework for this System Requirements Document (SRD) handbook. While no longer used by the United States Air Force (USAF) DI-IPSC-81431A is still in use by the United States Navy (USN). Since Acquisition Reform of the early 1990?s, DoD Programs have relied upon industry best practices and contractor formatted specification documents that continue to reflect the intent of this DID. As this document was once a stalwart of the DoD specification process, the SRD Team has chosen to use it as the baseline for this handbook. Any deviations from the latest DID version will become update recommendations for future versions. This SRD handbook includes a generic SRD template and format, and contains template examples representative of major weapon systems, e.g., Aircraft, Air Armament, Command & Control (C2), Nuclear Systems, and Space Systems. It is meant to be used as a guide to translate warfighter Capability Based Requirements (CBR), or other user/customer requirements, into performance based acquisition requirements, e.g., system requirements, for a system or subsystem in any program Milestone (MS) or phase. The handbook focus is on requirements analysis as related to SRD development, and is not intended to be a complete Systems Engineering Handbook or a repository for ?System Requirements.? Reference documents were used extensively in creating this handbook and were updated herein to current DoD policy and processes. Please refer to cited footnote references for further reading. One drawback to citing reference documents is that references change over time and it could be a challenge to keep current. With regulations and instructions, the latest is the one that should be followed. However, advantages outweigh drawbacks and this document will provide detailed background for anyone desiring a more in depth research into the subject. This handbook will be reviewed periodically for updates and will attempt to remain current.