by PRICE Systems
| January 22, 2015
Over the past several weeks several users have inquired about the best way to estimate costs associated with porting existing software to a new hardware environment. Normally for this situation some of the existing software will require some amount of adaptation to operate on a new server. However, a large portion of the existing software will only require integration into the new environment.
Estimating software costs associated with the above will require the use of several cost objects:
- Systems cost object if program management, Quality Assurance, configuration, and documentation costs are to be included in the estimate
- Assembly cost object to estimate integration costs
- Software component cost object to estimate software adaptation costs
- Software COTS cost object to model all existing software requiring only integration effort
The main input parameter that should be reviewed with care in the system cost object is project complexity. The default value for this input is nominal. Recommend the low value be reviewed since the team size will be small.
The main input parameter that should be reviewed with care in the assembly cost object is system complexity. If the software is just be ported to the new environment, recommend a low value be selected, since the requirements definition system design has been completed previously.
The software component input parameters will be treated in a normal fashion. All adapted software will be modeled as adapted new design, code and test.
The main input parameters that should be reviewed with care in the software COTS cost object are software size, integration team maturity, and external integration. This cost object should be used for all software that will only be integrated in the new environment. Functional size should be used if the size is unknown. The input parameters for integration maturity and external integration must be reduced. The recommended value is 0.05, which is the lowest value accepted by the model. This value will account for much lower integration activity for the existing software.
If you have any further questions, please contact a PRICE Systems Support.
Solutions Architect, PRICE Systems