BLOG USE CASE

From the picture above, there are two actors use case that user and admin, the admin duties here are only for monitoring data blogger. Here also if the user wants to log on, the user must have email and password to login to the blog, because to do manage profile, manage templates, manage comments and manage posts a user must log in first. Here the user can do several things such as manage profile, manage templates, manage comments, manage posts. In the manage profile there are several items such as delete profile, edit your profile and add profile. In the manage templates there are a few items such as templates, delete the template, edit the template. In the manage comment there are a few items such as replay, add comment comment, and delete the last comment and manage post there are a few items like edit posts, delete posts, and add a post. Use case diagrams describe the functionality expected from a system. That are emphasized are the "what" that made the system, and not the "how". A use case represents an interaction between the actors and the system. Use case is a particular job, for example, to log into the system, to create a shopping list, and so on. A/an actor is a human or machine entity that interacts with the system to perform specific jobs.

Manage Posting column is used to set some post of the article being made. In the Post there are some usecase chart include:
-Add the post to make a new post.
-Edit post to change the post that has been made.
-Delete to delete post.
-Send to draft to save the post to draft.

Manage Profile column is used to set the profile of the author. In the Manage Profile there are several usecase chart include:
-Add Profile to create a new profile
-Edit Profile to change the content of a profile has been created
-Delete Profile to remove the contents of the created profile

Column of the Manage Templates used to manage Template Design on the blog. In the Manage Templates there are some usecase chart include:


-Add the Template to use the new template has been provided
-Edit the Template to change the template
-Delete-the Template to remove the template that will be used
Manage Columns Comments for arranging comment. In the Manage Comments chart usecase some of them:
-Add Comment to add a comment on the blog.
-Edit to change the comments on the blog.
-Delete to delete comments on the blog.
Use case consists of
• Actor: user system/something that interacts with the system represents the message, not the individual user.
• Use case: how to use of the system by specific actors.
Use case Diagram:
• Is one of the diagrams to model aspects of the behavior of the system.
• Each shows a set of use case, actors, and their relationship.
• To visualize and document the needs of system behavior.
• Engage: System, actors, use case, and relationships.
The main purpose was to model a use case:
• Description of the functional needs and decide on the system.
• Provide clear and consistent descriptions of what to do.
• Provide the basis for conducting the testing system that verifies system.
• Provides the ability to track the analistis function needs to be classes, operations, and actual system.
Characteristics of the use case:
• A pattern of conduct that must be met by the system
• Transaction Sequence connected which is done the actors and the system
• Provide something valuable for the user (information)
The usefulness of the use case:
• Capture System requirements
• Communicating with the domain experts and end users problems
• Assessment System
A use case diagram at its simplest is a representation of a user's interaction with the system and depicting the specifications of a use case. A use case diagram can portray the different types of users of a system and the various ways that they interact with the system. This type of diagram is typically used in conjunction with the textual use case and will often be accompanied by other types of.
Use case class used to model and stating the unit functions/services provided by the system (or system parts: subsystems or classes) to the wearer.
● Use case can be covered with limits on a system that is labeled name system.
● Use case is something that provides measurable results to users or external systems.
Characteristics :
1 . Usecases are interaction or dialogue between the system and actors , including the exchange of messages and actions performed by the system .
2 . Usecases initiated by the actor and may involve the role of other actors . Usecases should provide a minimum value to the actor .
3 . Usecases have extensions that define specific actions in interactions or other usecase may be inserted .
4 . Usecase classes have an object called a use case scenario . Scenarios expressed sequences and single action message .