DI-SESS-82459
Software Metrics Report (SWMR) per Statement of Work (SOW)
Provides essential information on the software development for the system and is used to track the progress of the software development.
Approval DateJanuary 8, 2025
AMSC NumberN10517
Preparing ActivityAS
Project NumberSESS-2025-005
OPR—
DTIC Applicable—
GIDEP Applicable—
Limitation—
Applicable Forms—
Approval Limitation—
Form Version—
DID Formatfree_text
963C CompliantYes
DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.
Application & Interrelationship
—
Use & Relationship
The Software Metrics Report provides essential information on the software development for the system. This DID is used to track the progress of the software development.
This DID contains the format, content, and intended use information for the data product resulting from the work task described in the contract Statement of Work (SOW).
Preparation Instructions
1Reference documentsThe applicable issue of the documents cited herein, including their approval dates and dates of any applicable amendments, notices, and revisions, shall be as specified in the contract.
2FormatContractor's format is acceptable.
3ContentThe following shall be included in the Software Metrics Report:
3.1The Software Metrics Report shall include the following
3.1.1SW Cost (EVSPI, BCWS, BCWP, and Actual)
3.1.2SW Size (Planned versus actual, new, modified, reused)
3.1.3Staffing (planned versus actual baseline, current, and unplanned losses)
3.1.4SW Requirements Volatility (planned versus actual, added, modified, deleted, total requirements)
3.1.5Peer Review Defects (major, minor, and admin for SRS, ICD, IDD, SDD, STP, and cumulative)
3.1.6SW Defects (priority per IEEE 12207 Appendix J)
3.1.7Software metricshall be included for the number of requirements that have a test procedure or verification method developed.
3.1.8Additional software metricsshall also include SW development progress (baseline and current) for each of the following: requirement analysis, software design, coding, unit test, integration test, and system test.
3.1.9Notesshall be included for each metric as appropriate.
Schema v3.0Community-maintained · Verify against ASSIST