[Note to Preparers: Software should be delivered in a standalone fashion, i.e., not encumbered by any particular configuration management tool. Existing and future programs that ultimately will use the software or artifacts should have the ability to use whatever configuration management tool they desire without any overt or hidden dependencies on a given tool.] [Note to Preparers: When citing regulations such as the DFARS and FAR, dates are included where possible to reflect the most recent clause dates. Program Managers and Contracting Officers must verify the latest clause dates before signing the final SOW.] Prior to determining the CDRLs and DIDs required, it is recommended that the Program Office perform an assessment of its Intellectual Property Rights needs and craft its CDRL and Deliverable requirements accordingly. If the Program Office, PEO, Domain or Sponsor believes that the program deliverables would be of such interest that they warrant inclusion in the GCS repository or GCS Application Store, then the CDRL and deliverables should include those design, developmental, or diagnostic items needed to reproduce or recreate the asset. The ideal asset would have artifacts in most or all of the following categories. The key to obtaining these artifacts is to require that they be delivered as part of the terms of the contract. In order to facilitate reuse of these artifacts, these items must be delivered with the appropriate data or license rights, e.g., Government Purpose Rights (GPR) or suitable special license rights. In order to facilitate reuse, the asset should bundle the following or their equivalent: i. ii. iii.
iv. v. vi. vii.
viii. ix.
Requirements (e.g., Word documents, DOORS file or Excel or XML export or other file endings that apply.) Architecture models (e.g., System Architect files, including Department of Defense Architecture Framework (DoDAF) views where required or other file endings that apply.) Functional models (e.g., CORE file in native format or XML export) Software models (e.g., Rose/Rhapsody/iUML (Unified Modeling Language)/Artisan models in native or XMI format; minimum diagrams Class and State or Interaction/Sequence or other file endings that apply.) Hardware models (e.g., CAD DXF, IEGS files or other file endings that apply.) Human systems engineering models (e.g., IPME or Envision Ergo files or other file endings that apply.) Cost models (e.g., PRICE, SEER, COMET, VAMOSC, Excel files or other file endings that apply.) Modeling and Simulation data (e.g., NETWARS/OPNET, NSS, GCAM -scenarios, environmental, platforms, tactics, MOEs, MOPs in XMI format following JC3IEDM or XMSF standards or other file endings that apply.) Test plans and results (e.g., QA Run, Quality Center files or Word or Excel export or other file endings that apply.) Logistics data (e.g., COMPASS, CASA, PowerLOG in native or XML/CSV format or other file endings that apply.)
The following sections identify recommended CDRLs and DIDs the Program Manager shall consider in its GCS contract:
DISTRIBUTION STATEMENT A. Approved for public release, 10 February 2014. 14-S-0918 Appendix C-1