U.S. flag

An official website of the United States government

Dot gov

Official websites use .gov
A .gov website belongs to an official government organization in the United States.

Https

Secure .gov websites use HTTPS
A lock () or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.

Breadcrumb

  1. Home
  2. Communities of Practice
  3. Engineering
CommentCommunity

Engineering

DEMS CHART

This Community serves as a collaborative space to provide resources for systems engineering (SE) practitioners. These resources support program planning and design activities as well as implementation of SE processes. In addition, this Community offers a variety of ways for Engineering to network with other SE practitioners, to access current community contributions and discussions on SE tips and best practices, and to share expert knowledge related to SE. 

77
Members

Views

Community Contacts

COMMUNITY / Engineering
Mitchell Woods - Community Leader
COMMUNITY / Engineering
Monique Ofori - Community Leader
COMMUNITY / Engineering
Patrick Dallosta - Community Leader
COMMUNITY / Engineering
John Snoderly - Community Leader

Feed / Engineering

Resource / Engineering
Requirements Management Process
View Resource

 

Requirements Management  

The Requirements Management Process is the method to maintain a current and approved set of requirements over the entire acquisition life cycle. This method helps ensure delivery of capability that meets intended mission performance to the operational user. This sub-topical area contains information on the Requirements Management Process found in the Systems Engineering Guidebook, Section 4.1.4. 

https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
Resource / Engineering
Systems Engineering Technical Reviews and Audits
View Resource

Systems Engineering Technical Reviews and Audits 

For DoD systems development, a properly tailored series of technical reviews and audits provide key points throughout the system development to evaluate significant achievements and assess technical maturity and risk. Regardless of acquisition pathway, the Program Manager (PM), Systems Engineer, and Lead Software Engineer work to properly align the applicable technical reviews to support knowledge-based milestone decisions that streamline the acquisition life cycle and save precious taxpayer dollars. Technical reviews and audits allow the PM, Systems Engineer, and Lead Software Engineer to jointly define and control the program’s technical effort by establishing the success criteria for each review and audit. A well-defined program facilitates effective monitoring and control through increasingly mature points.  For additional information on Systems Engineering Technical Reviews and Audits see the Systems Engineering Guidebook, Section 3 Technical Reviews and Audits.  
 

Resource / Engineering
SE Modernization
View Resource

Systems Engineering (SE) establishes the technical framework for delivering materiel capabilities to the warfighter. It provides the foundation upon which program technical activities are built and supports program success. SE seeks to ensure the effective development and delivery of capability through a balanced approach to cost, schedule, performance, and risk, using integrated, disciplined, and consistent activities and processes regardless of when a program enters the acquisition life cycle. SE enables the development of resilient systems that are trusted, assured, and easily modified. 

 

Systems Engineering Modernization

Systems Engineering Modernization (SEMOD) brings an integrated approach across independent guidance provided down to the DoD SE and acquisition communities related to Digital Engineering, Modular Open Systems Approach (MOSA), Mission Engineering, and Software Engineering/ Agile/DevOps across the multiple pathways of the Adaptive Acquisition Framework.  

The DoD uses data-centric approaches to inform decision making. Modernizing the traditional approach to developing systems (systems engineering) requires digital methodologies, technologies, and practices (digital engineering). This fusion of traditional engineering rigor with digital data strengthens the comprehensive engineering process, as digital models and the underlying critical data advance the Department’s ability to design, develop, deliver, operate, and sustain systems. 

SE Modernization promotes implementing the digital transformation in systems engineering technical reviews and process flows that support the acquisition decision process. Moreover, using MOSA to build systems that can be upgraded to incorporate new technology and respond to emerging threats is an imperative for modernizing the SE practice.

 

The vision of SE Modernization is to use data and models to create a more agile and responsive acquisition system that can quickly and effectively meet the needs of the warfighter.

Resource / Engineering
Modular Design
View Resource

 

Modular Design 
 

Modular design allows for modifications to systems, recombination of existing capabilities and upgrade of system elements, to enable competition, innovation, rapidly responding to a changing environment. Designing for modularity is a technical principle for implementing a Modular Open Systems Approach (MOSA) and is a complementary piece to the open system practices in contracting. The major tenet of a modular design strategy is to develop loosely coupled modules, where modules can be decoupled, separated, or even rearranged in a major system platform and major system components developed under the program, as well as major system components developed outside the program that will be integrated into the major defense acquisition program. When designing for modularity, the system should be appropriately partitioned into discrete, scalable, self-contained functional elements by decomposing and decoupling the functions of a system. This functional partitioning results in elements that can now be composed into modules that can be reconfigured or even replaced.  

