Source code based function point analysis for enhancement projects

Klusener, Steven

doi:10.1109/icsm.2003.1235445

Cited by 4 publications

(5 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…So, the Function-Points must be taken from the code. 69 To that end, the first author introduced mechanisms in his source parser for recognizing input, output, and data access operations. The complexity of these operations-whether low, medium, or high-depends on the complexity of the code module as a whole.…”

Section: Calculating Redevelopment Costs With Function-pointsmentioning

confidence: 99%

“…The counting rules suggested by this OMG standard are very close to those already used by the first author and others. 69 With a few minor adjustments, these rules could be incorporated into the existing tools. Thus, one might rightfully claim that the Function-Point count in this project was made in accordance with the just mentioned OMG Standard.…”

Section: Calculating Redevelopment Costs With Function-pointsmentioning

confidence: 99%

See 1 more Smart Citation

Cost‐driven software migration: An experience report

Sneed¹,

Verhoef

2020

J Software Evolu Process

View full text Add to dashboard Cite

Software migration projects are often bound either by time or cost or by both. If the project is bound by both time and cost, the user must sacrifice something else, usually the quality. The migration strategy depends on how the project is bound. Most migration projects are bound by time. The new system must be in operation by a given date, no matter what it costs. The project described here—a state employee payroll system—is bound by cost. It must remain within the budget, no matter how long it takes. The original costs were estimated based on the code size and the productivity measured in previous migration projects using three different approaches: conversion, redevelopment, and reimplementation. The conversion approach would have been the cheapest, but it had already been tried and failed. The redevelopment approach was considered to be out of the question due to the high costs. Thus, reimplementation remained as the only alternative. The costs of this approach were estimated using three different estimation methods and approved by the state government. The project has been in progress for 4 years, and until now, the estimated costs and actual costs are in the same order of magnitude: the costs have remained within budget. In fact, the costs are less than what was estimated with some methods. As this particular project is not bound by time, it is a good example of continuous migration.

show abstract

Section: Calculating Redevelopment Costs With Function-pointsmentioning

confidence: 99%

Section: Calculating Redevelopment Costs With Function-pointsmentioning

confidence: 99%

Cost‐driven software migration: An experience report

Sneed¹,

Verhoef

2020

J Software Evolu Process

View full text Add to dashboard Cite

show abstract

“…An example of a portfolio-wide analysis effort is an analysis to automatically count function points from the source code of an entire IT-portfolio [115]. This is a prerequisite to calculated decision-making regarding proposals for modifications that impact an entire IT-portfolio, as in our case.…”

Section: Related Workmentioning

confidence: 99%

Automated Mass Maintenance of Software Assets

Veerman

2007

11th European Conference on Software Maintenance and Reengineering (CSMR'07)

View full text Add to dashboard Cite

Verder wil ik in het kader van het CALCE-project graag de betrokken mensen van het Centrum voor Wiskunde en Informatica, van de Software Improvement Group, en van Getronics PinkRoccade hartelijk danken voor de samenwerking. De mensen die me bij een specifiek onderwerp geholpen hebben, heb ik bij het betreffende hoofdstuk vermeld. Tot slot wil ik mijn leescommissie danken voor hun inspanningen om dit proefschrift te lezen en beoordelen, en voor hun suggesties voor verbeteringen: prof.dr. M.G.J. van den Brand, dr. L. O'Brien, prof.dr. J. Ebert, prof.dr. W. Fokkink, en prof.dr. P. Klint.

show abstract

“…An example of a portfolio-wide analysis effort is an analysis to automatically count function points from the source code of an entire IT-portfolio [42]. This is a prerequisite to calculated decision-making regarding proposals for modifications that impact an entire IT-portfolio, as in our case.…”

Section: Introductionmentioning

confidence: 98%

Automated mass maintenance of a software portfolio

Veerman

2006

Science of Computer Programming

View full text Add to dashboard Cite

This is an experience report on automated mass maintenance of a large Cobol software portfolio. A company in the financial services and insurance industry upgraded their database system to a new version, affecting their entire software portfolio. The database system was accessed by the portfolio of 45 systems, totalling nearly 3000 programs and covering over 4 million lines of Cobol code. We upgraded the programs to the new database version using several automatic tools, and we performed an automated analysis supporting further manual modifications by the system experts. The automatic tools were built using a combination of lexical and syntactic technology, and they were deployed in a mass update factory to allow large-scale application to the software portfolio. The updated portfolio has been accepted and taken into production by the company, serving over 600 employees with the new database version. In this paper, we discuss the automated upgrade from problem statement to project costs.

show abstract

Source code based function point analysis for enhancement projects

Abstract: Abstract

Cited by 4 publications

References 8 publications

Cost‐driven software migration: An experience report

Cost‐driven software migration: An experience report

Automated Mass Maintenance of Software Assets

Automated mass maintenance of a software portfolio

Contact Info

Product

Resources

About