Вы находитесь на странице: 1из 24

2010

System Building 2
The Tote All Case Study
Report

Nguyen Quang Hung


FPT - Greenwich University
3/8/2010

Contents
1.

Introduction ...................................................................................................................................................... 4

2.

Analysis And Design Prototype ................................................................................................................ 4

3.

4.

2.1.

Significant Ambiguities (Questions) ............................................................................................... 4

2.2.

Assumptions ............................................................................................................................................. 4

2.3.

Extra Heavy Load .................................................................................................................................... 4

2.4.

Standardisation Problem .................................................................................................................... 4

2.5.

Ships Movement Problem ................................................................................................................... 5

2.6.

Crane Coordinate .................................................................................................................................... 5

Use Cases ............................................................................................................................................................ 6


3.1.

Use Case Making Contracts................................................................................................................. 6

3.2.

Voyage Management ............................................................................................................................. 8

3.3.

Crane Operatoring.................................................................................................................................. 9

3.4.

Crane Controller ................................................................................................................................... 10

Activity Diagram .......................................................................................................................................... 11


4.1.
4.2.

5.

1.

2.

3.

4.

Making Contract .............................................................................................................................. 11


Unloading Progress............................................................................................................................. 12

State chart Diagram .................................................................................................................................... 13


5.1.

Unloading Progress............................................................................................................................. 13

5.2.

Making Contract ................................................................................................................................... 13

Sequence Diagram ....................................................................................................................................... 14


1.1.

Load Progress Sd ................................................................................................................................. 14

1.2.

Load Progress Part1 ........................................................................................................................... 15

1.3.

Load Progress Part2 ........................................................................................................................... 16

Class Diagram ................................................................................................................................................ 17


2.1.

Tote All ..................................................................................................................................................... 17

2.2.

Crane Controller ................................................................................................................................... 18

Architecture and Deployment ................................................................................................................ 19


3.1.

Tote All ..................................................................................................................................................... 19

3.2.

Crane Controlling System ................................................................................................................ 19

Human Computer Interaction ................................................................................................................ 20

4.1.

Devices ..................................................................................................................................................... 20

4.2.

Prototype User Interfaces ................................................................................................................ 21

4.2.1.

Select a row in vessel ................................................................................................................ 21

4.2.2.

Select a Container ....................................................................................................................... 21

Description: .................................................................................................................................................... 21

5.

4.2.3.

Find a Voyage (for Head Office) ........................................................................................... 22

4.2.4.

Find Voyage Results .................................................................................................................. 22

4.2.5.

Voyage Details .............................................................................................................................. 23

Pseudo Code ................................................................................................................................................... 24


5.1.

Unloading Progress............................................................................................................................. 24

1. Introduction
This document describes system analysis and partly system requirements specification of
Tote All international shipping company.

2. Analysis And Design Prototype


2.1. Significant Ambiguities (Questions)
1. How do we know exactly the position of container ship in dock? It includes the
position of the bow or the stern.
2. How many bays are there in a ship and each bay position?
3. How many kinds of Tote All staffs?

2.2. Assumptions
1. All containers have the same size.
2. All consignments of different clients in a particular container have only one
destination port.
3. There is more than one container but that there is no need to move any other
container than the one currently being loaded.
4. Crane Controller has already known about ship and container information such as
ship length, ship height, ship width and each container position.
5. Controller handles a specific cranes component (such as spreader) that is implicitly
control the actuator that effect to the component.

2.3. Extra Heavy Load


When the weight sensors reported an extra heavy load, crane controller need to make
sure the balance of container. It may calculate an extra weight that it can handle to prevent
error or accident may occur (such as cable broken, boom collapsed or cause damage to
goods in container). If the extra heavy load exceeds the maximum weight that crane can
handle, crane controller will signals to crane operator to stop load/unload progress (or it
may automatic stop the load/unload progress when needed).
Moreover, if crane can handle the extra heavy load, it will move sluggishly the container.
It means the whole crane system works more slowly and carefully than normal cases. The
inertial force may effect to crane system, and it may cause error if crane controller do not
works more slowly. Crane controller should warn to crane operator.

2.4. Standardisation Problem


We can find a solution for the lack of standardisation between various makers of
equipment regarding the actual commands use to effect control by using polymorphism
feature of Object-Oriented Programming. On the other hand, an interface IComponent
declared essential method and other Spreader classes have to implement this interface.

Each type of crane has a Spreader, for example Spreader that it must implements
IComponent interface, and when a method is called, program need not know what the
actual commands that affect the control are.

2.5. Ships Movement Problem


The system will have a chain of sensor (e.g. water sensor, movement sensor) will monitor
the movement of the ship and feedback to controller to perform a precise handling.

2.6. Crane Coordinate

