![calculate kloc cocomo model calculate kloc cocomo model](https://media.cheggcdn.com/study/00b/00bd765a-8150-4c50-8a50-c4abe648dbe3/2009616637526338073107254325009716.png)
- #Calculate kloc cocomo model how to
- #Calculate kloc cocomo model software
- #Calculate kloc cocomo model code
#Calculate kloc cocomo model software
The size of a software program by counting the number of lines in the
#Calculate kloc cocomo model code
Source lines of code (SLOC or LOC) is a software metric used to measure No way to know now but to get back to work.Source lines of code (LOC, SLOC, KLOC, LLOC) So how much was the discount on the actual cost and how much is technical debt? The latest project costs are now at $ 31,000/. The project has taken Time, Te = 36 months, then the team will be:Įxpected Budget cost for the 36 months with the mid-level developers in Kenya: The algorithm that is used to calculate Person-Months is:ĭevelopment Time (Td) = c(Effort Applied) d The coefficients in the equation and my lines of code are:Ĭoefficients a = 2.4, b = 1.05, c = 2.5, d = 0.38 This is a model of “small” teams with “good” experience working with “less than rigid” requirements. I found that this is a relatively well known model and I went down a rabbit whole as I tried to get a sense of what this project should have cost in terms of “Person-Months”.įinally, considering the type of team size we were, the project fell into the “Organic” model. For software development, the tried and tested system for doing this is the COCOMO - Constructive Cost Model. This answer on Quora was very close to my own experiences with web development projects. So I combed the Web.įirst, I found an answer to figuring out how big my project was. But the time period for development is crucial.
![calculate kloc cocomo model calculate kloc cocomo model](https://miro.medium.com/max/1118/1*8sh29GeO5z_b_mduRcHgUQ.png)
What the price of an hour costs is secondary since this would be figured out at the team needed was being put together.
#Calculate kloc cocomo model how to
I needed to figure out how to really estimate how much time is needed for the next web app development in terms of “person-hours” or “person-months”. I had a bigger concern now that projects of these size should be expected. Some documentation had been done but with tests, documentation would be far better. So here I was and I needed to write tests. That was three years ago and I made a decision build projects while doing testing properly.
![calculate kloc cocomo model calculate kloc cocomo model](https://image.slidesharecdn.com/cocomomodel-130715000002-phpapp01/95/cocomo-model-12-638.jpg)
Imagine some hot-shot developer/recruiter/prospective client looking at the GitHub repository of code and the elementary stuff had not been done. I was responsible of most of the backend code base, so the tech debt was mine to pay. I did not document the code as much as I thought I would. Later on, the project needed to be “open sourced” and everything now had to be up to global standards. Tests are almost always the first casualty. Why was I doing this? The project was underfunded and we, when laying out the project plan had to remove some items to stay within the budget we had set out. In fact, I had convinced myself that what I needed more than tests was well documented code. But in this project, deferred payments, favours and feature creep made the project grow out of hand. Normally, writing tests for a trivial, tiny app (≤ 5000 lines) can be deemed time consuming since most of the code can be in the developer’s head. The project was built out in 4 months and has undergone maintenance and a number of sprints over three years. I have been part of a medium sized Django project (~ 35,000 line of code and counting) of the custom code we built for the platform without writing tests for the modular apps.