First, it is clear that the main performer is the person who wants the system to do something for them, through the performer-target use case description to understand the scope of the project's function, the performer-target (performer, task-level goal, priority, trigger event, etc.) to analyze the scope. The design scope namely the system black box includes the system software and the hardware scope, and through the column scope, stated the enterprise and the organization behavior and so on eliminates the system difference to bring the difference, may use the chart to highlight the design scope with the appropriate icon to label each use case to be able to easily understand its scope, uses the scope to determine the work product , design scope chart, ' Inside/out ' list, performer-target list determines the scope of the system, these four are inseparable work products, ".... Jenny stood in front of the bank's ATM machine, which was very late. She has entered her pin and is looking for a confirmation button ... ", the main performer is Jenny, and the goal is to quickly find the confirmation button of the ATM machine in case of dark weather.
The scope of the performer can be from the system's project stakeholders, the main performer of the use case, the design system itself, the use case of the auxiliary performer, the internal performer, in the example of the company did not pay attention to the system project related personnel, resulting in the system did not provide full service modification requests flocked. Zhu Performer is directly trigger the use case of the executor, of course, the main performer does not necessarily have to be the trigger, the main performer is not important in the beginning of the requirements collection work and before the system release is important, once you start writing a use case a use case may have multiple primary performers.
The goal of the user is that the main performer strives to achieve the goal of the work, which is equivalent to the basic business process, stating whether the operation satisfies the main performer, and registering a blue use case in another use case when registered with the passing person, and the hierarchical goal of the summary contains multiple user goals, which shows the context of the user's running target. Displays the life cycle, provides the table of contents for the underlying target, is white on the color gradient, the summary use case usually takes a long time, the sub-functional level is the target that may be used when the user goal is realized, and the color gradient belongs to Indigo color. The target hierarchy should devote more effort to the investigation of sea level use cases and provide context for other use cases.
Writing effective use cases-Book 2
