Select a problem from the dropdown list shown below

Identify the domain classes from the following problem statement

The latest cab services agency in the city has approached you to develop a Cab Management System for them. Following is the information they have given to implement the system.

Mr. Bose is the boss of this agency. Cabs are solely owned by the agency. They hire drivers to drive the cabs. Most of the cabs are without AC. However, a few comes with AC.

The agency provides service from 8 AM to 8 PM. Presently the service is limited only within Kolkata. Whenever any passenger books a cab, an available cab is allocated for him. A booking receipt is given to the passenger. He is then dropped to his home, office, or wherever he wants to go. In case the place is in too interior, the passenger is dropped at the nearest landmark.

Payments are made to the drivers by cheque drawn at the local branch of At Your Risk Bank. All kind of finances required for the business are dealt with this bank.

Recently Mr. Roy, neighbour of Mr. Bose, has given a proposal to book one of the cab in the morning everyday to drop his son to school, and drop him back to home later. Few other persons in the locality have also found the plan a good one. Hence, Mr. Bose is planning to introduce this "Drop to school" plan also very soon.

Learning Objectives:

Identifying potential classes (and their attributes) from a given problem statement
Use expert knowledge on the subject matter to identify other relevant classes

Limitations: The workspace provided is constrained to solve the current problem only. This is not a general user interface to solve any problem. Moreover, the classes generated at the end are some rudimentary classes and not necessarily the only classes possible. UML works in an iterative approach -- propose and refine. In fact, one may model the problem from a different perspective. The objective here is to provide an idea on how one should begin identifying potential candidate classes.

Table #1: Add nouns / noun phrases identified from the problem statement Table #2: Categorization of the above identified nouns (Ross's method)

Potential objects	Category	Add

Table #3: List of categorized nouns (potential objects)

Place	People	Things	Organization	Concept	Event	Redundant

Table #4: Identify attribute(s) for objects

Object	Attributes	Add
	Address Color Cost Height Name Serial Number Time Weight

Table #5: Add other possibile attribute(s) [Optional] Table #6: List of objects and it's attribute(s) Table #7: Define classes from list of attribute(s)

Attributes	Class	Add
Address Color Cost Height Name Serial Number Time Weight

Table #8: List of classes and their attribute(s) Table #9: Add any other relevant class (based on domain knowledge) [Optional]

Result and Discussion

From the given problem statement we can identify the following nouns and noun phrases:

Noun and Noun Phrases
Mr Bose boss agency Cabs drivers AC	service Kolkata passenger booking receipt home office	place landmark Payments cheque branch At Your Risk Bank	finances business bank Mr Roy morning everyday	son school persons locality plan Drop to school	neighbour

Let us put the above into different categories.

People	Places	Things	Organizations	Concepts	Events
Mr Bose boss drivers passenger Mr Roy son persons neighbour	Kolkata home office place landmark branch locality	Cabs AC booking receipt cheque	agency At Your Risk Bank bank school	service Payments finances business plan	morning everyday Drop to school

The nouns and noun phrases in the problem statement gives us a list of 31 potential classes. However, all of them may not be relevant. For example, 'Moning' is not something related to the Cab Management System. And so is 'Everyday'. In a similar way, 'Service', 'Plan', 'Agency', 'AC', 'Locality', and 'Business' doesn't seem to be potential classes in this context. So, we may avoid to assign any attributes for those entries.

We need to assign some attributes for rest of the potential classes. For example, 'Mr Roy' may assigned attributes 'Adress', 'Height', 'Name', and 'Weight'. In addission to these, 'Customer id', may be consider as an attribute for 'Mr Roy', as, Mr Roy may be treated as a potential Customer for our Cab Management System. Similarly, we can assign attribute 'Employee id' with 'Adress', 'Height', 'Name', and 'Weight' for the potential class 'Drivers'.

These are the probable classes with their associated properties

Person	Employee	Customer	Place	Cab	Booking	Bank
Name Address Height Weight	Name Emlpoyee id Address Height Weight	Name Customer id Address Height Weight	Address	Color Cost Has AC Weight	Time Customer Starting Place Destination	Address Branch Name

According to the properties assigned to 'Mr Roy' and 'Drivers', Mr Roy will be an object of 'Customer' class and 'Drivers' will be an object of 'Emloyee' class.

Although not explicitly mentioned in the problem statement, based on knowledge in related area one may point out few other potential classes with their following properties:

Transaction	Payment
Transaction id Parties involved Time	Amount Name of Payee Serial number

For the given problem related to Cab Management System, one may conclude the final list of classes as :

Person
Employee
Customer
Place
Cab
Booking
Bank
Transaction
Payment