Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Let me pull out my handy copy of Software Estimation by, of course, Steve McConnell. On page 67 he has a nice chart of the average impact of different ratings factors on the development of a 100,000 line of code project. Their factors do not map directly to your list, but here is my best attempt to map it.
    1. Good documentation. This reflects the Requirements Analyst Capability, which has an impact factor of 2.00.
    2. Coding skills of team members. Maps to Programmer Capability (General), a factor of 1.76.
    3. Choice of framework or tools (aside from language). Closest choice is Use of Software Tools which has an impact of 1.50. Note that experience with your tools also has an impact of 1.43.
    4. Quality of project management. Maps best to Process Maturity, which has a factor of 1.43.
    5. Clean, well-organized code. Maps best to Developed for Reuse which has an impact of 1.31. Note that this is the impact on development time. No estimate is available on the impact on maintenance (which is what you really wanted to know).
    I couldn't find a good mapping in that table for the following factors:
    • Good (and plentiful) hardware.
    • Choice of implementation language.
    • Non-rushed deadline.
    • Automated tests.
    I put those in the order that I'd personally value them at for a smallish project.