Diagram Element Editing SYSTEM ARCHITECTURE

MUE: Multi User UML Editor – Suhadi Lili, Sutarsa, Siti Rochhimah ISSN 1858-1633 2005 ICTS 43 view consistency among diagrams, because it will only shown in one diagram. For this kind of element hierarchies, we do not apply bridge pattern [2][3].

2.3. Diagram Element

Diagram element represents the container of a glyph object. There are 8 derivation classes of UMLDiagram as being implemented by our application. The diagram hierarchy of these 8 classes can be seen in Figure 7. UmlDiagram UmlAct ivit yDiagram UmlClassDiagram UmlComponent Diagram UmlDeployment Diagram UmlSt at eChart Diagram UmlUseCaseDiagram UmlCollaborat ionDiagram UmlSequenceDiagram UmlElement Figure 10 Element Diagram Hierarchy

2.4. Editing

In our implementation, the editing process can be seen from two sides, i.e. at the client side and at the server side. Although the client application has the direct interaction with the user actions, any editing command on the model is not carried out by the client. The editing command, i.e. insert, update, or delete, is passed by the client to the server. The server takes the decision whether an editing command will be committed or not, and then notifies its decision to corresponding clients. As soon as client receives the notification, it will update its view accordingly. The client application consists of Diagram Editor Form and Model Explorer. The diagram editor form provides the user with means to edit a diagram. In this form, user interacts with the glyph objects. Figure 8 shows the use cases available in diagram editor form. autentified us er m em ilih elem en Drag elem en res ize elem ent hapus elem en m em buat elem en baru Form diagram render gam bar m em inta m em buat em en graph m em inta m odifikasi elem en graph m em inta delete elem en s inkronisas i data dengan s erver m enotifikas i client atas perubahan fro m Use-Ca se M o de l Diagram controller f rom U s e-C as e Model Figure 11 Use-cases for Diagram Editor Form The model explorer displays the model element according to the hierarchy of the element, which is viewed as a tree. In model explorer, user can interact with the model. Figure 9 shows the use cases available in model explorer. m enam bahkan elem en baru kondis inya dis ini adalah aplikas i client m em inta s erver untuk m em buat elem en renam e elem en autentified us er f rom ak si di f orm diagram ubah s pes ifikas i tam pilkan s pes ifikas i include delete elem en pada tree Model explorer m em inta delete elem ent m odel m em inta m odifikas i atribut m em inta m em buat elem en m odel baru Model Controller f rom U s e-C as e Model Figure 12 Use-cases for Model Explorer

2.5. Server Application Architecture