Z
X
Y
Figure 1: Crane Coordinate (adapted from http://www.exchange3d.com)

X
Y
Z

This is movement axis of major tower (i.e. the whole crane body)
This is movement axis of tracked boom (forward and backwards).
This is movement axis of spreader (hoist and lower).

3. Use Cases
3.1. Use Case Making Contracts

Figure 2 : Making contracts use case

Use Case
Add a new customer
Make enquiries for client
Prepare a new contract
Sign a contract
Confirm Locking Resources

Check clients requirements

Description
When a new customer come to Tote All, a full
details of the new customer are entered.
Agent collect clients requirement and send to
Head Office.
Agent prepares a contract base on clients
requirement.
Agent and client signs into a prepared contract.
After 4 hours working agent have to confirm
locking resources, if not the system will free the
resources.
Head office checks the requirements of client. If

Find a voyage
Lock the resources

these conditions are met, head office will lock


the resources for client and inform to local agent
to prepare a contact.
Agent will check these conditions:
Consignments
o Quantity
o Size (Height & Width)
o Volume
Port
o Initial port
o Destination port
Date/Time
o Departure time
o Estimated Time of Arrival
Head office find an appropriate voyage for
clients
Head office locks the resource in advance for
client.

3.2. Voyage Management

Figure 3 : Voyage management use case.

Use Case
Add new voyage
Change a voyage details
Assign initial port to a voyage
Assign destination port to a voyage
Assign container ships to voyage

Description
When Tote All decides to make a new voyage,
they will record information of the new voyage.
Update voyage details when it is changed.
Choose a particular port as an initial port of this
voyage.
Choose a port as destination port of this voyage.
Choose ships will sail in this voyage.

3.3. Crane Operatoring

Figure 4: Crane operating use case.

Use Case
Start automatic controller
Choose containers for automatic loading
Choose containers for automatic unloading
Choose position of containers

Stop automatic controller

Description
Crane operator start automatic controller for
load/unload containers.
Crane operator chooses one or some containers
to start automatic loading progress.
Crane operator chooses one or some containers
to start automatic unloading progress.
Crane operator chooses one or many positions
of containers for crane controller have
information to load or unload.
Crane operator stop automatic controller to do
something or due to error.

3.4. Crane Controller

Figure 5: Crane Controlling

Use Case
Move crane body to left
Move crane body to right
Move tracked boom forward
Move tracked boom backward
Lower spreader
Hoist spreader
Lock container
Unlock container

Description
Move crane to appropriate position
Move crane to appropriate position
Move tracked boom to new position
Move tracked boom to new position
Lower the spreader to lower position
Hoist the spreader to higher position
Lock container to the spreader
Unlock container from the spreader

4. Activity Diagram
4.1. Making Contract

Figure 6 Making Contract Activity Diagram

4.2. Unloading Progress

Figure 7: Unloading progress

5. State chart Diagram


5.1. Unloading Progress

Figure 8 Unloading Progress State chart

5.2. Making Contract

Figure 9 : Making contract state chart

1. Sequence Diagram
1.1. Load Progress Sd

Figure 10: Load Progress sequence diagram

1.2. Load Progress Part1

Figure 11: Load Progress Part 1

1.3. Load Progress Part2

Figure 12: Load Progress Part2

2. Class Diagram
2.1. Tote All

Figure 13: Tote All Class diagram

2.2. Crane Controller

Figure 14: Crane Controller Diagram

3. Architecture and Deployment


3.1. Tote All

Figure 15: Architecture of Tote All System

3.2. Crane Controlling System

Figure 16: Architecture of Crane Controlling System

4. Human Computer Interaction


4.1. Devices

Figure 17: Devices in system

Devices
Touch Screen

Control Buttons

Alarm

Functions
Display a set of UI for crane operator. Crane
Operators choose a job for automatic controller
to do (e.g. choose container positions and start
loading or unloading).
A set of physical buttons (start, pause, on/off)
allow crane operator handle automatic
controller system manually.
An alarm system will warn crane operator about
errors or accidents when they occur.

4.2. Prototype User Interfaces


4.2.1. Select a row in vessel

Figure 18: GUI select a row in vessel

4.2.2. Select a Container

Figure 19: GUI of select containers in vessel

Description:
Crane operators choose a row in the ship. The number of row in the ship based on the cargo
manifest that is inpputed to database. After crane operators select a row, they will select a
partitcular container on the ship to start automatic controlling.

4.2.3. Find a Voyage (for Head Office)

Figure 20: GUI of find a voyage

4.2.4. Find Voyage Results

Figure 21: GUI of find a voyage result

4.2.5. Voyage Details

Figure 22: GUI of voyage details

5. Pseudo Code
5.1.

Unloading Progress

if start automatic loading = TRUE then


start progress
request select containers
number of container = get selected containers
while number of container > 0
if location is ok then
position tracked boom
position spreader
shackle container
if shackle status is ok then
check container extra heavy
if container weight > handle able weight then
stop loading
else
if location is ok then
position tracked boom
position spreader
unshackle container
number of container-else
position crane body
end if
end if
else
shackle container again
end if
else
position crane body
end if
end while
end if