If you’ve taken my Software Training class, you’ve heard me use the analogy of “taking someone else’s spreadsheet and adding your own logic” to distinguish between modifications, adapted code and glue code.  But let’s take a step back to make sure we’re all in agreement {if not, blame me not the product!}

#1.) To be clear, COTS is shrink-wrapped, ready-to-go with near-zero modification to core functionality.  Generally, we really prefer to see COTS modification no more than 10%.

#2.) If this latter core functionality needs modification, then we recommend using the SW Component object with Adapted code, as well as Reused code for the functionality not needing modification.

#3.) If the Adapted code is significant, consider using a second SW Component object with new code, to supplement the first’s New, Adapted and/or Reused code.

#4.) Finally {since I’ve shown this example in class}, if you are using repeating systems of assemblies and objects to represent succeeding phases (e.g., TD -> EMD -> Production), then per above, use software components to capture New, Adapted & Reused code, while using COTS for that functionality that experiences no modifications through the phases. 

Success can be accelerated by the PRICE® Predictive Cost Analytics (PCA) integration of business, engineering, and program management objectives in order to produce competitive solutions. 

TruePlanning immediately facilitates objective quantitative assessment of customer needs/
requirements, winning-business solutions, and project lifecycle cost management.

Contact me for a demonstration, either in person or via telecon. 

We’ve had many success stories here.  You can be next!