• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.5
• /
• pp.566-570
• /
• 2010

Use Case Point(UCP) is a measure of a software project size for software effort estimation based on use case. UCP measures the size of the software project based on the use case model. Because UCP is based on the use case model, it is intuitive and easy to obtain. Also, it does not require extra artifacts. On the other hand, UCP has some problems. UCP assumes every transaction has the same complexity. But, the number of operations and complexity of operations may affect complexity of transaction. In addition, UCP uses simple rating scale of complexity, but it may be inadequate for detailed estimates. To solve these problems, we suggest "Transaction Point(TP)", a size measure based on use case transaction. TP considers actors and operations in transaction. Complexity of transaction is based on the number of operations and complexity of operation, so it can support detailed estimation.

• IE interfaces
• /
• v.17 no.spc
• /
• pp.122-130
• /
• 2004

Since the cost of software maintenance occupies about 50~75% in a general successful organization, the software maintenance plays an important role in software life cycle. In particular, if the managed system needs to be operated in a long term or the system is very large and complex, then the maintenance is especially more important. Software maintenance is defined as software modification activities after customer delivery, such as improvement of performance or functionality, error correction, adaptation to environmental changes, etc. In this paper, software cost estimation models are proposed, that is based on productivity of manpower in maintenance projects. In order to do this, the activities of maintenance are classified into function change, non-function change, user support and application operation. The proposed models are constructed and verified based on the real size and cost information of projects in the real world. The approach in this paper is to discriminate the heterogeneous activities in maintenance projects, and then to calculate the respective cost of each discriminated activity. By using the proposed models, the total cost of maintenance project is summed from the costs of four activities. In addition the number of conflicts between owner and order receiver about the amount of cost will be reduced and the reasonable cost estimation system will be established.

• Korean Management Science Review
• /
• v.19 no.2
• /
• pp.191-204
• /
• 2002

As the portion of information systems (IS) budget to the total government budget becomes greater, the cost estimation of IS development and maintenance projects is recognized as one of the most important problems to be resolved for scientific and efficient management of IS budget. Since IS budget makes much effect on the delivery time, quality and productivity of IS projects, the exact cost estimation is also necessary for the successful accomplishment of IS projects. The primary concern in the cost estimation of IS projects is software cost estimation, which requires the measurement of the size of softwares. There are two methods for sizing software : line-of-code approach, function point model. In this paper, we propose a function-point-based model for estimating software cost. The proposed model is derived by collecting about fifty domestic IT projects in public sector and analyzing their relationship between cost drivers and development effort. Since the proposed model is developed by simplifying the function point model that can be used only when detailed user requirements are specified, it can be also applied at project planning and budgeting phase.

• Journal of KIISE:Software and Applications
• /
• v.29 no.12
• /
• pp.873-882
• /
• 2002

Estimation of development cost, effort and time is difficult and a key problem of software engineering in the early stage of software development. These are estimated by using the function point which is measured from a requirement specification. However, it is often a serious Question of the staffing level required for the software development. The purpose of this paper is to show us the model which can be used to estimate a size of development team. Three hundred one software projects have been analyzed and studied for the model. First, an analysis was conducted for statistical algorithmic model. After various data transformation and regression analysis, it was concluded that no good model was available. Therefore, non-algorithmic model was suggested for analysis, which has random distribution of residuals and makes good performance using RBF (Radial Basis Function) network. Since the model provides a standard to determine the required size of development team, it ran be used as management information.

• Journal of Korea Society of Industrial Information Systems
• /
• v.4 no.3
• /
• pp.1-7
• /
• 1999

An important task for any software project manager is to be able to predict and control project size. Unfortunately, there is comparatively little work that deals with the problem of building prediction methods for software size in fourth-generation languages and database projects. In this paper, we propose a new estimation method for estimating for software size based on minimum relative error(MRE) criterion. The characteristic of the proposed method is insensitive to the extreme values of the observed measures which can be obtained early in the development life cycle. In order to verify the performance of the proposed estimation method for software size in terms of both quality of fit and predictive quality, the experiments has been conducted for the dataset Ⅰ and Ⅱ, respectively. For the data set Ⅰ and Ⅱ, our proposed prediction method was shown to be superior to the traditional method LS and RLS in terms of both the quality of fit and predictive quality when applied to data obtained from actual software development projects.

• Proceedings of the Korean Statistical Society Conference
• /
• 2005.05a
• /
• pp.233-238
• /
• 2005

S${\"{a}}$rndal (1996) and Knottnerus (2003) had a critical look at the well known variance estimator of Sen (1953) and Yates and Grundy (1953) in probability proportional to size sampling. In this paper, we point out that although their approaches can avoid the difficulties in variance estimation with respect to the joint probabilities, there exist the disadvantages in practice. Also, we describe a sampling procedure available in statistical software that are useful for the variance estimation.

• Journal of KIISE:Software and Applications
• /
• v.31 no.1
• /
• pp.20-28
• /
• 2004

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 development effort and duration estimation models presented by regression model of simple relation function point vs. effort and effort vs. duration instead of considering developer's productivity. But different project have need for different effort according to developer's productivity if the projects are same software size. Also, different duration takes according to developer's productivity if the projects require the same effort. Therefore, models that take into account of productivity have a limited application in actual development project. This paper presents models that can be estimate the duration according to productivity in order to compensate a shortcoming of the previous models. Propose model that could presume development period by various methods based on productivity and compared models' performance. As a result of performance comparison, an estimating model of development period from software size got simple and most good result. The model gives decision-making information of development duration to project management in the early stage of software life cycle.

• Journal of the Korea Computer Industry Society
• /
• v.2 no.6
• /
• pp.859-866
• /
• 2001

Successful project planning relies on a good estimation of the effort required to complete a project, together with the schedule options that may be available. Despite the extensive research done developing new and better models, existing software effort estimation models are present only the total effort and effort (or manpower： people per unit time) function for the software life-cycle. Also, Putnam presents constant effort rate in each subcycles. However, the size of total efforts are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in subcycle also differ from project to project. This paper suggests the linear and polynomial effort estimation models in specifying, building and testing phase followed by the project total effort. These models are derived from 128 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

• 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.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.6
• /
• pp.119-129
• /
• 2020

Software development activities are influenced by stochastic theory rather than deterministic one due to having process variability. Stochastic methods factor in the uncertainties associated with project activities and provides insight into the expected project outputs as probability distributions rather than as deterministic approximations. Thus, successful software projects systematically manage and balance five objectives based on historical probability: scope, size, cost, effort, schedule, and quality. Although software size estimation having much uncertainty in initial development has traditionally performed using deterministic methods: LOC(Lines Of Code), COCOMO(COnsructive COst MOdel), FP(Function Point), SLIM(Software LIfecycle Management). This research aims to present a function point method based on stochastic distribution and a case study based on Monte Carlo Simulation applying on an automotive electrical and electronics system software development. It is expected that the result of this paper is used as guidance for establishing of function point method in organizations and tools for helping project managers make decisions correctly.