For more information on Modular Design as a design consideration, see the Systems Engineering Guidebook, Section 5.15 and Section 2.2.5.  Also, see the MOSA Community of Practice
 

Discussions / Engineering

Discussions / Engineering
DoD SEP Outline v4.1 Now Posted to SE&A Site
0 Replies
View Discussion
May 31, 2023 - 11:15am
QUESTION

​DoD SEP Outline v4.1, 26 Apr 23, is now posted to the SE&A Engineering References for Program Office site in both Word and PDF formats. Links:

Word format

PDF format

SCENARIO
COMMENTS
Discussions / Engineering
Updates to DTRAM, IMP/IMS Guide, and SEP Outline published in Apr-May 2023
1 Replies
View Discussion
May 26, 2023 - 10:46am
QUESTION

​OUSD(R&E) SE&A has published updates to the following guidance documents in the past month:

DoD SEP Outline v4.1 adds a new Section 3.7 on Corrosion Prevention and Control (CPC). The sections after that were renumbered accordingly. v4.1 was released 26 Apr 23 but not yet posted on the SE&A website.

Defense Technical Risk Assessment Methodology (DTRAM) v6.4 adds emphasis on CPC by adding criteria 7.2.C5 to the Manufacturing parent criteria area and criteria 8.2.C4 to the RAM & Sustainment parent criteria area.

The Integrated Master Plan (IMP) and Integrated Master Schedule (IMS) Preparation and Use Guide update to the 2005 version was released in late May 2023. It, too, is not yet posted on the SE&A site but will be in the future.

SCENARIO
COMMENTS
Goulet, Joseph… September 25, 2023 - 12:35pm

