How Galorath Made Use Case Points Viable For Accurate Estimating
Use case points provide a measure of size based on Use Cases, a natural artifact of the software process. The original concept was developed by Objectory AB (now part of IBM Rational Software.) There have been many detractors of use case points including Rational Software itself and USC. The Galorath team approached Use Case estimating with a number of approaches. Lee Fischman, who led the project came up with the concept of Normalized Use Cases (NUCs), a new metric based on Use Case Points He also had Galorath’s Dr. Tarbet set off to create better results from Use Case Points. Use Case Points are based on:
- Based on the number of actors and transaction for each case.
- Categorization into simple, medium and difficult.
- Linear combination of weighted counts
When Dr. Tarbet finished his analysis he obtained an Adjusted Correlation Coefficient (R2 ) = 0.984802, showing an exceptional value to the enhanced Use Case Point method.
Counting XML Source Lines of Code
A customer recently asked how to count XML for their software sizing activity. Turned out the question was more detailed than just the syntax. They really wanted to know IF they should count XML and, if using lines of code, if they should adjust the XML lines. They pointed out that many of their projects include up to 25% XML lines.
The bottom line is that XML while it has no procedural statements (it is a data declaration language) can require significant effort in software development and should be counted. SEER users can use the code generation knowledge base in a component for XML… Also, due to syntax and if not using the code generation kbase , it is appropriate to adjust the XLM lines…. For Galorath research an XML line is about .29 SLOC.
Counting XML
XML is interesting to count since an XML document generally doesn’t actually do anything… that is, XML does not include procedural code. XML is pure declarations wrapped in tags. There is an if statement that can change the value of an element, not program logic. XML Separates Data from HTML. With XML, data can be stored in separate XML files so you can concentrate on using HTML for layout and display and ensure changes in the underlying data will not require any changes to the HTML.
The following are the generic logical source line counting rules:
Costs & Benefits of Software Quality
Rick Spiewak from The MITRE Corporation and Karen McRitchie, Galorath VP of development published a paper in the Crosstalk journal showing how increasing quality using basic quality principals during software development can reduce costs while also reducing defects. The abstract follows:
“Software can be considered a product whose production is fundamentally similar to other products. Improving the quality of software can be approached using the same basic principles espoused by quality pioneers such as W. Edwards Deming, Philip B. Crosby and Harold F. Dodge. These principles can form a practical framework for ensuring that appropriate requirements are set for software development projects. By connecting established software engineering practices to the objective of defect prevention, we can apply the principles of quality management to software development. Using modeling techniques, it is possible to predict the potential cost savings and defect reduction expected”.
Process Compliance Saves 15% of Development or Maintenance Costs
I had the opportunity to hear a brief on Computer Aid’s Tracer software and methodology. Tracer, when applied as recommended by CAI details all the process steps needed to accomplish every task and allows software personnel to entry time directly into the system as well as check off tasks completed. Tracer then show them what it takes to be compliant with processes. I believe if people started using something like Tracer they could actually get their CMMI type processes working and could achieve the 15 or more percent savings that Computer Aid themselves achieve. Amazing…. Simply by doing processes rather than giving them lip service: big savings and more successful projects. Applying Tracer to software projects can mitigate the issues of CMMI compliance. Of course CAI points out this doesn’t have to be CMMI.
Estimating Web Effort / Schedule
Reading an article for IEEE on Web effort estimation reminded me of how SEER estimates web page development projects using either traditional line of code inputs, functional inputs, or web pages. Of course any implementation methods can be handled, anything from HTML to java to C# to a content management system.
Of course reuse, security and other people, process and technology items are factored into the estimate.
Some people don’t believe it is necessary to estimate web developments. I shutter to think that all this effort is expended without an estimate or plan.
Make or Break: Why Accurate Cost Estimation Is Key
A recent article from executivebrief.com sent to me By Dr. Ricardo Valerdi of MIT discusses how the accuracy of the cost estimation process can make or break a project’s success.
“When it comes to controlling costs, it is a critical first step to make appropriate estimations at the outset of a project. Being able to control costs is largely a matter of adhering to established guidelines, oftentimes by learning from previous projects and reacting to current circumstances efficiently and effectively.”
It is amazing to me how simple this concept is, yet how many CEO’s don’t even know it is possible. Accurate estimates (of course with risk and uncertainty factored in) yield viable project plans which can then be successfully monitored and controlled. In fact the application of techniques such as earned value management, as powerful as they are, crumble when the baseline plan is unachievable.
The Danger of “Don’t Bring Me Problems, Bring Me Solutions”
I recall working for a manager who always said “don’t bring me problems, bring me solutions. I think his intent was to stop whining and get people working on problem solving before bringing the problem up. But I always thought it was counterproductive….. If I had a problem I might or I might not have a solution.. And I might need collaboration or leadership to obtain one. This Harvard Business Review article substantiated my long time concern over that management style.
“Instead of promoting accountability, it actually encourages employees to turn a blind eye to problems they see but cannot figure out how to fix. When you say “Don’t bring me problems—bring me solutions,” what you’re saying, in effect, is “Of all the problems you find, I only want to know about the ones you can solve.”
Identifying problems can be a solo sport, but finding solutions rarely is. This is especially true when the problems have any degree of complexity. If you’re giving people permission to tell you about just those problems they can solve, you’re missing out on many opportunities for improvement. You’re leaving performance boosters on the table simply because the problem and the solution aren’t collocated.”
Thank you HBR.
Of course in project estimation, planning and control part of the art is to identify both problems and solutions while bounding risk and uncertainty. That is part of the goal of the 10 step process.
SEER for Hardware, Electronics & Systems Can Control Cost Risk of ASICs
I have been pleased with the performance of the detailed IC estimation option in SEER for Hardware Electronics and Systems. Further I am excited that we have a customer providing a webinar in how to apply SEER-IC to costly military communications systems.
Today’s military communication systems are playing an ever expanding critical role in our domestic security as well as the security of our assets abroad. Satellites that are the core of these communication systems are being required to do more complex functions and perform them faster than ever before. To accomplish complex on-orbit tasks, modern space electronics are using advanced micro-electronics in their unit designs. The rapidly changing field of advanced micro-electronics, largely developed by commercial industry, presents a problem for the cost estimator. Common cost estimating techniques using historical data or cost estimating relationships based on historical data are not well suited to address the complexity of today’s electronic devices. . SEER for Hardware-Integrated Circuits Option parametric cost estimating model is being used to develop a cost estimate for ASICs, and what future estimating challenges may be on military space communication satellites.
If you are interested the webinar registration is here.
Typical Percentage Breakdown of Offshore Cost
Estimating offshoring is always interesting, especially when we have seen the the stronger dollar buy about 26% more in Indian currency over the past few months. But what do we get for the dollar. Offshoring is an important source of IT talent for the US.
I thought Don O’Neill’s breakdown of the cost of offshoring was interesting since is showed a similar distribution of costs from offshoring and organic development.
Software Estimation Much More Complicated Than Some Perceive
How many times have we been asked to submit a 5 minute or off the cuff estimate to stakeholders… Then be held to that estimate even though we missed the complexity in our haste.. Of course if we didn’t prepare an estimate until everything was known the estimate would be of little value. That is why uncertainty must be part of the process and off the cuff, manual estimations should be avoided when possible.
I thought these diagrams showing the perceived simplicity of the software estimation process versus complexities in the software cost estimation process were very interesting.
