Operating the DoDi SRE Planning Application


1.       Open the DoDi SRE Planning application as shown in the last step of the installation instructions. The below page is displayed.

2.       The first step is to either open an existing file or create a new one.  Let’s open and existing file first by selecting the File->Open menu item.  Select the “myproject.xlsx” file.  The “template.xlsx” file is a template which is used to create all new files.  The template file can be modified by you to minimize the amount of time you spend creating files for similar projects.

3.       Once the myproject.xlsx file is open the below is displayed.  There are several columns of information which you need to complete to tailor the IEEE 1633 Recommended Practices for Software Reliability to the Dodi 5000.2 program types, ACAT types and milestones.

4.       Select the MDAP or MAIS pulldown menu as shown below.  The first step of the tailoring is to select which program type is most applicable.  MDAP is for hardware and software intensive systems while MAIS is for systems that are mostly or entirely software.

5.       Select the ACAT pulldown menu as shown below.  There are three choices.  ACAT I is the most expensive type of system, ACAT II is less expensive than ACAT I and other is neither ACAT I or ACAT II.  Refer to DoDi 5000.2 for clarification of which one to select.


6.       Select the Current phase of the program as shown below. The six choices are shown below.  This tool will export all SRE tasks that apply to the selected milestone as well as all SRE tasks that apply to future milestones.  So, if you select “Milestone A” the SRE tasks for the entire program from Milestone A to Sustainment are exported.


7.       There are 9 specific types of programs/situations that can be present on any type of program.  Select either Yes or No as relevant for the particular program under analysis.


Program characteristic


Brand new hardware and software with many unknowns

This means that both the hardware and the software are at “version 1”.  There is very little reuse from another system.

A system will be produced in large quantities

Examples include radios, artillery, etc.

The system has a short mission life such as:  rocket, missile or space craft

Any system or subsystem that launches or flies is an example of a system with a short mission life.  The “mission” is the particular period of time for which the system must be operational.  For example, an Extended Aircraft must be operational for 14 hours.

Known risk of user related failures

If the user is an important part of the system and there is a history or potential of the user making mistakes then check this box yes.

Small but important program

This means that the program is not ACAT I or ACAT II but it is very critical to the overall system or system of systems.

Many different subcontractors, vendors, COTS components

There will be a significant amount of code developed by different organizations which must all come together and work

Fragile legacy software

This means that the code in this system is either very old (more than 10 years) or it is becoming increasing difficult to make any changes to the code without causing new defects.

Systems that required destructive testing to fully test

Examples of systems that require destructive testing are artillery, missiles, etc.

Ultra-high reliability requirements

This is a system that has reliability requirements that are unusually higher than others regardless of whether the system is safety critical.  An example might be the communications for a system of systems.

Safety critical - will fly over commercial airspace

This is a system that has significant safety issues even over and above occupational (pertaining to one soldier).


8.       When finished with the selection process, press the “Export” tab.  When you press the “Export” button the appropriate SRE tasks from IEEE 1633 Recommended Practices for Software Reliability, 2016 will be exported to the “Results” worksheet of the file that you have open.  Only those tasks that apply to the program type, ACAT type, milestone and particular risk areas will be selected.  The recommendations will be listed as “Essential”, “Highly recommended”, “Recommended”.  There are also some tasks that apply in special circumstances which will be identified as such.


9.       New files can be created using the File->New option. 

10.   You can use the File->Save As function to save many files that are similar.  Say for example, you want to save a file for each of the 6 milestones.  You can use the “Save As” function to do this.

11.   The Help menu shows the “About” page as well as the online help link.