Book notes for writing effective cases (5) -- three naming targets

1 , User target (Blue, sea level )( User goal ), Which is the goal of the primary executor's efforts to achieve the work, or the goal of the user's use of the system. It is equivalent to the "Basic Business Process" in the business process project ".

2, Outline level target (white, cloud, kite,Summary-level goal) Contains multiple user targets. When describing the system, they have the following three functions:

L displays the context of user target running.

L displays the lifecycle sequence of the target.

L provides a directory table for underlying use cases (including white and blue use cases.

For exampleHisThe patient cases in the case are a summary level. The case must contain registration, medical treatment at the doctor's office, payment, and drug retrieval steps, these steps can be a relatively low-level use case.

3Sub-functional level (Indigo/Black, under sea level/Clam,Subfunction-level goal) Goals are those that may be used to achieve user goals.

4There are three important considerations for the target layer:

L put a lot of energy into the test of sea level (user goal) cases, they are important use cases.

L write some outermost use cases to provide context for other use cases.

LDo not make a fuss about whether to use your favorite wording in the System Requirement Specification statement as the title of the use case.

5Find out the correct two guiding principles for the target layer:

L Find the user's target and ask two questions ( 1 ) What the main performer really wants ? ( 2 ) Why is the executor doing this? The answer may be the performer's goal.

L perform the 3 step to 10 step

The2I doubt whether the translation is wrong. It should be "every use case has3To10Steps (more appropriate)

6In order to raise the target level of one or more interaction steps, let's think about this question: "Why do executors do this ?" The answer may be a higher level goal.

For example, when writing a patient registration case, the answer to this question is "to see a patient in a hospital". Obviously, seeing a patient is a high-level goal.

 

By dividing the target into layers, you can take into account the overall situation and the section when obtaining the requirement, and find that the high-level goal is conducive to grasping the global situation. To refine the demand, you have to find the low-level goal, the user goal is the intermediate point of the two, and the steps to describe the user goal will be the prototype of the software system interface and process in the future.