The value of using established technology frameworks is proven. By adopting a software component for which many are skilled and experienced, it is easier for developers and IT managers to maintain a lingua franca.
While you’re reading this article, if you come across words – and even sentences – that you don’t understand, there’s a high chance you feel like developers do when they’re looking at lines of code with a high level of nested complexity. A high level of software complexity can make it difficult to determine architectural hotspots where risk and cost emanate.
On April 6th, CAST held a user group meeting on the topic of function point analysis and software productivity measurement. The meeting gathered more than 20 software measurement professionals from major companies in the banking, IT consulting, telecom, aviation and public sectors for a two-hour working session to discuss the benefits of function point analysis testing.
The event featured presentations including:
An IBM case study on how they worked with CAST to integrate and secure an Automated Function Point (AFP) approach with a big player in the aeronautic sector within TMA Systems
Functional sizing case study
Updates on the new CISQ standards for Automated Function Points
The importance of internal and external benchmarking
As Larry Quinlan, Global CIO, Deloitte Touche Tohmatsu Limited explains, “CIOs need the courage to make the investments that reduce technical debt — and the knowledge and the team to know where and when to make those investments.”
Yet, despite the advances that give IT management proper visibility into the cost and quality of their application development, one issue still remains unresolved: accurate technical debt estimation. The issue resides in how technical debt is calculated and communicated to management.