class diagram for system blog

Use case is a program that is used in making a variety of processes running in a system where there are a variety of menu use case that is used in accordance with the business processes that put more emphasis on the user or users .

• Discussed After the previous article about the usage and the menu on the blog using the metaphor of a use case diagram then this point that we can take the Conclusions in the use case diagram , namely :• Describe the expected functionality of a system .• Describe the system requirements from the user perspective• focuses on the process of computerization (automated processes)• Describe the relationship between use cases and actors• Use case describes the process of system• In general , the use case is :- The sequence of related transactions performed by an actor• Use case diagram consists of  - Use case  - Actors  - Relationship  - System boundary boxes ( optional )  - Packages ( optional )

• Use case purpose made ​​based actor• Use case given name stating what is Achieved from the interaction with the actors .• Use case denoted with images• Use case usually uses the verb• Name of the use case may Consist of several words and can not have 2 use case that has the same name

ACTOR• Actor describe people , systems or external entities / stakeholders who provide or receive information from the system• Actor describe a task / role and position rather than a position• Actor provide input or receive information from the system• Actor normally use nouns• There should be no direct communication between actors• Indications << system >> to an actor that is a system• An actor named " Time " which indicate scheduled events ( an event that Occurs Periodically / monthly )• Put your actors play in the top left corner of the diagram• Associations not describe the flow of data / information• Associations are used to Illustrate how the actors in the use case INVOLVED

•              There are 4 types of relationships that can arise in the use case diagram

• Association between actor and use case• Association between use case• Generalization / Inheritance between use case• Generalization / Inheritance between actorsWell that's a discussion of the use cases we can now introduce a class called class diagram diagram of how to describe what the menu is on the blog when we use a blog .Know the class diagram• What is the class diagram of the Class is a specification that if instantiated to produce an object and is at the core of development and object-oriented design .• Class describes the state ( attribute / property ) of a system , as well as offering services to manipulate the situation ( method / function) .• Class diagrams describe the structure and description of the class , along with the package and object relationships to each other as containment , inheritance , associations , and others .• Class has three play areas:- 1 . Name ( and stereotypes )- 2 . attribute- 3 . method• Attributes and methods can have one of the following properties :- Private , can not be called from outside the class in question- Protected , may only be invoked by the relevant class and the children who inherit- Public , can be called by anyone• Association , the static relationship between classes . Generally describes the attributes of a class that has another class , or classes that need to know the existence of another class . Navigability arrows indicate the direction queries between classes .• 2 . Aggregation , namely the relationship roomates section states ( " consists of .. " ) .• 3 . Inheritance , the hierarchical relationships between classes . Class can be derived from another class and inherits all the attributes and methods of class origin and adds new functionality , so she called the children of the inherited class . Inheritance is the opposite of generalization .• 4 . Dynamic relationship , roomates is a series of messages ( message) roomates is passed from one class to another class . Dynamic relationship can be described using sequence diagrams .In the blog so we can see that there are a lot of menus that can be accessed by the user , with a first look at the context of the class diagram that is the menu manage profile , manage posts , manage templates , manage income , manage overview , manage login .For the first menu that manage profile we can create new input profile . Edit profile and delete profile . That is the new input profile then we can make- our name , email , memos and all that distinguished between one user with another user with id_profile . In the process of dealing with changes in the edit id_profile set , get id_profile , set system_username , get system_username . Here is intended to see how such a system can be running a set of processes that are connected to each other as seen from the point of view of the user .If the theories are described by name , attributes and methodsFor the Tb profile name , attributes such as id_profile , system_username , email_user , and memos that accompanied each character .For the next menu , mange posts there are sub menu input new post , edit post , view and delete blog post post ,Class name : Tb postsAttribute : content_posting , content_status date , length of post• Method : set _content post , get _content post , set date ) post content, get date_contentpost . For further menu menu then almost Equally adapted to the main menu and then create an instance of the main menu and the menu derivative must have the linkages in the system and it is intended by the name of the association with the sense of the Association , the static relationship between classes . Generally describes the attributes of a class that has another class , or classes that need to know the existence of another class . Navigability arrows indicate the direction queries between classes .