Class Diagram Facebook

For this post, before the author explains about the class diagram of facebook, the authors first show usecase diagram of facebook. Here is the usecase facebook :

UseCase Diagram FB

At this usecase author uses two actors are admin and user. To run all existing cycles dilam image above as manage profile, manage status, and manage message then the user must log in first. It is marked with << include >>. Include the user means before doing so it is necessary to first login to the admin of terlegih facebook by entering the email and password that has been registered as a master of data in admin facebook. If it meets the user can run the facilities provided by the admin. Usecase is then obtained from the declaration of the class diagram as follows:

Diagram Class

• Main

Main is a collection of entities of the user or can be referred to a facility that can be used by the user . Notice in the first usecase image , the user can manage profile , manage messages , and manage the status . The play of table then split again from each generalize , because the table is playing entity in which there is generalization . From the table, it is broken down in accordance entities , such as : managing profiles , managing messages , and manage the status to obtain a new table is the database connection .

• Database connection

Serves as a database connection parameters to declare all these entities . From this database table all tables will be connected and serves to store data , such as to register or login and store user data with the master table of our data is stored .

• Manage profiles

In the table there are attributes that manage profile data type void . The void data type means that we create a facility with an automatic . In managing existing profile new profile , edit profile , and delete profiles where it can be done automatically . But before we can manage these profiles must login program and will run all the commands in accordance with the user profile of the run, and therefore there is a table for managing realize tbuser profile which is formed inside the declaration of attributes like id_profil a string data type . The string data type is a character string with a certain length . The string data type is actually not pure , because composed of elements of type character . After that the attribute ( id_profile ) dioprasikan with setId_profile : Void it means id_profil will be called automatically for dioprasikan and all the attributes that exist in the middle or represented by the symbol ( - ) then all attributes will dioprasikan with the operation symbol ( + ) .

• Manage status

In the table there is a generalization that is managing status : input and delete status . From this table it appears that the tables will implement the table . As the picture above ( image class diagram ) then appears tbStatus table . With the table which we can manage status . Of tb this status , to manage the status of the attributes contained therein as isi_status , tanggal_isi_status , and the length of the status of the attribute table then dioprasikan with set_IsiStatus ( ) : void , + get_IsiStatus ( ) : void , and so on .

• Manage message

From the table there send_message manage this message and delete the message with the declaration made ​​by tbMessage table . Implemented in managing these messages by entering the email and the recipient is done automatically by the program that we run the appropriate commands .