DI-SESS-81771

Reuse Management Report (ReMR)

Provides information about existing software products intended to be reused as-is or modified as part of the delivered operational software, including the current status of related reuse activities and alternative approaches.

Approval DateMay 20, 2009

AMSC NumberF9071

Preparing Activity13 (ESC/AQT)

Project Number—

OPR—

DTIC Applicable—

GIDEP Applicable—

Limitation—

Applicable FormsWorksheet Questions for Reused As-is/Modified Software Worksheet Questions for COTS/GOTS Software

Approval Limitation—

Form Version—

DID Formatfree_text

963C CompliantNo

DISTRIBUTION STATEMENT A: Approved for public release; distribution is unlimited.

Supersedes

—

Description & Purpose

—

Application & Interrelationship

—

Use & Relationship

The Reuse Management Report (ReMR) provides information about existing software products intended to be reused as-is or modified as part of the delivered operational software. The report also provides the acquirer insight into the current status of the activities associated with the reuse of these products as compared to the planned activities, and alternative approaches.

This Data Item Description (DID) contains the format, content and intended use information for the data product resulting from the work tasks described in the contract.

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 cited in the contract.

2FormatContractor format is acceptable.

3ContentThe report shall contain the following:

3.1Executive SummaryThis section shall identify and briefly describe all software products that will be reused as-is or modified (existing software requiring change) and integrated into the delivered operational software. Both commercial off-the-shelf (COTS) and government off-the-shelf (GOTS) shall be included.

3.2Current StatusThis section shall present the current status of the software reuse activities compared to the contractor's planned activities. Status shall include progress made and accomplishments for the engineering and management activities for each software reuse product.

3.3VarianceThis section shall identify any activities where work is not progressing in accordance with the plans and schedules, including the reasons for this lack of progress.

3.4MilestonesThis section shall describe the progress made against program milestones during the reporting period.

3.5Alternative ApproachesThis section shall describe alternative approaches for any reused as-is/modified and COTS/GOTS software products that are 1) considered high or moderate risk or 2) not available (i.e., fully documented and tested) at contract award. Alternative approaches provide options if these software reuse products cannot be implemented as planned.

3.6Impacts of Implementing Alternative ApproachesThis section shall include an assessment of the technical impacts to the program and estimates of the programmatic (i.e., effort and schedule) impacts of implementing alternative approaches.

3.7Decision PointsThis section shall include the decision points for implementing alternative approaches. These decision points shall identify when the alternative approach would need to be implemented in the event that the planned software reuse products are not available in time to preserve the program schedule.

3.8Worksheet QuestionsThis section shall include the completed forms (updated, if needed) for all reused as-is/modified and COTS/GOTS software products in accordance with the instructions embedded in the forms. Forms will be included for any newly identified software reuse products.

References

—

Schema v3.0Community-maintained · Verify against ASSIST

Community-maintained — not an official government database.
Verify against ASSIST·GitHub·About·Disclaimer