![]() The use case collects together those different scenarios. Different sequences of behavior, or scenarios, can unfold, depending on the particular requests made and conditions surrounding the requests. The system responds, protecting the interests of all the stakeholders. The primary actor initiates an interaction with the system to accomplish some goal. ![]() The use case describes the system’s behavior under various conditions as it responds to a request from one of the stakeholders, called the primary actor. Here I will support myself with the definition from Alistair Cockburn's "Writing Effective Use Cases" book (section 1.1).Ī use case captures a contract between the stakeholders of a system about its behavior. In your case, it is an External System that interacts with your system so it is your Actor. It clearly states a close list of who/what can become an Actor. Actors may represent roles played by human users, external hardware, or other systems I will use a definition from UML Specification, section 18.1.3.1Īn Actor models a type of role played by an entity that interacts with the subjects of its associated UseCases (e.g., by exchanging signals and data).
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |