October 2004 - Defense Technical Information Center

1 naval Systems Engineering Guide October 2004 Report Documentation PageForm ApprovedOMB No. 0704-0188 Public reporting burden for the collection of Information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, gathering andmaintaining the data needed, and completing and reviewing the collection of Information . Send comments regarding this burden estimate or any other aspect of this collection of Information ,including suggestions for reducing this burden, to Washington Headquarters Services, Directorate for Information Operations and Reports, 1215 Jefferson Davis Highway, Suite 1204, ArlingtonVA 22202-4302.

2 Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to a penalty for failing to comply with a collection of Information if itdoes not display a currently valid OMB control number. 1. REPORT DATE OCT 2004 2. REPORT TYPE 3. DATES COVERED 00-00-2004 to 00-00-2004 4. TITLE AND SUBTITLE naval Systems Engineering Guide 5a. CONTRACT NUMBER 5b. GRANT NUMBER 5c. PROGRAM ELEMENT NUMBER 6. AUTHOR(S) 5d. PROJECT NUMBER 5e. TASK NUMBER 5f. WORK UNIT NUMBER 7. PERFORMING ORGANIZATION NAME(S) AND ADDRESS(ES) naval Systems Engineering Steering Group,Washington,DC 8. PERFORMING ORGANIZATIONREPORT NUMBER 9. SPONSORING/MONITORING AGENCY NAME(S) AND ADDRESS(ES) 10.

3 SPONSOR/MONITOR S ACRONYM(S) 11. SPONSOR/MONITOR S REPORT NUMBER(S) 12. DISTRIBUTION/AVAILABILITY STATEMENT Approved for public release; distribution unlimited 13. SUPPLEMENTARY NOTES 14. ABSTRACT 15. SUBJECT TERMS 16. SECURITY CLASSIFICATION OF: 17. LIMITATION OF ABSTRACT Same asReport (SAR) 18. NUMBEROF PAGES 295 19a. NAME OFRESPONSIBLE PERSON a. REPORT unclassified b. ABSTRACT unclassified c. THIS PAGE unclassified Standard Form 298 (Rev. 8-98) Prescribed by ANSI Std Z39-18 DEPARTMENT OF THE NAVY naval AIR SYSTEMS command , PATUXENT RIVER, MD 20670-1547 naval SEA SYSTEMS command , WASHINGTON NAVY YARD, DC 20376-4065 naval SUPPLY SYSTEMS command , MECHANICSBURG, PA 17055-0791 SPACE AND naval WARFARE SYSTEMS command , SAN DIEGO, CA 92110-3127 MARINE CORPS SYSTEMS command , QUANTICO.

4 VA 22134-6050 NAVAIR NAVSEA 4400 4400 Ser00/118 Ser 007 NAVSUP SPAWAR 4400 4400 Ser00/ Ser00/ MARCORSYSCOM 4400 Ser00/ MEMORANDUM OF UNDERSTANDING VS-MOU-20 AMONG naval AIR SYSTEMS command naval SEA SYSTEMS command naval SUPPLY SYSTEMS command SPACE AND naval WARFARE SYSTEMS command MARINE CORPS SYSTEMS command Subj: MEMORANDUM OF UNDERSTANDING FOR AN INTRODUCTION AND PROMULGATION OF THE naval SYSTEMS ENGINEERING GUIDE Ref.

5 (a) Under Secretary of Defense Memorandum, Policy for Systems Engineering in DoD, of20 Feb2004 1. By reference (a), the Acting Under Secretary of Defense (Acquisition, Technology and Logistics) signed into policy the requirement that "All programs responding to a capabilities or requirements document shall apply a robust Systems Engineering (SE) approach that balances total system performance and total ownership costs w it hin the family-of-systems, system -of-systems context. Accordingly, a SE Plan shall be developed for Milestone Decision Authority approval in conjunction with each Milestone review". SE must be embedded in program planning and performed across the entire acquisition life cycle.

6 SE provides the integrating Technical processes to define and balance system performance, cost, schedule, and risks. 2. To assist naval programs in thoroughly implementing SE in their programs, we have developed the naval Systems Engineering Guide (NSEG). This document is based on the EIA-632 and expanded by the naval systems commands. The NSEG provides the tools needed to develop the required SE Plan and to implement the necessary SE discipline and is accessible on the Defense Acquisition University website below: 201&ID2=DO TOPIC Subj: MEMORANDM OF UNDERSTANDING FOR AN INTRODUCTION AND PROMULGATION OF THE naval SYSTEMS ENGINEERING GUIDE 3. This Virtual SYSCOM memorandum of understanding will assist in maximizing our performance in supporting the Fleet and realizing the potential capabilities of our products.

7 W. B. MASSENBURG, Commander, naval Air Systems command CQMNAVSEA (Acting) DTK, STONE, Commander, " naval Supply Systems command Space and Nayal Warfare Systems command (Acting) -LIAJvlD. CATTO, Commanding General, Marine Corps Systems command ii Table of Contents Page Number Introduction ..vi Executive Background ..vi Document Section 1 Scope .. 1 Purpose .. 1 1 2 Normative 2 3 Definitions and acronyms .. 2 Key 2 Acronyms .. 2 Terminology .. 2 4 4 Acquisition and Supply.

8 6 Supply 7 Acquisition Process .. 10 Technical 19 Planning 19 Assessment Process .. 43 Control 51 system Design .. 62 Requirements Definition Process .. 68 Solution Definition Process .. 84 Product 98 Implementation 98 Transition to Use Process ..101 Technical Evaluation ..103 system Analysis Process ..104 Requirements Validation Process ..123 system Verification Process.

9 135 End Products Validation 5 Application Enterprise factors ..149 Project factors ..149 Enterprise Project support of the Technical process ..150 External Influence of other enterprise projects ..151 6 Application key system concept ..151 Building block ..152 system End product element ..153 Subsystem Enabling product elements ..153 Building block Specifications.

10 155 Stages of maturity ..156 iii Table of Contents (cont.) Page Number Performance specifications ..156 Detail specifications ..156 Interface definition ..157 Multidisciplinary Risk management ..158 Technical reviews ..158 Cost collection and system structure concept ..159 Top-down development ..160 Bottom-up realization ..163 Engineering life cycle APPENDIX A B Enterprise-based Life Cycle ..173 C Process Task D Planning Documents ..205 E system Technical F Process Relationships.