Class Diagram of Blog

        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.
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.
Class diagrams are visual representations of the static structure and composition of a particular system using the conventions set by the Unified Modeling Language (UML). Out of all the UML diagram types it is one of the most used ones. System designers use class diagrams as a way of simplifying how objects in a system interact with each other. Using class diagrams, it is easier to describe all the classes, packages, and interfaces that constitute a system and how these components are interrelated. For example, a simple class diagram may be used to show how an organization such as a convenient store chain is set up. On the other hand, precisely detailed class diagrams can readily be used as the primary reference for translating the designed system into a programming code.
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.

Use Case Diagram

Use Case Definition

Use-case diagram is a diagram of the UML model is used to describe the functional requirement expected of a system. Use-case diagrams insists on the "who" is doing "what" in the environment of the system software will be built. Use-case diagrams actually consists of two major parts; the first is a use case diagram (use case dependencies including images) and use case description.

Use-case diagram is a graphical representation of some or all of the actor, the use-case, and the interactions among these components that introduce a system that will be built. Use-case diagrams describe the benefits of a system when viewed according to the views of people who are outside the system. This Diagram shows the functionality of a system or class and how these systems interact with the outside world.

Use-case diagrams can be used during the analysis process to capture system and the requirement to understand how the system is supposed to work. During the design phase, the use-case diagram acts to set behavior (behavior) when the system is implemented. In a model there may be one or more of the use-case diagram. Needs or requirements system is what functionality should be provided by the system are then documented in the use-case model which describes the expected system functions (use-case), and surrounds them (actor), as well as the relationship between actor and use-case (use-case diagram) itself.

● 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:

– Use cases is the interaction or dialogue between system and actor, including the exchange of messages and the actions taken by the system.

– Use cases initiated by the actor and the role may involve other actors. Use cases should provide a minimum of one actor.

– Use cases could have an extension which defines special measures in interaction or another use case may be inserted.

– Use case class has an object called use case scenarios. The scenario stated order message and a single action.

Here's how to draw a use-case diagram:

Note:

Before making the use-case diagram, we recommend that you start with making the FDD first. This is just to help identify the processes in the system.

1) Begin by registering an actor associated with the Use-case, as both the sender and the receiver.

2) component in the use-case diagram is the Use-case Descriptions, Use-case and actors participating and its role.

3) Discover the semantic relationships demonstrate dependency between two Use-case. If the Use-case "A" changes can result in a Use-case "B" will be changed anyway.

There are 2 kinds of dependency to note that include and extend.

Dependency include:

A Use-case can include updating the functionality of Use-case to another as part of the process in itself. In general it is assumed that the Use-case that you include will be called every time the Use-case is to include executed normally. A Use-case can include by more than one Use-case, so that duplication of functionality can be avoided by means of pulling out common functionality.

Use case is a set of/description of a group of intertwined and form a system of regularly conducted or supervised by an actor. Use case was used to create tingkah-laku objects/things in a model as well as in never achieved by a collaboration. General use case is described with an ellipse with a solid line, typically contains the name.Use case illustrates the process system (system requirements from the user's point of view).

In general use case is:

System behavior patterns:

-Order related transactions are performed by a single actor

Use case diagram consists of:

-Use case

-Actors

-Relationship

-System boundary boxes (optional)

-Packages (optional)

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 diagrams as well.

Use case above there are 2 actors i.e. User and admin. The User can make changes to the profile, modify the template, can do a post and can also reply to comments from the visitors. However, the User must first Login using your email and password that have been listed on the blog. In the profile, the User can change the profile or create a new profile. In the settings of the template, the user can change the templates or add new templates. The User can also make new postings or postings that have been changed in the previous post. In the blog, there is the comment from the visitor, User can reply to the comment or delete comment previously.