Chapter3UnderstandingRequirements課件.pptVIP

It is important to show how actors relate to the use case. Therefore, on finding a use case, establish the actors that will interact with it. To do this, you must define a communicates association that is navigable in the same direction as the transmission between the actor and the use case. Actors may be connected to use cases only by an association. An association between an actor and a use case indicates that the actor and the use case communicate with one another, each one able to send and receive messages. The communicates association can also be drawn in the other direction. A use case can initiate communication with an actor. Usually, this will occur with a non-human actor. The first use cases are preliminary, and you’ll have to change them a few times until they are stable. If the systems vision or requirements are deficient or if the system analysis is vague, the systems functionality will be unclear. Therefore, you must constantly ask yourself if you have found the right use cases. Furthermore, be prepared to add, remove, combine, and divide the use cases before you arrive at a final version. You better understand the use cases after you have described them in detail. The best way to find use cases is to consider what each actor requires of the system. Remember, the system exists only for its users and should be based on the users needs. You will recognize many of the actors needs through the functional requirements made on the system. The answers to these questions represent the flows of events that identify candidate use cases. Not all constitute separate use cases. Some may be modeled as variants of the same use case. It is not always easy to tell what is a variant and what is a separate and distinct use case. However, it will become clearer when you describe the flows of events in detail. Each use case should have a name that indicates what is achieved by its interactions with the actor(s). The name may have to be several words to be understood.