View in EDS PDF Full Text

Function-point analysis using design specifications based on the Unified Modelling Language.

Saved in:
Bibliographic Details
Title: Function-point analysis using design specifications based on the Unified Modelling Language.
Authors: Uemura, Takuya1 uemura@ics.es.osaka-u.ac.jp, Kusumoto, Shinji1 kusumoto@ics.es.osaka-u.ac.jp, Inoue, Katsuro1 inoue@ics.es.osaka-u.ac.jp
Source: Journal of Software Maintenance & Evolution: Research & Practice. Jul2001, Vol. 13 Issue 4, p223-243. 21p. 10 Diagrams, 7 Charts.
Subjects: Function point analysis, Software productivity measurement, Computer software, Software measurement, Software engineering
Abstract: Function-point analysis was introduced to help measure the functionality of software systems. For more than a decade, function points have been widely used to measure the size of information systems, often as a part of estimating the effort required for software development and maintenance processes. Limiting the use of function point measurement have been concerns about variable judgements on the part of the personnel doing the measurement, yielding differences in function-point measures for the same software product even in the same organization. Also, if an organization tries to introduce function-point analysis, the process normally starts with measurements from the organization's own past software products--a time consuming task with start-up costs. In this paper, we propose detailed function-point analysis measurement rules using design specifications based on the Unified Modelling Language and describe a function-point measurement tool, whose inputs are design specifications developed on Rational Rose ®. Then in this paper, we report tool validation work on software involved in software evolution at an organization where we have applied the tool to actual design specifications and examined the differences between the function point values obtained by the tool and those of an experienced function point measurement specialist at the organization. [ABSTRACT FROM AUTHOR]
Copyright of Journal of Software Maintenance & Evolution: Research & Practice is the property of Wiley-Blackwell and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
Description
Abstract:Function-point analysis was introduced to help measure the functionality of software systems. For more than a decade, function points have been widely used to measure the size of information systems, often as a part of estimating the effort required for software development and maintenance processes. Limiting the use of function point measurement have been concerns about variable judgements on the part of the personnel doing the measurement, yielding differences in function-point measures for the same software product even in the same organization. Also, if an organization tries to introduce function-point analysis, the process normally starts with measurements from the organization's own past software products--a time consuming task with start-up costs. In this paper, we propose detailed function-point analysis measurement rules using design specifications based on the Unified Modelling Language and describe a function-point measurement tool, whose inputs are design specifications developed on Rational Rose ®. Then in this paper, we report tool validation work on software involved in software evolution at an organization where we have applied the tool to actual design specifications and examined the differences between the function point values obtained by the tool and those of an experienced function point measurement specialist at the organization. [ABSTRACT FROM AUTHOR]
ISSN:1532060X
DOI:10.1002/smr.231