Measuring the Function Points for Migration Project: A Case Study

Function Point Analysis is a software measurement technique which is gaining wider diffusion all over the world even if some experts pointed out various problems affecting it. The present paper describes a new technique for Function Points estimation (Early and Extended Function Points Method) with the objective to solve some of these problems. The use of the proposed estimation technique allows: • To anticipate, in the life-cycle of a software project, the determination of the number of Function Points (FP) to be developed or maintained; • To highly reduce time and cost in the formulation of the measurement usually required by a detailed evaluation;

Software cost estimation is the one of the most desired capability in software development. It helps customer to make investment but also helps to project manager to making appropriate plans for development. It is recognized that current estimation techniques does not cover estimation for expert user programming. We have proposed a new general system characteristic "Expert user Programming". Expert user programming also affects the size of a software. By adding it in the list of general System characteristics, we have created a provision for taking expert user facilities into account, while estimating the size of a project. After adding this General System Characteristic-Size, Time, effort will be increased. Hence to estimate these things, We have used this new GSC for expert user programming. It will help to software developers to create information systems which can be helpful for technically inexperienced users. This paper has include Expert User Programming as new General System Characteristic which will give accurate result of function Point Analysis.

Since the introduction of object-oriented (OO) development in industrial practice, many Function Point (FP) technique adaptations have been introduced to improve software size estimation in these kinds of projects. Current research work only deal with OO modifications to the previous version of the FP Counting Practices Manual (4.1). In this paper, we propose the use of the composition relationship analysis in classes to improve the rules included in FP Counting Practices Manual 4.2.1 for Internal Logic Files (ILF) and External Interface Files (EIF) identification. We also show the results obtained by applying our proposal in six case studies performed by practitioners and comparing against the results we obtained with undergraduate students. These results have proved to be at least equal in accuracy and consistency to the original FPA technique.

Information and Software Technology, 2005

A systematic approach to software size estimation is important for accurate project planning. In this paper, we will propose the unified mapping of UML models into function points. The mapping is formally described to enable the automation of the counting procedure. Three estimation levels are defined that correspond to the different abstraction levels of the software system. The level of abstraction influences an estimate's accuracy. Our research, based on a small data set, proved that accuracy increases with each subsequent abstraction level. Changes to the FPA complexity tables for transactional functions will also be proposed in order to better quantify the characteristics of object-oriented software.

One of the key questions in software development is software size estimation. For systematic software size estimation, different methods are used, all of which have their roots in the Function Point Analysis (FPA) method. However, the elements and constructs of the FPA method are not directly applicable to object-oriented concepts: a mapping of object-oriented concepts to FPA elements is required. There are proposals for such mappings, but a serious calibration and validation process is required to ensure that the various parameters have been chosen in the most appropriate way. Such a validation implies the creation of effective product metrics working in environments like the industrial standard .NET platform. Since .NET is a typical multi-language environment, a product metric capturing all languages and producing comparable and accumulable results is hard and expensive to produce. Therefore we propose to solve the problem in the .NET Common Interface Language level: thus only one...

Early and accurate estimation of software size plays a crucial role in facilitating effort and cost estimation of software systems. One of the widely used methodologies for software size estimation is Function Point Analysis (FPA). Several approaches which adapt this methodology to Object Oriented (OO) Software have been proposed in the literature. However, these approaches lack clarity in providing precise directives for the identification of FPA components. Further, when a particular class is involved in multiple interactions such as aggregation, association and inheritance, its complexity calculation is ambiguous. In order to address these issues, this paper proposes a new and enhanced approach for OO software size estimation by providing rules that better guide the practitioners. This paper discusses a sample case study describing the applicability of the proposed approach. The developmental size predicted by applying the proposed approach for a set of sample projects correlates well with the size prediction obtained through the existing approaches. Thus, the proposed approach provides simple and unambiguous guidelines for the identification of FPA components as well as for the calculation of complexity due to each one of those components, without adversely affecting the accuracy of software size estimation.

1999

We present a method for estimating the size, and consequently effort and duration, of object oriented software development projects. Different estimates may be made in different phases of the development process, according to the available information. We define an adaptation of traditional function points, called "Object Oriented Function Points", to enable the measurement of object oriented analysis and design specifications. Tools have been constructed to automate the counting method. The novel aspect of our method is its flexibility. An organization can experiment with different counting policies, to find the most accurate predictors of size, effort, etc. in its environment. The method and preliminary results of its application in an industrial environment are presented and discussed.

Proceedings of the sixth conference on …, 2004

Final year students in the Bachelor of Computing complete an industry project where they work in teams to build an IT system for an external client. Grading projects in these circumstances is difficult because of the huge variability of projects and clients. A method of ameliorating ...

1999

Software functional size measurement is regarded as a key aspect in the production, calibration and use of software engineering productivity models because of its independence of technologies and of implementation decisions. In 1997, Full Function Points (FFP) was proposed as a method for measuring the functional size of real-time and embedded software. Since its introduction, the FFP measurement method has been field-tested in many organizations which have provided feedback on ways to improve it. Based on this feedback and in association with the Common Software Measurement International Consortium (COSMIC), version 2.0 of the COSMIC-FFP measurement method will be released in October 1999 for fieldtesting. This paper describes the new features of COSMIC-FFP version 2.0, including: a generic software model adapted for the purpose of functional size measurement, a two-phase approach to functional size measurement (mapping and measurement), a simplified set of base functional components (BFC) and a scalable aggregation function. Through its generic software model of functional users requirements, version 2.0 of the COSMIC-FFP measurement method is applicable to a broad range of software, including embedded, MIS, middleware and system software.

This paper describes the major characteristics of software engineering such as Maintainability, Reliability, Complexity, Understandability, Reusability and Testability. These characteristics measure by some software metrics. There are many software metrics maintainability, Reliability, Complexity and Reusability of the software. Such characteristics can be measured with the help of Coupling, Cohesion, Cyclomatic Complexity, Inherita These characteristics are used to improve the quality, reliability and understandability of the software and reduced the complexity and cost of the software. Abstract This paper describes the major characteristics of software engineering such as Maintainability, Reliability, Complexity, Understandability, Reusability and Testability. These characteristics measure by some software metrics. There are many software metrics but in this paper our emphasis on those software metrics, which effects the maintainability, Reliability, Complexity and Reusability of the software. Such characteristics can be measured with the help of Coupling, Cohesion, Cyclomatic Complexity, Inheritance, and Comment Percentage and size metrics. These characteristics are used to improve the quality, reliability and understandability of the software and reduced the complexity and cost of the software.