When he takes a picture, he has to switch the flash on, open the shutter, and then close the shutter but these activities are not of a high enough level to be represented in a use case. In the following example, the actor "photographer" does two things with the camera: take pictures and change the film. However, it would be poorly suited to describing the TCP/IP network protocol because there are many exception cases, branching behaviors, and conditional functionality (what happens when the connection dies, what happens when a packet is lost?) The <<extend> use case accomplishes this by conceptually inserting additional action sequences into the base use-case sequence. Listed below are some important components of Use Case diagrams: 1) System: It is also referred to as scenario or functionality.Further details can later be added to the diagram if you need to elucidate interesting points in the system behavior.Ī use case diagram is well suited to the task of describing all of the things that can be done with a database system by all the people who might use it. Use case diagrams contain a combination of different elements and specialized symbols and connectors. The answer is simple: your use cases should stand on their own, you shouldn’t expect people to have your use-case diagram in front of them. With a use case diagram, you immediately see a snapshot of the system functionality. To create a new model, select File > New Model, choose Object Oriented Model as the model type and Use Case Diagram as the first diagram, and then click OK. Use case diagrams are used to show the decomposition of a business problem or software solution into a set of discrete functions (the use cases) which can be. Note: To create a use case diagram in an existing OOM, right-click the model in the Browser and select New > Use Case Diagram.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |