scope:

USE/RELATIONSHIP: For background and detailed requirements related to Software Resources Data Reporting (SRDR), refer to DoD 5000.04-M-1, "Cost and Software Data Reporting (CSDR) Manual."

CSDR is the Department of Defense (DoD) system for collecting actual costs and software data and related business data. The resulting database serves as the primary contract cost and software data (CSD) database for most DoD resource analysis efforts, including cost database development, applied cost estimating, cost research, program reviews, analysis of alternatives (AoA), and life cycle cost estimates. All formats may be used in response to Government solicitations according to Defense Federal Acquisition Regulation Supplement (DFARS) sections 234.7100, 234.7101, 242.503-2, 252.234-7003, and 252.234-7004:

Format 1, DD Form 3026-1, "Software Development Report", consists of two parts. Part 1, Software Development Technical Data, reports the software development size, context, and technical information. It consists of Release Level and Computer Software Configuration Item (CSCI) Level sections. The Release Level Data includes all information applicable to the entire software release for the reporting event, defines each of the data elements as required, and describes the methods and rules used to perform the data measurement or estimation. The CSCI Level Data is used to obtain the estimated or actual (as-built) characteristics of a software product and its development process at the CSCI Level. Other terms for CSCI include Software End Item, Software Item (SI), etc., but this document will use CSCI as the primary term throughout. Part 2, Software Development Effort Data, reports the software development efforts associated with each reported release and CSCI. Format 1 uses the term "release" to refer to commonly used terms such as build, product build, and increment.

Format 2, DD Form 3026-2, "Software Maintenance Report", consists of two parts. Part 1, Software Maintenance Technical Data, reports the size, context and technical information. It consists of Top Level and Release Level sections. The Top Level Data includes all information applicable to the software maintenance release(s) for the reporting event, defines each of the data elements as required, and describes the methods and rules used to perform the data measurement or estimation. The Release Level Data is used to obtain the actual (asbuilt) characteristics of the maintenance product and its maintenance process at the Release level. Part 2, Software Maintenance Effort Data, reports the to-date software maintenance efforts for each in-progress and completed release(s) and the annual total software maintenance activities. In Format 2, the words "software release" refer to a set of changes to the existing baseline software that are delivered to end users and that require formal testing, i.e., a new software configuration has been created, including patches and emergency releases. Format 2 uses the term "release" to refer to commonly used terms such as release, build, increment or drop.

The SRDR is structured around formats that contain the content and relationships required for the electronic submissions. This Data Item Description (DID) summarizes the Software Development Report and the Software Maintenance Report and provides instructions to support the data and frequency requirements specified in the contract for CSDR reporting. The primary purpose of this data is as follows:

The intent of the SRDR process is to collect objective, measurable data commonly used by industry and DoD cost analysts. These data are used to compile a repository of estimated and actual software product sizes, schedules, effort, and quality that Government analysts can draw upon to build credible size, cost, and schedule estimates of future software-intensive systems.

The Software Development Report is not a management report. It is not intended for tracking progress of software development during contract execution. It does, however, collect the person-hours expended during software development, as well as other software measures.

The Software Maintenance Report collects the person-hours expended during software maintenance and other software measures. It is not a management report. It is not intended for tracking progress of maintenance during contract execution.

Ground Rules, Terms and Definitions

The minimum level of detail to be reported in each SRDR submission shall be in accordance with the CSDR Plan, as approved by the Office of the Secretary of Defense (OSD) Deputy Director, Cost Analysis (DDCA) or Service Cost Director if not an ACAT I program. Discrete reporting is required for all Work Breakdown Structure (WBS) elements identified in the CSDR Plan.

In the Software Maintenance Report, the maintainer must fill out the Top-Level Data section that defines the data elements. The definitions of the data items must address and provide context to the following categories of data: Context, Project Description, Size, Effort, and Schedule. Definitions as stated in ISO/IEC/IEEE 12207:2008, ISO/IEC 14764: 2006 and other cited standards, e.g. MIL-STD 881, shall be used.

At the annual reporting date, a Software Maintenance Report contains the Common Heading Data (or Metadata), Part 1 Top Level Data, the Part 1 Release Level Data, and the Part 2 data which provides effort by release(s) and annual total effort for associated software maintenance activities. The annual reporting date shall be in accordance with the government fiscal years.

ISO 14764:2006 defines software maintenance as "the totality of activities required to provide cost-effective support to a software system. In this DID, the words software maintenance and software sustainment are synonymous. In this DID, the word "maintainer" refers to the organization that is performing maintenance activities on software. An organization can be either a government institution or a commercial contractor.

This DID supersedes the following DIDs:

• DI-MGMT-81739B

• DI-MGMT-81740A