Software development is its own Bank, talking about a small team development software here:
1) Every developer must have a certain understanding of the things you want to develop, it is best to ask the demand in detail when you start, don't talk about the needs of all text, the most It is a matter of use of graphics to interact, and it has an experience that I have to make my interface. I will give it to the user. When I gave it a lot of demand, the developer will complain, saying that it has been in the document. Write clearly, this shows the importance of basic interface design in the demand document. 2) Development of the initial focus on some technical difficulties and frameworks, including interface framework and some public code, this stage During it, it will bring great benefits to the back, don't avoid the difficulties in the early days of development, the initial stage of development, the team is dry, and many technical difficulties can be resolved, if they will be dealt with later, these risk And time-consuming technical difficulties will dispense the enthusiasm of the entire team. The utility code is also very critical. The greater the software, the more public, the interface partial code can be public, the underlying code can also be public, the utility code is done, It will have a great advantage for the consistency and maintainability of the software. The most critical is to save people. Doing software may wish to reflect on the projects you have done, see where there are public, simple examples, The generation of the report, the import of data, the query of database data, which is the most easily modular.
3) Test is the most painful, most of which have insufficient test power, even if people are enough, it is not necessarily experienced. The key is that the test case should be written, bug is going to manage. BUG management has multi-faceted role, one It is quantified throughout the development. In software development, the progress is untrustworthy, only bug is the best evidence, bug can last for a period of time to explain another role of BUG management It is also a supervision of developers, which can stimulate the enthusiasm of developers (although this kind of enthusiasm is excited in the case of self-esteem). The importance of test cases is self-evident, if it is the final delivery product There is a problem in the scene, the first one of the crime is not a developer, but should be a person who writes test cases, why didn't you consider the wrong situation?
