Introduction. People can use this system to search movies and cinemas in any area specified by the user. Cinemas consists of rooms and seats. Users of.

Introduction

People can use this system to search movies and cinemas in any area specified by the user. Cinemas consists of rooms and seats. Users of the system can search forcinemas or movies. They should be able to narrow down the search to any area and time interval. Booking, payment and printing tickets is possible from any computer on-line. The central class is the session class that have information about movie, cinema, room, time, seats and bookings. Cinema managers can schedule, reschedule and correct movie session scheduling. Session information is collected in timetable-objects for making searching more efficient.

System definition

Functionality – searching, booking, buying, schedulingAppl. domain - serving cinema customers, clerks.Conditions - Cooperation with cinema clerks, other similar booking systems, (Multilingual system. Non skilled users. 99.99% uptime, almost unlimited ressources.)Technology - client-server, replicated server farms, incrementally built upon need, 1.000-1.000.000 concurrent users.Objects – Cinema, Room, Seat, Session, Movie, Booking, TimeTable.Responsibility - reliably searching movies and cinemas and booking and buying.

Factor Analysis:

Problem domain: Class diagram

Problem domain: Event table

Classes

Events Cinema Seat Room Session MovieTimetab

le Booking

seatSelected   *          

seatDeselected   *          

seatPayed   +   +     +

selectionBooked   +   +     +

bookCancelled   +   +     +

bookTimeOut   +   +     +

roomCreated + + +        

roomDeleted + + +        

cinemaEntered +   +     +  

cinemaExited +   +     +  

sessionScheduled   + + + + +  

sessionTimeOut       +   +  

sessionCancelled       +   + +

ticketPrinted       +      

movieEntered         +  +  

Problem domain: behaviour

Application Domain: Actors and Use cases

Actors Use Cases Enduser Cinema ManagerSearch XBooking XPayment XTicket print XSesseion editing XCinema editing X

Use case diagram

State chart diagram

Function Update Read Signal

Compute

Complexity

Search GetContinentList + +GetCountryList + +GetRegionList + +GetSessionList + ++GetCinemaList + ++GetMovieTitleList + ++SetTimeInterval + +

Booking DisplaySessionSeats

+ +++

SelectSeat + ++DeselectSeat + ++BookSelectedSeats + ++

Payment CalculatePrice + +CreateReceipt + +PrintReceipt + +CreateTickets + +

PrintTickets + ++Cinema manager

GetSessions + +

HasAnyBookings + ++EditSession + +StoreSessionInfo + +GetCinema + +GetRoomPlan + +GetSeatList + +SetPayTimeOut + +SetBuyTimeOut + +EditCinema + +EditSeatList + +

Functions

Design: Design Criteria

Criterion Very Important

Important Less Important

Irrelevant Easily fulfilled

Usable XSecure XEfficient XCorrect XReliable XMaintainable X XTestable XFlexible XComprehensible

X

Reusable XPortable XInteroperable

X

Component Architecture

:Client User

user interface

system interface

:Client Clerk

user interface

system interface

:Server

user interface system interface

function

model

Other system

Process Architecture

Class diagram, design document

Function Component