Object-Oriented Application Development

Laboratory
A.

Case Study: Student Grading System

A manufacturing management system is required. The company produces two
major different types of spare parts, that is spare part for air vehicle and spare
part for land vehicle. A vehicle is something which, is used for transport. A plane
is used for transport in air and a car is used for transport on the ground. All
vehicles contain engines. Two different types of engine are, oil powered engines
and petrol powered engines. Every engine contains some pistons, a fuel pump and
an exhaust. Some planes have propellers and some have jet engines. Some cars
have two doors while others have four doors.
1. Identify classes or objects in the problem statement above? (Do not worry if
you are not sure how to identify objects yet, it will be covered in the later
lecture. Perhaps you may use class and object definition to get better picture of
what are the classes and objects in the statement)
2. Identify the relationship between classes (or objects) then develop an
objectmodel.
3. Let assume that customer will order parts from this manufacturing company.
Develop an interaction diagram( e.g., sequence diagram) show how
manufacturing company response to this purchasing order.
4. Develop an activity diagram showing manufacturing process to produce parts
(e.g., produce piston, etc)
5. Develop state diagram showing state of the part (e.g., piston,etc)

B.

Case Study: Student Grading System

1. Users will be able to specify travel dates and times, start and end airports,
number of passengers, and will be provided a list of available outbound flight
sequences and return trips that meet their requirements.
2. A User will be able to choose a departing and returning flight sequence from the
list of available flight sequences, and the number of passengers. If the flights can
be reserved, the system will show a full itinerary and specify the price. The flights
will be held for sufficient time (1 hour) for the users to book the reservation.
3. If the flight is no longer available, the user will be so informed, and asked to make
another choice.
4. If the user asks to make a reservation, the user is presented a page for submitting
credit card information.
5. Before credit card information is submitted, user is informed that the flight will be
booked and they will not be able to obtain a refund if they proceed.
6. If the credit card submission is validated, a reservation is booked, and a
confirmation number is presented to the customer.
7. At any time prior to booking the reservation, the customer can propose changes to
the proposed travel. Existing holds on flights will be removed if the customer
changes the itinerary.

Use Rational Rose modeling tool to draw the diagrams below:

a) Analyze the written requirements.
i) Identify the actors. List the humans or group(s) that interact with the
system under design. Also list any systems that interact with the system
under design.
ii) Identify the use cases. List the functionality or services provided.
b) Diagram the use cases.
c) Draw associations/relationships between use cases.
d) Draw the Class Diagram for the system.
i) Draw the nouns as classes.
ii) Draw the verbs as associations/relationships between classes.
iii) Assign a multiplicity to each association (i.e., one-to-one, one-to-many,
many-to-many)
e) Update the Class Diagram with class attributes.
f) Update the Class Diagram with class methods.
g) Draw the sequence diagram for each use case.

Please note: A UML diagram might need to be revisited if required to fine-tune the
information. For example, if you have finished the class diagram and currently doing a
sequence diagram, it is possible that you would need to consider a new message in the
sequence diagram and therefore you might have to go back to the class diagram to
incorporate the method corresponding to the message.