Documents describing the needs are often referred to as a demand analysis manual. In order to make the document easy to understand, two elements of example and scripts can be added. Use an example as the most popular diagram in the UML, suitable for describing the user interface and system processing of the system. Scripts describe a specific functional execution process.
These two tools are also difficult to either in a short message. In the project of multiplayer, the test is a very important step. When the test starts, in theory, the programming has been completed. I have previously mentioned that the author advocates "rolling development" and wants to come with iterative ideas. This is also true, and some parties are detected, some are still processing. Here, the test refers to the system first centralized test. It is necessary to connect to the script according to the script before this. Otherwise, when a test point is attacked, the plan will have to consume some human work.
This one is a bit short, and then find the opportunity to increase the content.
