I don't know if it is not lucky recently, I always have disputes with Leader or the class long. I am a pragmatic. In the development of efficiency, it is very difficult for those who produce a complicated form in order to correspond to "later", "possible". Slightly analyze my current situation first. This week, mainly is the code analysis. Of course, our team leader creates a very complex document template. First, we must write the test items he do, 1, 2, 3; then write the process for each test; then write a database related; after that
Summarize the information of the DB of the operation in the form of a table. There is no problem in such a format itself. But the boss, the code I analyzed is the page operation. There is almost no content about DB, but the team leader requires, but also says that there is no "no" to indicate. As a result, the three pages can be expressed in the document. The following sections are supported from the top, and the repeated flow chart and labeled "None" useless format. It is very good to explain, "
It is used for future STANDALONE transformation. According to the above format, a newbie will easily understand the big input and output of the entire program, it will be relatively clearer. "What is the problem? First, this is an intermediate document, can't replace DD, the second novice is not only" later ", or" possibly ", this is called over-design, this is called Official article. A document format that does not meet the actual situation, not just a waste of our time, and the real value content can not be seen, so that the viewer is difficult to discover the problem early.
