Introduction to GDSS Global Delivery Service System

1
Introduction to GDSS(Global Delivery Service
System)

• Team member
• Mingzhu Wei, Di Yang
• Cs509 project

2
Outline

• Main Features
• Architecture Design
• Implementation and integration strategy
• Our changes for the bug
• Possible Enhancement

3
Main Features

• Three type of users
• Sender or receiver
• Branch staff
• Headquarter staff
• For the sender and receiver
• Estimate price and delivery time
• Search nearest branch
• Track shipment
• For the branch users
• Create a shipment
• Update status of a package

4
Main features

• For the headquarter users
• Add a new branch
• Update branch information
• Show connection information

5
Architecture Design
6
Integration strategies

• We use a bottom-up integration strategies.
• Implement basic classes first
• Branch, branchList, map, sender etc.
• Implement the GUI and add the corresponding
  functions which manipulate on the data structure
• Test the GUI with real data
• Integrate to top modules

7
Fix bugs

• In the "estimate price and time" function.
• If a package depart form Worcester to Beijing and
  the shipping type is chosen to be 'express', the
  actual price is 20.0 and estimated time is 2.
• The expected price is 33 the expected estimate
  time is 9.
• A similar bug exists from Worcester to Salisbury
  when the shipping Type is chosen to be 'ground'.
• Actual output is that "estimated price is 10.0
  Delivery time 3 days". The expected price is 10
  and Time is 4.
• This is because the code of calculation of time
  doesnot work.

8
Fix bugs

• Another problem in the "update status of a
  package" in the branch interface.
• When the user input a tracking number 000024,
  when user click "search database", it should show
  all the path this package will go through in the
  list below.
• It always report an error message No result is
  found!".
• Solve this problem the corresponding routing
  path the new package is actually not written into
  Oracle database at all.

9
Fix bugs

• 5. Worcester to Beijing Ground Shipment does not
  exist. According to the map there is no ground
  path from Worcester to Beijing.
• we change our map to make the ground path exist
  among all the connection point. Now when user
  choose to ship form Worcester to Beijing and the
  shipping type is ground, we will show the
  estimate price and time.

10
Fix bugs

• Agreement Between Estimation and Order Placement.
  
• In the "estimate price and time" function, for a
  ground shipment from Worcester to Salisbury it
  gives an estimated price of 10.00 and an
  estimated time of 3 days.
• When actually placing this order the system
  claims the price will be 20.00 and the time will
  be 2 days.
• This is because the code for the two function is
  inconsistent. We have fixed this bug.
• 7. The problem of "Update Successful Without
  Updating".
• After searching for the database for track no
  000026, a message stating a successful update was
  displayed when no update commands were given.
• This happens because we did not check whether it
  is updated or not.

11
New extended Features

• Add a new branch
• Add a new connection point and add the connection
  information
• Show the connection information

12
Possible Enhancement

• 1Show connections (implemented)
• 2Add new branch (implemented)

13
Possible Enhancement

• 3Add new connection edges
• That is easy to be done, by just inserting new
  edge tuples in "map" table of database.
• 4 Allow to delete a branch
• That is relatively easy, but we need a new
  algorithm to judge whether target branch is a
  critical point, which
• means deleting it will cause the whole map
  disconnected.

14
Possible Enhancement

• 5Provide capability to see complete route.
• Actually ,this function has already been
  implemented, but embedded in the function called
  "update package status"
• 6 Introduce "vehicle" for each connection.
• It is not easy to be done with current design,
  for we totally do not have schedule conception
  for the whole system.
• To implement it, we need redesign, and introduce
  a "global schedule" to the system.

15
Possible Enhancement

• 7Simulator
• It is easy to introduce a simulator into the
  system. But if we want it to be more meaningful,
  we still need a schedule in our system.