Analysis effort method

It is proposed that this article be deleted because of the following concern:

Searched google and it seems mot notable as a standalone subject although possibly someone might suggest a merge (proposed by Chidgk1)

If you can address this concern by improving, copyediting, sourcing, renaming, or merging the page, please edit this page and do so. You may remove this message if you improve the article or otherwise object to deletion for any reason. Although not required, you are encouraged to explain why you object to the deletion, either in your edit summary or on the talk page. If this template is removed, do not replace it.

This message has remained in place for seven days, so the article may be deleted without further notice.

If you created the article, please don't be offended. Instead, consider improving the article so that it is acceptable according to the deletion policy.
Find sources: "Analysis effort method" – news · newspapers · books · scholar · JSTOR

Timestamp: 20230821081233 08:12, 21 August 2023 (UTC)
Administrators: delete

This article does not cite any sources. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Analysis effort method" – news · newspapers · books · scholar · JSTOR (May 2007) (Learn how and when to remove this message)

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.

References