Use Case of Blog

Use case on blog, ok here I will explain about what we can do in our blog. Before we go to the explanation, the tools or software that I use to create this picture is Astah. Astah is like software that we can make a description about the process that include in every case. If you know about software of Visio that include in Microsoft office?? Yeah, the function of use case almost same with Visio but with use case we can describe with design that more easy to understand. I think that’s all about use case, so I will continue to the next or point of this article.

A use-case model is a model of how different types of users interact with the system to solve a problem.  As such, it describes the goals of the users, the interactions between the users and the system, and the required behaviour of the system in satisfying these goals.

A use-case model consists of a number of model elements.  The most important model elements are: use cases, actors and the relationships between them. 

A use-case diagram is used to graphically depict a subset of the model to simplify communications.  There will typically be several use-case diagrams associated with a given model, each showing a subset of the model elements relevant for a particular purpose.  The same model element may be shown on several use-case diagrams, but each instance must be consistent.  If tools are used to maintain the use-case model, this consistency constraint is automated so that any changes to the model element (changing the name for example) will be automatically reflected on every use-case diagram that shows that element.

Well guys, here I will explain about use case of blog that I made with my own self. You can live your comment if you disagree with my argument. Ok let’s begin:

First you have to know about the components that include in use case:

Actor: 

A model element representing each actor. Properties include the actors name and brief description.

Extend:

Is used to include common behaviour from an include optional behaviour from an extending use case in an include use case into a base use case in order to support re-use of common behaviour.

Generalisation:

A relationship between actors to support re-use of common properties.

Include:

Is used  to include common behaviour from an included use case into a base use case in order to support re-use of common behaviour.

Use case: 

A model element representing each use case. Properties include use case into a base use case in order to support re-use of common behaviour.

And I will explain each use case that I can use to describe about the situation in blog:

Manage Posting: for manage posting we as the author, we can do some actions like input edit and delete our posting.

Manage Template: for manage template we can edit our template as we want.

Manage Profile: for manage profile we can input, edit and delete our profile.

Logon: logon is operate by admin of blog that he will check true or false of password and email that actor use to logon.

Manage Comment: Also doing by admin, he will show or approve everything that enters in blog.

Read Article: As visitor we can read the article and doing some actions like leave a comment, reply and delete our comment.

characteristics:
- Use cases are interaction or dialogue between the system and actors, including the exchange of messages and actions performed by the system.
- Use cases initiated by the actor and may involve the role of other actors. Use cases should provide a minimum value to the actor.
- Use cases can have an extension that defines specific actions in interactions or other use case may be inserted.
- Use case class has an object called a use case scenario. Scenarios expressed sequences and single action message.

Use case is the circuit / description of a group of inter-related and form a system of regularly conducted or supervised by an actor. Use case are used to establish behavior of objects / things in a model and in Realized by a collaboration. General use case is described by an ellipse with a solid line, usually containing nama.Use case describes the process of the system (system requirements from the user perspective).
In general use case is:
Patterns of system behavior
Sequence of related transactions performed by an actor
Use case diagram consists of
Use case
Actors
Relationship
System boundary boxes (optional)
Packages (optional)