1.4, a writing example of a USE CASE:
XXX USE Case
PRIMARY ACTOR:
Level: Summary, Uses Goal, Sub Function
Stake Holder: Other people or system interested in this
PRECONDITION
Prerequisites of current USE CASE. For example, in a system in a network instant messaging, the CASE premise of the web conference may be due to the server transfer information, the server's network must be in a normal state. The premise for some CASE may be that a component must be in an abnormal state.
Flow of Events:
A. PRIMARY SCENARIO:
Described is Basic path. Just like the principle mentioned earlier, it seems to be a stream of water accounts. According to 1, 2, 3, 4 ... to describe things clear
B. Secondary Scenarios:
Here you need to describe the individual exceptions that occur under the Primary scene, with the number in the primary Scenario, which step is clearly explained or which step may happen, and how to process it after a problem, here Important description is logical errors
Exception Scenarios:
In the format, the violation of the violations can be clear, including how to handle it after the occurrence. It is important to describe the various violations that may occur in the program, such as: network interruption, IO violation ...
POST CONDITION:
The system should be in what state after the entire USE case is executed, it takes special instructions.
This completes the entire USE CASE, you can find that USE CASE is actually surrounding the actor. In the actual work, the change or refinement of the demand may occur, and a USE CASE is split into several USE CASE.
1.5 Domain Model
Domain model is essentially Conceptual Class, feature:
1, nouns;
2, each Object maps to the counterparts in the real world;
3. Describe the association between each other;
4, does not contain methods
Domain Model is directly obtained from the USE CASE, the following is how Domain Model is obtained from the USE CASE:
Conceptual Classes Category In Perfect Scenario:
1. Physical Objects:
2. Specification, Design or Description:
3. Places:
4. TRANSACTION:
5. Transaction Line Items:
6. Role of people:
7. Container:
8. Things in the container:
9. Other extend systems intended:
10. ORGANIZATION:
11. Events:
12. PROCESS:
13. Rules and policy:
14. RECORDS:
This allows you to get Domain Model. The more Object obtained in the current phase, the better, and there will be no omissions in the next step. This is an example: System alarm Case Domain Model:
