Question

It seems odd that cost and size estimates are developed during software project planning-before detailed software requirements analysis or design has been conducted. Why do we think this is done? Are there circumstances when it should not be done?

Answer 1

Answer:

Defining the price of the software is a big issue in software development. For example, say someone asked how much money it took to make a X software (or any software). They did not say anything about this software but asked only how much it costs (without requirement). But what could be the answer, because without the

necessary information it can't be answered. In the case of software development many have a cost estimation but have no way to do a software development cost estimation without requirement collection. Is this also a problem you have come across?