Class Diagram Blog

The Class diagram is a diagam that used to show some class and packages that exist in the system/software we are using. Class diagram gives us an overview (diagram static) about the system/software and relas-relation that exists therein.
Definition Of The Class Diagram
Class is a collection of objects with a common structure and common behavior, public relations, and semantic/common words. Class-class determined/found by way of checking objects in sequence diagrams and collaboration diagrams. A class is represented as a square with three sections of the room. Class should be named using the noun corresponding to domain/section/group (Jeffery l. Whitten et al, 2004).
The Class Diagram is a diagram that shows the existing classes of a system and its relationship to logic. Class diagram describes the static structure of a system. Therefore the class diagram is the backbone or the strength of the Foundation of almost every object-oriented methods including UML (Henderi, 2008). While according to (Jeffery l. Whitten et al. 2004: 432) class diagram is a graphical picture of the structure of a static object system, indicating the classes of objects that make up a system and also the relationship between the object class.
The elements class diagram eleman in UML modeling consists of: classes, class structure, the nature of class (the class behavior), assembly/combined (association), gathering/Union (agregation), dependence (dependency), its relationships, diversity and navigation, indicators and role name (roles/task name).
Class diagram symbols
1. Class: Class is a block-block builders in object-oriented programming.A class described as a box which is divided into 3 parts. The top is part of the name of the class. The middle section defines the property/attribute class. The final section defines a clas of methodmethod.
Association: an association is a relationship between the 2 most common class and denoted by a line which connects between the 2 class. These lines could represent the types of relationship and also can display a multiplicity of laws on a relationship.(Example: One-to-one, one-to-many, many-to-many).
Composition: If a class can not stand alone and must be part of another class, then the class has a relation Composition of class where he is dependent. A composition relationship is depicted as a line with a parallelogram-shaped tip contains/solid.
Dependency: Sometimes a class using the class to another. This is called a dependency. Generally the use of dependency is used to indicate the operation on a class that uses a class to another. A dependency is represented as an arrow bertitik-titik.
Aggregation Aggregation: indicates the overall relationship and commonly referred to as relation.
The Class has three principal areas

The name (and stereotype)
Attribute
Method
Attribut Class
Attributes and methods can have one of the following properties:
Private, it cannot be called from outside the class in question
Protected, can only be called by the class in question and children who have inherited
Public, can be invoked by anyone
Component Class Diagram
1. Subsystem
While a package is a mechanism for organizing the common element-element models, subsystems describes a unit of behavior in physical systems.
2. Class
A class is the description for a set of objects with similar structure, behavior, and behavior/relationship/relation.
3. the Interface
An interface is to specify an externally-visible operations of a class, component, or other penggolong/classifier (including subsystems) without the specification of the internal structure.
4. Signal
Signal is one which describes the specification of asynchronous stimulus communicated between instances.
5. Exception
An Exception is a signal raised by behavior in a when an error occurs.
6. Port
Port is a structural one peng-class, which defines a difference that shows interactions between peng-class's and their environment or between (behavior) peng-class and its internal parts.
The class diagram is the main building block of object oriented modelling. It is used both for general conceptual modelling of the systematics of the application, and for detailed modelling translating the models into programming code. Class diagrams can also be used for data modeling.[1] The classes in a class diagram represent both the main objects, interactions in the application and the classes to be programmed.
Determine the class
A good way to find classes were started from watching the flow of events ( flow of events ) of a use case . Note the noun in the flow of events , may be one of the following four points .
1 . Actor
2 . class
3 . Attributes of the class
4 . Expression , not the actor , not a class , and not attributes .
By selecting the object in the flow of events , classes can be found in the system . Other alternatives , can test objects in sequence diagrams and collaboration diagrams .
There are two common ways of defining sequence of inter -related classes in the class diagram and sequence diagram or a collaboration diagram . The first , by creating a sequence diagram or a collaboration diagram first . Then proceeded to create the class diagram . In contrast , the second , is to find classes and create class diagrams first, then use a stretcher classes as " Dictionary " objects and their relationships to create a sequence diagram or a collaboration diagram .
Elements-elements relevant in modeling UML class diagram consists of: classes, class structure, the nature of class (class behavior), association / union (association), collection / unity (aggregation), dependency (dependency), derivatives relations, diversity and navigation indicators, and role name (role / task name).
In the design of a system, a number of classes are identified and grouped together in a class diagram which helps to determine the static relations between those objects. With detailed modelling, the classes of the conceptual design are often split into a number of subclasses.
In order to further describe the behaviour of systems, these class diagrams can be complemented by state diagram or UML state machine.[2]
In software engineering, a class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system's classes, their attributes, operations (or methods), and the relationships among objects.

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 .