Key Process Measurements

To ensure the effectiveness of our .NET COE and to be able to make continuous improvements, we measure key aspects of our process.

Productivity

We measure development and testing productivity. Our metric for development productivity is lines of code written per person per staff day. As a typical example, for a recent project on which we added features to an application, we averaged 80 to 85 non-commented lines of code (NCLOC) per staff day. Redevelopment time is generally 25% to 30% less than for a new project, thanks to savings at the requirements phase.

Estimation accuracy

A critical aspect of our ability to deliver projects on time and on budget is our ability to accurately estimate the code size of new projects. We begin with the size of the existing .NET modules, then estimate what would be needed to add the new features and functions. Our estimates always closely match the outcome.

Review effectiveness

We measure the effectiveness of our code reviews by counting the number of defects found during the software test phase. Our review process finds most of the coding bugs, saving development time fixing bugs at the test phase. Currently, our review effectiveness is 88%.

Delivered defect density

We use the internationally accepted standard of 0.5 defects per 1,000 NCLOC to measure our delivered defect density. Our applications consistently meet this standard.

you can visit our website www.hanusoftware.com for more information on .Net KPM's