华师大面向对象程序设计-Lec04_用例图2.pptVIP

* 3. Guideline 3.1 (ch6.11) Write use cases in an essential style; keep the user interface out and focus on actor intent. 1/ Find “the goal of the goal “. Example, “Log on” ? thinking of a GUI, dialog box, user ID, and password . But this is the mechanism, not the goal the system analyst arrives at a mechanism-independent goal : identify myself and get authenticated “ prevent theft …. 2/ essential style, example “Manage Users” use case … Administrator identifies self. System authenticates identity. … 针对这种意图和职责的设计,可以非常灵活:生物信息读取、GUI 等 * 3. Guideline 3.1 (ch6.11) Write use cases in an essential style; keep the user interface out and focus on actor intent. 3. Concrete Style may be avoid during early requirements Work, example, … Adminstrator enters ID and password in dialog box. System authenticates Administrator. System displays the edit users window. … 这种方式可以用, 但尽量不要在需求分析的早期! * 3. Guideline 3.2 (ch6.12) Write Terse(简洁的)Use Cases 用词简洁 “System authenticates…” ? “The system authenticates… ” 3.3 (ch6.13) Write Black-Box Use Cases do not describe the internal workings of the system, its components, or design. Rather, the system is described as having responsibilities one can specify what the system must do (the behavior or functional requirements) without deciding how it will do it (the design). Example Black-box style Not The system records the sale. The system writes the sale to a database. …or (even worse): The system generates a SQL INSERT statement for the sale… * 3. Guideline 3.4 (ch6.14) Take an Actor and Actor-Goal Perspective an observable result of value to a particular actor” is a subtle but important concept that Jacobson considers critical, because it stresses two attitudes during requirements analysis: Write requirements focusing on the users or actors of a system, asking about their goals and typical situations. Focus on understanding what the actor considers a valuable result * 3. Guideline 3.5 (ch6.15) How to Find Use Cases Choose