all of my life

Class diagrams for the blog will be described in the explanation this time. Class diagrams for a blog in which business processes or the plot has been described in the use case diagram in the previous blog we will discuss the meaning of the first class diagram is used as a knowledge base.

The most used, Instant diagrams of the Unified Modeling Language. Models the static design view of a system. Also useful in modeling business objects. Specifying and used for the structure (attributes and operations), relationships between classes and interfaces that form the foundation of the system architecture. Primary codes diagram for generating models from Unified Modeling Language. Class is a description of assets of objects that share the same attributes, operations, relationships and semantics. A unit of software that implements one or more interfaces, and graphically rendered usually Including a name, attributes and operations. Class of noation include three components is the top compartment holds the class name and other general properties of the class, the second one is the middle compartment holds a list of attributes, and the last is the buttom compartment holds a list of operations. And the alternative presentation style are the attributes compartment suppress and suppress the operation compartment. And for classes one we can use stereotypes. Stereotypes is the list of attributes of operations in a class may be organized using stereotypes. The stereotypes is a new class of a methamodel element introduced at the modeling time. It’s represents a sub class of an existing metamodel element with the same form where attributes and operations but with different intent. And also motation – the name of a metamodel element within the matched guillemets e.g. <<changeintent>>.

Class diagrams provide a comprehensive view of the system by showing the classes and their relationships. Class diagrams are static; illustrates the relationship is not what happens what happens if they are related.

Class diagram has three kinds of relationships, as follows:

• Association

A relationship between the parts of the two classes. Occurs association between two classes if one part of the class knowing that others in doing an activity. In the diagram, an association is a link connecting two classes.

• Aggregation

An association in which one class is part of a collection. Aggregation has a center point which covers the entire piece. For example: OrderDetail is a collection of Order.

 

• Generalization

A relationship derived by assuming one class is a superclass (super class) from other classes. Generalization has centered on the superclass level.

Example: ManagePosting is a super class of input New posts, edit posts, and delete posts.

For added that the association had 2 points can have a label to explain the association.

Example: Posting is a line item for each manage post.

Navigability arrows (setting flow direction) in an association which describes the direction of association can be wired or organized. As in the example are:

Order Item Detail has. Association without the direction of a bidirectional or commonly referred to as back and forth.

Others point the multiplicity of the association is likely part of a figure with a single instance of class relations Which was the point of the other part.

Multiplicity is a single number called single number or range of number that is a limitation. In the same example for this is only for one user for every single google adsense.

Multiplicity syntax that can be used are as follows:

a. 0 .......... 1: Zero or more, explain the notation nm n to m

b. 0 .. *: Not up to the range of parts including zero

c. 1: Exactly one piece

d. 1 .......... *: At least only one part.

e. 1 .......... 1: One

f. *: Unlimited number

g. <literal>: Exact number

h. <literal> .. *: Exact number or more

i. <literal> .. <literal>: Specified range

j. <literal>. <literal>, <literal>: Specified range or exact number

k. <literal> .. <literal>, <literal> .. <literal>: Multiple specified ranges

For each class has a Class diagram, association and multiplicity. And while navigability ie, flow or direction and role of the activity is not required opitional meaning. And for an explanation of the class diagram as shown above on the blog are as follows,

In the picture on the blog Claas diagram above describes the relationship that occurs during user using blogs or what the user can do on their blog. Relationships that exist in the case of blogs, namely:

Association arising from the relationship between the two classes in this case there are eight relations association. We can see an example on manage posts, manage domain, manage widgets, manage design blogs, manage profile, manage monetize blogs, view and manage follower posts related to login. In this case the association between two classes where one part of the class megetahui others do a kegiata which is essentially a connecting link between the two classes. Aggregation occurs in the relationship depicted between the posts with managing posts, manage widgets with widget, to manage design blog design blogs, manage follower to follower, and to manage the user profile. Sedngkan, Generalization contained in the post is a superclass of the input new posts, edit and delete posts.

In the picture above there are sixteen class described comprising, play, manage profile, user, manage followers, follower, view posts, manage design blog, design blogs, manage widgets, widgets, connect database (connectDB), manage domain, manage posts, posts, login, manage an monetize blogs.

For class notation in class diagrams for blog images depicted are five class notation. Class notation which is divided into three compartments as in, to the top with the class name to play and there are general properties of a class that is managing the post, and then a middle compartment with attributes manage input posting new posts, edit posts and delete posts. And the last compartment is the buttom compartment holds a list of operations that isiPosting  set_isiPosting and get_isiPosting, and tgl_isiPosting  set_tglPosting and get_tglPosting. And the other one for example manage widget (class name or top compartment), widget (middle compartment), and idWidget include of se_idWidget and get_idWidget (last compartment).