Actions

Analysis Effort Method

Revision as of 13:42, 6 February 2021 by User (talk | contribs) (The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).)

The analysis effort method is a method for estimating the duration of software engineering projects. It is best suited to producing initial estimates for the length of a job based on a known time duration for preparing a specification. Inputs to the method are numeric factors which indicate Size (S), Familiarity (F) and Complexity (C). These, with a duration for preparing the software specification can be used in a look up table (which contains factors based on previous experience) to determine with length of each of the following phases of the work. These being Design, Coding and Unit testing and Testing. The method does not include any times for training or project management. This method should be used as one of a number of estimation techniques to obtain a more accurate estimate.[1]


With the analysis effort method, the stage of the project that forms the basis for the estimates is the analysis of requirements. Estimates for this can be arrived at by considering the stakeholders to be involved, the methods to be used (interviews or workshops for example) and by allocating sensible amounts of effort to these. The analysis effort method is probably the best choice where there is only a vague idea of the actual requirement but where the stakeholders to be involved in the analysis work can be identified.[2]


References

  1. Defining Analysis Effort Method Wikipedia
  2. What is Analysis Effort Method Coursehero