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:
- Cocoon - $287,750
- MyFaces - not listed
- Struts - $490,040
- Spring - not listed (add to index form - I'd do it, but I'm not a developer on the project)
- Tapestry - $278,185
- WebWork - $109,025
- Ruby on Rails - $181,985
Are these costs accurate? Probably not, but it's still an interesting indicator.
Posted by vanto on June 20, 2005 at 04:34 PM MDT #
Posted by Ahmed Mohombe on June 20, 2005 at 05:41 PM MDT #
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 06:07 PM MDT #
Posted by Dan Allen on June 20, 2005 at 06:47 PM MDT #
Posted by 64.170.69.114 on June 20, 2005 at 09:10 PM MDT #
Posted by Mike March on June 21, 2005 at 06:20 AM MDT #
Posted by 203.126.136.223 on June 23, 2005 at 08:02 AM MDT #