Departure from the role
(Circular in 2005 is written or left. Because the pen is misunderstood, the time has changed)
In our design process, the term "role" is relatively rare, "business", "process" more. We get the needs or design documentation, sequence diagram, flowchart is The main components. ISE Case is also, mainly for brief description of the event stream.
Perhaps thinking that the concept is not very complicated, or it has been analyzed enough, so it is not necessary to mention it. In fact, what roles do you have in the system, but feel the essence of the role, the details of the character , The interoperability between the characters, the insufficient refinement, abstract summary is not enough.
If starting from the role, it may be roughly thus analyzed.
1: Define the role of the role
2: Define the general properties of the role
3: Define the possible extension attributes (considering implementation, etc.)
4: Define the general behavior of the role, including access to the method of managing its properties.
5: Define the interaction behavior and operation interface between the characters, the interface is largely based on role properties and behaviors
6: Definition When the role itself changes, the new role is added or the behavior when the role disappears.
Need to consider the granularity, level (entire system or subsystem) of the character, whether there is interdependence or conflict. The role should be high polymer, low coupling.
The role is relatively fixed as the system. When the role itself and the interaction between the characters are basically clear, the process changes more, and the order of changing the interaction between the characters.
The above idea is not a mature example, just a little. In short, in the artificial, first, people, and then consider doing things, this principle is not wrong.
