Misunderstandings about the author's use case: China Forum Network collection Source: http: //www.51one.net Add Time: 2004-8-25 misunderstanding about the use case use case is to look at from the outside of the system to an external role "there Dongdong (usually using the verb start), mainly from the user's point of view, do not divide USE CASE as the functionality of the system, because it is as a programmer's point of view. What is "valuable"? It is the user to meet a series of operations by completing the system to meet his demand (wear). From this perspective, as long as your USE case is good enough, the user's needs should not change, and if you write Use Case as the functionality provided by the system, you may need to modify your use. Case (of course, this is incorrect). Finally, USE Case should not be a single step, such as "Press button", "Print Report", etc., but should be a series of interactions.
