How Software Can Improve with Automated Software Analysis and Measurement: IV Edition CIO Conference

On May 13th, a group of IT executives highlighted the importance of these software analysis and measurement in order to maintain software quality standards and to uphold a healthy and efficient relationship with business stakeholders and application service providers.

Summary of the 2015 International Function Point User Group Conference (IFPUG) & International Software Measurement & Analysis Conference (ISMA10)

From SNAP to Automated Function Points – Creating Value from Measurement
Infographic from “Enabling Enterprise Productivity Measurement by Combining Manual and Automated Functional Sizing”
CAST sponsored the 2015 International Software Measurement & Analysis Conference (ISMA10) held in Charlotte, on April 30th.  This conference, hosted by the International Function Point User Group (IFPUG), brings software measurement professionals from Europe, North America, and South America to exchange software measurement and function point expertise and to network.  The conference was attended by more than 50 software measurement professional and certified function point counters from across the global.  The full day event featured presentations including:

What Does Software Size Have to Do with It?

As the impact computers have on our lives increases at an unprecedented rate, software systems are becoming increasingly complex. For example, a pacemaker has less than 100,000 lines of code written into it. A F-35 Fighter jet has about 250,000 lines. Facebook on the other hand has upwards of 600,000. Now what about that fancy new Lexus you just purchased? That has about a million lines of code. As the applications that make up these various systems are becoming more and more integrated and intricate, it is crucial for those in application development to take a multifaceted approach to developing their technologies and measuring their software size.

Function Points — A Primer

This post covers function points in general and then takes a deeper dive into the CAST approach to automated function point counting.

1. What is a Function Point?
2. How are function points used?
3. What is a CAST-Computed Function Point?
4. How does CAST’s automated approach to counting function points compare with IFPUG’s manual approach?
5. Which approach is better? Which one should I use?
6. When should I use CAST-computed function points?
7. Can CAST-Computed Function Points be used for benchmarking?
8. Can CAST-Computed Function Points be used to measure productivity?
9. How can CAST’s automated function point counts inform key management decisions?
10. What steps can I take today to improve my organization’s productivity?
11. Where can I get more information?

A function point, first defined by Allen Albrecht of IBM in 1979, is a measure of the amount of functionality in a software application. While Albrecht defines the attributes of functionality, his definition does not specify a particular method or process for measuring these attributes. Hence, two function point counts may differ because they follow different procedures for measuring or summing the constituents of functionality (the attributes) to come up with a total count of function points.