This short paper examines a high-level business case to to rebuild a Cobol legacy application in Java. ISBSG Data, for similar Java projects, provides metrics for: cost, effort, maintenance and support. This information is used as the basis for the business case.
We examine number of COBOL Projects submitted to the ISBSG Repository, since the year 2000. The median Project Delivery Rates are compared to determine whether there has been an in increase in productivity for COBOL projects.
In this short paper, we explain the way ISBSG data can be used to contract application development teams based on output instead of the usual Time & Materials method.
Much has changed in the IT industry over 25 years. This presentation discusses the evolution of software measurement and the people and organizations that have contributed to ISBSG over this period.
It is believed that software maintenance activities represents somewhere between 65 and 85 percent of an application’s total ownership cost. This study focuses on ISBSG’s Maintenance and Support data. It identifies maintenance trends for various activities.
With agile, you choose to develop the functionality that provides the most value for the customer, post-development. What functionality does the customer receive and how can it be measured?
One of the biggest problems in software development is the quality assurance of the delivered product. This depends directly on the testing process used. See how to improve testing processes with the use of market data.
“Low Code/No Code” is a new development paradigm. It shortens re-development times (and costs) when an organization decides to move software system/application from old, legacy architecture to a newer, more maintainable one.