• The KIPS Transactions:PartD
• /
• v.8D no.2
• /
• pp.154-165
• /
• 2001

A number of attempts to develop methods for measuring software effort have been focused on the area of software engineering and many models have also been suggested to estimate the effort of software projects. Almost all current models use algorithmic or statistical mechanisms, but the existing algorithmic effort estimation models have failed to produce accurate estimates. Furthermore, they are unable to reflect the rapidly changing technical environment of software development such as module reuse, 4GL, CASE tool, etc. In addition, these models do not consider the paradigm shift of software engineering and information systems(i.e., Object Oriented system, Client-Server architecture, Internet/Intranet based system etc.). Thus, a new approach to software effort estimation is needed. After reviewing and analyzing the problems of the current estimation models, we have developed a model and a system architecture that will improve estimation performance. In this paper, we have adopted a neural network model to overcome some drawbacks and to increase estimation performance. We will also address the efficient system architecture and estimation procedure by a similar case-based approach and finally suggest the heuristic search method to find the best estimate of target project through empirical experiments. According to our experiment with the optimally parsimonious neural network model the mean error rate was significantly reduced to 14.3%.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.616-623
• /
• 2003

Since the computing environment changes very rapidly, the estimation of software effort is very difficult because it is not easy to collect a sufficient number of relevant cases from the historical data. If we pinpoint the cases, the number of cases becomes too small. However if we adopt too many cases, the relevance declines. So in this paper we attempt to balance the number of cases and relevance. Since many researches on software effort estimation showed that the neural network models perform at least as well as the other approaches, so we selected the neural network model as the basic estimator. We propose a search method that finds the right level of relevant cases for the neural network model. For the selected case set, eliminating the qualitative input factors with the same values can reduce the scale of the neural network model. Since there exists a multitude of combinations of case sets, we need to search for the optimal reduced neural network model and corresponding case set. To find the quasi-optimal model from the hierarchy of reduced neural network models, we adopted the beam search technique and devised the Case-Set Selection Algorithm. This algorithm can be adopted in the case-adaptive software effort estimation systems.

• The KIPS Transactions:PartD
• /
• v.9D no.2
• /
• pp.259-266
• /
• 2002

The main issue in software development is the ability of software project effort and cost estimation in the early phase of software life cycle. The regression models for project effort and cost estimation are presented by function point that is a software sire. The data sets used to conduct previous studies are of ten small and not too recent. Applying these models to 789 project data developed from 1990 ; the models only explain fewer than 0.53 $R^2$(Coefficient of determination) of the data variation. Homogeneous group in accordance with project delivery rate (PDR) divides the data sets. Then this paper presents general effort estimation models using project delivery rate. The presented model has a random distribution of residuals and explains more than 0.93 $R^2$ of data variation in most of PDR ranges.

• Journal of the Korea Computer Industry Society
• /
• v.3 no.3
• /
• pp.295-306
• /
• 2002

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 instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort are variable according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differ from project to project. This paper suggests the criteria for effort allocation in planning, specifying, building, testing and implementing phase followed by the project total effort. These criteria are derived from 183 different projects. This result can be considered as a practical guideline in management of project schedule and effort allocation.

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

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.865-876
• /
• 2002

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. Existing software effort estimation models are present only the total effort and instantaneous effort function for the software life-cycle. Also, Putnam presents constant effort rate in each phase. However, the size of total effort varies according to the software projects under the influence of its size, complexity and operational environment. As a result, the allocated effort in each phase also differs from one project to another. This paper suggests models for effort allocation in planning, specifying, building, testing and implementing phases followed by the project size and development types. These models are derived from 155 different projects. Therefore, these models can be considered as a practical guideline in management of project schedule and effort allocation.

• The KIPS Transactions:PartD
• /
• v.8D no.3
• /
• pp.241-246
• /
• 2001

Area of software measurement in software engineering is active more than thirty years. There is a huge collection of researches but still no a concrete software cost estimation model. If we want to measure the cost-effort of a software project, we need to estimate the size of the software. A number of software metrics are identified in the literature ; the most frequently cited measures are LOC(line of code) and FPA(function point analysis). The FPA approach has features that overcome the major problems with using LOC as a measure of system size. This paper presents an neural networks(NN) models that related software development effort to software size measured in FPs and function element types. The research describes appropriate NN modeling in the context of a case study for 24 software development projects. Also, this paper compared the NN model with a regression analysis model and found the NN model has better estimative accuracy.

• International Journal of Computer Science & Network Security
• /
• v.24 no.6
• /
• pp.17-22
• /
• 2024

Software cost and schedule estimation is usually based on the estimated size of the software. Advanced estimation techniques also make use of the diverse factors viz, nature of the project, staff skills available, time constraints, performance constraints, technology required and so on. Usually, estimation is based on an estimation model prepared with the help of experienced project managers. Estimation of software cost is predominantly a crucial activity as it incurs huge economic and strategic investment. However accurate estimation still remains a challenge as the algorithmic models used for Software Project planning and Estimation doesn't address the true dynamic nature of Software Development. This paper presents an efficient approach using the contemporary Constructive Cost Model (COCOMO) augmented with the desirable feature of fuzzy logic to address the uncertainty and flexibility associated with the cost drivers (Effort Multiplier Factor). The approach has been validated and interpreted by project experts and shows convincing results as compared to simple algorithmic models.

• Journal of KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.134-147
• /
• 2000

Even though software industry has been activated, there lack in results of studies on evaluation effort and cost of software systems including Information Technology Security System (ITSS). In this paper, we present a process and a tool for evaluation effort and cost of ITSS, which are conformed to a ITSS evaluation criteria(i. e., Common Criteria or ISO/IEC 15408), by utilizing Evaluation Work Break-down Structure (EWBS) and conventional software development cost estimation methods. Even though we concentrate on ITSS, results of this paper can be applied to estimation of effort and cost of evaluation of software development process and software products.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.103-110
• /
• 2005

Software Development is converting from structural to object oriented method. The later software development prefers the iterative process applications, not aterfall process and based on use case model, the requirements are expressed and based on this, analysis, design and coding are accomplished. Therefore, size of the software to be developed is estimated basing on use case and it is only possible to maintain the project success by estimating development effort, cost and development period. Even though development effort estimation models related current use case point. there is no appropriate development effort estimating. This paper shows, as a result of applying the development effort estimating model about UCP to the growth curve, a superior performance improvement to current statistical models. Therefore, estimation of development effort by applying this model, project development maintenance can be appropriately carried out.