Professional Documents
Culture Documents
Object Oriented Programming
Object Oriented Programming
Object Oriented Programming
MANDAL'S
PRAGATI COLLEGE OF
ARTS,COMMERCE AND SCIENCE
S.Y. B.Sc.(IT)
PRESENTED ON : 15 / 10 / 2009
SUBMITTED BY
1. Introduction
• Problem Statement
• Analysis
• Requirement Specification
2. Domain Modelling
• Identifying Classes
• Identifying Attributes
• Identifying Methods
• Inheritance Relationship
3. Use-case Modelling
• Identifying Actors
• Developing Use-cases
• Developing Interaction Sequence Diagrams
5. Implementation
6. Conclusion
INTRODUCTION
• PROBLEM STATEMENT
• ANALYSIS
The numerous problems identified with the manual system affect the
regular functioning of the hotel. Since the manual system is slow, this can lead
to operational problems such as the customer may be prevented from using the
facilities (services) which may be available but may appear to the hotel staff
that the particular service is already engaged. As the process is manual, there is
no backup system if the forms (sheets) gets destroyed and retrieving the same is
not as easy as there is no record of what had been lost. Finally, it is very time
consuming to get even minute details of the simple information that has been
lost.
For these reasons, the system that is developed should be automated for
minimising human error, improving the accuracy of the system and to make it
easy for hotel staff to transfer all the manual details to the new system. When
new entries are recorded or changes are made to the existing entries, the display
should be immediately updated so that hotel staff are always working with the
latest information available. Operations of the system will be as far as possible
by direct manipulation of the data presented on the screen. For example, it
should be possible to change the time of the booking, or the table it is allocated
to, simply by dragging the booking to an appropriate place on the screen.
• REQUIREMENT SPECIFICATION
• Customer Registration
• Booking Transactions
• Ordering Transactions
• Billing Operation
• Payment Operation
• Storing Operation (.i.e. keeping track of all these transactions
till the customer check – outs )
DOMAIN MODELLING
IDENTIFYING CLASSES
Customer Catering
Contact number Room Service
Name Account Number
Address Hygiene
Enquiry Restaurant
Booking system Telephone section
Booking Payment system
Date and time Payment
Table Amount
Room Advance
Hall Credit card
Type Cash
Capacity Engine
Ordering system Cashier
Order Transactions
Meal Bill
Beverages Bill number
Quantity Duration
Services Balance
Manager Tax
Duty Discount
Staff
Department
• IDENTIFYING ATTRIBUTES
Room Meal
quantity type
price
Figure (a)
The class diagram in above figure (a) provides a solid basis for the
structure of our model but the diagram is not complete. We need to
identify the operation that the objects will perform during the program
execution.
The classes that play a major role in achieving system goals and
requirements by using their methods are as follows :
Customer Class : Customer is an individual who interacts with the
system by means of ordering, booking and payment and has its own
details.
Booking Class : This is a class that allows the customer to book the
facilites granted by the hotel.
INHERITANCE RELATIONSHIP
The fig (e) shows the sequence interaction diagram showing the
interaction between the customer and the system. The classifier roles
involved in the interaction are displayed at the top of the diagram. The
vertical dimension in the sequence diagram represents time and the
messages in an interaction are drawn from top to bottom of the
diagram, in the order that they are sent. Each role has a dashed line
known as its lifeline extending below it. Lifeline indicates the period
of time during which objects playing that role actually exists. In the
figure, all objects exists throughout the entire interaction but some
objects are not required till the end.
Class booking
{
private :
int cover;
setcover();
public :
int date;
int arrtime;
int deptime;
setarrtime();
setdeptime();
getdate();
};