Attachment_2_DBD_CCDR_RFP_Data_Request.xlsx

Guide

COLOR KEY / TABS

Input Expand WBS as necessary and specify Hardware Modules or CSCIs as required for the proposed program

Traceability Matrix Identify BOE # and WBS reporting element mappings/definitions

SEPM Hours by Month Provide proposed SEPM by month. Make the necessary adjustments to column B to align with the POP timeline.

SLOC Provide the software SLOC and hours for the proposed CSCI's

Module Design Provide the details related to the modules that will change or be re-designed

These WBS reporting elements do not align directly with the CSDR format. The reporting elements have been adjusted to collect the necessary information needed to evaluate the proposal.

Input

Traceability Matrix

CCDR Summary

(all customers for this Item)

ELEMENT

CODE WBS REPORTING ELEMENTS NUMBER OF

UNITS AT

FEE Reporting Contractor Profit/Loss or Fee

Total Price $0.0

22. REMARKS

Labor Hours Table

WBS

ELEMENT

SEPM Hours by Month

Proposed

SLOC

In attempt to compare the software hours to NAVAIR datasets we want to ensure we are making comparisons accurately. Please identify any hours associated with NAVAIR software elements (listed below) that are captured elsewhere in the proposal if not included within the Software hours line.

NAVAIR datasets include the following elements:

Elements not included in NAVAIR datasets :

Jennifer.Meredith: Jennifer.Meredith:

Instructions Enter the logical Source Lines of Code (SLOC)

New - This is the amount of new code defined for the CSCI.

Mod – This is the amount of modified code defined for the CSCI.

Reuse – This is the amount of reuse code defined for the CSCI. Reuse code is different from Commercial Off-The-Shelf (COTS) code. Reuse typically comes from a previous weapon system development with limited applicability to a broad spectrum of users. The goal is to use the code without modification, however it must be retested in the new application environment. Frequently there will be some minor redesign and recode required to make the reuse code function in the new environment.

COTS – This is the amount of COTS code defined for the CSCI. COTS is not meant to cover things like the size of an Operating System (like Linux or MS-DOS). Rather it is applications software that meets a functional need of the program. For our purposes this is considered unmodified COTS. Any COTS that requires “tweaking” or modification is not COTS and should be treated as reuse or modified depending on the amount of modification required.

i.e., ADA, Assembly, C, C++, COBOL, Fortran, etc Mod Design % - This factor should reflect the amount of redesign that needs to take place for the code to be modified relative to designing it new. Note that this is effort and not lines of code. The amount of design effort required is often disproportionately higher than the amount of effort to recode the software. This is driven by unfamiliarity with the modified code, quality of the donor code, and how closely the new requirements match the original codes functionality.

Mod Code % - This factor reflects the amount of effort required to code the modified software relative to writing it as new. Frequently the amount of recoding required is higher, sometimes much higher, than the redesign %.

Reuse Design % - This factor reflects the amount of effort the design community will spend familiarizing themselves with the reuse code relative to having designed it new. Even code that will be completely untouched requires design effort to research and validate the code application.

Reuse Code % - This factor reflects the amount of effort required to code the reused software relative to writing it as new. It is rare that code can be truly reused without some minor coding effort.

Design % - This factor should reflect the amount of effort that needs to take place for the code to be designed/redesigned.

Code % - This factor reflects the amount of effort required to code the software.

Test % - This factor reflects the amount of effort required to test/retest the software. Simple - Code that performs easily tested functions, has generally linear inputs and outputs, i.e. linear domain & range relationships, single SW & hardware relationship, and performs simplistic data management functions like look up tables or library functions. The main difference between simple and routine code is the relative degree of testing required to determine code functionality. Simple code can consist of simulation, maintenance, data handling, or human interface components.

Routine - Code that has multiple input and output paths requiring a moderate degree of testing to certify functionality, maybe newly written or adaption of existing code from other DOD programs and generally performs non real time, non algorithm intense functions like simulation, tools, maintenance, Graphical User Interface (GUI) or data handling. Code is rarely constrained by the operating environment.

Complex - Code that has a very high number of input and output paths making it very difficult to test, may perform real time mathematical intense functions, maybe constrained by the operating environment, maybe written in a highly secure environment, or involves new or novel algorithms or applications. Complex code tends to be found in functions that emulate or interface with the physical world, i.e. radar signal processing, missile detection, data links protocol implementation, and electronic warfare. Human interface is infrequent with this type of code. Key to identifying complex code is the difficulty in verifying and validating the code in a laboratory environment. This should be the total Software hours proposed as compared to NAVAIR datasets for an apples to apples comparison.

Module Design

Vendor List Summary

$ - 0

BOM Example CLIN SOW Paragraph WBS Part Number Description EST Method Bullard, Michelle A CIV NAVAIR 4.2: Estimating Method used -

For example:

- Quote (Q)

- Purchase Order (PO)

- Estimate (E)

- Long Term Agreement (LTA) Validity Date / Expiration Date Bullard, Michelle A CIV NAVAIR 4.2:

When do quotes/LTAs expire?

If Estimating Method was PO history, what was the date the part was procured? Supplier Name Qty Unit Cost Extended Escalation Factor Bullard, Michelle A CIV NAVAIR 4.2: