Cập nhật nội dung chi tiết về Create A Uml Use Case Diagram mới nhất trên website Techcombanktower.com. Hy vọng thông tin trong bài viết sẽ đáp ứng được nhu cầu ngoài mong đợi của bạn, chúng tôi sẽ làm việc thường xuyên để cập nhật nội dung mới nhằm giúp bạn nhận được thông tin nhanh chóng và chính xác nhất.
You can create a UML use case diagram in Visio to summarize how users (or actors) interact with a system, such as a software application. An actor can be a person, an organization, or another system.
Use case diagrams show the expected behavior of the system. They don’t show the order in which steps are performed. (Use a sequence diagram to show how objects interact over time.)
Defining the system boundary determines what is considered external or internal to the system.
An actor represents a role played by an outside object. One object may play several roles and, therefore, is represented by several actors.
An association illustrates the participation of the actor in the use case.
A use case is a set of events that occurs when an actor uses a system to complete a process. Normally, a use case is a relatively large process, not an individual step or transaction.
On the File tab, point to New.
in the Search box, type UML use case.
In the dialog box, select the blank template or one of the three starter diagrams. (A description of each one is shown on the right when you select it.) Then select either Metric Units or US Units.
The diagram opens. You should see the Shapes window next to the diagram. A UML Use Case stencil is open in the Shapes window.
Drag a Subsystem shape onto the drawing page. The subsystem can represent your entire system or a major component.
To resize the subsystem, select the shape, and then drag a selection handle.
Drag Use Case shapes from the UML Use Case stencil and place them inside the subsystem boundary, and then drag Actor shapes to the outside of the subsystem boundary.
Use connector shapes to indicate relationships between shapes in the diagram. There are five connectors available:
Example: To indicate a relationship between an actor and a use case
In a use case diagram, drag an Association connector shape onto the drawing page.
Glue one endpoint of the Association shape to a connection point on an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.
Open Visio for the web.
In the Gallery, scroll down to the UML Use Case row, about midway down the page.
The first item in the row represents a blank template plus the companion stencil. The other items in the row are sample diagrams that have some shapes already drawn to help you get started quickly.
The new diagram, with the related stencil, opens in your browser.
Drag a Subsystem shape onto the drawing page. The subsystem can represent your entire system or a major component.
To resize the subsystem, select the shape, and then drag a selection handle.
Drag Use Case shapes from the Use Case stencil and place them inside the subsystem boundary
Drag Actor shapes to the outside of the subsystem boundary.
Use connector shapes to indicate relationships between shapes in the diagram. There are five connectors available:
Example: To indicate a relationship between an actor and a use case
In a use case diagram, drag an Association connector shape onto the drawing page.
Glue one endpoint of the Association shape to a connection point on an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.
On the File tab, point to New.
in the Search box, type UML use case.
In the dialog box, select the blank template. Then select either Metric Units or US Units.
The diagram opens. You should see the Shapes window next to the diagram. A UML Use Case stencil is open in the Shapes window.
To resize the subsystem, select the shape, and then drag a selection handle.
Drag Use Case shapes from the UML Use Case stencil and place them inside the subsystem boundary, and then drag Actor shapes to the outside of the subsystem boundary.
Use connector shapes to indicate relationships between shapes in the diagram. There are five connectors available:
Example: To indicate a relationship between an actor and a use case
In a use case diagram, drag an Association connector shape onto the drawing page.
Glue one endpoint of the Association shape to a connection point on an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.
On the File tab, point to New.
A blank page appears, and the UML Use Case stencil becomes the top-most stencil. An icon representing the diagram is added to the tree view.
Note: If the tree view is not visible, on the UML tab, in the Show/Hide group, select Model Explorer.
To indicate a System Boundary in a use case diagram
Drag a System Boundary shape onto the drawing page.
To resize the system boundary, select the shape, and then drag a selection handle.
Drag Use Case shapes from the Use Case stencil and place them inside the system boundary, and then drag Actor shapes to the outside of the system boundary.
Use Communicates shapes to indicate relationships between use cases and actors.
To indicate a relationship between an actor and a use case
Glue one endpoint of the Communicates shape to a connection point on an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.
If you want to add an arrow to indicate the flow of information, do the following:
Use Uses and Extends shapes to indicate the relationships between use cases.
To indicate a uses relationship between two use cases
Glue the Uses endpoint without an arrowhead to a connection point on the Use Case shape that uses the behavior of the other use case.
To indicate an extends relationship between two use cases
Glue the Extends endpoint without an arrowhead to a connection point on the use case providing the extension.
Save the diagram.
A blank page appears, and the UML Use Case stencil becomes the top-most stencil. An icon representing the diagram is added to the tree view.
To indicate a system boundary in a use case diagram
Drag a System Boundary shape onto the drawing page.
To resize the system boundary, select the shape, and then drag a selection handle.
Drag Use Case shapes from the Use Case stencil and place them inside the system boundary, and then drag Actor shapes to the outside of the system boundary.
Use Communicates shapes to indicate relationships between use cases and actors.
To indicate a relationship between an actor and a use case
Glue one endpoint of the Communicates shape to a connection point on an Actor shape. Glue the other endpoint to a connection point on a Use Case shape.
If you want to add an arrow to indicate the flow of information, do the following:
Use Uses and Extends shapes to indicate the relationships between use cases.
To indicate a uses relationship between two use cases
Glue the Uses endpoint without an arrowhead to a connection point on the Use Case shape that uses the behavior of the other use case.
To indicate an extends relationship between two use cases
Glue the Extends endpoint without an arrowhead to a connection point on the use case providing the extension.
Save the diagram.
Tại Sao Phải Có Use Case Diagram Trong Uml
Nhìn vào hình ảnh sau đây ắt hẳn các bạn có thể thấy một phần chính mình trong đó. Những thứ ngớ ngẩn ấy tưởng chừng không thể xảy ra nhưng nó vẫn chực chờ xuất hiện trong những hiểu lầm của team dev và khách hàng. Vì thế Usecase Diagram sinh ra để phần nào giải quyết vấn đề ấy.
Usecase Diagram là gì?
Usecase Diagram được hiểu là sơ đồ tính năng của sản phẩm cung cấp cho người dùng. Bản vẽ này sẽ cho người dùng hiểu được sản phẩm này cung cấp những tính năng gì cho người dùng, hoặc người dùng có thể làm được gì với nó.
Actor
Actor trong UML được thể hiện bởi một stickman. Để chỉ một người nào đó tương tác với phần mềm (lấy ví dụ bạn là người ấn vào các nút trên remote, bạn là một actor).
Lưu ý: Actor không phải là một thành phần của phần mềm.
Usecase
Usecase là các chức năng của phần mềm được actor sử dụng (giống như các nút bấm trên remote điều hòa)
Quan hệ
Association
Thường dùng để chỉ mối quan hệ giữa Actor với Use Case hoặc giữa các Use Case với nhau.
Generalization
Là quan hệ kế thừa, chỉ quan hệ giữa đối tượng con với đối tượng cha (thường dùng cho Actor)
“Con to hơn cha (về khả năng) vì thế con làm đc tất cả cha làm và hơn thế nữa”Ví dụ: Trong trang chúng tôi Contributor cũng là một User, có thể làm các việc như đăng nhập, học tập, codewar,… ngoài ra còn có thể đăng bài luyện tập, đăng blog,…
Include
Thường dùng giữa các Use Case. Nó mô tả việc một Use Case lớn được chia ra thành các Use Case nhỏ để dễ cài đặt (module hóa) hoặc thể hiện sự dùng lại.
Trong Include, hành động ở đuôi mũi tên (verify captcha) phải được hoàn thành trước khi thực hiện hành động ở đầu mũi tên (login)
Extend
Extend dùng để mô tả quan hệ giữa 2 Use Case. Quan hệ Extend được sử dụng khi có một Use Case được tạo ra để bổ sung chức năng cho một Use Case có sẵn và được sử dụng trong một điều kiện nhất định nào đó.
Trong Extend, hành động có thể có hoặc có thể không thực hiện cũng được.
Extension point: dùng để ghi chú khi nào hành động trong quan hệ Extend được thực hiện.
System Boundary
Được hiểu đơn giản là đường biên, được sử dụng để xác định phạm vi của thiết kế. Các đối tượng nằm ngoài phạm vi này có tương tác với phần mềm có thể được xem là Actor.
Quay lại ví dụ về cái remote cho dễ hiểu, bạn chỉ có thể bấm vào các nút nằm trong remote thôi. Nếu bạn bấm vào tường rồi yêu cầu điều hòa thực hiện một chức năng thì điều đó thật vô lý.
Ứng dụng
Thiết kế hệ thống.
Làm cơ sở cho việc phát triển, kiểm tra các bản vẽ như Class Diagram, Activity Diagram, Sequence Diagram, Component Diagram.
Làm cơ sở để giao tiếp với khách hàng.
Hỗ trợ việc kiểm thử tính năng, chất lượng,….
Tạm kết
Đón xem kỳ sau: Thực hiện vẽ một Use Case Diagram với Star UML
How To Draw Use Case Diagram?
How to Draw Use Case Diagram?
Use case diagram is a kind of UML diagram that enables you to model system functions (i.e. goals) as well as the actors that interact with those functions. You can draw use case diagrams in Visual Paradigm as well as to document the use case scenario of use cases using the flow-of-events editor. In this page, you will see how to draw use case diagram with the UML tool.
Creating a use case diagram
Perform the steps below to create a UML use case diagram in Visual Paradigm.
In the New Diagram window, select Use Case Diagram.
Enter the diagram name and description. The Location field enables you to select a model to store the diagram.
Drawing a system
Drawing an
actor
Drawing a use case
Besides creating a use case through diagram toolbar, you can also create it through Resource Catalog:
Move the mouse over a source shape (e.g. an
actor
).
Press on the Resource Catalog button and drag it out.
Release the mouse button until it reaches your preferred place.
The source shape and the newly created use case are connected. Finally, name the newly created use case.
Line wrapping use case name
If a use case is too wide, you may resize it by dragging the filled selectors for a better outlook. As a result, the name of use case will be line-wrapped automatically.
NOTE: Alternatively, you can press Alt + Enter to force a new line.
Structuring use cases with package
You can organize use cases with package when there are many of them on the diagram.
Select Package on the diagram toolbar.
Drag the mouse to create a package surrounding those use cases.
Finally, name the package.
Drawing business use case
The uml diagram tool also supports the representation of business actor and use case. To show an ordinary use case as business use case:
After selected, an extra slash will be shown on the left edge of the use case.
Related Resources
The following resources may help you to learn more about the topic discussed in this page.
Uml Deployment Diagrams Overview Of Graphical Notation.
Deployment diagram shows execution architecture of systems that represent the assignment (deployment) of software artifacts to deployment targets (usually nodes).
Nodes represent either hardware devices or software execution environments. They could be connected through communication paths to create network systems of arbitrary complexity. Artifacts represent concrete elements in the physical world that are the result of a development process and are deployed on nodes.
Note, that components were directly deployed to nodes in UML 1.x deployment diagrams. In UML 2.x artifacts are deployed to nodes, and artifacts could manifest (implement) components. So components are now deployed to nodes indirectly through artifacts.
The following nodes and edges are typically drawn in a UML deployment diagram: deployment, artifact, association between artifacts, dependency between artifacts, component, manifestation, node, device, execution environment, composition of nodes, communication path, deployment specification, deployment specification dependency, deployment specification association.
You can find some deployment diagrams examples here:
Manifestation
Manifestation is an abstraction relationship which represents concrete physical rendering (implementation) of one or more model elements by an artifact or utilization of the model elements in the construction or generation of the artifact. An artifact manifests one or more model elements.
Note, that since UML 2.0 artifacts can manifest any packageable elements, not just components as it was in previous versions of UML.
The artifact owns the manifestations, each representing the utilization of a packageable element.
Specific profiles are expected to stereotype the manifestation relationship to indicate particular forms of manifestation. For example, ” tool generated” and ” custom code ” might be two manifestations for different classes embodied in an artifact.
A manifestation is notated in the same way as abstraction, i.e. as a dashed line with an open arrow head directed from artifact to packageable element, (e.g. to component or package) and is labeled with the keyword ” manifest “.
EJB component UserService and skeleton of web services are manifested (implemented) by EJB module chúng tôi artifact
In UML 1.x, the concept of manifestation was referred to as implementation and annotated as ” implement“. Since this was one of the many uses of the word “implementation” this has been replaced in UML 2.x by ” manifest “.
Deployment Target
Artifacts are deployed to deployment targets. Deployment target is the location for a deployed artifact.
UML 2.4 definition of deployment target
Instance specification was extended in UML 2.0 to allow instance of a node to be deployment target in a deployment relationship.
Property was also extended in UML 2.0 with the capability of being a deployment target in a deployment relationship. This enables modeling the deployment to hierarchical nodes that have properties functioning as internal parts.
Deployment target owns the set of deployments that target it.
Deployment target has no specific notation by itself, see notations for subclasses.
Node
Node is a deployment target which represents computational resource upon which artifacts may be deployed for execution.
Node is shown as a perspective, 3-dimensional view of a cube.
Application Server Node
Node is associated with deployments of artifacts and indirectly with packageable elements that are involved in the manifestations by the artifact that is deployed on the node.
Nodes can be interconnected with communication paths. Communication paths can be defined between nodes such as application server and database server to define the possible communication paths between the nodes. Specific network topologies can then be defined through links between node instances.
Node is specialized by:
Hierarchical Node
Hierarchical nodes can be modeled using composition or by defining an internal structure. Internal structure of the node is defined in terms of parts and connectors. Parts of the node could be only nodes.
Application server box runs several web servers and J2EE servers
Execution environment is usually part of a general node or “device” which represents the physical hardware environment on which this execution environment resides. Execution environments can be nested (e.g., a database execution environment may be nested in an operating system execution environment).
Several execution environments nested into server device
Execution environment instances are assigned to node instances by using composite associations between nodes and execution environments, where the execution environment plays the role of the part.
Device
A device is a node which represents a physical computational resource with processing capability upon which artifacts may be deployed for execution.
A device is rendered as a node (perspective, 3-dimensional view of a cube) annotated with keyword ” device “.
Application Server device
UML provides no standard stereotypes for devices. Examples of non-normative stereotypes for devices are:
“application server”
“client workstation”
“mobile device”
“embedded device”
Device may be depicted using custom icon. Profiles, stereotypes, and tagged values could be used to provide custom icons and properties for the devices.
Application Server device depicted using custom icon
Computer stereotype with tags applied to Device class.
Database Server device depicted using custom icon
Mobile smartphone device depicted using custom icon
Devices may be complex (i.e., they may consist of other devices) where a physical machine is decomposed into its elements, either through namespace ownership or through attributes that are typed by devices.
Execution Environment
An execution environment is a (software) node that offers an execution environment for specific types of components that are deployed on it in the form of executable artifacts. Components of the appropriate type are deployed to specific execution environments.
Execution environment implements a standard set of services that components require at execution time (at the modeling level these services are usually implicit). For each deployment of component, aspects of these services may be determined by properties in a deployment specification for a particular kind of execution environment.
Execution environment is notated the same way as a node (perspective, 3-dimensional view of a cube), annotated with the standard UML stereotype ” executionEnvironment “.
Execution environment – J2EE Container
This ” executionEnvironment ” is pesky sesquipedalian to use. UML provides no other standard stereotypes for execution environments. Examples of reasonable non-normative stereotypes are:
“OS”
“workflow engine”
“database system”
“J2EE container”
“web server”
“web browser”
Linux Operating System Execution Environment
Oracle 10g DBMS Execution Environment
An execution environment can optionally have an explicit interface of system level services that can be used by the deployed elements, in those cases where the modeler wants to make the execution environment software execution environment services explicit.
Communication Path
A communication path is association between two deployment targets, through which they are able to exchange signals and messages.
Communication path is notated as association, and it has no additional notation compared to association.
Communication path between several application servers and database servers.
Note, that when deployment targets are some physical devices, communication path will typically represent a physical connection between the nodes.
Gigabit Ethernet as communication path between application and database servers.
When deployment targets are execution environments, communication path will typically represent some protocol.
TCP/IP protocol as communication path between J2EE server and database system.
Deployment
A deployment is a dependency relationship which describes allocation (deployment) of an artifact to a deployment target. Deployment could be also defined at instance level – as allocation of specific artifact instance to the specific instance of deployment target.
A component deployment is deployment of one or more artifacts or artifact instances, optionally parameterized by a deployment specification.
It is not very clear why UML defines deployment as a dependency, and not as an association or just a directed relationship. The major contradiction is that dependency in UML does not have any runtime implications, and is defined in terms of the model elements, not in terms of their instances. At the same time UML 2.4 allows and shows examples of instances of artifacts deployed to instances of nodes.
Deployment could be shown as a dependency that is drawn from the artifact (supplier) to the deployment target (client) and is labeled with ” deploy “. Note, that dependency usually points from the client to the supplier, i.e. in the direction opposite to what is recommended by UML 2.4 for deployment. On the other hand, UML specification allows to change direction for a dependency based on user’s stipulations.
J2EE web application archive portfolio.war deployed on Apache Tomcat JSP server.
At the “instance level” instances of artifacts could be deployed to specific instances of the deployment target. The underlining of the name of artifact instance may be omitted.
J2EE web application archive chúng tôi deployed on two instances of Apache Tomcat JSP server – psrv_023 and psrv_037.
For modeling complex deployment target models consisting of nodes with a composite structure defined through “parts,” a property (that functions as a part) may also be the target of a deployment.
Deployment could be shown with deployed artifacts contained by a deployment target.
The chúng tôi artifact deployed on application server.
Deployment could be shown using textual list of deployed artifacts within a deployment target.
The chúng tôi chúng tôi chúng tôi artifacts deployed in J2EE 1.4 container.
Deployment could be shown within a rectangular frame with deployment name in a compartment in the upper left corner. The long form name for the diagram heading is deployment and abbreviated form is dep.
User Services deployment shown in the diagram frame.
Deployment Specification
A deployment specification is an artifact that specifies a set of deployment properties that determine execution parameters of a component artifact that is deployed on a node. A deployment specification can be aimed at a specific type of container for components.
A deployment specification is a general mechanism to parameterize a deployment relationship, as is common in various hardware and software technologies. The deployment specification element is expected to be extended in specific component profiles. Non-normative examples of the standard stereotypes that a profile might add to deployment specification are, for example, ” concurrencyMode” with tagged values {thread, process, none}, or ” transactionMode ” with tagged values {transaction, nestedTransaction, none}.
A deployment specification at specification level is rendered as a classifier rectangle with optional deployment properties in a compartment.
The chúng tôi deployment specification
An artifact that reifies or implements deployment specification properties at instance level is a deployment descriptor. A deployment descriptor is rendered as a classifier rectangle with the name underlined and with deployment properties having specific values in a compartment.
The chúng tôi deployment descriptor
An instance of a deployment specification with specific values for deployment properties may be contained in a complex artifact.
Deployment Specification Dependency
A deployment specification could be displayed as a classifier rectangle attached to a component artifact using a regular dependency arrow pointing to deployed artifact.
The chúng tôi deployment specification for chúng tôi artifact.
Deployment Specification Association
Deployment specification could be associated with the deployment of a component artifact on a node. In this case deployment specification could be shown as a classifier rectangle attached to the deployment.
Note, that UML 2.4 specification shows this association as a dashed line (while association is normally displayed as solid line.)
The chúng tôi deployment specification attached to deployment.
Bạn đang đọc nội dung bài viết Create A Uml Use Case Diagram trên website Techcombanktower.com. Hy vọng một phần nào đó những thông tin mà chúng tôi đã cung cấp là rất hữu ích với bạn. Nếu nội dung bài viết hay, ý nghĩa bạn hãy chia sẻ với bạn bè của mình và luôn theo dõi, ủng hộ chúng tôi để cập nhật những thông tin mới nhất. Chúc bạn một ngày tốt lành!