Table of Contents

Table of Figures. 2

Ques 1 Sequence Diagram.. 3

Ques 2 Communication Diagram.. 4

Ques 3 Class Diagram.. 5

Ques 4 Gasp Method. 6

Table of Figures

Figure 1: Sequence Diagram.. 3

Figure 2: Communication Diagram.. 4

Figure 3: Class Diagram.. 5

Ques 1 Sequence Diagram

Define sequence diagram in UML

A sequence diagram is a communication diagram that exhibits how exactly the systems function among one another and in which sense and try to gauge their demands. A sequence diagram displays object coordinated efforts arranged in ordered manner that is related to every time sequence. It portrays the objects and classes comprised in the circumstances and the order of communications exchanged among the things needed to finish the handiness of the circumstances. Sequence diagrams are typically joined with use-case diagrams and try to display the Logical View of the structure being shown in the system. (Agilemodeling.com, 2014)

Figure 1: Sequence Diagram

Ques 2 Communication Diagram

Describe the basic differences of communication diagram with sequence diagram

Sequence diagram make it easier to take afterward the participation subsequently they are completed through and through, so finding message asking for is truly fundamental. Nevertheless on the off chance that you have various things imparting, the diagram becomes hard to scrutinize.

Communication diagrams demonstration what communications are conveyed among the things with the sequence made on top out of the communication. For a considerable measure of things, it is less complex to grasp than the sequence diagram; though message ordering is quite difficult to manage or get. (Cs.cityu.edu.hk, 2014)

Figure 2: Communication Diagram

Ques 3 Class Diagram

Class Diagram

Figure 3: Class Diagram

Ques 4 Gasp Method

Expert:

The expert of the class is the Admin class as it is the main regulatory class taking all the actions on the system.

Creator:

Out of the all the class the admin is the class that is going to invoke all the objects of other classes and interacts with entire system as explained in the case of being expert for the same. All the classes will report to admin directly or indirectly.

Low Coupling:

All the classes are independent and do not need the other classes to be dependent to perform their work hence low coupling in the system.

High Cohesion:

Low coupling leads to high cohesion, all classes in the system are focused and purposely developed and have the independent responsibilities and focus.

Controller:

All the control manages by the Admin class and the system is administrated by admin UI based or non-UI based classes it doesn’t matter hence Admin is the controller.

References

Cs.cityu.edu.hk,. (2014). Communication Diagram vs. Sequence Diagram vs. State Machine Diagram | Dr. Wing-Kwong Chan’s Homepage. Retrieved 22 September 2014, from http://www.cs.cityu.edu.hk/~wkchan/content/communication-diagram-vs-sequence-diagram-vs-state-machine-diagram

Agilemodeling.com,. (2014). UML 2 Sequence Diagrams: An Agile Introduction. Retrieved 23 September 2014, from http://www.agilemodeling.com/artifacts/sequenceDiagram.htm

Msdn.microsoft.com,. (2014). UML Class Diagrams: Reference. Retrieved 23 September 2014, from http://msdn.microsoft.com/en-us/library/dd409437.aspx