What is Uml diagram – Troubleinthepeace


Looking at the following image, you can probably see a part of yourself in it. Those silly things seem impossible but it is still waiting to appear in the misunderstandings of the dev team and the customer. So Usecase Diagram was born to partly solve that problem.

You are viewing: What is Uml diagram

*

In this article, we also learn about Usecase Diagram and use Star UML to demo some functions of a “Cforum” created by us.

What is Usecase Diagram?

Usecase Diagram is understood as the feature diagram of the product provided to the user. This drawing will let the user understand what features this product provides to the user, or what the user can do with it.

In life, we can see a lot of similar things, maybe it’s the control panel in the car cabin, train, plane, ATM button system, …. In this article, I will give an example around the air conditioner remote pictured below.

*

Actor

*

Actor in UML represented by a stickman. To indicate someone to interact with the software (for example, you are the one pressing the buttons on the remote, you are the actor).

Actoris an entity that requires software to perform a function to help get their job done.

One Usecase Diagram there can be many Actor.

A user can also perform many functions of the Actor different.Usually a noun

Note:Actor is not part of the software.

Usecase

*

Usecase are the functions of the software used by the actor (like the buttons on the air conditioner remote)

Relationship

Association

*

Usually used to indicate the relationship between Actorwith Use Case or between theUse Casetogether.

Generalization

*

Is an inheritance relationship, only the relationship between the child object and the parent object (usually used for Actor)

“I’m bigger than you (in terms of ability) so I can do everything you do and more”For example: In the websitegiaidap.com Contributor is also a User, can do things like login, study, codewar, … in addition, can also post exercises, blogs, …

Include

*

Usually used between Use Case.It describes a Use Case Larger use cases are broken down into small use cases for ease of implementation (modularization) or to demonstrate reuse.

See also: What is Art – Art… for what

In Includeaction at the end of the arrow (verify captcha)right is completed before performing the action at the arrowhead (login)

Extend

*

Extend Used to describe the relationship between two use cases. Relationship Extend Used when a Use Case is created to add functionality to an existing Use Case and is used in a certain condition.

In Extendthe action may or may not be performed.

Extension point: used to note when to act in a relationship Extend be done.

System Boundary

*

Simply understood as the border, used to define the scope of the design. Objects outside this scope that interact with the software may be considered Actor.

Going back to the example of the remote for easy understanding, you can only press the buttons located in the remote. If you click on the wall and then ask the air conditioner to perform a function, it makes no sense.

Application

System design.

As a basis for developing, checking drawings such as Class Diagram, Activity Diagram, Sequence Diagram, Component Diagram.

Serve as a basis for communicating with customers.

Support testing features, quality, ….

See also: What is Ssid – What is Ssid Service Set Identifier

Ending

In this article, I only encapsulate the content in the theoretical part. In the next post, I will talk about how to draw a Use Case Diagram with CForum made up by myself as well as the errors you often encounter.

Source: internet

About Troubleinthepeace

Troubleinthepeace specializing in synthesizing information about daily life activities

View all posts by Troubleinthepeace →

Trả lời

Email của bạn sẽ không được hiển thị công khai.