Software Data

Software Data

Software Resources Data Reporting (SRDR) is a mechanism used by the Department of Defense (DoD) cost and acquisition communities to collect cost and technical data on government and contractor software development, software maintenance and Enterprise Resource Planning (ERP) development efforts. The reporting thresholds for each of these SRDRs is outlined in DoD Instruction (DoDI) 5000.73. The SRDR Data Item Description (DID) provides the guidance and instruction for the preparation of data and information that is submitted using these three reporting formats:

  • Format 1, DD Form 3026-1, Software Development Report, provides the reporting format for software development efforts. Software development reports accommodate initial reports with estimated values, interim reports with a combination of estimated and actual values, and final reports with actual values.
  • Format 2, DD Form 3026-2, Software Maintenance Report, provides the reporting format for software maintenance efforts. Software Maintenance Reports provide actual values and are submitted on an annual basis unless the Cost Working Integrated Product Team (CWIPT) deems otherwise.
  • Format 3, DD Form, 3026-3, ERP Software Development Report, provides the reporting format for ERP programs. ERP or Defense Business Systems are considered a special case of a software development effort.

Each SRDR format requires that information and data be submitted in two Parts. Part 1 includes identifying information, as well as, software size, schedule, and technical characteristics. Part 1 is required to be submitted in eXtensible Markup Language (XML) format when cPet functionality is available to generate an XML file from the completed Excel forms (coming soon in spring 2021). Part 2 provides effort data by month must be submitted in Excel format. Where possible, the information provided in Part 2 should align with the data provided in companion Contractor Cost Data Reports (CCDRs). Until the cPet functionality is available to generate the XML format, both Part 1 and Part 2 must be submitted in Excel format.

Any phase of a program may use any of the SRDR formats, the CWIPT will make a determination as indicated on the Cost and Software Data Reporting (CSDR) plan which SRDR format(s) is required for the specific effort based on the software scope and effort.

Reference material for the SRDR:

  • All CSDR DIDs, Forms and example CDRLs can be accessed through the DIDs and FORM TABLE
  • Implementation Guidance

  • The Software Development Report and the Software Maintenance Report require that Source Lines of Code (SLOC) are reported as the primary metric for software size. The SRDR DID requires that the Unified Code Counter-Government (UCC-G) tool be used to count and report SLOC. Information regarding how to obtain the UCC-G tool can be found here:

    • Unified Code Counter - Government Info
    • If data submitters have an issue accessing and obtaining the UCC-G tool, the University of Southern California Center for Systems and Software Engineering’s (USC CSSE) publicly available Unified Code Counter is also acceptable for SRDR.
  • Application Domains - The SRDR DID requires that Application Domains are identified for reported software activities. The brief linked below provides a description and a definition for each of the Application Domains.

    Application Domain Brief

SRDR Unified Review Function (SURF)

The purpose of the SURF team is to maintain the Government Verification & Validation (V&V) efforts for SRDR. The intent is to supplement the Defense Cost and Resource Center (DCARC) review at the time of the SRDR submission in order to improve the quality of the data collection and decrease the amount of time required for Government review and contractor processing.

Read the Department of Defense Software Resource Data Report (SRDR) Verification and Validation (V&V) Guide version 4.0

SURF V&V Question Templates are MS Excel files that accompany the V&V guide. The four templates provide a check list to aid SURF and DCARC analysts in the review of Legacy, Development, Maintenance and ERP software data reports.