You are on page 1of 9

Use Case Diagram

A use case illustrates a unit of functionality provided by the system. The main purpose of the use-case diagram is to help development teams visualize the functional requirements of a system, including the relationship of "actors" (human beings who will interact with the system) to essential processes, as well as the relationships among different use cases.

Usecase

Login

Movie details

Theator details user

Show details

Booked Details

Logout

Dependency: The relationship between two entities refers to a position where changes caused to one entity may have its effect to another entity .The Dependency relationship symbol is represented by a dashed arrow proceeding in one direction. -----------------------------------Association: he structural relationship that shows a connection (links) among the objects is called as an Association. This is represented by a straight line.

Generalization: In this relationship the objects of one entity can be substituted with the objects of another entity. The entity whose objects are substituted is known as parent entity and the entity which is providing objects for replacement is known as child entity.

Aggregation: Aggregation depicts whole-part relationship among several classes. Whole reflects a class carrying many things whereas part refers to a class carrying only few things when compared to whole class.

Class Diagram: It is a collection of objects that shares the common properties and
relations. Every representation of a class includes name, attributes and responsibilities

Sequence diagram
Sequence diagrams show a detailed flow for a specific use case or even just part of a specific use case. They are almost self explanatory; they show the calls between the different objects in their sequence and can show, at a detailed level, different calls to different objects.

A sequence diagram has two dimensions: The vertical dimension shows the sequence of messages/calls in the time order that they occur; the horizontal dimension shows the object instances to which the messages are sent.

Sequence Diagram
user login movie show theater available seats Book database Login Authentication Valid/invalid Get Movie List Send_Request Response Select Movie GetShows

Send_Request Response

Select Show

Get Theaters List

Send_Request Response

Select Theater Get Available Tickets

Send_Request Response Book Ticket Submit Acknowledgement

Logout

Collaboration diagram
UML Collaboration diagrams (interaction diagrams) illustrate the relationship and interaction between software objects. They require use cases, system operation contracts, and domain model to already exist. The collaboration diagram illustrates messages being sent between classes and objects (instances). A diagram is created for each system operation that relates to the current development cycle (iteration).

Collaboration Diagram
1: Login user login 4: Get Movie List 7: Select Movie movie

16: Get Available Tickets theater available seats

8: GetShows 11: Select Show 12: Get Theaters List 15: Select Theater 22: Logout 13: Send_Request

2: Authentication 6: Response 5: Send_Request

show

14: Response

3: Valid/invalid 19: Book Ticket

18: Response 17: Send_Request

9: Send_Request

10: Response 20: Submit Book 21: Acknowledgement database

You might also like