The use of functional size measurement(FSM) methods in software development organizations is growing during the years. Also, object oriented(OO) techniques have become quite a standard to design the software and, in p...The use of functional size measurement(FSM) methods in software development organizations is growing during the years. Also, object oriented(OO) techniques have become quite a standard to design the software and, in particular, Use Cases is one of the most used techniques to specify functional requirements. Main FSM methods do not include specific rules to measure the software functionality from its Use Cases analysis. To deal with this issue some other methods like Kramer's functional measurement method have been developed. Therefore, one of the main issues for those organizations willing to use OO functional measurement method in order to facilitate the use cases count procedure is how to convert their portfolio functional size from the previously adopted FSM method towards the new method. The objective of this research is to find a statistical relationship for converting the software functional size units measured by the International Function Point Users Group(IFPUG) function point analysis(FPA) method into Kramer-Smith's use cases points(UCP) method and vice versa. Methodologies for a correct data gathering are proposed and results obtained are analyzed to draw the linear and non-linear equations for this correlation. Finally, a conversion factor and corresponding conversion intervals are given to establish the statistical relationship.展开更多
In the software engineering literature, it is commonly believed that economies of scale do not occur in case of software Development and Enhancement Projects （D＆EP）. Their per-unit cost does not decrease but increa...In the software engineering literature, it is commonly believed that economies of scale do not occur in case of software Development and Enhancement Projects （D＆EP）. Their per-unit cost does not decrease but increase with the growth of such projects product size. Thus this is diseconomies of scale that occur in them. The significance of this phenomenon results from the fact that it is commonly considered to be one of the fundamental objective causes of their low effectiveness. This is of particular significance with regard to Business Software Systems （BSS） D＆EP characterized by exceptionally low effectiveness comparing to other software D＆EP. Thus the paper aims at answering the following two questions： （1） Do economies of scale really not occur in BSS D＆EP？ （2） If economies of scale may occur in BSS D＆EP, what factors are then promoting them？ These issues classify into economics problems of software engineering research and practice.展开更多
文摘The use of functional size measurement(FSM) methods in software development organizations is growing during the years. Also, object oriented(OO) techniques have become quite a standard to design the software and, in particular, Use Cases is one of the most used techniques to specify functional requirements. Main FSM methods do not include specific rules to measure the software functionality from its Use Cases analysis. To deal with this issue some other methods like Kramer's functional measurement method have been developed. Therefore, one of the main issues for those organizations willing to use OO functional measurement method in order to facilitate the use cases count procedure is how to convert their portfolio functional size from the previously adopted FSM method towards the new method. The objective of this research is to find a statistical relationship for converting the software functional size units measured by the International Function Point Users Group(IFPUG) function point analysis(FPA) method into Kramer-Smith's use cases points(UCP) method and vice versa. Methodologies for a correct data gathering are proposed and results obtained are analyzed to draw the linear and non-linear equations for this correlation. Finally, a conversion factor and corresponding conversion intervals are given to establish the statistical relationship.
文摘In the software engineering literature, it is commonly believed that economies of scale do not occur in case of software Development and Enhancement Projects （D＆EP）. Their per-unit cost does not decrease but increase with the growth of such projects product size. Thus this is diseconomies of scale that occur in them. The significance of this phenomenon results from the fact that it is commonly considered to be one of the fundamental objective causes of their low effectiveness. This is of particular significance with regard to Business Software Systems （BSS） D＆EP characterized by exceptionally low effectiveness comparing to other software D＆EP. Thus the paper aims at answering the following two questions： （1） Do economies of scale really not occur in BSS D＆EP？ （2） If economies of scale may occur in BSS D＆EP, what factors are then promoting them？ These issues classify into economics problems of software engineering research and practice.
