Jump to content

Talk:Cost estimation in software engineering

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by Jksmith85 (talk | contribs) at 18:06, 23 September 2019 (→External links modified). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

Template:Findsourcesnotice I 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)[reply]

SCRUM

I'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)[reply]

Change of name

I 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)[reply]

Suggestion of name

How 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)[reply]

Size measures and estimation methods are mixed up

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

Han691 (talk) 21:15, 13 February 2015 (UTC)[reply]

Hello fellow Wikipedians,

I have just modified one external link on Cost estimation in software engineering. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 13:43, 13 August 2017 (UTC)[reply]

A merge suggestion

Can this be merged with Software development effort estimation? power~enwiki (π, ν) 16:51, 24 October 2017 (UTC)[reply]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Cost_estimation_in_software_engineering&oldid=917408091"