Online examples:
Sometimes the project is tight, we do not have the time to good use cases are designed and written to use case management system using Mind Mapping is a better way, and more and more sought after by people. However, in the implementation process, there may be some problems, such as use cases A classmate designed only he Nengkanmingbai, B students is difficult to understand, this is not difficult to understand, because it is like the human brain, his thinking is unique when the mind how to think, this is how design. But since it is the use case, we need to ensure its readability and reusability, ease of review and to others multiplexing. I got all my work out for everyone to share some experience today.
Note the use of Mind Mapping use case design:
1. Classification:
First stage: by type of testing, such as functional testing, interoperability testing, performance testing (such as may be lazy loading, and other asynchronous loading relates to performance improvement), abnormal test (can also be placed in the functional test) and the like. For functions involving a wide range must be strictly separated out, and need special attention to the contents of the abnormal test;
Second stage: the division according to the test point requirements can generally be divided into a plurality of test points;
Third level: If the test points can be broken down into sub-item test, put the test as a child of the third stage, or write use cases directly behind the test point.
2. For the next function test grading:
It may be graded according to components, functions, procedures, data level, the UI level anomalies and the like.
3. For the preparation of specific test cases, pay attention to logic and rational:
1) If the case is completed with several well under certain conditions, the relationship is part of the control and controlled, can be placed under the condition of the nodes;
2) If the case is part of a function point, comprising the belonging relationships included, it is also placed below it;
3) If there is performed between the cases with the requirements of the order, the number marks good 1,2,3;
4) ensure that between use cases is the same level parallel to each other, independently of each other, if there is mutual influence, it certainly had to have a hierarchy;
5) When demand analysis can be applied "if it is possible, could" and other words to ponder valid and invalid equivalence class, but the definition of expected results when writing use cases to be drawn is positive or negative conclusion, with the narrative in the form described.
6） 用例中最好不要出现操作步骤，这个属于具体用例中的内容，但如果不多可以使用括弧备注。
总之，思维导图是指导我们的思维过程，但是所有的思维发散都要有一个模型，在模型基础上进行发散思维，这样子，我们思考时候才是有条理的，进行测试时也才有条理性，没有条理性的用例迟早会出乱子，有遗漏。
我画了个示例图。以简单的邮件订阅为例：
