DIAGRAM CLASS DIAGRAM USE CASE DIAGRAM

CRC

` ` `

Akshat Sapra(RIT2009008) Mohit Kumar Lal(RIT2009014) Kshitij Bansal(RIT2009078)

A use case diagram is a diagram that shows the relationships among actors and use cases within a system. Use case diagrams are often used to: Provide an overview of all or part of the usage requirements for a system or organization in the form of an essential model or a business model Communicate the scope of a development project Model your analysis of your usage requirements in the form of a system use case model A use case model is comprised of one or more use case diagrams and any supporting documentation such as use case specifications and actor definitions. Within most use case models the use case specifications tend to be the primary artifact with use case diagrams filling a supporting role as the glue that keeps your requirements model together. Use case models should be developed from the point of view of your project stakeholders and not from the (often technical) point of view of developers. There are guidelines for:

Use Cases Actors Relationships System Boundary Boxes

` USE

CASE DIAGRAM

For Multiplex Booking System

Log In to System
ENQUIRES ON AVAILABILITY

INFORMS STATUS OF AVAILABILITY

u BOOK TICKET

PAY PRICE

Credit Card Payment

Change the u password

Log out from system

Enquires about movie

Seat Availaibility

ACTORS :Customer Software Database USE CASES:Login To The Database Enquires On Availaibility Enquires About Movie Informs About Status Availaibility Book Ticket Pay Price Logout from System

1. 2. 3.

1. 2. 3. 4. 5. 6. 7.

` ` ` ` ` `

It is a Static model type A view of the system in terms of classes and relationships Classes not only describe attributes but also behavior Description of object types . Attributes and behavior of a type of objects All objects are instances of a certain class

A Class Responsibility Collaborator (CRC) model (Beck & Cunningham 1989; Wilkinson 1995; Ambler 1995) is a collection of standard index cards that have been divided into three sections. A class represents a collection of similar objects, a responsibility is something that a class knows or does, and a collaborator is another class that a class interacts with to fulfill its responsibilities.

LOGIN CLASS
1. Check Login Credentials Movie Class

TICKET CLASS
1. Shows Movie Name 2. Shows Seats Name 3. Shows Screen Name 4. Shows Movie Details 5. Shows Timing of the Show 6. Shows Seats Class Movie Class

MOVIE CLASS
1. Fetches Movie ID 2. Fetches Movie Name 3. Fetches Movie Casting 4. Fetches Movie Producers 5. Fetches Movie Director 6. Fetches Movie Genre 7. Fetches Movie Synopsis 8. Fetches Movie Language Movie_GUI Class

Movie_Show_Details CLASS
1. Shows Movie ID 2. Shows Movie Name 3. Shows Movie Casting 4. Shows Movie Producers 5. Shows Movie Director 6. Shows Movie Genre 7. Shows Movie Synopsis 8. Shows Movie Language Book Ticket Class

BOOK_MOVIE CLASS
1. User can choose date, time and class for a particular movie. Movie Class

CUSTOMER CLASS
1. Shows Customer ID 2. Shows Customer Name 3. Shows Customer Address 4. Shows Customer Contact Details. Login Class

SEATING PLAN CLASS

1. Shows Full Seating Plan of a Particular Screen with array of Seats in which each seat has a Record of a customer ID and seat ID. Seat Book Class

Choose Bank CLASS

1. Choose Bank for Payment for Tickets Payment class Seating_Plan class

PAYMENT CLASS
1. Takes Input in Authentication Details of the user bank Account for Payment of the Tickets . Customer Class Choose Bank Class

CLASS DIAGRAM
For Multiplex Booking System

`THANK

YOU