[Keyword] Development process, software engineering, large software development management
1. The development of large universal software is to sell to dozens of sets by the principle of quality first, the quality will be able to go, but once the software sells thousands of sets, the quality must not be dealive. Otherwise, the maintenance department's phone is to be exploded. Test staff generally achieved 1/3 of the developer, it is reasonable, if it is a company that started, considering cost factors, and mostly based on development projects, it can relax on the test, but once After the company enters the right track, it must pay attention to the test after the development scale increases. Test persons, developers, designers are working around the demand, the demand document is also the main basis for all personnel. Test persons actually play the role of supervising and developers, and also provide quantitative basis for the performance appraisal. 2 The test cannot be "tutorious" testing, and it is also a practical job. A test personnel have long been tested by a product, naturally accumulating a lot of experience, which is difficult to return to some test theory. In some development, there is a tendency to have some excess superstition theory, in fact, actual operation is not so complicated, an ERP system test is mainly functional test, and it is a cigarette point, if you hold it all day Thick software engineering book, but complicated simple questions, of course, after having certain test experience, look back to see theory. It is also beneficial to clarify your own ideas. 3. All documents, the demand document is most important, everyone is consistent with various documents, demand documents, profile design, detailed design, test report, etc., but if you want If a demand document is undoubtedly, the demand document is not the most important, and it is worth it. Secondly, the design document is also important. As for the general design document into summary and detailed It seems that the necessity is not large. If it is a corporate information system, the design document should focus on the background's business logic description. If there is anything to write the SQL statement, if the system reaches a certain size, there should be a lot of UI Public controls, so as long as the main profile of the interface can be described in the design document, the input data is constrained. On time distribution, general, demand accounts for 1/4, design 1/4, encoding, and The test accounted for 1/2. Moreover, in the period of encoding and testing, pure encoding time is better, and the test is often necessary to make repeated modifications to the code.
