Talk:Cost estimation in software engineering
| This is the talk page for discussing improvements to the Cost estimation in software engineering article. This is not a forum for general discussion of the article's subject. |
Article policies
|
| Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL |
 | This article has not yet been rated on Wikipedia's content assessment scale. It is of interest to the following WikiProjects: | ||||||||||
| |||||||||||
Untitled
editI think the name of the article should be changed. Estimation in software engineering is not a proper title for en encyclopedic article. The article does not even currently give a definintion for that word. Not sure though what the best title would be. Perhaps Effort estimation (redirects here)? That is a term mostly used in software engineering (37 000 of the 43 200 pages that Google finds on effort estimation includes the word software). Lakeworks (talk) 13:24, 26 January 2008 (UTC)
SCRUM
editI'm wondering if parts of "Agile Project Management with SCRUM" should be leasted here? Burn down charts, and task complexity estimation? Mathiastck (talk) 00:52, 4 March 2008 (UTC)
Change of name
editI suggest that the name should be "software development effort estimation". I think we should avoid general, non-software specific names, and names that do not say anything about what we estimate. I don't think we should mix software development effort estimation and other project management means (ref. burn down charts), unless the connection is very obvious, i.e., use of work breakdown structures in bottom-up effort estimation.¨¨¨¨ —Preceding unsigned comment added by Magnej (talk • contribs) 13:23, 23 April 2008 (UTC)
Suggestion of name
editHow about "Software effort estimation". That is what we learn and called it at class.
- Our course book, Software Project Management by Hughes & Cotterell, uses the title "Software effort estimation" for the subject. I believe the book is quite reliable source. 87.94.152.31 (talk) 14:20, 4 November 2008 (UTC)
Size measures and estimation methods are mixed up
editIt seems that a few quite different kinds of methods are mixed up in the list. Yes, COCOMO, SEER-SEM, and some of the others are (effort) estimation methods. But Function Points and Use Case Points are not. They are size measures, that can be used as *input* for effort estimation, but they are not effort (or cost) estimation methods themselves.
A merge suggestion
editCan this be merged with Software development effort estimation? power~enwiki (π, ν) 16:51, 24 October 2017 (UTC)