Software Data

Software Data

        “Current software data reports suffer from many shortcomings, including inconsistency of data reporting, inability to track to cost reports, and use of non-standard formats. Over the past two years the DoD cost community has jointly developed a new software data reporting system that will mitigate many of the existing shortcomings. CAPE is now implementing the use of the updated SRDR, found on the CADE public website, for collection of software data on efforts that meet Cost and Software Data Reporting (CSDR) thresholds.”

               -DoD Cost Analysis Improvement Memo, January 9, 2017

DoD Cost Analysis Data Improvement Memo Signed by Dr Morin 2017.01.09

A new SRDR Data Item Description (DID), DI-MGMT-82035, with an updated format for development and new format for maintenance was approved in June 2016 and is available in our DID & Form Table page (link is provided below). It replaces the previous Initial and Final SRDR DIDs and must be used for all new contracts and government efforts over $20M development or over $1M per year maintenance. Contract data requirements lists (CDRLs) may be amended to implement the new DIDs for future software releases at the discretion of the Program Manager and Cost Working Integrated Product Team (CWIPT). Example SRDR CDRL language to address the new SRDR DID is available in our CDRL page (link is provided below).

  • DD Form 3026-1 (Format 1) provides the reporting format for software development efforts. Development SRDRs should align with acquisition Contract Cost Data Reports (CCDR) (DD Forms 1921 and 1921-1). Format 1 accommodates initial reports with estimated values, interim reports with a combination of estimated and actual values, and final reports with actual values.
  • DD Form 3026-2 (Format 2) provides the reporting format for software maintenance efforts. Maintenance SRDRs should be accompanied by sustainment CCDRs (DD Forms 1921 and 1921-1 or 1921-5) at a comparable Work Breakdown Structure (WBS) level. Format 2 is to be submitted on an annual basis.
  • Each SRDR format contains a Part 1 and a Part 2. 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, and cPet functionality will be available to generate an XML file from the completed Excel forms. Part 2 must be submitted in Excel format only and validated against companion CCDR submissions as noted above.

SRDR development reporting thresholds remain unchanged at $20M, then year dollars. If a program either has previously qualified for SRDR development reporting or currently qualifies for CCDR sustainment reporting (i.e., total contract exceeding $50M, then year dollars), and the total current annual software maintenance effort exceeds $1M per year, then year dollars, then maintenance SRDRs are required. These thresholds apply to both contractor and government efforts. The services may use the new forms for SRDR submission at any level.

CDRL TABLE

DID & FORM TABLE

Reference material for the 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

  • Unified Code Counter - Government (UCC-G) - The SRDR DID requires the use of the latest Government-approved version of the University of Southern California (USC) Center for Systems and Software Engineering (CSSE) Unified Code Counter (UCC). The Government has conducted Independent Verification and Validation (IV&V) that ensures the code counter can be used on Government systems and provides standardized results across the DoD community. Directions for downloading the tool are included below:

    Access to the UCC-G requires the interested party to acquire a DI2E (Defense Intelligence Information Enterprise) account. This process is outlined below.

    Step 1: Please request a DI2E account following the process outlined on the following link: https://www.di2e.net/display/DI2E/Accounts

    The DI2E account request has two parts. (1) Proof of U.S. Citizenship, and (2) an online registration form.

    Step 2: Once an interested party obtains their DI2E account, please follow the instructions here to request Read Access to the UCC-G project (U2C2 Read)

    Once the user is approved, they will be able to access the UCC-G here.

    Questions about UCC-G can be directed to uccg@integrity-apps.com