• Journal of Internet Computing and Services
• /
• v.10 no.4
• /
• pp.115-126
• /
• 2009

A software size estimation has to be analyzed in the beginning of the software life-cycle and helpful to the prediction of its size and cost. The software cost has been calculated by estimating software size from the user's point of view since the function point method based on international standards was introduced for the estimation of software size in 2004. However, the current function point method is not easy to be exploited for unfamiliar user, and has a problem that it cannot estimate the proper size for software such as engineering software, scientific calculations and simulation with complicated internal computational logic. This paper presents an improved model which can simplify the existing function point measurement procedure, and perform the estimation of software size in easy and fast way at the initial stage of project. Moreover, it presents a mathematical weighted value calculation model which can solve the problem of the fixed complexity weighted value and reflect the characteristics of organization as its data is pilled up. Our evaluation shows that the presented model has advantage that it can measure the size more rapidly than the existing FPA methods and has more correlation with LOC.

• The KIPS Transactions:PartD
• /
• v.10D no.7
• /
• pp.1127-1136
• /
• 2003

Estimation of software project cost, effort and duration in the early stage of software development cycle is a difficult and key problem in software engineering. Most of models estimate the development effort using the function point that is measured from the requirement specification. This paper presents optimal team size and duration prediction based on function point in order to provide information that can be used as a guide in selecting the most Practical and productive team size for a software development project. We introduce to productive metrics and cost for decision criteria of ideal team size and duration. The experimental is based on the analysis of 300 development and enhancement software project data. These data sets are divide in two subgroups. One is a development project; the other is a maintenance project. As a result of evaluation by productivity and cost measured criteria in two subgroups, we come to the conclusion that the most successful projects has small teams and minimum duration. Also, I proposed that predictive model for team sire and duration according to function point size based on experimental results. The presented models gives a criteria for necessary team site and duration according to the software size.

• The Journal of Society for e-Business Studies
• /
• v.7 no.2
• /
• pp.173-190
• /
• 2002

Over the past decade, numerous software managers and engineers have been concerned with measuring the size and complexity of software systems. Function point analysis technique is one of the most popular software sizing techniques. A reasonable software development plan through cost and time estimation should be a prerequisite for the successful project at the beginning stage of the project. It is generally known that software size measurement is useful for this kind of estimation and the function point analysis technique would be more effective than the others. However, it is difficult to apply the technique to object-oriented methodology widely used in the software industry. Thus, the purpose of this study is to present a case study on how to apply function point analysis technique to sizing of the software systems based on UML. The results of this study can be useful to managers and engineers.

• The Transactions of the Korea Information Processing Society
• /
• v.6 no.1
• /
• pp.90-95
• /
• 1999

A software growth model, a mathematical model describing the growth behavior of a software system during the evolution process, enables us to predict the future system size and incremental erfort required to meet the planned system size. This paper first introduces a software growth model defined with respect to the cumulative incremental effort. It was assumed that the incremental growth of a software system is proportional to the incremental effort and function of the system size is suggested as a system complexity and then applied to real data for its validation. such a system complexity additionally provides us with a measure for complexity comparison. since the measure is independent of the system size, it is useful for comparing complexities of software systems of different size.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.12
• /
• pp.225-232
• /
• 2009

Function Point Method have been applied to measure software size estimation in industry because it supports to estimate the software's size by user's view not developer's. However, the current function point method has some problems for example complexity's upper limit etc. So, In this paper, an enhanced function point model. Micro FP model, was suggested. Using this model, software effort estimation can be more efficiently because this model has some regression equation. This model specially can be applied to estimate in detail the large application system's size Analysis results show that measured software size by this Micro FP model has the advantage with more correlative between the one of LOC, as of 10 applications operated in an large organization.

• The Journal of Society for e-Business Studies
• /
• v.6 no.2
• /
• pp.143-157
• /
• 2001

There has been a need for predicting development efforts and costs of the system during the early stage of the software process and hundreds of metrics have been proposed for computer software, but not all provide practical support to the software engineer. Some demand measurement that is too complex, others are so esoteric that few real-world professionals have any hope of understanding them, and others violate the basic intuitive notions of what high-quality software really is. It is worthwhile that metrics should be tailored to best accommodate specific products and processes after grasping their good and no good point. This paper describes two size estimation techniques, the Karner technique and the Marchesi technique, and compares and analyzes them with proposed evaluation criteria. Both techniques are to estimate software size analyzed by use case that is mainly described during the object-oriented analysis phase. We also present an empirical comparison of them, both are applied in the Internet Medicine Prescription System. We also propose some guidance for experiments based on our analysis. We believe that it should be facilitating project management more effective by adjusting software metrics properly.

• Journal of Internet Computing and Services
• /
• v.6 no.2
• /
• pp.37-47
• /
• 2005

Most of the methods of estimating the size of software are based on the functions provided to costumers and in the process of granting the score to each function we consider the complexity during the process. The FFP technique has advantages applied to vast areas like data management. real-time system, algorithmic software, etc, but on the other hand, has disadvantage on estimating sizes for weights for necessary function elements. This paper proposes the estimating method for software size by considering the complexity of each function elements in full function point calculation method applied to a new developed project and maintenance projects. For this, based on function point by using surveyed data proved the validity of proposed method. The valid result. was that the function elements, the attributes used in size estimation of software, est mated better estimated sizes than in the case of other weights being applied.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.9
• /
• pp.35-43
• /
• 2011

To develop a software, there is a relationship between development organization's productivity, effort, development schedule, and software size. It is software equation that motive these relations. Basically, relationship between size-effort and size-schedule is applied. If this relationship is not proper, there would be no effect of the cost-schedule tradeoff equation that is derived from software equation, and the manpower profile analysis, etc. To solve these unwanted problems, we presented a modified software equation and a cost-schedule tradeoff model based on the modified software equation. To improve software development success rate, applying proposed model will help in contract negotiation or bid.

• The KIPS Transactions:PartD
• /
• v.10D no.7
• /
• pp.1137-1144
• /
• 2003

The existing Function Point method to estimate the software size has been utilized frequently with the management information system. Due to the expanding usage of the real-time and embedded system, the Full Function Point method is being proposed. However, despite many research is being carried out relation to the software size, the research on the model to estimate the development cost from the measured software size is inadequate. This paper analyzed the linear regression model and power regression model which estimate the development cost from the software FFP The power model is selected, which shows its estimation is most adequate.

• The KIPS Transactions:PartD
• /
• v.13D no.5 s.108
• /
• pp.717-724
• /
• 2006

The cost estimation of software is getting more important as the portion of software is increasing in acquiring weapon systems. However, the cost estimation of embedded software in a weapon system follows the cost estimation method for general purpose softwares and uses the PRICE S model as a tool. However, any validation result of the estimated cost through an evaluated software size is not well known. Hence, we propose an approach to estimate the cost through evaluating the embedded software site in weapon systems. In order to achieve our research goal, we evaluate the software size of using the line of codes and function points which are produced by the PRICE S model. Finally, we compare the estimated cost data the actual cost data provided by the production company. As a result, we propose an approach to estimate the size and the cost of embedded software in weapon systems which are not easy to estimate objectively. We also expect that the Proposed approach is used for the cost validation and negotiation in the acquisition of weapon systems in the future.