Effort Estimation Techniques for Legacy Systems

2.1 Introduction

In the case of project management, effort estimation in software development is an emerging trend. Effort estimation will come under the analyzed variables. In cases of considering prediction and estimation there are some unresolved issues. By adopting higher reliability, the process of estimation of effort is not yet possible. The process of estimating effort is still a tedious process for project managers.

For processes like project planning, project budgeting, and project bidding the estimation of effort in software projects is considered fundamental. This effort estimation is taken seriously in software companies because inaccurate planning and budgeting can lead to serious consequences. If negative plans and budgets are made the software industry will face a loss of business opportunities. Effective cost estimations are necessary for software development. Some of the work related to this determination of estimation effort is reviewed as follows.

The Importance of Precise Effort Estimation Terminology

The development of accurate and standardized techniques will not effectively solve the issues related to effort estimation. The necessary importance must be placed on the technique for solving problems easily and effectively. At the same time, a high degree of precision must be applied. Examples of the most likely problems are illustrated in Table 2.1.

A comparison analysis was conducted for the performance of effort estimation for the developed technique and for the techniques which are surveyed. It is not possible to obtain a better result because there will be variations in sizes and types.

Traditional Techniques of Effort Estimation

Traditional software models are directed towards large monolithic software development projects. In a component-based software development environment, effort estimation models can benefit from a fine-grained view of parameters that influence effort. Software development can be viewed through a structured programming paradigm. The projection of software costs is made at a general system level for these models.

TABLE 2.1

List of Problems Occurring Due to Lack of Precision

SI.

No.

Problem

Example

1.

A mixture of procedures for various reasons.

A combination of procedures with attention to authenticity (estimation of in all probability exertion), an emphasis on productive improvement work (estimation of arranged exertion), an attention on shirking of spending (choices on planned exertion), and an emphasis on winning an offer (estimation of cost to-win). The absence of partition between these procedures has been found to decrease the authenticity of estimation in all probability exertions.

2.

Estimation error comparison for various software projects when they are not actually comparable.

One of the software projects may have made an estimation error, estimation with respect to the distinction between arranged exertion and genuine exertion, while another task may have made theirs with respect to the contrast between all likelihoods of exertion and real exertion.

 
Source
< Prev   CONTENTS   Source   Next >