Taxi project

1
Taxi project

• Group 302
• Fredrik Aaben
• Anders Blomkvist
• Linda Benroth
• Johanna Boström
• Marcus Fredriksson
• Karl Lundmark
• Gothenburg 19 maj 2006

2
Subjects

• System Description(Fredrik)
• RMI, Database(Karl)
• Testing(Linda, Johanna)
• Demonstration(Anders)
• Further Extensions(Marcus)

3
Cars

• 2 types
• Regular cars (4 seats for customers)
• Minibus (8 seats for customers)
• Position
• Holds the position the car
• Schedule
• All bookings for the particular car

4
Cars

• Status
• Occupied, free, out of order
• Requirements
• Handle several cars
• Best car booked
• Right type of car chosen
• Add more cars
• Remove cars

5
Customers

• Needed information
• Cust_id, name, phone_nbr
• Optional information
• Address, invoice customer
• Requirements
• Add a customer
• Remover a customer
• Associate with a booking

6
Customers

• Requirements (cont)
• Update address
• Update phone number

7
Bookings

• Two types
• Planed (Admin)
• Impulse (driver)
• Compulsory informaiton
• Id, start- and stop address, time
• Best car selected for booking
• When admin adds the booking

8
Bookings

• Requirements
• Add a booking
• Remove a booking
• Search for a booking
• Modify a booking
• View details of a booking
• Display booking on screen

9
Database

• Bookings
• Customers
• Cars

10
RMI

• System (server)
• GUI (client)

11
Tests in the first iteration

• JUnit tests
• Add a booking
• Travel time not zero or negative
• System tests
• Car performs the booking at the start time
• Integration tests
• A day in the taxi company
• How the system behaves in the long run
• 100 bookings added

12
Results, iteration 1

• JUnit

13
Results, iteration 1

• Integration
• 4 cars 51 of 100 bookings were added
• 10 cars All bookings were added

14
Tests in the second iteration

• Manually tests
• GUI
• Add a booking
• Change time and date in the schedule
• JDBC
• The right information is stored in the database
• Java RMI
• Information should be sent between the server and
  the client

15
Results, iteration 2

• Manually
• Most of the requirements were not fullfilled
• JDBC
• The test passed!
• RMI
• Not working properly

16

• Tests in the third iteration
• Add a booking created by the administrator
• Remove a booking
• Change a booking
• Add a customer with all possible information
• Search for a booking

17

• Add a booking created by the administrator
• The test is successfully passed.
• Remove a booking
• The test is not fully passed. The booking is
  deleted from the database but a local copy still
  remains
• Change a booking
• The test is not fully passed. The booking is
  changed in the database but the booking is not
  shown in the schedule again.
• Add a customer with all possible information
• The test is successfully passed.
• Search for a booking
• The test is successfully passed.

18
Stress test

• The stress test was performed by adding bookings
  into the system.
• We used two different types of tests
• Add bookings in the server class
• The same t type of test as in iteration one
• Three tests add 10 ,200,500 bookings in the
  database.
• Add bookings in the client class
• Test how the system handles bookings from several
  clients in the same time
• The server is running. The clients start at the
  same time and add 10, 25 and 50bookings each.

19
Resulttest server

• 1 add 10 bookings at the startup of the server
• The bookings were added to the schema of the car
  that is scheduled for each particular booking.
  All booked trips were also successfully performed
  on time.
• All functions of the program (add and remove
  bookings, adding customers and so on) worked as
  supposed during the test. Several clients were
  also connected to the server during the whole
  test.
• Increases of the speed of the system time every
  8 seconds in reality was 1 second during the
  test.
• 2 Add 200 bookings at the startup of the server.
  
• The system worked with satisfacted result and no
  errors were found.
• 3 Add 500 bookings added at the startup of the
  server
• SQL exception Maximum cursors exceeded when the
  startup was almost done. This exception will
  probably not occur when running in real time.

20
Resulttest client

• 10 bookings / client 13 were successfully added
• 25 bookings / client 36 were successfully added
• 50 bookings / client76 were successfully added

21
Further Extensions

• Some more functionality
• Some more information