DI-IPSC-82412
Software Metrics Plan
This DID shall be used by DoD programs in preparing the Software Metrics Plan covering the processes for collection and analysis of all software metrics.
Approval DateMay 23, 2023
AMSC Number10405
Preparing ActivityMDA
Project NumberIPSC-2023-001
OPR—
DTIC ApplicableNo
GIDEP ApplicableNo
Limitation—
Applicable FormsNone
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
This Data Item Description shall be used by Department of Defense (DoD) programs in preparing the Software Metrics Plan (SMP) covering the processes for collection and analysis of all software metrics. The SMP provides the acquirer insight regarding the software metrics selected, rationale for choosing the metrics, and the costs for collecting the metrics, along with how the data analysis and trends from each software metric will support the quantitative software engineering management of the effort. The SMP will also include the format for the software metrics report to include: metrics data collected, trends, analysis of metrics data, and opportunities for process improvement.
This Data Item Description (DID) contains the format and content preparation instructions for the data product generated by the specific task requirement included in the contract. It is intended that all requirements contained herein shall apply to all applicable DoD acquisition programs through all program phases.
Preparation Instructions
1Reference documents.The applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revision, shall be as specified in the contract.
2Format.The SMP shall be specified in Section 3 with tailored instructions identified in block 16 of the Contract Data Requirements List (this CDRL) (DD 1423).
3.1Identification.This paragraph shall contain a full identification of the system and the software to which this document applies, including, as applicable, identification number(s), title(s), abbreviation(s), version number(s), and release number(s).
3.2System overview.This paragraph shall briefly state the purpose of the system and the software to which this document applies. Included shall be the viewpoint architectures that identify the humans, hardware, and software interactions with the system.
3.3Overview of required work.Provide a detailed description of the following, in its own subsection:
3.3.1Software Metrics Identification.This paragraph shall summarize the set of software metrics being collected to include rationale for its collection, expected cost of collection, along with the frequency of collection.
3.3.2Software Metrics Collection Process.This section shall:
3.3.2.1Identify the software metrics collection process overall, and by software metric, based on maximizing automation while minimizing the costs of collection.This shall include how the software metrics are collected and the specific tools employed during the collection process.
3.3.2.2Address how the integrity of the software metrics data are maintained to include "chain of custody"
3.3.2.3Timeliness of delivery of the software metrics data to government stakeholders.
3.3.3Software Metrics Analysis Process.This section shall:
3.3.3.1Address software analysis for each software metric and the specific tools employed during the software metrics analysis process
3.3.3.2Identify the software metrics analysis process overall, and by software metric, based on the approaches and methodologies being employed for analysis of historical software metrics data in order to achieve quantitative management for the software development effort.
3.3.3.3Include trend analysis and prediction of potential problematic areas (e.g. breakdown in defect containment).
3.3.3.4Identify potential opportunities for continuous software development process improvement.
3.3.3.5Timeliness of delivery of the software metrics analysis data to Government stakeholders.
3.3.4Software Metrics Report Process.This section shall identify the process covering the generation of the software metrics report to include data, analysis, format, presentation, media, delivery frequency along with the tools utilized in automating the process to the maximum extent possible while ensuring timely delivery of the software metrics report to government stakeholders.
3.3.5Appendixes.Appendixes shall be used to provide the following information: Alphabetical listing of acronyms, abbreviations, and associated meanings as used in this document, list of any terms and definitions needed to understand this document, supporting charts, architectures, and classified sections. As applicable, each appendix shall be referenced in the main body of the document where the data would normally have been provided. Appendixes shall be bound as separate documents for ease in handling. Appendixes shall be lettered alphabetically (A, B, etc.).
Schema v3.0Community-maintained · Verify against ASSIST 