The problem of proportion distribution of requirement analysis and design time and development time in software project development

From graduation to now do the development has been nearly 7 years, large and small projects have experienced dozens of. Few projects have invested much time in the design phase of the project development process,

There are many cases, not even how to do the design directly began coding, in a side development side design to state, and sometimes, the design is to complete some documents to cope with, very

Few seriously do design, and then directly start coding, if you encounter demand problems, and then confirm. There are also times when it's time to identify the needs, start prototyping, and then move on

Hair, this way is better, at least in the early detection of a lot of problems, to avoid the possibility of major problems follow.

In fact, from my personal point of view, many times we re-develop light design is also forced by the environment, there are several reasons:

1. Companies want to receive the project, immediately can see the effect, every day to talk about demand or demand for too long, the boss can not see the actual output, not willing to spend too much time to do demand analysis and research.

2. Customers do not like you to find him every day to understand the needs of the problem, one is that users can not accurately express themselves to the expectations, you can not be very accurate to induce users to say their own expectations, such is not

Wait until you've made the real thing, and see if you meet expectations, or make further changes.

3. Many developers think that to do the requirements analysis and design is to write a pile of documents, simply do not want to do this thing, rather than direct coding readily, many programmers prefer to deal with the code, rather than

Document.

The above several reasons cause we often enter a vicious circle, the demand is not clear on the start, the development has not been completed to find that has deviated from the direction to change, so it is recommended to use the prototype method

and iterative development model to step-up the project, so that more reliable, so that the knife can not mistakenly cut wood workers, and will not let customers and bosses think you have no output for a long time.

The problem of proportion distribution of requirement analysis and design time and development time in software project development