![cocomo model implementation cocomo model implementation](https://i.ytimg.com/vi/XYoiYFz-o6s/sddefault.jpg)
I'm wondering if I should apply a twiddle factor to the LLOC input - I know people do something like this for some languages when using LOC (eg: dividing Python LOC by a factor of 6). Unlike other Estimation models, COCOMO is a necessary model.
Cocomo model implementation software#
This seems high to me - is it actually? I don't think I have the experience to know for sure. COCOMO cost estimation model will be used by thousands of software project managers, along with hundreds of software project. Using these numbers, COCOMO II gives me something like 30 man-months of effort. In two new model structures to estimate the effort required for software projects using Genetic Algorithms (GAs) were proposed as a modification to the famous Constructive Cost Model (COCOMO).
![cocomo model implementation cocomo model implementation](https://cdn.educba.com/academy/wp-content/uploads/2020/03/COCOMO-Model.jpg)
Under one strategy, I estimate somewhere around 10% of the 165k LLOC project will need to be rewritten, and about 5% of the remainder will undergo significant modification. COCOMO (Constructive Cost Model) is a model that allows software project managers to estimate project cost and duration.
![cocomo model implementation cocomo model implementation](https://alaahamed.files.wordpress.com/2010/11/6.png)
Both COCOMO 81 (except the Basic model) and COCOMO II use cost drivers. In either case, not all 1,000 function point applications would be expected to require the same effort and schedule to implement. The book is accompanied with a CD that contains the USC implementation of the COCOMO model and some instructional videos.
Cocomo model implementation code#
I have used USC's Unified Code Count tool to determine the Logical Lines of Code (LLOC) in the project as a whole and in specific assemblies of interest. (Not Basic COCOMO 81 but the other models did.) They were similar but the COCOMO II versions were more refined. The model can accept estimates of either logical lines of code or function points as the primary input parameter. However, I'm having trouble deciding on numbers for the SLOC (source lines of code) input. It appears people seem to like the COCOMO II for this type of task. Unlike other cost estimation models, COCOMO is an open model, so all of the details are published, including: The underlying cost estimation equations. I would now like to develop a time estimate for implementation of those changes. The COCOMO cost estimation model is used by thousands of software project managers, and is based on a study of hundreds of software projects. From this, I've cultivated some (very rough) estimates on what percentage of each assembly will need to be rewritten. I've already conducted an analysis to identify the native libraries that will need to be ported or replaced with managed code, and identified the Windows-only API calls for which equivalents on Linux/OS X will need to be found. I've been asked to determine the feasibility of migrating an existing Windows-only C# software package to Mono. I'm a student currently on an internship.