Matt RaibleMatt Raible is a Web Developer and Java Champion. Connect with him on LinkedIn.

The Angular Mini-Book The Angular Mini-Book is a guide to getting started with Angular. You'll learn how to develop a bare-bones application, test it, and deploy it. Then you'll move on to adding Bootstrap, Angular Material, continuous integration, and authentication.

Spring Boot is a popular framework for building REST APIs. You'll learn how to integrate Angular with Spring Boot and use security best practices like HTTPS and a content security policy.

For book updates, follow @angular_book on Twitter.

The JHipster Mini-Book The JHipster Mini-Book is a guide to getting started with hip technologies today: Angular, Bootstrap, and Spring Boot. All of these frameworks are wrapped up in an easy-to-use project called JHipster.

This book shows you how to build an app with JHipster, and guides you through the plethora of tools, techniques and options you can use. Furthermore, it explains the UI and API building blocks so you understand the underpinnings of your great application.

For book updates, follow @jhipster-book on Twitter.

10+ YEARS


Over 10 years ago, I wrote my first blog post. Since then, I've authored books, had kids, traveled the world, found Trish and blogged about it all.

RECENT ENTRIES


Tag Cloud


abbie appfuse birthday denver family grails gwt jack java javascript jsf linkedin maven montana roller skiing softwaresummit spring springmvc struts2 travel trish vacation webframeworks wicket
« HowTo set the defaul... | Main | Bike to Work Day »
Monday June 20, 2005

AppFuse cost $78K to develop

I somehow stumbled upon Koders.com this morning, where they have a cost-of-development based on LOC in the project's CVS repository. Apparently, AppFuse has cost around $78K to develop. Here are a few other project costs I discovered:

Are these costs accurate? Probably not, but it's still an interesting indicator.

Posted in Java at Jun 20 2005, 09:20:53 AM MDT 7 Comments
Comments:

The estimation is probably done by Cocomo II. It was firstly published by Barry Boehm (you know...) and shall allow one to estimate the cost, effort, and schedule when planning a new software development activity. http://sunset.usc.edu/research/COCOMOII/

Posted by vanto on June 20, 2005 at 10:34 AM MDT #

These costs are totaly random and have nothing to do with the reality. If there were that easy to evaluate costs, than our life would be much easier and most of developers would have no deadline problems, cause an LOC estimation could always be done :).

Posted by Ahmed Mohombe on June 20, 2005 at 11:41 AM MDT #

Hi There,

An excerpt from the interview(http://www.vanwardtechnologies.com/bsletten01print.html) with an expert on USEFUL software code metrics.

=============================
Vanward: Yeah, I agree. I think past abuses are hard to forget. Lines of code doesn't equal productivity! Are there particular metrics you've found useful? Conversely, which ones do you find are useless?

Brian: I think a lot of metrics are useful depending on what your goals are. If you are trying to predict failure, the only metrics that seem to correlate even remotely are complexity, coupling and length of methods/classes. If you are trying to make software easier to maintain there are a ton of metrics that can be useful.

Robert Martin's metrics are useful for managing dependencies and validating that your class categories are appropriately decomposed on package boundaries. Cyclomatic complexity is great for identifying code for refactoring, adjusting your LOE guesstimates and determining how sufficient your test coverage is. Identifying violations of the Law of Demeter helps find unnecessary structural coupling between modules. Depth of inheritance is a reasonable measure of the cognitive load a developer needs to page in and the potential for conceptual entropy in the class decomposition.

As far as metrics that are useless, I've never found number of children (NOC) to make that much of a difference. SLOC is the most misused metric. I understand the desire for managers to be able to measure productivity, but SLOC basically measures typing volume. It doesn't factor in reuse, defects or design quality.
=============================
BR,
~A

Posted by Anjan Bacchu on June 20, 2005 at 12:07 PM MDT #

While I agree these statistics are completely subjective, it is interesting to see the estimated cost of Eclipse, which is more than 11 million! Wow! I certainly do hope that it lives up to its investment.

Posted by Dan Allen on June 20, 2005 at 12:47 PM MDT #

I wonder if the 78k is an accurate measure of how much is saved per project by using appfuse.

Posted by 64.170.69.114 on June 20, 2005 at 03:10 PM MDT #

Rails actually cost much less. It was developed as a side effect of the Basecamp project so it was relatively cheap and I think the investition has returned very quicky. Not mention thousand of people all over the world rescued by Rails from the messy overcomplicated java world. They are very happy people now and are making a great stressless Rails community. But it's good for you that you are still well paid for doing your job and there are people who like watching your shows. Take care. Mike

Posted by Mike March on June 21, 2005 at 12:20 AM MDT #

Hight time they outsource open source work to india. They could have finished POI for much less than $100K compared to $550K+ :D

Posted by 203.126.136.223 on June 23, 2005 at 02:02 AM MDT #

Post a Comment:
  • HTML Syntax: Allowed