SE&A's updated IMP/IMS guide and SEP Outline have been posted to SE&A's "Policy and Guidance" site at [https://www.cto.mil/sea/pg/]. Also, SE&A just posted the updated RIO Guide (Sep 2023)

Discussions / Engineering
Human Systems Integration (HSI) is a key enabler to Systems Engineering processes
0 Replies
View Discussion
July 5, 2022 - 09:52pm
QUESTION

Integrating human performance considerations into the defense acquisition system can present substantial challenges for Human Systems Integration (HSI) practitioners and stakeholders. The DAU HSI Community of Practice (CoP) provides a unique resource in this pursuit, offering a convenient platform to share knowledge aimed at achieving effective and relevant HSI practice across government, industry, and academia. Learn more about HSI as a Specialty Engineering discipline described within DODI 5000.88 for incorporating human needs during system design at the following resources:

DAU HSI COP

OUSD(R&E) HSI website:


SCENARIO
COMMENTS

Events / Engineering

No content available.

Announcements / Engineering

Community Announcement / Engineering
New HSI tool for Systems Engineers
View Announcement

Integrating human performance considerations into the defense acquisition system can present substantial challenges for Human Systems Integration (HSI) practitioners and Systems Engineers. The DAU HSI Community of Practice (CoP) provides a unique resource in this pursuit, offering a convenient platform to share knowledge aimed at achieving effective and relevant HSI practice across government, industry, and academia. The HSI COP aims to help stakeholders find knowledge that can be readily applied in practice, including references, standards, templates, lessons learned, and best practices. 

A key resource for Systems Engineers to be compliant with the requirements outlined in DoDI 5000.95 is use of the HSI Framework (HSIF) tool.  Check out this invaluable tool here. The HSIF tool details all the required HSI activities for a program to successfully comply with HSI planning, management, and execution. Register for access today!!

Community Announcement / Engineering
DoD Engineering Recruitment Tool (Brochure) - Now Available for Use
View Announcement

SE CoP Members - In coordination with the Engineering Career Field Functional Integrated Product Team (FIPT) and OSD Graphics Division, a new DoD engineering recruitment tool has been developed to help attract new engineering talent to DoD’s workforce, and increase DoD’s recognition as one of the best places to work as an engineer.  The Defense Services and Agencies can use this brochure to augment their current recruiting and marketing material/messaging.  Included are examples which showcase how you can make a difference as a DoD engineer; descriptions of the unique work being done throughout the Department, and what you can look forward to as a DoD engineer. Also included are figures displaying the wide geographic distribution and variety of engineers employed by DoD.

Image removed.DoD Engineering Recruitment Tool (Brochure).pdf


Resources / Engineering

Community Resource / Engineering
Requirements Management Process

 

Requirements Management  

The Requirements Management Process is the method to maintain a current and approved set of requirements over the entire acquisition life cycle. This method helps ensure delivery of capability that meets intended mission performance to the operational user. This sub-topical area contains information on the Requirements Management Process found in the Systems Engineering Guidebook, Section 4.1.4. 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource
Community Resource / Engineering
Systems Engineering Technical Reviews and Audits

Systems Engineering Technical Reviews and Audits 

For DoD systems development, a properly tailored series of technical reviews and audits provide key points throughout the system development to evaluate significant achievements and assess technical maturity and risk. Regardless of acquisition pathway, the Program Manager (PM), Systems Engineer, and Lead Software Engineer work to properly align the applicable technical reviews to support knowledge-based milestone decisions that streamline the acquisition life cycle and save precious taxpayer dollars. Technical reviews and audits allow the PM, Systems Engineer, and Lead Software Engineer to jointly define and control the program’s technical effort by establishing the success criteria for each review and audit. A well-defined program facilitates effective monitoring and control through increasingly mature points.  For additional information on Systems Engineering Technical Reviews and Audits see the Systems Engineering Guidebook, Section 3 Technical Reviews and Audits.  
 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
SE Modernization

Systems Engineering (SE) establishes the technical framework for delivering materiel capabilities to the warfighter. It provides the foundation upon which program technical activities are built and supports program success. SE seeks to ensure the effective development and delivery of capability through a balanced approach to cost, schedule, performance, and risk, using integrated, disciplined, and consistent activities and processes regardless of when a program enters the acquisition life cycle. SE enables the development of resilient systems that are trusted, assured, and easily modified. 

 

Systems Engineering Modernization

Systems Engineering Modernization (SEMOD) brings an integrated approach across independent guidance provided down to the DoD SE and acquisition communities related to Digital Engineering, Modular Open Systems Approach (MOSA), Mission Engineering, and Software Engineering/ Agile/DevOps across the multiple pathways of the Adaptive Acquisition Framework.  

The DoD uses data-centric approaches to inform decision making. Modernizing the traditional approach to developing systems (systems engineering) requires digital methodologies, technologies, and practices (digital engineering). This fusion of traditional engineering rigor with digital data strengthens the comprehensive engineering process, as digital models and the underlying critical data advance the Department’s ability to design, develop, deliver, operate, and sustain systems. 

SE Modernization promotes implementing the digital transformation in systems engineering technical reviews and process flows that support the acquisition decision process. Moreover, using MOSA to build systems that can be upgraded to incorporate new technology and respond to emerging threats is an imperative for modernizing the SE practice.

 

The vision of SE Modernization is to use data and models to create a more agile and responsive acquisition system that can quickly and effectively meet the needs of the warfighter.

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
Modular Design

 

Modular Design 
 

Modular design allows for modifications to systems, recombination of existing capabilities and upgrade of system elements, to enable competition, innovation, rapidly responding to a changing environment. Designing for modularity is a technical principle for implementing a Modular Open Systems Approach (MOSA) and is a complementary piece to the open system practices in contracting. The major tenet of a modular design strategy is to develop loosely coupled modules, where modules can be decoupled, separated, or even rearranged in a major system platform and major system components developed under the program, as well as major system components developed outside the program that will be integrated into the major defense acquisition program. When designing for modularity, the system should be appropriately partitioned into discrete, scalable, self-contained functional elements by decomposing and decoupling the functions of a system. This functional partitioning results in elements that can now be composed into modules that can be reconfigured or even replaced.  

For more information on Modular Design as a design consideration, see the Systems Engineering Guidebook, Section 5.15 and Section 2.2.5.  Also, see the MOSA Community of Practice
 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
SE Planning and Processes
 
 

Systems Engineering Planning
 

Systems Engineering planning, as documented in the Systems Engineering Plan (SEP), formulates the approach to conduct, manage and control all the technical activities to deliver a desired capability. SE Planning begins with the identification and decomposition of user needs and concepts, and progresses through development, delivery and sustainment of the final product. The Systems Engineering Guidebook provides overarching guidance on the systems engineering discipline, its activities and processes, and its practice in defense acquisition programs. This topical area contains information on SE Planning for DoD acquisitions. 
 

    

 

 

Systems Engineering Processes
 

SE processes are used by contractor and Government organizations to provide a framework and methodology to plan, manage and implement technical activities throughout the acquisition life cycle. SE planning and execution should focus on applying the processes and tools in a rigorous, integrated, and disciplined manner to achieve a system solution that balances performance, cost, schedule, and risk.

                                                    

Technical Management Processes

Technical management processes are applicable to all acquisition pathways, providing a consistent framework for managing technical activities, as well as identifying the technical information and events critical to the success of the program. Technical information includes controlled unclassified information (CUI) as well as classified and unclassified Critical Technical Information (CTI) about DoD sponsored research, technology, programs, and systems being acquired.

 

Technical Processes

Technical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
Specialty Engineering and Design Considerations

Specialty Engineering 

{insert text}

Design Considerations
 

The PM, Systems Engineer, and Lead Software Engineer should address and document design considerations, including all statutory and regulatory requirements in order to:

  • Translate the end-user desired capabilities into a structured system of interrelated design specifications that support delivery of required operational capability.
  • Enable trade-offs among the design considerations in support of achieving desired mission effectiveness within cost and schedule constraints.
  • Incorporate design considerations into the set of system requirements, as some are mandated by laws, regulations, or treaties, while others are mandated by the domain or DoD Component or Agency; these mandates should be incorporated during the Requirements Analysis process to achieve balance across all system requirements.
     

The DoD has put additional emphasis on the four Specialty Engineering design considerations as well as Value Engineering identified in the tiles below resulting in development of additional policy (DoDI 5000.88) and additional guidance. Select the tiles below and please refer to Section 5 of the Systems Engineering Guidebook for more information.
 


 

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
View Resource
Community Resource / Engineering
SE Processes

Systems Engineering Processes

The SE processes are used by contractor and Government organizations to provide a framework and methodology to plan, manage and implement technical activities throughout the acquisition life cycle. SE planning and execution should focus on applying the processes and tools in a rigorous, integrated, and disciplined manner to achieve a system solution that balances performance, cost, schedule, and risk. 

The eight technical management processes, applicable to all acquisition pathways, provide a consistent framework for managing technical activities and identifying the technical information and events critical to the success of the program. Technical information includes controlled unclassified information (CUI) as well as classified and unclassified Critical Technical Information (CTI) about DoD sponsored research, technology, programs, and systems being acquired. The eight technical processes ensure the system design and the delivered capability reflect the requirements that the stakeholders have expressed. The 16 SE processes are applicable to all the AAF pathways to some degree. The PM and SE will determine which processes to use for their program. 

Whereas the technical management processes provide insight of, and control over, the technical development of a system throughout its life cycle, the technical processes are used to design, develop and analyze the system, system elements and enabling system elements required for integration, test, production, deployment, support, operation and disposal. The eight technical processes provide a framework for ensuring and maintaining traceability between stakeholder requirements, systems design and the eventual delivered capability.
 

For more information refer to Section 4 of the Systems Engineering Guidebook.
 

Technical Management Processes
 
Technical Processes
 
Technical Planning  Stakeholder Requirements Definition
Decision Analysis  ​Requirements Analysis 
Technical Assessment  ​Architecture Design 
Requirements Management Implementation 
Risk Management Integration 
Configuration Management  Verification 
Technical Data Management  Validation 
Interface Management  Transition 

 

 

 


CREATED:
BY:
Rhyne, Darren
LAST MODIFIED:
BY:
Rhyne, Darren
View Resource
Community Resource / Engineering
Technical Planning Process

 

Technical Planning Process

The Technical Planning Process is the method to define the scope of the technical effort required to develop, field, and sustain the system, as well as provides critical quantitative inputs to program planning and life-cycle cost estimates. Technical planning provides the program office with a framework to accomplish the technical activities that collectively increase product maturity and knowledge and reduce technical risks.  This sub-topical area contains information on the Technical Planning Process found in the Systems Engineering Guidebook, Section 4.1.1.

CREATED:
BY:
Content Author No Reply
LAST MODIFIED:
BY:
Content Author No Reply
https://www.cto.mil/wp-content/uploads/2023/06/SE-Guidebook-2022.pdf
View Resource

Documents / Engineering

Software Center Operator Manual SCOM Data Item Description DID
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

The Software Center Operator Manual (SCOM) provides personnel in a computer center or other centralized or networked software installation information on how to install and operate a software system.  The SCOM is developed for software systems that will be installed in a computer center or other centralized or networked software installation, with users accessing the system via terminals or personal computers or submitting and receiving inputs and outputs in batch or interactive mode.  This Data Item Description (DID) is used when the developer is tasked to identify and record information needed by persons who will operate software in a computer center or other centralized or networked software installation, so that the software can be used by others. The SCOM DID (DI-IPSC-81444) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205923. BOV

Establishing the Technical Foundation - MSA Phase
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

From the DASD(SE) web site: "In the Defense Acquisition Research Journal article Establishing the Technical Foundation: Materiel Solution Analysis Is More than Selecting an Alternative, DASD(SE) team members Aileen G. Sedmak, Zachary S. Taylor, and Lt Col William A. Riski, USAF (Ret.) discuss evidence that adequately resourced systems engineering and technical planning before Milestone A can help a program define realistic requirements, establish executable programs, and deliver systems on time and on budget. "Several government and independent studies indicate effective systems engineering and program planning in the early stages of acquisition are essential to controlling costs and improving program results. The article describes the challenge of conducting good systems engineering and technical planning during the Materiel Solution Analysis (MSA) phase after completion of the Analysis of Alternatives and before Milestone A. "The article also presents the work of the DoD Development Planning Working Group to mitigate this challenge by describing the technical activities in the MSA phase necessary to develop the level of knowledge and system concept maturity necessary to proceed into the next phase of acquisition. These technical activities are represented in a notional MSA Phase Activity Model." .

Public Law, document synopsis, e.g.,
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

TBD TBD

DASD SE Policy
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

TBD TBD

Technology Readiness Assessment TRA
Document Type:
Document
Modified: Changed by Content Author No Reply on
Summary

A Technology Readiness Assessment (TRA) is a systematic, metrics-based process that assesses the maturity of, and the risk associated with, critical technologies to be used in Major Defense Acquisition Programs (MDAPs). It is conducted by the Program Manager (PM) with the assistance of an independent team of subject matter experts (SMEs). It is provided to the Assistant Secretary of Defense for Research and Engineering (ASD(R&E)) and will provide part of the bases upon which he advises the Milestone Decision Authority (MDA) at Milestone (MS) B or at other events designated by the MDA to assist in the determination of whether the technologies of the program have acceptable levels of risk—based in part on the degree to which they have been demonstrated (including demonstration in a relevant environment)—and to support risk-mitigation plans prepared by the PM. The plan for conducting a TRA is provided to the ASD(R&E) by the PM upon approval by the Component Acquisition Executive (CAE). A TRA is required by Department of Defense Instruction (DoDI) 5000.02 for MDAPs at MS B (or at a subsequent Milestone if there is no MS B). It is also conducted whenever otherwise required by the MDA.  Instructions for conducting TRAs are contained in "Technology Readiness Assessment (TRA) Guidance",  April 2011, revision posted 13 May 2011, prepared by the ASD(R&E):  http://www.acq.osd.mil/rd/publications/index.html .

Software User Manual SUM Data Item Description DID
Document Type:
Document
Modified: Changed by Content Author No Reply on
Summary

The Software User Manual (SUM) tells a hands-on software user how to install and use a Computer Software Configuration Item (CSCI), a group of related CSCI's, or a software system or subsystem.  It may also cover a particular aspect of software operation, such as instructions for a particular position or task.  The SUM is developed for software that is run by the user and has a user interface requiring on-line user input or interpretation of displayed output.  If the software is embedded in a hardware-software system, user manuals or operating procedures for that system may make separate SUMs unnecessary.  This Data Item Description (DID) is used when the developer is tasked to identify and record information needed by hands-on users of software. The SUM DID (DI-IPSC-81443) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205922>. BOV

Requirements Allocation Sheets RAS Data Item Description DID
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

Requirements Allocation Sheets (RAS) are used to translate functions into design requirements.  The analysis of functional flow diagrams is documented on RAS. The RAS DID (DI-GDRQ-81222) can be found on the DoD DLA ASSIST website at http://quicksearch.dla.mil/qsDocDetails.aspx?ident_number=205261 .

GAO Reports, document webpage, e.g.
Document Type:
Page Link
Modified: Changed by Content Author No Reply on
Summary

TBD TBD

To participate in this community, you must be registered. Join Now