Use case diagrams define the requirements of the system being modeled and hence are used to write test scripts for the modeled system. Use case diagrams have another important use. Due to the simplicity of use case diagrams, and more importantly, because they are shorn of all technical jargon, use case diagrams are a great storyboard tool for user meetings. As you discuss the functionality and processes of the system, you discover significant characteristics of the system that you model in the use case diagram. More specifically, it captures the business processes carried out in the system. The above statement pretty much sums up what a use case diagram is primarily made up of-actors and use cases.Ī use case diagram captures the functional aspects of a system. The primary elements are termed as “actors” and the processes are called “use cases.” The Use case diagram shows which actors interact with each use case. The Use case diagram is used to identify the primary elements and processes that form the system. Basics of Use Case Diagramsīefore starting off today’s article, iti is worth revisiting the definition of use a case diagram, as described in the first article. Finally, you’ll see how to use case diagrams for the case study application-the Courseware Management System-used in the previous articles. Additionally, you will see what a use case specification is. We’ll present the basics of use case diagrams and show you how to draw a use case diagram.
In this article, you’ll explore the Use case diagram. Now that you have the clear, you’ll start to learn about the the nine UML diagrams. In the previous two articles, you saw a brief review of the nine UML diagrams and what kind of tools can be used to model UML diagrams.
0 kommentar(er)
