miv final report

MINISTRY OF EDUCATION AND TRAINING

FPT UNIVERSITY

Capstone Project Document

Maritime Information Visualization

6Fingers

Group

Members

Tran Hai Dang – 00606

Ta Duc Tung – 00544

Pham Quang Hung – 00396

Ha Thi Tham – 01188

Nguyen Hai Ha – 00740

Duong Hue Linh – 00596

Supervisor Mr. Huynh Anh Dung

Ext Supervisor Mr. Nguyen Tat Trung

Project code MIV

- HaNoi, 04/2012 -

________________________________________________________________________ Final Report, Maritime Information Visualization, Version 1.0 Page | 2 Prepared by 6Fingers

Acknowledgements

part from the efforts of all team members, the success of any project depends

largely on the encouragement and guidelines of many others. We take this

opportunity to express our gratitude to the people who have been instrumental

in the successful completion of this project.

We would like to show my greatest appreciation to mentor Huynh Anh Dung. We cannot

say thank you enough for his tremendous support and help. We feel motivated and

encouraged every time we attend his meeting. Without his encouragement and guidance

this project would not have materialized.

We are highly indebted to mentor Nguyen Tat Trung for his guidance and constant

supervision as well as for providing necessary information regarding the project & also for

his support in completing the project.

We would like to express my gratitude towards our parents for their continuously

encouragement which help us in completion of this project.

Our thanks and appreciations also go to our colleague in developing the project and people

who have willingly helped us out with their abilities.

A


Preface

ietnam is a maritime country with more than 1 million square kilometers of

exclusive economic zone (EEZ) where there are many economics activities,

especially 20,000 far shore fishing vessels have been bringing benefits to both

fishermen and the government.

However, Vietnam is also suffered from many natural disasters, especially those from the

sea including seasonal typhoons which claim over hundred lives and many fishing vessels

lost every year, causes of poverty and suffering. Thus, applying advanced technology to

solve this problem, ensuring safety for fishermen is urgently needed.

The MIV project aims to develop an additional method of communicating text messages

on HF band that along with retaining existing method of communicating (voice

transmitting), using software-modem to modulate and demodulate messages. System will

transfer data from coastal station to vessels and vice-versa.

The proposed system consists of the coastal station, vessels, and has the following major

characteristics:

Compatible and complement existing communication equipment on fishing vessels

Using advanced digital modulation technique for communication

Visualization Information at both sides (coastal station, vessels)

V


Brief Contents

Acknowledgements ................................................................................................................................... 2

Preface ..................................................................................................................................................... 3

Brief Contents .......................................................................................................................................... 4

Definitions and Acronyms ........................................................................................................................ 8

1 Introduction ..................................................................................................................................... 9

2 Project Management Plan .............................................................................................................. 12

3 Software Requirement Specification ............................................................................................... 18

4 Software Design ............................................................................................................................. 44

5 Software Testing .......................................................................................................................... 124

6 Installation Guide......................................................................................................................... 191

7 User Manual ................................................................................................................................ 197

8 Appendixes .................................................................................................................................. 209


Contents Acknowledgements ................................................................................................................................... 2

Preface ..................................................................................................................................................... 3

Brief Contents .......................................................................................................................................... 4

Definitions and Acronyms ........................................................................................................................ 8

1 Introduction ..................................................................................................................................... 9

1.1 Literature review ................................................................................................ 9

1.1.1 Coastal Station System ................................................................................ 9

1.1.2 Viettel Coastal and Islands Base Transceiver Station (BTS) System .................. 9

1.1.3 Movimar System ......................................................................................... 9

1.2 Project Idea ..................................................................................................... 10

1.3 General view ................................................................................................... 11

1.4 Proposal and Project’s Benefits .......................................................................... 12

1.5 Critical Assumption and Constraints ................................................................... 12

1.6 Potential Risks ................................................................................................. 12

2 Project Management Plan .............................................................................................................. 12

2.1 Project Overview ............................................................................................. 12

2.1.1 Core Business Cases and Approach ............................................................. 12

2.1.2 Project Milestones and Deliverables ............................................................ 12

2.2 Boundaries of the System .................................................................................. 13

2.3 Development Environment ................................................................................ 13

2.3.1 Hardware requirements .............................................................................. 13

2.3.2 Software requirements ............................................................................... 13

2.4 Project Organization ......................................................................................... 14

2.4.1 Software Process Model ............................................................................ 14

2.4.2 Roles and Responsibilities.......................................................................... 14

2.5 Project Management Plan .................................................................................. 15

2.5.1 Tasks ....................................................................................................... 15

2.5.2 Task Sheet: Assignments and Timetable ...................................................... 15

2.6 Risk Management ............................................................................................ 16

2.7 Coding Conventions ......................................................................................... 17

2.7.1 Naming Conventions ................................................................................. 17

2.7.2 Coding Styles ........................................................................................... 17

2.7.3 Comments ................................................................................................ 17

3 Software Requirement Specification ............................................................................................... 18

3.1 High Level Requirements .................................................................................. 18

3.2 Domain Model ................................................................................................. 18

3.2.1 Diagram ................................................................................................... 18

3.2.2 Domain Object Description ........................................................................ 18

3.3 Business process flow ....................................................................................... 20


3.3.1 Storm message broadcasting process ........................................................... 20

3.3.2 Normal message broadcasting process ......................................................... 21

3.3.3 Position message sending (from vessel) process ............................................ 22

3.3.4 SOS message sending (from vessel) process ................................................. 23

3.4 Use cases and Actors ........................................................................................ 24

3.4.1 On-sea Terminal System ............................................................................ 24

3.4.2 Coastal Station System .............................................................................. 26

3.4.3 Viewer System ......................................................................................... 28

3.5 Functional Requirements .................................................................................. 29

3.5.1 Use cases Description ................................................................................ 29

3.5.2 Screen Description .................................................................................... 35

3.6 Nonfunctional Requirements ............................................................................. 43

3.6.1 User access and security ............................................................................ 43

3.6.2 Capacity and performance .......................................................................... 43

3.6.3 Availability .............................................................................................. 43

3.6.4 Security ................................................................................................... 43

3.6.5 Systems management ................................................................................ 43

3.6.6 Scalability ................................................................................................ 43

3.6.7 Maintainability ......................................................................................... 43

3.6.8 Usability Requirement ............................................................................... 43

3.7 Other Requirements.......................................................................................... 44

3.8 Requirement Completeness Criteria ................................................................... 44

4 Software Design ............................................................................................................................. 44

4.1 Design Overview ............................................................................................. 44

4.1.1 System Context......................................................................................... 44

4.2 Architecture Overview ...................................................................................... 46

4.2.1 Diagram ................................................................................................... 46

4.3 Detailed Design Description .............................................................................. 50

4.3.1 On-land System ........................................................................................ 50

4.3.2 On-sea Terminal ..................................................................................... 101

4.4 Database Design ............................................................................................ 114

4.4.1 Database Diagram ................................................................................... 114

4.4.2 Table design description .......................................................................... 114

4.4.3 Broadcast Message Structure .................................................................... 116

4.5 Algorithm ..................................................................................................... 118

4.5.1 Error Detection & Correction Algorithm .................................................... 118

4.5.2 Software Modem – Sound Modem ............................................................ 123

5 Software Testing .......................................................................................................................... 124

5.1 Requirements for Test .................................................................................... 124


5.1.1 Feature to be tested ................................................................................. 124

5.1.2 Feature not to be tested ............................................................................ 127

5.2 Test strategy .................................................................................................. 127

5.2.1 Test types ............................................................................................... 127

5.2.2 Test Environment .................................................................................... 128

5.2.3 Risk list ................................................................................................. 128

5.3 Deliverables .................................................................................................. 128

5.4 Checklist ....................................................................................................... 129

5.4.1 Checklist of Validation ............................................................................ 129

5.4.2 Submission checklist ............................................................................... 129

5.5 Test cases ...................................................................................................... 132

5.5.1 Onsea Terminal ...................................................................................... 132

5.5.2 Coastal Station system ............................................................................. 142

5.5.3 Viewer ................................................................................................... 155

5.6 Test Summary Report ..................................................................................... 190

5.6.1 Test Execution Summary ......................................................................... 190

5.6.2 Test Results ............................................................................................ 190

5.6.3 Summary of Incident Reports Raised During Project ................................... 190

5.6.4 Conclusion ............................................................................................. 191

6 Installation Guide......................................................................................................................... 191

6.1 Environment Requirement............................................................................... 191

6.2 Installation Package........................................................................................ 191

6.3 Installation Guide for On-sea Terminal ............................................................. 191

6.4 Installation Guide for Database server .............................................................. 193

6.5 Installation Guide for Coastal Station ............................................................... 194

6.6 Installation Guide for Viewer .......................................................................... 195

7 User Manual ................................................................................................................................ 197

7.1 Application Overview ..................................................................................... 197

7.1.1 Requirements ......................................................................................... 197

7.1.2 Available Features .................................................................................. 197

7.1.3 Roles ..................................................................................................... 198

7.2 User Manual for Functions .............................................................................. 199

7.2.1 Functions for Fishers ............................................................................... 199

7.2.2 Functions for Operators ........................................................................... 203

7.2.3 Functions for Central Operators ................................................................ 206

8 Appendixes .................................................................................................................................. 209

8.1 Messages ...................................................................................................... 209


Definitions and Acronyms Acronym Definition

MIV Maritime Information Visualization

PM Project Manager

PTL Project Technical Leader

TL Team Leader

QA Quality Assurance Officer

DV Developer

URD User Requirement Document

SRS Software Requirement Specification

ADD Architecture Design Document

DDD Detail Design Document

TP Test Plan

TC Test Case

SC Source Code

CM Configuration Manager

UC Use case

UI User Interface

GUI Graphical User Interface

AT Acceptance Test

IT Integration Test

ST System Test

UT Unit Test

TR Test Report

UAT User Acceptance Test

CS Coastal Station

CO Central Operator

Table 0-1: Definitions and Acronyms


1 Introduction

1.1 Literature review

1.1.1 Coastal Station System In Vietnam, weather forecast information, storm alerting, meteorological information and

other rescue information are transmitted to fishing vessels by Coastal Station System. In

order to update the information, fishing vessels need to continuously listen to messages

broadcasted from coastal stations. On the other hand, whenever there is any issue

concerning about safety, rescuing… vessels need to alert coastal stations.1

These station need to be online 24 hours per day, 7 days per week on the frequency of

7.903 KHz. In this case, station staff will transmit messages by talking and listen to

rescuing information from fishing vessels.2

Advantages Disadvantages

Easy to use Anti-interference

In many urgent cases, sailor cannot

hear the message clearly, which lead

to misunderstanding and damaging

1.1.2 Viettel Coastal and Islands Base Transceiver Station (BTS) System From the beginning of 08 – 2009, Viettel Corporation set up a system of BTSs along

Vietnam’s coast, on Vietnam’s islands for providing mobile phone signal on coastal area,

islands and other area on the sea. In the range of 30 nautical from BTS, Viettel mobile

phone signal is very good. However, out of this range, especially from 61 nautical away

from BTS, signal is very weak, cannot use.3


Can use cell phone Narrow range

Cannot cover full range of South –

East Asia Sea

1.1.3 Movimar System Movimar System is a very high-end system which is set up by Vietnamese Government

and French Government with the investment of €13.9 million and implement period is 3

years, 2011 – 2013. System will be deployed in 28 provinces in Vietnam. In the target of

Movimar project, about 3000 vessels will be equipped satellite communicating device.

Moreover, about 150 navy vessels will be equipped with supporting device, prepared for

communicating and processing rescuing information.4

After finishing the project, fishing vessels will be able to automatically receive weather

information transmitted from coastal station. Along with this, coastal station can

1 Tailieu. “Các đài thông tin duyên hải Việt Nam”. Tailieu.vn. Jan 13, 2012 <http://tailieu.vn/xem-tai-

lieu/cac-dai-thong-tin-duyen-hai-viet-nam.496951.html> 2 Bộ giao thông vận tải, văn bản “Số: 4212/BGTVT-PCLB&TKCN.”

3 Viettelonline. “Đưa sóng di động ra biển”. Viettelonline.com. Jan 13, 2012

<http://viettelonline.com/tin-tuc-viettel/dua-song-di-dong-ra-bien.html> 4 Hà Minh. (Jul 18, 2011). “Kết nối thiết bị vệ tinh cho 2.850 tàu cá”. Ictnews.vn. Jan 13, 2012

<http://www.ictnews.vn/beta/thoi-su/71/Ket-noi-thiet-bi-ve-tinh-cho-2850-tau-ca/85299/index.ict>


continuously monitor fishing vessels’ position and take action immediately when

emergency come.5


High technology

Guarantees a high quality of

communicating and rescuing

High capital investment

Number of monitored vessel is only

2850

Technology dependency (depend on

France)

1.2 Project Idea Along with retaining existing method of communicating (voice transmitting), the main

purpose of this idea is to develop an additional method of communicating on HF band.

System will transfer data from coastal station to vessels and vice-versa.

The system consists of 2 main subsystems deployed in coastal stations and vessels.

Coastal station subsystem

Coastal station will broadcast weather forecast or storm notification to all vessels

on the sea.

On the other hand, vessels can send SOS message, coastal stations will receive and

take action.

Every vessel needs to register its identity and its basic information will be stored in

a centralized database at national level.

Vessels position and voyage path will be monitored and stored in database. This

information can also be processed and displayed on a visual map like Bing or

Google map.

Figure 1-1: Display on Coastal Station

5 Thành Công. (Mar 22, 2011). “Tàu cá hoạt động theo hình thức tổ, đội sẽ được nhà nước gắn

thiết bị kết nối vệ tinh miễn phí”. Agroviet.gov.vn. Jan 13, 2012 <http://www.agroviet.gov.vn/Pages/news_detail.aspx?NewsId=15943>


Vessel subsystem

Display vessel’s current position on a map

Visualize messages broadcasted by coastal stations.

Store message history

Notify coastal stations about vessel’s position each 10 minutes (or any defined

period of time)

Broadcast SOS signal in emergency cases

Figure 1-2: Display message on Vessel

1.3 General view

HF

HF

HF

HF

Text Data

Text Data

Text Data

Text Data

Database

Database

HFText Data

Visualization

Visualization

Visualization

Visualization

Coastal Station

Coastal Station

Syn

chro

niz

e

Visualization

Viewer

Figure 1-3: General view


1.4 Proposal and Project’s Benefits Implementing this system will improve communication efficiency between coastal station

and fishing vessels.

Better accuracy in message transmitting

Near real-time monitor vessels, support to rescuing effectively

Information is managed in a centralized database

On vessel side, message can be queried and displayed on a visual screen which

leads to better understanding from sailors.

1.5 Critical Assumption and Constraints

The system will be deployed on both Coastal Station and Fishing Vessels. MIV system

will work only when Coastal Station is equipped with necessary hardware and an Internet

line. Device equipment is also applied to fishing vessels except that no Internet line is

needed in vessels side.

1.6 Potential Risks Domain

Lack of knowledge about Vietnam maritime system and safety

Technology

Lack of experience about communication protocol which using HF band.

Lack of experience about using and programming with digital map.

Lack of experience about GPS.

Need some time for studying and training

Human Resource

3 members will go to Japan for 10 days in the end of January

Time

Too much time spending on finding idea

2 Project Management Plan

2.1 Project Overview

2.1.1 Core Business Cases and Approach

The main system will be a software system. There will be applications on coastal station,

specific device for fishers and a centralized database system in national class.

The system will provide the following main features:

Coastal station can monitor the vessels position and voyages, receive SOS message

in urgent case. Besides it can broadcast the weather forecast to fishers

Information will be stored and managed in centralized database system

Vessels can receive weather forecast, send SOS message when have an accident

2.1.2 Project Milestones and Deliverables

No Stage Committed Actual Deviation


1 Project Management Plan 02 – Feb – 12 02 – Feb – 12 0 day

2 SRS v1.0 07 – Feb – 12 09 – Feb – 12 2 days

3 Detailed design v1.0 09 – Mar – 12 15 – Mar – 12 6 days

4 Final package 20 – Mar – 12 30 – Mar – 12 10 days

5 Test report v1.0 22 – Mar – 12 03 – April – 12 12 days

6 User Manual v1.0 30 – Mar – 12 04 – April – 12 5 days

Table 2-1: Project milestones and deliverables

2.2 Boundaries of the System

The system under development of this Capstone Project will include:

The software installer

User manual

SRS

Design documents

Test documents

Source code

2.3 Development Environment

Below is the list of hardware and software requirements needed for development

environment:

2.3.1 Hardware requirements

Visualizing device for fishing vessel

A computer on coastal station with the minimum configuration: 4 Gb of RAM,

100Gb of hard disk, Core 2 Duo 2.0 Ghz

Marine transceivers, GPS device

2.3.2 Software requirements

Operating system: Windows 7, Android 2.1

Framework: .NET Framework 4.0

IDE: Visual Studio 2010, Eclipse 3.7.1, Android SDK 2.1

DBMS: SQL Server 2008 R2 Express

Source Control: Tortoise SVN 1.7

Oxygen XML Editor


2.4 Project Organization

2.4.1 Software Process Model

The process model used for developing this project is iterative and incremental

development model.6

Figure 2-1: Iterative and incremental model

We have only approximately 3 months for doing everything of this project and not every

member has experience for the similar systems before. Besides, the beginning the problem

definition is not totally clear and we need to clarify it in iterative model. The iterative way

lead us to reduce the misunderstand requirements and make sure project runs in the right

way. So we should choose this iteration rather than water fall model. Furthermore,

incremental model can help us to break down many phases into small steps and do some

steps in parallel. Working in parallel some steps can help us to reduce effort and project

can be delivered on only 3 months.

2.4.2 Roles and Responsibilities

Project Instructor

Mr. Huynh Anh Dung

Mr. Nguyen Tat Trung

Project team member

TungTD

(CM, DV)

HungPQ

(DV)

ThamHT

(DV)

HaNH

(DV)

LinhDH

(Tester)

DangTH

(PM)

Figure 2-2: Project Team Organization

6 Wikipedia. (Jan 28, 2012). “Iterative and incremental development”. Wikipedia.org. Feb 3, 2012

<http://en.wikipedia.org/wiki/Iterative_and_incremental_development>

http://en.wikipedia.org/wiki/Iterative_and_incremental_development


2.5 Project Management Plan

2.5.1 Tasks

2.5.1.1 Create Software Requirements Specification

Description: create SRS

Output: SRS document

Deliverables: deliver SRS document before Feb 7, 2012

Resources needed: 6 people in 2 days for brainstorming, 2 people in 5 days for doing SRS

Risks: because there is no actual user, and the requirements come from all the team

members, misunderstandings may happen regularly

2.5.1.2 Create Software Design Description

Description: create design for overall systems

Output: SDD

Deliverables: deliver with SDD before Mar 9, 2012

Resources needed: 6 people in 2 days for brainstorming, 2 people in 26 days for doing

SDD

Dependencies and Constraints: depends on the completion of SRS

Risks: SRS may not be detailed enough to capture the business rules, causing the detailed

design to be inappropriate or will be changed much in the future

2.5.1.3 Coding

Description: implement the system to reflect the requirements

Output: source code of the project, unit test reports

Deliverables: executable programs and source code before Feb 23, 2012

Resources needed: all developers in 30 days

Dependencies and Constraints: depends on the completion of SRS, SDD

Risks:

Unit test may not be performed thoroughly causing spending many efforts in system

test phase

May lack of time to implement all the requirements

Team members may not easily get used to new technologies and new knowledge such

as algorithm or communication protocol

2.5.1.4 System Test

Description: perform system test for the system

Output: system test report

Deliverables: Software Test Documentation before Apr 2, 2012

Resources needed: 2 people in 39 days

Dependencies and Constraints: Coding is finished

Risks: 39 days may be too short to check whole system works well or not

2.5.2 Task Sheet: Assignments and Timetable Refer to the Master Plan document.


2.6 Risk Management

ID Risk Description Probability Effect Status Action Contingency

1 User

Involvement:

It's quite difficult

to communicate

and get

involvement from

users

Very high Tolerabl

e Occurred

Get

requirement

from other

sources like

news or

internet

2 Testing:

Unable to test in a

deployed

environment

Very high Serious Occurred

Create

simulation

environment

3 Hardware

availability:

Lack of devices

such as text-to-

speech modem,

GPS device

Very high Serious Occurred

Borrow FPT

Technology

Research

Institute

Purchase

4 New Technology:

Android, Map

API, Encoding-

decoding

algorithm

Very high Serious Potential

Prepare

knowledge for

new

technologies

by materials

and internet

Request

support from

friends or

someone that

is expert of

that new

technology

5 Resource

Experience:

Team member

lack of software

development

experience

Moderate

In-

significa

nt

Not

relevant

OJT can help

us to get more

experience in

software

engineering

We have may

experienced

colleagues in

software

engineering to

ask and get

advice

6 Project

Management

skill:

Project Manager

lacks of project

management skill

Moderate Serious Potential

Project

Manager

prepares

knowledge

from text book

in library

Ask many

experienced

Project

Manager

when getting

trouble

Table 2-2: Risk Management


2.7 Coding Conventions The following rules follow the standard rules for developing applications using .NET and

C#.

2.7.1 Naming Conventions Refer to .NET Naming Guidelines.

7

2.7.2 Coding Styles Refer to FxCop rules and Code Analysis for Managed Code Warnings.

8

2.7.3 Comments

Comments should be written in order to make code understandable and maintainable.

Only write comments when necessary, do not write comments for every line of code

and every variable declared.

Use // or /// for comments. Avoid using /* … */

Do not write comments if the code is easily understandable without comment. The

drawback of having lot of comments is that if you change the code and forget to change

the comment, it will lead to more confusion.

Fewer lines of comments will make the code more elegant. But if the code is not

clean/readable and there are less comments, that is worse.

Writes clean, readable code such a way that it doesn't need any comments or very little

to understand.

Perform spelling check on comments and also make sure proper grammar and

punctuation is used.

7 MSDN. NET Naming Guidelines. Jan, 16, 2012. <http://msdn.microsoft.com/en-us/library/ms229002.aspx>

8 MSDN. FxCop rules and Code Analysis for Managed Code Warnings. Jan, 16, 2012.

<http://msdn.microsoft.com/en-us/library/ee1hzekz.aspx>

http://msdn.microsoft.com/en-us/library/ms229002.aspx

http://msdn.microsoft.com/en-us/library/ms229002.aspx

http://msdn.microsoft.com/en-us/library/ee1hzekz.aspx


3 Software Requirement Specification

3.1 High Level Requirements

3.2 Domain Model

3.2.1 Diagram

Normal

Message

creates

Central

Operator Fisher

SOS

Message

creates

Viewer DatabaseServer OnSeaTerminal

servicePush toNormal

Message

CoastalStation

Normal

Message

Storm

Messagecreates

Query from

servicePush toStorm

MessageNotify to

Broadcast to

Broadcast toStorm

Message

view

view

Send toSOS

Messageservice Push to

SOS

MessageNotify to

view

Position

MessageSend to

Position

Messageservice Push to

Position

MessageQuery fromview

Operator

view

view

view

view

Diagram 3-1: Domain Model Diagram

3.2.2 Domain Object Description

Object Description

Vessel The vessel has an unique ID that registered with MIV system

Message The structured information to transfer between device on vessel and

station. There are 2 types of messages:

Message from Coastal Station to Vessel

Message from Vessel to Coastal Station

Messages might contain information of weather, storm notification,

SOS notification, vessel position

Viewer The central system which is responsible for creating broadcasting

messages and visualize information received from vessels

Database System The software system which responsible for storing vessel information

and messages from Viewer and On-seaTerminal. The system also

handles and notifies if there is any urgent message (Storm message,

SOS message, etc).

Coastal Station The coastal station responsible for automatically broadcasting messages


Object Description

to vessels and receiving messages from vessels

On-sea Terminal The software system on vessels for visualizing information received

from coastal station and sending messages back to coastal station

Central Operator Person who uses Viewer software to broadcast message or monitor

vessels on map

Fisher Person who is the owner of a vessel and also the user of on-sea terminal

device

Operator Person who uses Coastal Station software to observe broadcasted &

received messages at each coastal station

Table 3-1: Domain Object Description


3.3 Business process flow

3.3.1 Storm message broadcasting process

Storm Message Broadcasting

Me

ssa

ge

Cre

atin

gM

essa

ge

Sa

vin

gM

essa

ge

Bro

ad

ca

stin

gM

essa

ge

Re

ce

ivin

gM

essa

ge

Vie

win

g

FisherCoastal Station

SystemDatabase System On-seaTerminalCentral Operator

Create storm

message

Save storm

Message into

Database

Notify Coastal

Station

Encode

Message

Broadcast

message

Decode

message

Visualize

information

View storm

message

End

Start

Diagram 3-2: Storm message broadcasting process


3.3.2 Normal message broadcasting process

Normal Message BroadcastingM

essa

ge

Cre

atin

gM

essa

ge

Sa

vin

gM

essa

ge

Bro

ad

ca

stin

gM

essa

ge

Re

ce

ivin

gM

essa

ge

Vie

win

g

FisherOn-seaTerminalCoastal Station

SystemCentral Operator Database System

Encode

Message

Broadcast

message

End

View

message

Save

Message into

Database

Start

Display

information

Decode

message

Create

message

Loop:

Get message

from

database

Diagram 3-3: Normal message broadcasting process


3.3.3 Position message sending (from vessel) process

Position Message Sending (From Vessel)M

essa

ge

Cre

atin

g &

Se

nd

ing

Me

ssa

ge

Re

ce

ivin

gM

essa

ge

Sa

vin

gM

essa

ge

Vis

ua

lizin

gM

essa

ge

Vie

win

g

Central OperatorViewerCoastal Station

SystemDatabase SystemOn-seaTerminal

Start

Save

Message into

Database

Decode

Message

View map

End

Visualize

information

Receive

message

Loop: update

position from

database

Loop:

Send position

message

Diagram 3-4 Position message sending (from vessel) process


3.3.4 SOS message sending (from vessel) process

SOS Message Sending (From Vessel)M

essa

ge

Cre

atin

gM

essa

ge

Se

nd

ing

Me

ssa

ge

Re

ce

ivin

gM

essa

ge

Sa

vin

gM

essa

ge

Vis

ua

lizin

gM

essa

ge

Vie

win

g

Fisher Central OperatorViewerDatabase SystemCoastal Station

SystemOn-seaTerminal

End

Save

Message into

Database

Start

Receive

message

View map

Decode

Message

Visualize

information

Press “SOS”

button

Create SOS

message

Send SOS

message

Encode SOS

message

Notify Viewer

Diagram 3-5 SOS message sending (from vessel) process


3.4 Use cases and Actors

3.4.1 On-sea Terminal System

3.4.1.1 Diagram

Diagram 3-6: On-sea Terminal UCs

3.4.1.2 Description of Actors

Actor Name Description



Fisher A end user of the On-sea terminal (generally vessel pilot or fisher),

who will use the terminal to view map, weather, vessel information

… or send SOS notification if necessary

Table 3-2: On-sea Terminal Actors description

3.4.1.3 Description of Use cases

Use case Name Description

View map This use case allows fisher to view the maritime map where he’s on

View storm notification This use case allows fisher to view storm notifications broadcasted

by coastal stations. The notifications will be visualized and

displayed in images

View weather information This use case allows fisher to view other weather information like

wind power, temperature…The information will be display in text

View vessel position The fisher can trace his position by using the terminal. His position

will be displayed inside the map

View forbidden area warning This use case allows fisher to be warned when vessel is going to

enter a forbidden area

Send SOS notification This use case allows fisher to send SOS notification in case he got

a bad situation.

Auto send position message to

Coastal Station

This use case allows position of vessel to be sent back to Coastal

Station for tracking automatically

Receive messages from

Coastal Station

This use case allows messages broadcasted from Coastal Station to

be received and be informed to fisher

Table 3-3: On-sea Terminal Use cases description


3.4.2 Coastal Station System

3.4.2.1 Diagram

Diagram 3-7 Coastal Station UCs



Usecase Name Description

Operator A user who has responsibilities for observing coastal station system

and message forwarding between Viewer system and vessels.

Table 3-4: Coastal Station System Actors description



View message history This use case allows Operator to view history of messages which

are broadcasted and received by this coastal station

View broadcasted message This use case allows Operator to view or be alerted whenever the

coastal station broadcasts a message to vessels

View received message This use case allows Operator to view or be alerted whenever the

coastal station receives a message (except position message) from

vessel

Broadcast message to

vessels

This use case allows Operator to send message to Transceiver

device, then it will be broadcasted to vessels via HF band

Receive messages from

vessels

This use case allows message sent from vessels to be received by

Transceiver device, then to be push into PC’s COM ports to

process.

Commit message into

database

This use case allows message received from vessels to be inserted

and stored into Maritime database in Database Server

Table 3-5: Coastal Station System Use case description


3.4.3 Viewer System

3.4.3.1 Diagram

Diagram 3-8: Viewer System UCs



Central Operator A user who has responsibilities for vessel management,

observation and salvage

Table 3-6: Station System Actors description




Create broadcast messages This use case allows central operator to send messages to all

vessels

View all vessels’ positions

on map

This use case allows central operator to observe vessel position on

map at a specific time

View a vessel’s voyage This use case allows central operator to observe a vessel’s voyage

through an interval of time

View a vessel’s information This use case allows central operator to view information of vessel

Auto update vessels’

position

This use case allows all vessels position to be updated after a

specified interval of time

Table 3-7: Station System Use cases description

3.5 Functional Requirements

3.5.1 Use cases Description

3.5.1.1 On-sea Terminal Use case Description

3.5.1.1.1 UC1: View map

Name View map

Description This use case allows fisher to view the maritime map at his position. The

map contains Asian maritime map, name of the famous places. The map

will be full-screen

Actor Fisher

3.5.1.1.2 UC2: View storm notification

Name View storm notification

Description This use case allows fisher to view the storm notification broadcasted by

coastal station. The notification will be displayed in image. In contains

the eyes of the storm, the strongly influenced area and the lightly

influenced area

Actor Fisher

3.5.1.1.3 UC3: View weather information

Name View weather information

Description This use case allows fisher to view the weather information broadcasted

by coastal station. The information contains temperature, moisture ... and


will be displayed in text form. The frame of weather information will be

located at right-bottom of the map

Actor Fisher

3.5.1.1.4 UC4: View vessel position

Name View vessel position

Description This use case allows fisher to view the position of his vessel. The

position will be displayed inside the map, with a vessel icon. The

position will be updated continuously

Actor Fisher

3.5.1.1.5 UC5: View message history

Name View message history

Description This use case allows fisher to view 5 latest messages broadcasted from

coastal station

Actor Fisher

3.5.1.1.6 UC6: Send SOS notification

Name Send SOS notification

Description This use case allows fisher to send SOS notification in bad situation. He

can push a button inside the On-sea terminal device, and the notification

will be sent to the rescue team.

Actor Fisher

Trigger User press [SOS] button

Post condition A SOS message is generated and continuously sent to the coastal station

until user presses [SOS] button or device is no longer available to use

(because of the accident, for example)

3.5.1.1.7 UC7: Auto send position message to Coastal Station

Name Auto send position message to Coastal Station

Description This use case allows fisher to send the current position of vessel to

Coastal Station automatically. The position is generated according to

GPS device

Actor Fisher

Pre condition Computer must connect to GPS device and transceiver device


3.5.1.1.8 UC8: Receive message from Coastal Station

Name Receive messages from Coastal Station.

Description This use case allows fisher to receive message from Coastal Station.

Messages are received in many divided packages, so the application

must assemble, correct (if errors) and process it.

The application should define a mechanism in case of losing packages.

Actor Fisher

Pre condition Computer must connect to transceiver device

Post condition Inform user about message (in text form or visualized form)

3.5.1.1.9 UC9: View forbidden area warning

Name View forbidden area warning

Description This use case allows fisher to be warned when vessel enters into a

defined forbidden area. Warning mean may be by text and/or sound

Actor Fisher

Pre condition Computer must connect to GPS device

3.5.1.2 Coastal Station System

3.5.1.2.1 UC10: View message history

Name View message history

Description This use case allows Operator to view history of messages which are

broadcasted and received by this coastal station

Refer to SC6 – [Message history screen]

Actor Operator

Trigger

Pre-condition

Post-condition

3.5.1.2.2 UC11: View broadcasted message

Name View broadcasted message

Description This use case allows Operator to view or be alerted whenever the



Actor Operator

Trigger A message has just been broadcasted to vessels

Pre-condition Computer must connect to transceiver device

3.5.1.2.3 UC12: View received message

Name View received message

Description This use case allows Operator to view or be alerted whenever the

coastal station received a message from vessels (except for position

message)

Actor Operator

Trigger A message has just been received by the coastal station


Post-condition The message will be commit to save into database server

3.5.1.2.4 UC13: Broadcast messages to vessels

Name Broadcast messages to vessels

Description This use case allows Operator to broadcast the latest message to

vessels through audio port

Actor Operator

Trigger User click button [Phát bản tin]


Post-condition The message will be commit to save into database server

3.5.1.2.5 UC14: Update messages from database

Name Update messages from database

Description This use case allows Operator to update the latest broadcast

messages from database server

Actor Operator

Trigger User click button [Cập nhật bản tin]

Pre-condition Computer must connect to database server

Post-condition The latest message will be displayed into GUI


3.5.1.2.6 UC15: Receive messages from vessels

Name Update messages from database

Description This use case allows Operator to receive messages from database

server. Message is divided into multiple packages, so that

application should process to assemble these packages.

Actor Operator

Pre-condition Computer must connect to transceiver device through audio port

(mic port)

Post-condition The content of received message will be displayed into GUI

3.5.1.3 Viewer Use cases Description

3.5.1.3.1 UC16: Create broadcast messages

Name Create broadcast messages

Description This use case allow user to broadcast messages to all vessels. There

are 3 types of messages:

Weather messages: contains information of weather forecast

on the sea. This type of message is sent frequently every day.

Storm messages: contains information of the current storm

status on the sea. This type of message is sent whenever the

storm can be seen.

Urgent messages: contains information of other urgent cases.

Message content, broadcasting time and frequency depends

on Central Operator.

Actor Central Operator

Trigger User open [Tạo bản tin] tab and fill appropriate information into a

designated form, then click [Đồng ý] button.

Pre-condition Application must connect to database server

Post-condition The message will be saved into database server

3.5.1.3.2 UC17: View all vessels’ positions on map

Name View all vessels’ positions on map

Description This use case allows Central Operator observe all registered vessels

on background map at the current time. This view is main screen of

Tracker application.


Pre-condition Internet connection is available for map downloading


Business Rules

BR

Code

Description

BR1 Background map’s dimension and limitation

The background map should contain some regions as Vietnam land, Vietnam

sea, Philippine sea and China sea.

BR2 Automatically update the positions onto the map

The vessels might be moving on the sea, so that their positions change

continuously. The position messages are sent to station frequently. The view

should acknowledge all these changes.

BR3 Acceptable delayed time rule

The system should assure the delayed time at most 5 seconds at the normal

condition.

BR4 No vessel case

In case of no vessels, the view displays only background map.

3.5.1.3.3 UC18: View a vessel’s voyage

Name View a vessel’s voyage

Description This use case allows central operator to observe a vessel’s voyage on

a time interval.


Trigger User click to a vessel’s position on the map of main screen.

Pre-condition There is at least a vessel displayed on the map

Business Rules

BR

Code

Description

BR5 Voyage figure selection

The view should choose display the vessel’s voyage as a line from start position

to ending position.

3.5.1.3.4 UC19: View a vessel’s information

Name View a vessel’s information

Description This use case allows central operator view the information of a

registered vessel, including an unique ID, current position, weight,

etc.



Trigger User points mouse to the vessel position on the map and click

Pre-condition There is at least one vessel displayed on the map

Post-condition Information of vessel is displayed in a pop up context

3.5.1.3.5 UC20: Auto update vessel position

Name Auto update vessel position

Description This use case allows Central Operator not need to update vessel

position manually. The application will update those information

automatically each period of time.


Trigger User points mouse to the vessel position on the map and click

Pre-condition There is at least one vessel displayed on the map

Post-condition Information of vessel is displayed in a pop up context

3.5.2 Screen Description

3.5.2.1 Viewer screen

3.5.2.1.1 SC1 – Map view screen XO-

Quản lý

Đ

I

Ề

U

K

H

I

Ể

N

T

Ì

M

K

I

Ế

M

X

Maritime Information VisualizationMaritime Information Visualization

Tạo bản tin Lịch sử đi tàu

Figure 3-1: Map view screen


Field name Control

Type

Editable Mandatory Description

Window title Label No Yes Default value is “Maritime

Information Visualization”

[Quản lý] tab Tab No Yes This is the default tab when start

MIV Viewer program.

Map view area Image No Yes This is the map view which shows

background map and all vessel

positions.

Zoom control Control Yes Yes This control allow user to zoom in

/ out the background map and

vessel distance.

Table 3-8: Map view screen description

3.5.2.1.2 SC2 – SOS notification screen XO-

X


Đ

I

Ề

U

K

H

I

Ể

N

T

Ì

M

K

I

Ế

M

Quản lý Tạo bản tin Lịch sử đi tàu

Figure 3-2: SOS notification screen

Field name Control

Type


SOS icon Icon No No This icon is displayed when

Viewer system receives a SOS

message from vessel.

The color should be easy to get

attention (red is recommended).

Table 3-9: SOS notification screen description


3.5.2.1.3 SC3 – Vessel information view screen XO-

X


Biển kiểm soát: 103QN

Kinh độ: 123.456

Vĩ độ: 14.362

Các thông tin khácCác thông tin khác

Quản lý Tạo bản tin

Đ

I

Ề

U

K

H

I

Ể

N

T

Ì

M

K

I

Ế

M

Lịch sử đi tàu

Figure 3-3: Vessel information view screen

Field name Control

Type


Information

Context

Context No Context shows vessel information

when user click to vessel symbol

in map view area

Table 3-10: Vessel information view screen description

3.5.2.1.4 SC4 – Vessel voyage view screen XO-

X


Lịch sử đi tàu

Đ

I

Ề

U

K

H

I

Ể

N

T

Ì

M

K

I

Ế

M

Quản lý Tạo bản tin

Figure 3-4: Vessel voyage view screen


Field name Control

Type


Vessel voyage UI

control

No The line draws a vessel voyage

from a start point to an ending

point

Table 3-11: Vessel voyage view Screen description

3.5.2.1.5 SC5 – Storm message creating screen XO-

Quản lý X


Tạo bản tin

Bản tin báo bãoBản tin báo bão

Vị trí tâm bão 1:

Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150

Bản tin thời tiết biển

Bản tin cảnh báo

Bản tin khẩn

Các bản tin khác

11/02/2012 06:00

Vị trí tâm bão 2: 11/02/2012 10:00

Phạm vi ảnh hưởng 3: 320

Đồng ý

Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150

Vị trí tâm bão 3: 11/02/2012 10:00

Phạm vi ảnh hưởng 3: 320Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150

Vị trí tâm bão 4: 11/02/2012 10:00

Phạm vi ảnh hưởng 3: 320Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150

ĐIỀUKHIỂN

TÌ

MKIẾM

Figure 3-5: Storm message creating screen

Field name Control

Type


Tab title Text No Yes Text: “Tạo bản tin”

Message type Drop-down

list

Yes Yes List of message type

Message content Grid-view Yes Yes A form with blank items to fill

[Đồng ý] button Button No Yes Text: “Đồng ý”

Click this button when

completing message

Table 3-12: Storm message creating screen description


3.5.2.2 Coastal Station System Screen

3.5.2.2.1 SC6 – Message history screen

XO-Lịch sử bản tinLịch sử bản tin

Số các bản tin được lưu trữ: 1

Thời gian nhậnSTT Loại Thời gian phát Ghi chú

14:00:00 10/02/20121Bản tin thời tiết

biển16:00:00 10/02/2012

Figure 3-6: Message history screen

Field name Control

Type


Title Text No Yes Text: “Lịch sử bản tin”

Amount of

messages Text

Text No Yes Color: red

Length: 255

Message history Table No Yes Table of message records

Table 3-13: Message history view screen description


3.5.2.2.2 SC7 – Message view screen

XO-Coastal Station Coastal Station

Nhận được 4 thông báo khẩn (SOS) mới. Bấm vào đây để xem

Bản tin này sẽ được tự động phát vào lúc 12:00:00 12/02/2012

Loại: Bản tin thời tiết biển.

Nội dung:

Bắc Vịnh Bắc bộ: Có mưa nhỏ.Tầm nhìn xa : từ 4 – 10km.Gió đông bắc cấp 5, có lúc cấp 6, giật

trên cấp 6. Biển động.

Nam Vịnh Bắc Bộ: Có mưa nhỏ.Tầm nhìn xa : từ 4 – 10km.Gió đông bắc cấp 5, có lúc cấp 6,

giật trên cấp 6. Biển động.

Quảng Trị đến Quảng Ngãi: Có mưa vài nơi.Tầm nhìn xa : trên 10km.Gió đông bắc cấp 5.

Bình Định đến Ninh Thuận: Có mưa vài nơi.Tầm nhìn xa : trên 10km.Gió đông bắc cấp 5.

Bình Thuận đến Cà Mau: Có mưa rào vài nơi.Tầm nhìn xa : trên 10km.Gió đông bắc cấp 5.

Cà Mau đến Kiên Giang: Không mưa.Tầm nhìn xa : trên 10km.Gió nhẹ.

Bắc Biển Đông:Có mưa vài nơi.Tầm nhìn xa : trên 10km.Gió đông bắc cấp 6, giật trên cấp 6.

Biển động.

Vùng Giữa Biển Đông: Có mưa vài nơi.Tầm nhìn xa : trên 10km. Gió đông bắc cấp 5, có lúc cấp

6, giật trên cấp 6. Biển động.

Vùng Nam Biển Đông: Có mưa rào rải rác và có nơi có dông.Tầm nhìn xa : trên 10km, giảm

xuống 4 – 10km trong mưa.Gió đông bắc cấp 4 - 5.

Vịnh Thái Lan: Có mưa vài nơi.Tầm nhìn xa : trên 10km.Gió nhẹ.

Cài đặt Lịch sử các bản tin

Phát bản tinCập nhật bản tin

Phát bản tin

Figure 3-7: Message view screen

Field name Control

Type


Message Content Text No Yes The text of message content

Length of text: 500

[Cài đặt] button Button No Yes Text: “Cài đặt”

[Cập nhật bản tin]

button

text No Yes Text: “Cập nhật bản tin”

The system will connect to

database to update new messages

[Phát bản tin]

button

Button No Yes Text: “Phát bản tin”

Functionality: Broadcast the

message to vessels manually

[Lịch sử bản tin]

button

Button No Yes Text: “Lịch sử bản tin”

Functionality: show the SC6 –


Field name Control

Type


Message history screen

Table 3-14: Message view screen description

3.5.2.3 On-sea Terminal screen

3.5.2.3.1 SC8 – Map view screen

Figure 3-8: Map view screen

Field name Control

Type


Background map Image No Yes The image of map contains

Vietnamese land, Vietnamese sea.

The system should use map API

support from existing systems to

get background image.

Vessel position

symbol

Image No Yes A symbol at the point as real

vessel position

Vessel position

text

text No Yes The text as real vessel position

putted near Vessel position

symbol


Field name Control

Type


Weather textbox Textbox No Yes The textbox containing

information of weather, putted at

the below right corner

SOS button Button No Yes Text: “SOS”

User will use this button in case of

urgency

Table 3-15: Map view Screen

3.5.2.3.2 SC9 – Storm (on map) view screen

Figure 3-9: Storm view screen

Field name Control

Type


Storm image Image No Yes This image is for visualizing storm

information in current and

forecasted status.

Use a red line to present the main

storm orbit

Use different colors to differ

degrees of storm damage.

Table 3-16: Storm view Screen description


3.6 Nonfunctional Requirements

3.6.1 User access and security

3.6.2 Capacity and performance

The system should run with the existing system, including maximum 100 coastal

stations.

The size of each message is up to 5KB

The data speed on HF channel is up to 300b/s

3.6.3 Availability

The complete system will be available during normal business hours (GMT+7).

The database servers will operate 24 hours a day, 7 days a week.

The database servers will have a 99.5% availability to ensure a meaningful error

message is provided to the users if the portal application is unavailable.

3.6.4 Security

Data must be encrypted when transferring via HF communication or Internet.

Authentication is required when accessing into or querying from database system.

3.6.5 Systems management

Database backup: There is a weekly backup process in place on Saturday night which

requires the application servers to be brought down. The downtime will be between

2:00 p.m. and 4:00 p.m.

3.6.6 Scalability

The system will be able to scale to support additional vessels, coastal stations or viewer

systems.

3.6.7 Maintainability

The solution will be compliant with industry standard technologies.

3.6.8 Usability Requirement

The system’s architecture should be open for future development and maintenance

The system shall be easy to use

The system shall be easy to learn

The system shall prompt customer with friend easy to read error messages

The system shall utilize consistent symbols and color for clear notification


3.7 Other Requirements

Language: Vietnamese

3.8 Requirement Completeness Criteria

The below table list all completeness criteria for MIV project in scope of Capstone Project.

All other complements will be developed in second phases (release to market and go live)

Scope Functions/Features Related

Use case

Completeness Remain

functions/features

Capstone

project

Communication from

Coastal Station to On-sea

Terminal, and vice-versa

6, 7, 8, 13,

15

via UHF/VHF

band

via HF band

Read/write data from/into

transceiver through audio

port

6, 7, 8, 13,

15

100%

Read position from GPS

device

4 100%

Divide a message into

multiple packages and

assemble them

6, 7, 8, 13,

15

100%

Visualize vessel position

information using Google

Earth API

18, 19 100%

Visualize storm information

on map (On-sea Terminal)

1, 2 100%

Visualize vessel position on

map (On-sea Terminal)

1, 4 100%

Remote to manage Maritime

database

14, 16, 19,

20

100%

Release to

market and

go live

Availability to work with a

system with more than 100

Coastal Station and about

20000 vessels

to be

developed

in future

Communication via HF to be tested

& deployed

in future

Table 3-17: Requirement Completeness Criteria

4 Software Design

4.1 Design Overview

4.1.1 System Context

4.1.1.1 Diagram


Diagram 4-1: System Context Diagram

4.1.1.2 System Context Description

Object Description

On-land system

Central operator User of Viewer application, responsible for

- Monitoring vessel positions, voyages

- Create weather messages, storm messages

Operator User of Coastal Station application, responsible for

- Monitoring messages to be broadcasted to vessels, received

from vessels

- Broadcasting messages to vessels

Viewer Windows application for monitoring vessel positions, vessel voyages,

creating messages

Coastal Station Windows application for monitoring broadcasted messages, received

messages. It connects to radio station hardware for that tasks

Database server Windows application that connects to SQL Server for managing

Maritime database

Land-sea Communication

Radio station Hardware at each coastal station for broadcasting messages, receive

messages through HF wave

Transceiver Hardware at each vessel for receiving messages, send messages through


Object Description

HF wave

On-sea System

Fisher User of On-sea Terminal application, responsible for monitoring their

own vessel position on map, being alerted about storm, weather

information

On-sea Terminal Application on portable computing device that connects to transceiver,

then visualizes received information to fisher, automatically send back

vessel position to transceiver.

Table 4-1: System Context Description

4.2 Architecture Overview

4.2.1 Diagram

4.2.1.1 On-land System

4.2.1.1.1 Database Server

Diagram 4-2: Database Server Architecture

No Package Name Description

1 UI (Console) Console display, informs user about

connections or database altering activities

2 Controller Main controller

3 From-Client Remote Manage processes when Viewer or



Coastal Station remotes to server

4 To-Client Remote Manage processes when server remotes to

Viewer / Coastal Station clients

5 SQL Database Access Connects to SQL Database Server

(default: local host), control data flow

from/to SQL Database Server

6 Configuration Contains application setting up parameters

7 Common Struct Common objects for binding data

8 Exception Management Exception management

Table 4-2: Database Server Architecture Description

4.2.1.1.2 Viewer

Diagram 4-3: Viewer Architecture Diagram


1 GUI Display graphical interface


3 Boast cast Messages Creator Create “Boast cast” Messages



4 Google Earth Handler Prepare display data and control Google

Earth API

5 Server Connection Connect to database server, read data

from/write data into database server


7 Math Helper Provide math functions

8 Logs Management Log files management

9 Exception Management Exceptions management


Table 4-3: Viewer Architecture Description

4.2.1.1.3 Coastal Station

Diagram 4-4: Coastal Station Architecture


1 GUI Display graphical interface


3 Server Connection Connect to database server, read data

from/write data into database server



4 Transceiver Connection Connect to transceiver, receive data from /

send data to transceiver

5 Error Correction Algorithm Algorithm to correct errors, eliminate

noises generated through land-sea HF

communication

6 Audio Decode/Encode Modem Transform text into audio, audio into text



9 Exception Management Exception management

Table 4-4 Coastal Station Architecture Description

4.2.1.2 On-sea Terminal

Common Struct

Presentation Layer

Business Layer

Data Access Layer

Common Layer

Exception

Management

GUI

ControllerData correctionAudio Soft-

Modem

Tranceiver

connection

<<uses>>

<<uses>> <<uses>>

Utility

«uses»

Diagram 4-2: On Sea Terminal Architecture


1 GUI Display graphical interface to fisher

2 Controller Control the main program, process data

3 Transceiver Connection Connect to transceiver, receive data from /

send data to transceiver

4 Error Correction Algorithm to check the correctness of

data, generated by audio noise through

land-sea HF communication, correct it if



possible

5 Audio Soft-modem Convert audio data from analog to digital

and digital to analog, communicate with

the device audio in/out port

6 Common Struct Common message type receive/broadcast

from/to coastal stations

7 Exception Management Manage exception of on-sea terminal

program

8 Utilization Contains utilization function for the

program

Table 4-2 On-sea Terminal Architecture Description

4.3 Detailed Design Description

4.3.1 On-land System

4.3.1.1 Database Server

4.3.1.1.1 Class diagram

4.3.1.1.1.1 Diagram

Diagram 4-5: Database server – class diagram


4.3.1.1.1.2 Class Description

4.3.1.1.1.2.1 Server class

4.3.1.1.1.2.1.1 Attributes

No Name Type Description

1 Port int

2 dbConnectManager MaritimeDAL

4.3.1.1.1.2.1.2 Methods

4.3.1.1.1.2.1.2.1 ConfigConnection

Method name void ConfigConnection()

Description Setup connection so that server can listen if there is any client connect to

server, using SOAP

Parameters void

Return void

4.3.1.1.1.2.1.2.2 CloseConnection

Method name void CloseConnection()

Description Close connection

Parameters void

Return void

4.3.1.1.1.2.1.2.3 StartPositionMessageThread

Method name void StartPositionMessageThread()

Description Create a queue to manage all vessel position updating into Maritime database

Parameters void

Return void

4.3.1.1.1.2.1.2.4 AddViewerClient

Method name void AddViewerClient(string clientID)

Description add clientID string into list of Viewer client ID

Parameters clientID: string client ID, generated by Viewer client

application

Return void


4.3.1.1.1.2.1.2.5 AddCoastalStationClient

Method name void AddCoastalStationClient (string clientID)

Description add clientID string into list of CoastalStation client ID

Parameters clientID: string client ID, generated by CoastalStation

client application

Return void

4.3.1.1.1.2.1.2.6 RemoveViewerClient

Method name void RemoveViewerClient(string clientID)

Description remove clientID string from list of Viewer client ID, usually be called when

Viewer client disconnects to server

Parameters clientID: string client ID, generated by Viewer client

application

Return void

4.3.1.1.1.2.1.2.7 RemoveCoastal StationClient

Method name void RemoveCoastalStationClient(string clientID)

Description Remove clientID string from list of CoastalStation client ID, usually be called

when CoastalStation disconnects to server

Parameters clientID: string clientID, generated by CoastalStation

client applicaton

Return void

4.3.1.1.1.2.1.2.8 AddPositionMessageIntoQueue

Method name void AddPositionMessageIntoQueue(VesselPosition positionRecord)

Description Add position message update calling function into a queue so that they will

process in order, prevent Maritime database connection conflicts

Parameters positionRecord: VesselPosition position information to be inserted

into database

Return void

4.3.1.1.1.2.1.2.9 PopPositionMessageFromQueue

Method name VesselPosition PopPositionMessageFromQueue()

Description Pop position record of vessel from queue to be processed

Parameters void


Return the popped VesselPosition, null if the queue is empty

4.3.1.1.1.2.1.2.10 InsertBroadcastMessage

Method name void InsertBroadcastMessage(BroadcastMessage message)

Description Insert broadcast message into Maritime database. It calls MaritimeDAL

method to insert.

Parameters message: BroadcastMessage message to be inserted

Return void

4.3.1.1.1.2.1.2.11 InsertSOSMessage

Method name void InsertSOSMessage(SOSMessage message)

Description Insert SOS message into Maritime database. It calls MaritimeDAL method to

insert.

Parameters message: SOSMessage message to be inserted

Return void

4.3.1.1.1.2.1.2.12 GetVesselLastestInfo

Method name List<VesselPosition> GetVesselLastestInfo()

Description Connect to Maritime database, then get latest position records of all vessels

Parameters void

Return list of position records, null if there is no information

4.3.1.1.1.2.2 TransporterDelegate

It is not a class. We just use it to group these following delegates.

4.3.1.1.1.2.2.1 NewStormMessageHandler

Method name void NewStormMessageHandler (BroadcastMessage message)

Description delegate for CoastalStation client to be able to register a handler for processing

a new storm message

Parameters message: BroadcastMessage new storm message

Return void

4.3.1.1.1.2.2.2 NewSOSMessageHandler

Method name void NewSOSMessageHandler(SOSMessage message)

Description Delegate for Viewer client to be able to register a handler for processing a new


SOS message

Parameters message: SOSMessage new SOS message

Return void

4.3.1.1.1.2.3 ConfigIniFileManager class

4.3.1.1.1.2.3.1 Attributes


1 fileName string name of .ini configuration

file

2 port int server listening port

3 dbConnectionString string connection string to

Maritime database

4.3.1.1.1.2.3.2 Methods

4.3.1.1.1.2.3.2.1 Read

Method name void Read (string filename)

Description Open ini file, read values, then save into its members

Parameters filename: string file path to be read

Return void

4.3.1.1.1.2.3.2.2 Save

Method name void Save(string filename)

Description Open ini file, write its members’ value into file

Parameters filename: string file path to be written

Return void

4.3.1.1.1.2.4 MaritimeDAL class

4.3.1.1.1.2.4.1 Attributes


1 connectionString string connection string to connect into

Maritime database


4.3.1.1.1.2.4.2 Methods

4.3.1.1.1.2.4.2.1 Open

Method name bool Open(string connectionString)

Description Open connection to Maritime database

Parameters connectionString: string connection string to Maritime

database

Return bool

4.3.1.1.1.2.4.2.2 Close

Method name void Close()

Description Close connection to Maritime database

Parameters void

Return void

4.3.1.1.1.2.4.2.3 GetBroadcastMessage

Method name List<BroadcastMessage> GetBroadcastMessage(DateTime fromDateTime)

Description Get the broadcast message which has created date time after fromDateTime

Parameters fromDateTime: DateTime created date time of message

Return list of broadcast message, null if there is no messages

4.3.1.1.1.2.4.2.4 GetVesselInfoByVesselID

Method name Vessel GetVesselInfoByVesselID(int vesselID)

Description Get vessel information from Maritime database by vessel ID

Parameters vesselID: int vessel ID (primary key of Vessel

table in Maritime database)

Return Vessel object, null if there is no information

4.3.1.1.1.2.4.2.5 GetVoyageByVesselID

Method name List<VesselPosition> GetVoyageByVesselID(int vesselID)

Description Get voyage of a vessel that has vesselID



Return list of position records of this vessel, null if there is no information


4.3.1.1.1.2.4.2.6 InsertBroadcastMessage

Method name void InsertBroadcastMessage(BroadcastMessage message)

Description Insert broadcast message into Maritime database

Parameters message: BroadcastMessage message to be inserted

Return void

4.3.1.1.1.2.4.2.7 InsertSOSMessage

Method name void InsertSOSMessage(SOSMessage message)

Description Insert SOS message into Maritime database

Parameters message: SOSMessage message to be inserted

Return void

4.3.1.1.1.2.4.2.8 InsertPositionMessage

Method name void InsertPositionMessage(VesselPosition positionRecord)

Description Insert position information into Maritime database

Parameters positionRecord: VesselPosition position record to be inserted

Return void

4.3.1.1.1.2.4.2.9 GetVesselLastestPosition

Method name List<VesselPosition> GetVesselLastestPosition()

Description Get list of the latest position records of all vessels

Parameters void


4.3.1.1.1.2.5 ICoastalStationRemote interface

4.3.1.1.1.2.5.1 Attributes

This interface has no attributes.

4.3.1.1.1.2.5.2 Methods

4.3.1.1.1.2.5.2.1 RegisterCoastalStationTransporter

Method name void RegisterCoastalStationTransporter(string clientID,

CoastalStationTransporter csTransporter)

Description Inform server that CoastalStation client is connected and allow server to

remote CoastalStation client through transporter object


Parameters

clientID: string client ID string, generated by

CoastalStation application

csTransporter: CoastalStationTransporter

transporter object to be used in

remote from server to

CoastalStation client

Return void

4.3.1.1.1.2.5.2.2 UnregisterCoastalStationTransporter

Method name void UnregisterCoastalStationTransporter(string clientID)

Description Inform server that CoastalStation client is disconnected and server cannot use

transporter object to remote

Parameters clientID: string client ID string, generated by

CoastalStation application

Return void



Description Get the broadcast message which has created date time after fromDateTime


Return list of broadcast message, null if there is no messages

4.3.1.1.1.2.5.2.4 GetVesselInfoByID

Method name Vessel GetVesselInfoByID(int vesselID)





4.3.1.1.1.2.5.2.5 CommitPositionMessageFromVessel

Method name void CommitPositionMessageFromVessel(VesselPosition positionRecord)

Description Commit vessel position information to Database Server

Parameters positionRecord: VesselPosition position record to be committed

Return void


4.3.1.1.1.2.5.2.6 CommitSOSMessageFromVessel

Method name void CommitSOSMessageFromVessel(SOSMessage message)

Description commit SOS message to Database Server

Parameters message: SOSMessage message to be committed

Return void

4.3.1.1.1.2.6 IViewerRemote interface

4.3.1.1.1.2.6.1 Attributes


4.3.1.1.1.2.6.2 Methods

4.3.1.1.1.2.6.2.1 RegisterViewerTransporter

Method name void RegisterViewerTransporter(string clientID, ViewerTransporter

vTransporter)

Description Inform server that Viewer client is connected and allow server to remote

Viewer client through transporter object

Parameters clienID: string client ID string, generated by Viewer

application

vTransporter: ViewerTransporter transporter object to be used in

remote from server to Viewer client

Return void

4.3.1.1.1.2.6.2.2 UnregisterViewerTransporter

Method name void UnregisterViewerTransporter(string clientID)

Description Inform server that Viewer client is disconnected and server cannot use

transporter object to remote

Parameters clientID: string client ID string, generated by Viewer

application

Return void

4.3.1.1.1.2.6.2.3 GetVesselLastestInfo

Method name List<VesselPosition> GetVesselLastestInfo()

Description Get list of the latest position records of all vessels

Parameters void



4.3.1.1.1.2.6.2.4 GetVoyageByVesselID

Method name List<VesselPosition> GetVoyageByVesselID(int vesselID)

Description Get voyage of a vessel that has vesselID



Return list of position records of this vessel, null if there is no information

4.3.1.1.1.2.6.2.5 GetVesselInfoByID

Method name Vessel GetVesselInfoByID(int vesselID)





4.3.1.1.1.2.6.2.6 CommitBroadcastMessage

Method name void CommitBroadcastMessage(BroadcastMessage message)

Description Commit broadcast message to Database Server

Parameters message: BroadcastMessage message to be committed

Return void

4.3.1.1.1.2.6.2.7 GetLastestStormMessage

Method name BroadcastMessage GetLastestStormMessage()

Description Get the latest storm message in Maritime database

Parameters void

Return BroadcastMessage with type of Storm, null if there is no information


4.3.1.1.2 Sequence Diagram

4.3.1.1.2.1 Start / Close Program

Diagram 4-6: Database Server – Start program sequence diagram

Diagram 4-7: Database server – Close program sequence diagram


4.3.1.1.2.2 Start position message thread

Diagram 4-8: Database Server – Start position message thread sequence diagram

4.3.1.1.2.3 Register / Unregister Viewer Client

Diagram 4-9: Database Server – Register Viewer client sequence diagram

Diagram 4-10: Database server – Unregister Viewer client sequence diagram


4.3.1.1.2.4 Register / Unregister CoastalStation client

Diagram 4-11: Database server – Register CoastalStation client sequence diagram

Diagram 4-12: Database server – Unregister CoastalStation client sequence diagram

4.3.1.1.2.5 Insert position message from vessel

Diagram 4-13: Database server – Insert position message sequence diagram


4.3.1.1.2.6 Insert Broadcast message from Viewer

Diagram 4-14: Database server – Insert broadcast message sequence diagram

4.3.1.1.2.7 Insert SOS message from vessels

Diagram 4-15: Database server – Insert SOS message sequence diagram


4.3.1.1.2.8 Insert storm message from Viewer

Diagram 4-16: Database server – Insert storm message sequence diagram


4.3.1.2 Viewer

4.3.1.2.1 Class Diagram

4.3.1.2.1.1 Diagram

Diagram 4-17: Viewer – class diagram


4.3.1.2.1.2.1 MainController class

4.3.1.2.1.2.1.1 Attributes


1 autoUpdateData AutoUpdateData Manages automatically

updating message from

database



2 serverConnectManager ServerConnectManager Connects to database &

manages database data

altering

3 searchForm SearchForm Application search GUI

Form

4 mainForm MainForm Application main GUI

Form

5 overViewForm overViewForm Application overview

GUI Form

6 createMeesagesForm CreateMeesagesForm Application create new

broadcast messages GUI

Form

7 vesselManager VesselManager Management Vessel list

4.3.1.2.1.2.1.2 Methods

4.3.1.2.1.2.1.2.1 AutoBroadcastMessage

Method name void ControlGetData()

Description Synchronize threads during time the application get data from data base. It is

called by AutoUpdateData when time interval is reached.

Parameters void

Return void

4.3.1.2.1.2.1.2.2 ControlUpdateData

Method name void ControlUpdateData()

Description Synchronize threads during time the application get update data to GUI. It is

called by AutoUpdateData when it finished get data from database.

Parameters void

Return void

4.3.1.2.1.2.1.2.3 ControlDisplayVessel

Method name void ControlDisplayVessel()

Description Display Vessels as layers on GoogleEarth API. It is called by

ControlUpdateData.

Parameters void


Return void

4.3.1.2.1.2.1.2.4 ControlDisplayTyphoon

Method name void ControlDisplayTyphoon()

Description Display Typhoon as a layer on GoogleEarth API. It is called by

ControlUpdateData after it calls ControlDisplayVessel().

Parameters void

Return void

4.3.1.2.1.2.1.2.5 ControlDisplaySOS

Method name void ControlDisplaySOS()

Description Display SOS messages as layers on GoogleEarth API. It is called by

ControlUpdateData after it calls ControlDisplayTyphoon ().

Parameters void

Return void

4.3.1.2.1.2.1.2.6 ConfigParameters

Method name void ConfigPagrameters()

Description Configuration parameters

Parameters void

Return void

4.3.1.2.1.2.2 ServerConnectManager class

4.3.1.2.1.2.2.1 Attributes


1 ServerIP string IP of server

2 ServerPort int Port of server

3 eventHandler IServerConnectManager Handle event from

database

4.3.1.2.1.2.2.2 Methods

4.3.1.2.1.2.2.2.1 Connect

Method name bool Connect()

Description Make a connection to database to get data.


Parameters void

Return true if connect success, false if fail

4.3.1.2.1.2.2.2.2 CommitMessages

Method name bool CommitMessages(string message)

Description Commit Broadcast messages to database.

Parameters message : string Content of message

Return true if connect success, false if fail

4.3.1.2.1.2.2.2.3 GetVesselLatestInfo

Method name Vessel GetVesselLatestInfo()

Description Get VesselLatestInfo from database

Parameters void

Return New List<Vessel>

4.3.1.2.1.2.2.2.4 GetVesselHistory

Method name Vessel GetVesselHistory()

Description Get VesselHistory from database

Parameters void

Return New List<Vessel>

4.3.1.2.1.2.2.2.5 GetVesselOwner

Method name Owner GetVesselOwner()

Description Get VesselOwner from database

Parameters void

Return New Owner object

4.3.1.2.1.2.2.2.6 GetLatestTyphoonMessage

Method name Owner GetLatestTyphoonMessage()

Description Get TyphoonMessage from database

Parameters void

Return New Typhoon object


4.3.1.2.1.2.3 AutoUpdateData class

4.3.1.2.1.2.3.1 Attributes


1 Interval int Interval of Auto Update

Data

2 CallBackFunction object Callback when update

data finished

4.3.1.2.1.2.3.2 Methods

4.3.1.2.1.2.3.2.1 Start

Method name void Start()

Description Start AutoUpdateData

Parameters void

Return void

4.3.1.2.1.2.3.2.2 Stop

Method name void Stop()

Description Stop AutoUpdateData

Parameters void

Return void

4.3.1.2.1.2.3.2.3 AutoUpdateLatestInfo

Method name void AutoUpdateLatestInfo()

Description Get VesselLatestInfo from database and add to List<vessel>

Parameters void

Return void

4.3.1.2.1.2.3.2.4 AutoUpdateTyphoon

Method name void AutoUpdateTyphoon()

Description Get Typhoon data from database and add to object Typhoon

Parameters void

Return void


4.3.1.2.1.2.4 VesselManager class

4.3.1.2.1.2.4.1 Attributes


1 VesselList List<Veseel> List of Vessel

4.3.1.2.1.2.4.2 Methods

4.3.1.2.1.2.4.2.1 AddVessel

Method name bool AddVessel(Vessel vessel)

Description Add vessel to list Vessel

Parameters vessel:Vessel vessel object to add in List<Vessel>

Return true if vessel is added success, fall if fail

4.3.1.2.1.2.4.2.2 RemoveVessel

Method name bool RemoveVessel(int index)

Description Remove vessel from list Vessel

Parameters index: int Index of vessel in List<Vessel>

Return true if vessel is remove success, fall if fail

4.3.1.2.1.2.4.2.3 EditVessel

Method name bool EditVessel(int index)

Description Edit vessel from list Vessel

Parameters index: int Index of vessel in List<Vessel>

Return true if vessel is edit success, fall if fail

4.3.1.2.1.2.4.2.4 Count

Method name int Count()

Description Return number of vessels in List<Vessel>

Parameters void

Return number of vessels in list

4.3.1.2.1.2.4.2.5 ToTable

Method name Datatable Totable()

Description Return a Table of vessels in List<Vessel>


Parameters void

Return Datatable of List<Vessel>

4.3.1.2.1.2.4.2.6 FindByVesselNo

Method name Vessel FindByVesselNo (string vesselNo)

Description Return a vessel in List<Vessel> base on vessel number

Parameters vesselNo: string Number of vessel

Return New Vessel object

4.3.1.2.1.2.4.2.7 FindByVesselID

Method name Vessel FindByVesselID (int ID)

Description Return a vessel in List<Vessel> base on vessel ID

Parameters ID:int ID of vessel


4.3.1.2.1.2.4.2.8 FindByVesselOwner

Method name Vessel FindByVesselOwner (string name)

Description Return a vessel in List<Vessel> base on name of owner

Parameters name: string Name of owner


4.3.1.2.1.2.5 Vessel class

4.3.1.2.1.2.5.1 Attributes


1 VesselID int Id of vessel

2 VesselOwner string Owner of vessel

3 VesselHistoryID int HistoryId of vessel

4 VesselNumber string Number of vessel

5 VesselType enum Type of vessel

6 VesselLat float Latitude of vessel

7 VesselLng float Longtitude of vessel



8 VesselHeading float Heading of vessel

9 VesselSpeed float Speed of vessel

10 Vesse LastReceiveData Datetime Last Receive data of

vessel

11 VesselSOS bool Vessel being transmits

SOS messages

12 VesselApiID int ID in GoogleEarth API

13 VesselIsNew bool Vessel is new

14 VesselIsRead bool Vessel is displayed

4.3.1.2.1.2.5.2 Methods

4.3.1.2.1.2.5.2.1 Equals

Method name bool Equals (Vessel vessel)

Description Compare 2 vessels

Parameters vessel: Vessel Vessel to compare

Return true if 2 vessel is equals, fail if not

4.3.1.2.1.2.6 MathHelper class

4.3.1.2.1.2.6.1 Attributes

4.3.1.2.1.2.6.2 Methods

4.3.1.2.1.2.6.2.1 Distance2point

Method name Float Distance2point(GLatLng g1, GLatLng g2)

Description Calculate distance of 2 point

Parameters

g1:GLatLng Position 1

g2: GLatLng Position 2

Return Distance of 2 point

4.3.1.2.1.2.6.2.2 PointsOfCircle

Method name GLatLng PointsOfCircle(Circle circle,double angle)

Description Calculate position of a point in circle


Parameters

circle: Circle Circle to calculate

angle: double Angle at the center of circle

Return New GLatLng object

4.3.1.2.1.2.6.2.3 FindTangents

Method name GLatLng[] FindTangents (Circle c1,Circle c2)

Description Calculate tangents of 2 circle

Parameters

c1: Circle Circle 1

c2: Circle Circle 2

Return New array GLatLng[] objects

4.3.1.2.1.2.7 GLatLng class

4.3.1.2.1.2.7.1 Attributes


1 EarthRadiusInKilometers float Earth Radius

2 Longitude float Longitude

3 Latitude float Latitude

4.3.1.2.1.2.7.2 Methods

4.3.1.2.1.2.7.2.1 DegreeToRadian

Method name float DegreeToRadian(float deg)

Description Calculate radian of a degree

Parameters deg: float Angle in degree

Return Angle in radian

4.3.1.2.1.2.7.2.2 RadianToDegree

Method name float RadianToDegree(float rad)

Description Calculate degree of a radian

Parameters rad: float Angle in radian

Return Angle in degree


4.3.1.2.1.2.7.2.3 DistanceTo

Method name float DistanTo(GLatLng endPoint)

Description Calculate distance of this point to another point

Parameters endPoint : GLatLng End point to calculate

Return Distance of this point to another point

4.3.1.2.1.2.7.2.4 BearingTo

Method name float BearingTo(GLatLng endPoint)

Description Calculate bearing of this point to another point

Parameters endPoint: GLatLng End point to calculate

Return Bearing of this point to another point

4.3.1.2.1.2.8 GoogleEarthCommands class

4.3.1.2.1.2.8.1 Attributes


1 IconScale1 float Icon scale when display

2 IconScale2 float Icon scale when click

3 SOSIconScale1 float Icon SOS when display

4 SOSIconScale1 float Icon SOS when click

5 DefaultRange float Default range on

GoogleEarth API

6 CenterLat float Center point latitude

7 CenterLng floar Center point longitude

4.3.1.2.1.2.8.2 Methods

4.3.1.2.1.2.8.2.1 DrawCircle

Method name void DrawCircle (Circle circle)

Description Draw a circle on GoogleEarth

Parameters circle:Circle Circle to draw

Return void


4.3.1.2.1.2.8.2.2 DrawLine

Method name void DrawLine (GLatLng p1,GLatLng p2)

Description Draw a line on GoogleEarth

Parameters

p1: GLatLng Begin position

p2: GLatLng End position

Return void

4.3.1.2.1.2.8.2.3 DrawTyphoon

Method name void DrawLine (Typhoon typhoon)

Description Draw a typhoon on GoogleEarth

Parameters typhoon: Typhoon Typhoon to draw

Return void

4.3.1.2.1.2.8.2.4 SetVesselApiID

Method name void SetVesselApiID (int ID)

Description Set ApiID of a vessel

Parameters ID: int ID of Vessel

Return Void

4.3.1.2.1.2.8.2.5 DrawVessel

Method name void DrawVessel (Vessel vessel)

Description Draw a vessel on Google Earth

Parameters vessel:Vessel Vessel to draw

Return Void

4.3.1.2.1.2.8.2.6 UpdateVessel

Method name void UpdateVessel (Vessel vessel)

Description Update vessel on Google Earth

Parameters vessel :Vessel Vessel to update

Return Void


4.3.1.2.1.2.8.2.7 ChangeIcon

Method name void ChangeIcon (object obj)

Description Change Icon of a layer on Google Earth

Parameters obj:object Object need to be change Icon

Return Void

4.3.1.2.1.2.8.2.8 DeleteVessel

Method name void DeleteVessel (Vessel vessel)

Description Delete a vessel on Google Earth

Parameters vessel:Vessel Vessel to delete

Return Void

4.3.1.2.1.2.8.2.9 DeleteAll

Method name void DeleteAll ()

Description Delete all layers on Google Earth

Parameters Void

Return Void

4.3.1.2.1.2.8.2.10 SetVesselDescription

Method name void SetVesselDescription(Vessel vessel)

Description Set description for Vessel on Google Earth

Parameters vessel: Vessel Vessel should be displayed

description

Return Void

4.3.1.2.1.2.8.2.11 SOSVisualization

Method name void SOSVisualization (Vessel vessel)

Description Set Display SOS Vessel on Google Earth

Parameters vessel: Vessel Vessel in troble

Return Void

4.3.1.2.1.2.8.2.12 CreateLookAt

Method name void CreateLookAt (int alt,float lat,float lng)


Description Create “look at” at a position

Parameters

alt: int Altitude of “look at”

lat: float Latitude of position

lng: float Longitude of position

Return Void

4.3.1.2.1.2.8.2.13 CreatePlaceMark

Method name void CreatePlaceMark (GLatLng p)

Description Create a place mark on GoogleEarth

Parameters p: GLatLng Point to create place mark

Return Void

4.3.1.2.1.2.8.2.14 DeletePlaceMark

Method name void DeletePlaceMark (PlaceMark pm)

Description Delete a place mark on GoogleEarth

Parameters pm:PlaceMark PlaceMark to delete

Return Void

4.3.1.2.1.2.9 MainForm class

4.3.1.2.1.2.9.1 Attributes


1 GeIsReady bool Loading GoogleEarth is

finished

4.3.1.2.1.2.9.2 Methods

4.3.1.2.1.2.9.2.1 UpdateData

Method name void UpdateData ()

Description Updata data to GUI

Parameters void

Return void

4.3.1.2.1.2.9.2.2 DrawLayers

Method name void DrawLayers ()


Description Call methods drawing in GoogleEarthCommand for drawing on Google Earth

Parameters void

Return void

4.3.1.2.1.2.9.2.3 GeReady

Method name void GeReady ()

Description Callback function of GoogleEarth API, set GeIsReady to true

Parameters void

Return void

4.3.1.2.1.2.9.2.4 GeFailed

Method name void GeFailed ()

Description Callback function of GoogleEarth API, set GeIsReady to false

Parameters void

Return void

4.3.1.2.1.2.9.2.5 SetApiID

Method name void SetApiID ()

Description Callback function of GoogleEarth API, set ApiID of Vessel

Parameters void

Return void

4.3.1.2.1.2.9.2.6 VesselClick

Method name void VesselClick (int vesselID)

Description Callback function of GoogleEarth API, a vessel is click on GoogleEarth

Parameters vesselID: int ID of vessel clicked

Return void

4.3.1.2.1.2.9.2.7 ShowShipHistory

Method name void ShowShipHistory (int vesselID)

Description Callback function of GoogleEarth API, vessel should be show its history

Parameters vesselID: int ID of vessel clicked


Return void

4.3.1.2.1.2.9.2.8 SetPlaceMarkLocation

Method name void SetPlaceMarkLocation(float lat,float lng)

Description Callback function of GoogleEarth API, PlaceMark is “relocation”

Parameters

lat: float New latitude of PlaceMark

lng: float New longitude of PlaceMark

Return void

4.3.1.2.1.2.10 SearchingForm class

4.3.1.2.1.2.10.1 Attributes


1 ResultData Datatable Result data

4.3.1.2.1.2.10.2 Methods

4.3.1.2.1.2.10.2.1 btnSearch_Click

Method name void btnSearch_Click (object sender, EventArgs e)

Description Button Search clicked

Parameters

sender: object Default arguments of delegate for

event handler

e: EventArgs Default arguments of delegate for

event handler

Return void

4.3.1.2.1.2.10.2.2 createMenu

Method name void createMenu ()

Description Create menu for SearchingForm

Parameters void

Return void


4.3.1.2.1.2.11 OverviewForm class

4.3.1.2.1.2.11.1 Attributes

4.3.1.2.1.2.11.2 Methods

4.3.1.2.1.2.11.2.1 FillData

Method name void FillData ()

Description Display data to GUI

Parameters void

Return void

4.3.1.2.1.2.11.2.2 CreateMenu

Method name void CreateMenu ()

Description Create menu for OverviewForm

Parameters void

Return void

4.3.1.2.1.2.12 CreateMessagesForm class

4.3.1.2.1.2.12.1 Attributes

4.3.1.2.1.2.12.2 Methods

4.3.1.2.1.2.12.2.1 btnOK_Click

Method name void btnOK_Click (object sender, EventArgs e)

Description Button OK Clicked

Parameters


event handler


event handler

Return void

4.3.1.2.1.2.12.2.2 checkInputDouble

Method name bool checkInputDouble(string input)

Description Check input string is a double

Parameters input: string Input should be checked

Return True if input is double, fall if not


4.3.1.2.1.2.12.2.3 checkInput

Method name bool checkInput(string input)

Description Check input

Parameters input:string Input should be checked

Return True if input has length >0


4.3.1.2.2.1 Start program

Diagram 4-18: Viewer – Start program sequence diagram

4.3.1.2.2.2 Update VesselLatestInfo


Diagram 4-19: Viewer – Update Vessel Latest Information sequence diagram

4.3.1.2.2.3 Display Vessel History

Diagram 4-20: Viewer – Display Vessel History sequence diagram

4.3.1.2.2.4 S.O.S Messages process


Diagram 4-21: Viewer – SOS Messages Process sequence diagram

4.3.1.2.2.5 Searching vessel information

Diagram 4-22: Viewer – Searching Vessel Information sequence diagram


4.3.1.3 Coastal Station

4.3.1.3.1 Class Diagram

4.3.1.3.1.1 Diagram

Diagram 4-23: Coastal Station – Class Diagram


4.3.1.3.1.2.1 MainController class

4.3.1.3.1.2.1.1 Attributes


1 serverConnectManager ServerConnectManager Connects to database &

manages database data

altering

2 transceiverConnectManager TransceiverConnectManager Connects to transceiver &

read/write data into

transceiver

3 iniConfigManager ConfigIniFileManager Read/write initial

configuration settings of

application

4 mainForm MainForm Application main GUI

Form

5 updateTimer AutoRunTimer Manages automatically

updating message from

database



6 broadcastTimer AutoRunTimer Manages automatically

broadcasting messages to

vessels

4.3.1.3.1.2.1.2 Methods

4.3.1.3.1.2.1.2.1 AutoBroadcastMessage

Method name void AutoBroadcastMessage()

Description Automatically broadcast messages to vessels. It is called by AutoRunTimer

when time interval is reached.

Parameters void

Return void

4.3.1.3.1.2.1.2.2 Broadcast Message

Method name void BroadcastMessage(BroadcastMessage message)

Description

Broadcast a message to vessels, actually implementing through:

- Encode message

- Modulate message

- Send data to transceiver

Parameters message: BroadcastMessage Message to be broadcasted

Return void

4.3.1.3.1.2.1.2.3 HandleStormMessage

Method name void HandleStormMessage(BroadcastMessage message)

Description process storm message: broadcast it immediately and display it into GUI

Parameters message: BroadcastMessage storm message to be broadcasted

Return void


Method name BroadcastMessage GetBroadcastMessage()

Description Get broadcast message from Database Server.

Parameters void

Return BroadcastMessage, null if there is no messages or error


4.3.1.3.1.2.1.2.5 ReconfigParameters

Method name void ReconfigParameters(object parameter)

Description Change parameters due to new value

Parameters parameter: object value of parameters to be updated

Return void

4.3.1.3.1.2.1.2.6 ShowMessageHistory

Method name void ShowMessageHistory()

Description Show MessageHistoryForm as a modal form

Parameters void

Return void

4.3.1.3.1.2.2 MessageHistoryForm class

4.3.1.3.1.2.2.1 Attributes

This is a class that is inherited System.Windows.Forms and generated by Visual Studio 2010 tool.

We do not mention its non-public attributes here.

4.3.1.3.1.2.2.2 Methods

4.3.1.3.1.2.2.2.1 ShowDialog

Method name DialogResult ShowDialog()

Description Show dialog as a modal dialog form. This method is inherit from

System.Windows.Forms in C#

Parameters void

Return value of type System.Windows.Forms.DialogResult (C#)

4.3.1.3.1.2.3 MainForm class

4.3.1.3.1.2.3.1 Attributes



4.3.1.3.1.2.3.2 Methods

4.3.1.3.1.2.3.2.1 InformBroadcastMessage

Method name void InformBroadcastMessage(BroadcastMessage message)

Description display message onto GUI and inform this message to have just been

broadcasted

Parameters message: BroadcastMessage Message to have been broadcasted


Return void

4.3.1.3.1.2.3.2.2 btnMessageBroadcast_Clicked

Method name void btnMessageBroadcast_Clicked(object sender, EventArgs e)

Description Delegate for event handler when Broadcast message button is clicked. This

method is generated by Visual Studio 2010 tool

Parameters


event handler


event handler

Return Void

4.3.1.3.1.2.3.2.3 InformNewBroadcastMessage

Method name void InformNewBroadcastMessage(BroadcastMessage message)

Description Display message onto GUI and inform this message to have just updated from

Database Server

Parameters message: BroadcastMessage message that have been updated

from Database Server

Return void

4.3.1.3.1.2.3.2.4 btnConfigSetting_Clicked

Method name void btnConfigSetting_Clicked(object sender, EventArgs e)

Description

Delegate for event handler when Config Setting button is clicked. This method

is generated by Visual Studio 2010 tool.

It call ShowDialog() method of SettingForm.

Parameters

sender: object Default argument of delegate for

event handler

e: EventArgs Default argument of delegate for

event handler

Return void

4.3.1.3.1.2.3.2.5 btnMessageHistoryShow_Clicked

Method name void btnMessageHitoryShow_Clicked(object sender, EventArgs e)

Description

Parameters sender: object Default argument of delegate for


event handler

e: EventArgs Default argument of delegate for

event handler

Return void

4.3.1.3.1.2.4 SettingForm class

4.3.1.3.1.2.4.1 Attributes



4.3.1.3.1.2.4.2 Methods

4.3.1.3.1.2.4.2.1 ShowDialog

Method name void ShowDialog()

Description Display SettingForm as a modal form

Parameters void

Return void

4.3.1.3.1.2.4.2.2 Setting ParameterChanged

Method name void SettingParameterChanged(object parameter)

Description Event handler when user change setting parameters. It changes value of

relative members of FileIniConfigManager.

Parameters parameter: object parameter value has changed

Return void

4.3.1.3.1.2.5 ConfiglniFileManager class

4.3.1.3.1.2.5.1 Attributes


1 filename string filename to be read/written

2 serverIP string server IP address

3 serverPort int server listening port

4 broadcastTimecodeList object list of time code for

automatically broadcasting

5 updateTimecodeList object list of time code for

automatically updating


4.3.1.3.1.2.5.2 Methods

4.3.1.3.1.2.5.2.1 Read

Method name void Read(string filename)

Description It opens .ini file and reads the file and save it into its attributes

Parameters filename: string file path to be read

Return void

4.3.1.3.1.2.5.2.2 Write

Method name void Write(string filename)

Description It opens .ini file and writes attributes’ value into this file

Parameters filename: string file path to be written

Return void

4.3.1.3.1.2.6 ErrorCorrectManager class

4.3.1.3.1.2.6.1 Attributes

This class has no attributes.

4.3.1.3.1.2.6.2 Methods

4.3.1.3.1.2.6.2.1 Encode

Method name byte[] Encode(byte[] source)

Description Encode data before sending, using xxx algorithm

Parameters source: byte[] data to be encoded in bytes

Return encoded data in bytes

4.3.1.3.1.2.6.2.2 Decode

Method name byte[] Decode(byte[] source)

Description Decode data after receiving, using Viterbi decoding algorithm

Parameters source: byte[] data to be decoded in bytes

Return decoded data in bytes

4.3.1.3.1.2.7 AudioModem class

4.3.1.3.1.2.7.1 Attributes

This class has no attributes.


4.3.1.3.1.2.7.2 Methods

4.3.1.3.1.2.7.2.1 Modulate

Method name byte[] Modulate(byte[] source)

Description Embed source data into audio so that it can be transferred using HF

communication, using AFSK algorithm

Parameters source: byte[] data to be modulated

Return modulated data in bytes

4.3.1.3.1.2.7.2.2 Demodulate

Method name byte[] Demodulate (byte[] source)

Description Get embedded data in audio stream after receiving it from transceiver

Parameters source: byte[] data to be demodulated

Return demodulated data in bytes

4.3.1.3.1.2.8 AutoRunTimer class

4.3.1.3.1.2.8.1 Attributes


1 timecodeList object list of time code for processing

2 callbackFunction object delegate function for when a call is

active by timer

3 timer System.Timers.Timer timer for calling callbackFunction

when time code is reach

4.3.1.3.1.2.8.2 Methods

4.3.1.3.1.2.8.2.1 SetupWithTimecodeList

Method name void SetupWithTimecodeList(TimecodeList timecodes, ElapsedEventHandler

callbackFunction)

Description Setup with list of timecode. It saves the list of timecode and starts running

timer

Parameters timecodes: TimecodeList list of time code when timer calls

callback function

callbackFunction:

ElapsedEventHandler

callback function called when time

code reaches

Return void


4.3.1.3.1.2.8.2.2 ConfigNextInterval

Method name void ConfigNextInterval()

Description

It changes time interval for the next call so that the next call is called at the

next timecode in timecodeList. If timecodeList reaches its end, it rolls back to

its beginning, but plus one day, so that the next call is available tomorrow.

Parameters void

Return void

4.3.1.3.1.2.8.2.3 Stop

Method name void Stop()

Description Stop timer.

Parameters void

Return void

4.3.1.3.1.2.9 TransceiverConnectManager class

4.3.1.3.1.2.9.1 Attributes


1 audioDevice object audio port

2 MessageReceiveHandler ITransceiverConnectManager handler for processing

when receiving data

4.3.1.3.1.2.9.2 Methods

4.3.1.3.1.2.9.2.1 Connect

Method name void Connect()

Description It looks for audio input/output ports and opens stream to these devices.

Parameters void

Return void

4.3.1.3.1.2.9.2.2 Send

Method name void Send(byte[] data)

Description It checks connections to audio output device and send data to audio stream to

transceiver

Parameters data: byte[] pointer to data to be sent


Return void

4.3.1.3.1.2.9.2.3 Close

Method name void Close()

Description It cancels audio streams between audio ports and close connections to these

ports

Parameters void

Return void

4.3.1.3.1.2.10 ServerConnectManager class

4.3.1.3.1.2.10.1 Attributes


1 serverIP string server IP address

2 serverPort int server listening port

3 eventHandler IServerConnectManager handler for errors,

connection status

(disconnected, connected)

4.3.1.3.1.2.10.2 Methods

4.3.1.3.1.2.10.2.1 Connect

Method name void Connect(string serverIP, int serverPort)

Description It opens connection to Database Server

Parameters

serverIP: string server IP address

serverPort: int server listening port

Return void

4.3.1.3.1.2.10.2.2 CommitPositionMessage

Method name void CommitPositionMessage(VesselPosition positionRecord)

Description It checks for connection to Database Server, then inserts a new position

message of a vessel into Maritime database

Parameters positionRecord: VesselPosition record of a vessel’s position

Return void


4.3.1.3.1.2.10.2.3 CommitSOSMessage

Method name void CommitSOSMessage(SOSMessage message)

Description It checks for connection to Database Server, then inserts a new SOSMessage

of a vessel into Maritime database

Parameters message: SOSMessage message generated and sent from

vessel when vessel needs help

Return void



Description It gets the broadcast messages which were created after fromDateTime


Return list of BroadcastMessage, null if there is no available messages

4.3.1.3.1.2.11 IServerConnectManager interface

4.3.1.3.1.2.11.1 Attributes


4.3.1.3.1.2.11.2 Methods

4.3.1.3.1.2.11.2.1 HandleErrorMessage

Method name void HandleErrorMessage(string errorDetail)

Description It handles error message when errors is generated from server connection and

remoting

Parameters errorDetail: string error description

Return void

4.3.1.3.1.2.11.2.2 ServerDisconnected

Method name void ServerDisconnected()

Description Handler in case of that the connection changes from connected into

disconnected

Parameters void

Return void

4.3.1.3.1.2.11.2.3 ServerConnected

Method name ServerConnected


Description Handler in case of that the connection changes from disconnected into

connected

Parameters void

Return void

4.3.1.3.1.2.12 IMainFormEventHandler interface

4.3.1.3.1.2.12.1 Attributes

The interface has no attributes.

4.3.1.3.1.2.12.2 Methods

4.3.1.3.1.2.12.2.1 GetLatestBroadcastMessage

Method name Broadcastmessage GetLastestBroadcastMessage()

Description Get the latest broadcast message from Database Server

Parameters void

Return Broadcastmessage

4.3.1.3.1.2.12.2.2 ShowMessageHistory

Method name void ShowMessageHistory()

Description Show the MessageHistoryForm

Parameters void

Return void

4.3.1.3.1.2.13 ITransceiverConnectManager interface class

4.3.1.3.1.2.13.1 Attributes

4.3.1.3.1.2.13.2 Methods

4.3.1.3.1.2.13.2.1 MessageReceived

Method name void MessageReceived(byte[] data)

Description Handler for processing data when transceiver receives data through audio

input port

Parameters data: byte[] data in bytes to be processed

Return void

4.3.1.3.1.2.13.2.2 HandleErrorMessage

Method name void HandleErrorMessage(string errorDetail)


Description Handler in case of error is generated while connecting to audio input/output

ports and reading/sending data

Parameters errorDetail: string error content

Return void


4.3.1.3.2.1 Start program

Diagram 4-24: Coastal Station – Start program Sequence Diagram


4.3.1.3.2.2 Broadcast messages

4.3.1.3.2.2.1 Automatically broadcasting

Diagram 4-25: Coastal Station – Automatically broadcast message sequence diagram

4.3.1.3.2.2.2 Manually broadcasting

Diagram 4-26: Coastal Station – Manually broadcast message sequence diagram


4.3.1.3.2.2.3 Broadcast messages

Diagram 4-27: Coastal Station – Broadcast message sequence diagram

4.3.1.3.2.3 Receive messages (from vessels)

Diagram 4-28: Coastal Station – Receive message (from vessel) sequence diagram


4.3.1.3.2.4 Handle Storm messages (received from database server)

Diagram 4-29: Coastal Station – Handle storm message sequence diagram

4.3.1.3.2.5 Update messages (from database server)

4.3.1.3.2.5.1 Automatically updating

Diagram 4-30: Coastal Station – Automatically update message sequence diagram


4.3.1.3.2.5.2 Manually updating

Diagram 4-31: Coastal Station – Manually update message sequence diagram

4.3.1.3.2.6 Configure application parameters

Diagram 4-32: Coastal Station – Configure application parameters sequence diagram


4.3.1.3.2.7 Show message history

Diagram 4-33: Coastal Station – Show message history sequence diagram


4.3.2 On-sea Terminal

4.3.2.1 Class Diagram

4.3.2.1.1 Diagram

Diagram 4-34: On-sea Terminal – Class Diagram

4.3.2.1.2 Class description

4.3.2.1.2.1 MainProgram class

4.3.2.1.2.1.1 Attributes


1 Draw_State int The current drawing state of

the program(map/text

information)



2 messageQueue ArrayList<String> Store new messages received

3 stormMessageQueue Queue<StormMesage> Store last 5 new storm

messages

4 weatherInfoMessageQ

ueue

Queue<WeatherInfoMessage> Store last 5 new weather text

message

5 updatingThread Thread A thread which run

continuously, update data of

the program.

6 messageDisplayer MessageDisplayer Use java graphics API to draw

messages content

4.3.2.1.2.1.2 Methods

4.3.2.1.2.1.2.1 paintComponent

Method name void paintComponent()

Description When the screen of the program reload, this method will be call to paint all the

screen, background, messages content

Parameters void

Return void

4.3.2.1.2.1.2.2 bindMessageData

Method name void bindMessageData()

Description Check and process new message received, push it to message queue of the

program

Parameters void

Return void

4.3.2.1.2.1.2.3 drawMap

Method name void drawMap()

Description Switch the program draw state to draw map and storm messages

Parameters void

Return void


4.3.2.1.2.1.2.4 drawWeatherInfo

Method name void drawWeatherInfo()

Description Switch the program draw state to draw weather information text message

Parameters void

Return void

4.3.2.1.2.2 MessageDisplayer class



1 mapBackground Image The map of the Vietnam sea area

2 weatherInfoBackground Image The background to draw text message

3 mapWidth int The width of the background to draw

4 mapHeight int The height of the background to draw

4.3.2.1.2.2.2 Methods

4.3.2.1.2.2.2.1 getScreenX

Method name int getScreenX(float longitude)

Description Convert from geographical longitude to screen dimension

Parameters longitude:float Real longitude

Return The converted x-dimension

4.3.2.1.2.2.2.2 getScreenY

Method name int getScreenX(float latitude)

Description Convert from geographical latitude to screen dimension

Parameters latitude:float Real latitude

Return The converted y-dimension

4.3.2.1.2.2.2.3 drawMapBackground

Method name void drawMapBackground(int screenWidth, int screenHeight, Graphic

graphics)

Description Draw Vietnam sea map

Parameters screenWidth: int Width of the map


scrreenHeight:int Height of the map

Graphic:Graphics The JPanel Graphics which is use to

draw

Return void

4.3.2.1.2.2.2.4 drawWeatherInfoBackground

Method name void drawWeatherInfoBackground(int screenWidth, int screenHeight, Graphic

graphics)

Description Draw background image to draw text message content

Parameters

screenWidth: int Width of the background

scrreenHeight:int Height of the background

Graphic:Graphics The JPanel Graphics which is used

to draw

Return void

4.3.2.1.2.2.2.5 drawStorm

Method name void drawStorm(StormMessage message, Graphics graphic)

Description Visualize storm data to screen

Parameters

message:StormMessage The StormMessage to be drawed


to draw

Return void

4.3.2.1.2.2.2.6 drawWeatherInfo

Method name void drawWeatherInfo(WeatherInfoMessage message, Graphics graphic)

Description Draw text message data to screen

Parameters

message:WeatherInfoMessage The WeatherInfoMessage to be

drawed


to draw

Return void

4.3.2.1.2.2.2.7 drawObject

Method name void drawObject(Image object, int x, int y, Graphics graphic)


Description Draw a object to screen

Parameters

Object:Image Object image to be drawed

x:int x dimension to be drawed

y:int y dimension to be drawed


to draw

Return void

4.3.2.1.2.3 Updating thread class


Name Type Description

mainProgram MainProgram The mainprogram, which this thread will

update data while running

4.3.2.1.2.3.2 Methods

4.3.2.1.2.3.2.1 run

Method name void run()

Description While running, the thread will update data continuously

Parameter void

Return void

4.3.2.1.2.4 Vessel class



frames Image The Image array, which is used to draw

vessel icon as animation

currentFrame Image The current Image frame of animation

current Float Current longitude of the vessel

currentY Float Current latitude of the vessel

4.3.2.1.2.4.2 Methods

4.3.2.1.2.4.2.1 update

Method name void update(float lat, float lon, long timer)


Description Update the vessel location and frame of animation

Parameter

lat:float New latitude to be updated

lon:float New longitude to be updated

timer:long Current time, use to update animation

frame

Return void

4.3.2.1.2.5 IComPortListener interface


This interface has no attribute

4.3.2.1.2.5.2 Methods

4.3.2.1.2.5.2.1 comPortCallback

Method name void comPortCallback()

Description The callback interface of mainprogram, which is called when new message

received

Parameter data:string New message data

Return void

4.3.2.1.2.6 TranceiverConnection interface


This interface has no attribute

4.3.2.1.2.6.2 Methods

4.3.2.1.2.6.2.1 connect

Method name void connect()

Description Connect to the com port, then listen data continuously

Parameter void

Return void

4.3.2.1.2.6.2.2 modulateToSound

Method name void modulateToSound(String data)

Description Send string data as amateur radio analog signal

Parameter Data: String Data to be sent


Return void

4.3.2.1.2.6.2.3 comPortCallback

Method name void comPortCallback()

Description Listen to comport and send push new received data to main program

Parameter Data: String

Return void

4.3.2.1.2.7 MaritimeMessage class



content String Raw data of the message

4.3.2.1.2.7.2 Methods

4.3.2.1.2.7.2.1 getMessageType

Method name int getMessageType(String message)

Description Return the type of the message (storm message/ weatherinfo message)

Parameter message: String

Return 0 if StormMessage, 1 if WeatherInfoMessage

4.3.2.1.2.7.2.2 messageRegistered

Method name boolean messageRegistered(String message)

Description Check if the message has already been received and processed

Parameter message:String Raw data of the message

Return true if message has already been received, otherwise false

4.3.2.1.2.8 StormEye class



time String Time forecasted of the storm eye

level int Level of the storm



windPower int The power/velocity of the storm wind

latitude float Latitude of the storm eye

Longitude float Longitude of the storm eye

Influence1 float The strongest influence area

Influence2 float The next strong influence area

Influence3 float The weakest influence area

4.3.2.1.2.8.2 Methods

This class has no method

4.3.2.1.2.9 StormMessage class



stormEyes StormEye[] The 4 forecasted storm eyes

4.3.2.1.2.9.2 Methods

4.3.2.1.2.9.2.1 processData

Method name void processData(String message)

Description Process data to get information about 4 forecasted storm eyes


Return void

4.3.2.1.2.10 WeatherInfo class



weatherInfo weatherInfo The content of the weather information text

message

4.3.2.1.2.10.2 Methods

4.3.2.1.2.10.2.1 processData

Method name void processData(String message)

Description Process data to get content of the message



Return void

4.3.2.1.2.11 SOSMessage class


This class has only attribute inherited from super class MaritimeMessage

4.3.2.1.2.11.2 Methods

4.3.2.1.2.11.2.1 packageData

Method name void packageData(float lat, float lon, float bearing, float speed)

Description Create a SOSMessage to send to the coastal station

Parameter

lat: float Latitude of the vessel

lon: float Longitude of the vessel

bearing: float Bearing of the vessel

speed: float Speed of the vesssel

Return void

4.3.2.1.2.12 PositionMessage class


This class has only attribute inherited from super class MaritimeMessage

4.3.2.1.2.12.2 Methods

4.3.2.1.2.12.2.1 packageData

Method name void packageData(float lat, float lon, float bearing, float speed)

Description Create a PositionMessage to send to the coastal station

Parameter

lat: float Latitude of the vessel

lon: float Longitude of the vessel

bearing: float Bearing of the vessel

speed: float Speed of the vesssel

Return void


4.3.2.1.2.13 InvalidMessageException



message string The exception description

4.3.2.1.2.13.2 Methods

4.3.2.1.2.13.2.1 getMessage

Method name String getMessage()

Description Return the description of the exception

Parameter void

Return The description of the exception

4.3.2.1.2.14 DataCorrection class


This class has no attribute

4.3.2.1.2.14.2 Methods

4.3.2.1.2.14.2.1 isCorrect

Method name boolean isCorrect(String message)

Description Check if a message data has been changed by noise or not

Parameter message:String Content of the message

Return True if data is correct, false if it has been changed

4.3.2.1.2.14.2.2 correctData

Method name correctData(String[] messages)

Description Get true message data from several error-detected messages

Parameter message: String[] Error-detected messages array

Return void


4.3.2.2 Sequence Diagram

4.3.2.2.1 Start program

Diagram 4-35: On-sea Terminal – Start Program sequence diagram

4.3.2.2.2 Process received data

Diagram 4-36: On-sea Terminal – Received Data Process sequence diagram


4.3.2.2.3 Draw storm

Diagram 4-37: On-sea Terminal – Draw Storm sequence diagram

4.3.2.2.4 Draw text message

Diagram 4-38: On-sea Terminal – Draw Text Message sequence diagram


4.3.2.2.5 Send position message

Diagram 4-39: On-sea Terminal – Send Position Message sequence diagram

4.3.2.2.6 Send SOS message

Diagram 4-40: On-sea Terminal – Send SOS Message sequence diagram


4.4 Database Design

4.4.1 Database Diagram

Diagram 4-41: Database Diagram

4.4.2 Table design description

4.4.2.1 Owner

This table contains static (not frequently changed) information of vessel owners.

No Field name Field type Null Key Description

1 OwnerID int No Yes Primary key

Auto increment

2 OwnerName nvarchar(50) Yes Owner’s name

3 IDNumber Varchar(20) No

Registered id number of each

Vietnamese, provided by

government.


4.4.2.2 Vessel

This table contains static information of vessels.


1 VesselID int No Yes Primary key

Auto increment

2 VesselNumber varchar(50) No Registered id number of each vessel,

provided by government.

3 OwnerID int Yes Foreign key

Vessel owner ID

4.4.2.3 Vessel History

This table contains dynamic information of vessel with time log.


1 VesselHistoryID int No Yes Primary key

Auto increment

2 VesselID int No Foreign key

Vessel ID

3 CreatedDateTime datetime2(7) No The time when position messages

are created (from on-sea terminal)

4 Longitude float No Longitude of vessel (got from GPS)

when position message is generated

5 Latitude float No Latitude of vessel (got from GPS)

when position message is generated

6 Speed smallint Yes Speed of vessel at the time position

message is generated

7 TrueHeading smallint Yes

Angle from north-intending vertex

to velocity vertex of vessel at the

time position is generated

4.4.2.4 Vessel Latest Information

This table contains information of the newest positions of vessels. The structure of this table is

almost the same with Vessel History table.


1 VesselID int No Yes Primary key

2 CreatedDateTime datetime2(7) No

The time when position

messages are created (from on-

sea terminal)

3 Longitude float No

Longitude of vessel (got from

GPS) when position message is

generated

4 Latitude float No

Latitude of vessel (got from

GPS) when position message is

generated

5 Speed smallint Yes Speed of vessel at the time

position message is generated

6 TrueHeading smallint Yes Angle from north-intending

vertex to velocity vertex of


vessel at the time position is

generated

4.4.2.5 Message Type

This table contains information of broadcast message type. The kinds of message types are listed in

Broadcast Message Structure.


1 TypeID int No Yes Primary key

Auto increment

2 TypeName nvarchar(50) No Name of message type

4.4.2.6 Broadcast Message

This table contains all broadcast message created and committed to database server by Viewer

system.


1 MessageID int No Yes Primary key

Auto increment

2 TypeID int Yes Foreign key

Message type ID

3 CreatedDateTime datetime2(7) Yes The time when broadcast message

is created (at Viewer application)

4 Description Nvarchar(500) Yes

Content of message, in defined

structures

Reference to Broadcast Message

Structure to see kinds of message

structure

4.4.2.7 SOS Message

This table contains information of SOS messages from vessels.

4.4.3 Broadcast Message Structure The message structure depends on the message type.

4.4.3.1 Storm Message

The fields will be separated by ‘;’ character in the message (for example “a;b;c”)

MessageID MessageType StormName

Integer Integer String

+Time1 StormLevel1 WindPower1 Latitude1 Longitude1 Radius1.1 Radius1.2 Radius1.3

“dd/mm-hh” Integer Integer Real number Real number Real number Real number Real number







No Data Description


No Data Description

1 MessageID The id of the message broadcasted

2 MessageType Type of the message: Storm, SOS,

Position, Text-weather message

3 Storm name Name of the storm

4 Time1-4 Time of the four predicted storm eyes

5 StormLevel1-4 Level of the four predicted storm eyes

6 WindPower1-4 Power/velocity of the four predicted storm

eyes

7 Latitude1-4 Latitude of the four predicted storm eyes

8 Longitude1-4 Longitude of the four predicted storm

eyes

9 Radius1.1-4.1 The strongest influence area radius of the

four predicted storm eyes

10 Radius1.2-4.2 The next strong influence area radius of

the four predicted storm eyes

11 Radius1.3-4.3 The weakest influence area radius of the

four predicted storm eyes

4.4.3.2 Weather Message

The fields will be separated by ‘;’ character in the message ( for example “a;b;c”)

MessageID MessageType Content

Integer Integer String

No Data Description




3 Content The weather information broadcasted by

the coastal stations

4.4.3.3 Position Message


MessageID MessageType Latitude Longitude Heading Speed


Integer Integer Real number Real number Real number Real number

No Data Description




3 Latitude Latitude of the vessel

4 Longitude Longitude of the vessel

5 Heading Heading of the vessel

6 Speed Speed of the vessel

4.4.3.4 SOS Message


MessageID MessageType Latitude Longitude Heading Speed

Integer Integer Real number Real number Real number Real number

No Data Description




3 Latitude Latitude of the vessel

4 Longitude Longitude of the vessel

5 Heading Heading of the vessel

6 Speed Speed of the vessel

4.5 Algorithm

4.5.1 Error Detection & Correction Algorithm

4.5.1.1 Introduction

Broadcasting message via HF band has big challenge of noise and low speed, so we have to face up

with two problems: loss bits and wrong bits. We can use check sum to detect loss bits and

convolutional encoding with Viterbi decoding algorithm to correct wrong bits to the original ones.

In a packet the size of raw data bits is approximately 50 per cents and we can extend Viterbi

Decoding to new version that it can combine many wrong packets to one correct packet. At the

terminal sides the more packet with the same content the more concise percent the final packet we


have. Using this extended version we can detect and correct many bits, we have tested on

simulation: base on about 10 wrong packets still find correct one and rarely did we fail on testing.

Figure 4-1: Encoding Decoding Model

No Item Description

1 Convolutional Encoding Algorithm for error correction (encoding)

2 Viterbi Decoding Algorithm for error correction (decoding)

3 Protocol Encoding data link layer protocol, using checksum

for bit loss detection

4.5.1.2 Protocol Encoding

AX.25 is a data link layer protocol derived from the X.25 protocol suite and designed for

use by amateur radio operators. It is used extensively on amateur packet radio networks.

Flag Address Control PID Info FCS Flag

01111110 N * 8 bits 8 bits 8 bits N * 8 bits 16 bits 01111110

Table 4-5: The original frame of AX.25 Protocol

Since we see that many fields on this frame are redundant for our system, and MIV needs to fill

raw data (Info field) into some fields like address or PID to maximize the capacity of original

information in a packet. We simplify above frame to:

Flag 0 Packet ID Info FCS Flag 1 Flag 2

01111101 16 bits N * 8 bits 16 bits 01111110 01111111

Table 4-6: The customized Protocol for MIV system

Base on the name we can understand that Flag fields are the one that mark the beginning and

ending of the packet. Info field contains raw data; FCS field is the sum of packet ID and the length

of info in bytes.

4.5.1.3 Convolutional Encoding Algorithm

You can think of the encoder as a simple state machine. There are four possible states which are 00,

01, 10 and 11. Initially, the encoder is in the all-zeroes state, which is 00. Each time when we

receive an input bit, we change the current state to the next state and output a couple of bits based

on two tables below:

Current State Input = 0 Input = 1

http://en.wikipedia.org/wiki/Data_link_layer

http://en.wikipedia.org/wiki/Protocol_(computing)

http://en.wikipedia.org/wiki/X.25

http://en.wikipedia.org/wiki/Amateur_radio

http://en.wikipedia.org/wiki/Packet_radio

http://en.wikipedia.org/wiki/Computer_network


00 00 10

01 00 10

10 01 11

11 01 11

Table 4-7: Next state table

Current State Input = 0 Input = 1

00 00 11

01 11 00

10 10 01

11 01 10

Table 4-8: Output symbols table

For example, if we have raw data bit string like 01011100101002, after finishing this decoding

algorithm, we get the output bit string 00 11 10 00 01 10 01 11 11 10 00 10 112.

However, we want the final state to be the same as the initial state (00) so we have to add four input

bits 0 to assure that expectation. The truth is that two additional input bit 0 are good enough for that

criteria; but the length of input bit is divided by 8 and we want the length of output bits has the

same property so four input bits 0 is suitable number.

This is the flow chart for this decoding algorithm

Diagram 4-42: Encoding algorithm flow chart


4.5.1.4 Viterbi Decoding Algorithm

Perhaps the single most important concept to understand the Viterbi algorithm is the trellis

diagram. The figure below shows the trellis diagram for our example for a 13-bit message:

Diagram 4-43: Trellis diagram for Viterbi decoding algorithm

The four possible states of the encoder are depicted as four rows of horizontal dots. There

is one column of four dots for the initial state of the encoder and one for each time instant

during the message. For a 13-bit message with four additional bits, there are 17 time

instants in addition to t = 0, which represents the initial condition of the encoder. The solid

lines connecting dots in the diagram represent state transitions when the input bit is a one.

The dotted lines represent state transitions when the input bit is a zero.

Notice the correspondence between the encoder output symbols and the output

table discussed above:

Diagram 4-44: Next state diagram

Remember that dotted lines represent cases where the encoder input is a zero, and solid

lines represent cases where the encoder input is a one.

Suppose we receive the above encoded message with a couple of bit errors:

Diagram 4-45: Trellis diagram with two wrong bits

http://home.netcom.com/~chip.f/viterbi/algrthms.html#outputtable

http://home.netcom.com/~chip.f/viterbi/algrthms.html#outputtable


Each time we receive a pair of channel symbols, we're going to compute a metric to

measure the "distance" between what we received and all of the possible channel symbol

pairs we could have received. The distance is computed by simply counting how many bits

are different between the received channel symbol pair and the possible channel symbol

pairs. The results can only be zero, one, or two.

We define F(i, j) is the minimum accumulated error at the dot of row i column j (i for time

dimension and j for state dimension). So the formulation for F is:

Diagram 4-46: Function F at time t = 5

However, because of many wrong packets with the same original content, the probability

that we have more than one optimal path is very small and nearly impossible. All above

describes the Viterbi decoding algorithm for just one wrong packet, it can correct about 2 –

4 bits depends on some cases. But when expend accumulated error metric to sum of many

bits from many packet at the same time we can detect and correct many bits, we have

tested on many random wrong data packet bits and the result hasn’t got an wrong answer.

This is the flow chart for the Viterbi decoding algorithm


Diagram 4-47: Viterbi decoding algorithm flow chart

4.5.2 Software Modem – Sound Modem

4.5.2.1 Introduction

A Softmodem, or software modem, is a modem with minimal hardware capacities,

designed to use a host computer's resources (mostly CPUpower and RAM but sometimes

even audio hardware) to perform most of the tasks performed by dedicated hardware in a

traditional modem.

In MIV project, the software modem will

utilize computer sound card for modulating

and demodulating

4.5.2.2 Modulation

Modulation is the process of encoding digital

data into analog signal.

Func modulate

Input byte[]

Output short[]

Output from modulate function will be used

as raw data for sound card. Sound card will

play the sound represented by that raw data.

http://en.wikipedia.org/wiki/Modem

http://en.wikipedia.org/wiki/Central_Processing_Unit

http://en.wikipedia.org/wiki/Random_Access_Memory

http://en.wikipedia.org/wiki/Sound_card


4.5.2.3 Demodulation

Demodulation is modulation’s reverse process. This process will decode the analog signal

(generated from modulation) to digital data.

Func demodulate

Input short[]

Output byte[]

Output from demodulate function will be used by other application for projecting or analyzing.

5 Software Testing

5.1 Requirements for Test

5.1.1 Feature to be tested

5.1.1.1 Viewer system

5.1.1.1.1 Manage message

Feature name Manage message

Description Allows CO to create a new storm message, weather message, control

command and other message and save in the server database

5.1.1.1.2 View all vessels’ positions on map

Feature name View all vessels’ positions on map

Description Allows CO to view all vessels’ positions on [Map view] screen

5.1.1.1.3 View vessel’s voyage

Feature name View vessel’s voyage

Description Allows CO to observe a vessel’s voyage on a time interval

5.1.1.1.4 View SOS notification

Feature name View SOS notification

Description Allows CO to view vessels’ SOS symbols on map when had SOS notification

5.1.1.1.5 View vessel’s information

Feature name View vessel’s information

Description Allows CO to view the information of a registered vessel, including unique ID,

current position, direction, etc

5.1.1.1.6 View vessel’s information

Feature name View vessel’s information


Description Allows CO to view the information of a registered vessel, including unique ID,

current position, direction, etc

5.1.1.1.7 Performance test

Feature name Performance test

Description Map load and display time, each click event time

5.1.1.2 CS system

5.1.1.2.1 View messages history

Feature name View messages history

Description Allows Operator to view history of messages which are broadcasted and

received by this CS: broadcasted message, and received message

5.1.1.2.2 View broadcast message

Feature name View broadcast message

Description Allows Operator to view or be alerted whenever the coastal station broadcasts

a message to vessels

5.1.1.2.3 View receive message

Feature name View receive message

Description Allows Operator to view or be alerted whenever the coastal station received

SOS messages from vessels

5.1.1.2.4 Broadcast a message to all vessel

Feature name Broadcast a message to all vessel

Description Allows Operator to send messages to all vessels

5.1.1.2.5 Update message

Feature name Update message

Description Allows CS system to auto update/ or be updated by Operator

5.1.1.2.6 CS setting

Feature name CS setting

Description Allows Operator to set up CS system as: connection, message history

recording time, broadcast time, message updating time




Description Send and receive message time

5.1.1.3 On-sea Terminal

5.1.1.3.1 View map

Feature name View map

Description Allows fisher to view the maritime map at his position. The map contains

Asian maritime map, name of the famous places. The map will be full-screen

5.1.1.3.2 View storm notification

Feature name View storm notification

Description

Allows fisher to view the storm notification broadcasted by CS. The

notification will be displayed in image. In contains the eyes of the storm, the

strongly influenced area and the lightly influenced area

5.1.1.3.3 View weather information

Feature name View weather information

Description

Allows fisher to view the weather information broadcasted by CS. The

information contains temperature, moisture ... and will be displayed in text

form. The frame of weather information will be located at right-bottom of the

map

5.1.1.3.4 View vessel position

Feature name View vessel position

Description Allows fisher to view the position of his vessel. The position will be displayed

inside the map, with a vessel icon. The position will be updated continuously

5.1.1.3.5 View messages history

Feature name View message history

Description Allows fisher to view 5 latest messages broadcasted from CS

5.1.1.3.6 Send SOS Notification

Feature name Send SOS Notification

Description

Allows fisher to send SOS notification in bad situation. He can push a button

inside the On-sea terminal device, and the notification will be sent to the

rescue team




Description Send and receive message time

5.1.2 Feature not to be tested Message broadcast distance limit

Conflict when vessel sends SOS from Vessel, and receives storm message from coastal station

in the long distance

Message transferring speed with different distance

5.2 Test strategy

5.2.1 Test types

5.2.1.1 Function Testing

Function testing of the target-of-test should focus on any requirements for test that can be

traced directly to use cases or business functions and business rules. The goals of these

tests are to verify proper data acceptance, processing, and retrieval, and the appropriate

implementation of the business rules. This type of testing is based upon black box

technique that is verifying the application and its internal processes by interacting with the

application via the Graphical User Interface (GUI) and analyzing the output or results.

5.2.1.2 User Interface Testing

User Interface (UI) testing verifies a user’s interaction with the software. The goal of UI

testing is to ensure that the User Interface provides the user with the appropriate access and

navigation through the functions of the target-of-test. In addition, UI testing ensures that

the objects within the UI function as expected and conform to fishers, operators or CO.

5.2.1.3 Performance testing

Performance profiling is a performance test in which broadcast time, SOS transferring

time, and other time-sensitive requirements are measured and evaluated. The goal of

Performance Profiling is to verify performance requirements have been achieved.

Performance profiling is implemented and executed to profile and tune a target-of-test's

performance behaviors as a function of conditions such as distance or hardware

configurations.


5.2.2 Test Environment

5.2.2.1 Test Viewer configuration

Hardware Intel® Core™ 2 Duo CPU T6600 @ 2.20GHz

Software Windows 7

SQL server 2008 Express

5.2.2.2 Test CS configuration


Software Windows 7

.NET 4.0

5.2.2.3 Test vessel configuration


Software Windows 7

Jre 7

5.2.3 Risk list

Project is a complex system base on new idea Lack of experience about system

testing

Deployment, test environment: device, testing condition(distance),etc

Data of vessels is private, get weather information data provide source

Performance test: Change GUI, map, and displaying image

5.3 Deliverables

No Deliverables Delivered Date Delivered by Delivered to

1 Test Plan 08 – 02 – 2012 LinhDH MIV team

2 System Test case 09 – 02 – 2012 LinhDH MIV team

3 Defect Update daily LinhDH MIV team

4 Test report 03 – 04 – 2012 LinhDH MIV team


5.4 Checklist

5.4.1 Checklist of Validation

Question Yes No N/A

1. Does a failure of validation on every field cause a sensible user error

message?

x

2. Is the user required to fix entries which have failed validation tests? x

3. Have any fields got multiple validation rules and if so are all rules being

applied?

x

4. If the user enters an invalid value and clicks on the OK button (i.e. does not

TAB off the field) is the invalid entry identified and highlighted correctly with

an error message? x

5. Is validation consistently applied at screen level unless specifically required

at field level? x

6. For all numeric fields check whether negative numbers can and should be

able to be entered. x

7. For all numeric fields check the minimum and maximum values and also

some mid-range values allowable? x

8. For all character/alphanumeric fields check the field to ensure that there is a

character limit specified and that this limit is exactly correct for the specified

database size? x

9. Do all mandatory fields require user input? x

10. If any of the database columns don't allow null values then the

corresponding screen fields must be mandatory. (If any field which initially was

mandatory has become optional then check whether null values are allowed in

this field.) x

5.4.2 Submission checklist

Question Yes N/A

TABLES AND FIGURES

Does every table column, including the stub column, have a heading? x

Are all tables referred to in text? x

Are the elements in the figures large enough to remain legible after the

figure has been reduced to the width of a journal column or page? x


Is lettering in a figure no smaller than 8 points and no larger than 14

points? x

Are the figures being submitted in a file format acceptable to the

publisher? x

Has the figure been prepared at a resolution sufficient to produce a high-

quality image? x

Are all figures numbered consecutively with Arabic numerals? x

Are all figures and tables mentioned in the text and numbered in the order

in which they are mentioned? x

REFERENCES

Are references cited both in text and in the reference list? x

Do the text citations and reference list entries agree both in spelling and

in date? x

Are journal titles in the reference list spelled out fully? x

Are the references (both in the parenthetical text citations and in the

reference list) ordered alphabetically by the authors’ surnames? x

Are inclusive page numbers for all articles or chapters in books provided

in the reference list? x

Are references to studies included in your meta-analysis preceded by an

asterisk? x

FORMAT

Have you checked the journal’s website for instructions to authors

regarding specific formatting requirements for submission? x

Is the entire manuscript—including quotations, references, author note,

content footnotes, and figure captions—double-spaced? Is the manuscript

neatly prepared? x

Are the margins at least 1 in. (2.54 cm)? x

Are the title pages, abstracts, references, appendices, content footnotes,

tables, and figures on separate pages (with only one table or figure per

page)? Are the figure captions on the same page as the figures? Are

manuscript elements ordered in sequence, with the text pages between the

abstract and the references? x

Are all pages numbered in sequence, starting with the title page? x

PARAGRAPHS AND HEADINGS


Is each paragraph longer than a single sentence but not longer than one

manuscript page? x

Do the levels of headings accurately reflect the organization of the paper? x

Do all headings of the same level appear in the same format? x


5.5 Test cases

5.5.1 Onsea Terminal

ID Test Case Description Test Case Procedure Expected Output Inter-test case

Dependence Result Test date

View Map

[OT-1] Check [Map view] screen is displayed on

device successfully

Precondition:

- Open application on on-sea terminal device

Look at [MIV] application

screen.

Default screen is [Map view]

screen

pass 9/4/2012

[OT-2] Check Asian maritime map is displayed on

[Map view] screen successfully

Precondition:

- [Map view] screen is displaying on device

Look at [Map view] screen Asian maritime map is displayed

full screen on [Map view] screen

successfully

pass 9/4/2012

[OT-3] Check name of famous place is displayed on

Asia maritime map successfully

Precondition:


Look at Asian maritime

map

Name of famous place is displayed

on Asian maritime map as: Hà

Nội, TP. Hồ Chí Minh…

pass 9/4/2012

[OT-4] Check control buttons is displayed on [Map

view] screenPrecondition:- [Map view] screen

is displaying on device

Look at [Map view] screen Control buttons are displayed on

[Map view] screen and include:-

Previous message view button is

displayed as back icon- Weather

Information View button is

displayed as weather icon- Storm

Notification view button is

displayed as storm icon- Next

message view button is displayed

as forward icon(Control button

refers to Figure1- On-sea Terminal

sheet)

pass 9/4/2012


[OT-5] Check SOS button is displayed on [Map view]

screen successfully

Precondition:

- [Map view] screen is displaying

Look at [Map view] screen SOS button is displayed at the left-

top of [Map view] screen

(SOS button icon refers to

Figure1- On-sea Terminal screen

sheet)

pass 9/4/2012

View weather information

[OT-6] Check weather information screen is

displayed on device successfully

Precondition:

- [Map view] screen is displaying on desktop

of on-sea terminal device

1. Click on weather icon

2. Look at weather

information screen

1. [Map view] screen is replaced

by weather information screen

2. Weather Information screen

includes:

- Title

- DateTime

- Control buttons

- Content of weather broadcast

message

…

(Weather Information screen

refers to Figure 2- On-sea

Terminal sheet)

pass 9/4/2012

[OT-7] Check weather information view icon is

highlighted on weather information

screenPrecondition:- Weather information

screen is displaying on device

Look at weather

information view icon

Weather information view icon is

highlighted

pass 9/4/2012

[OT-8] Check weather information is displayed on

[Map view] screen

Precondition:

- Weather information screen is displaying on

device

Look at weather

information screen

- Title is [Bản tin dự báo thời tiết]

- [dd/mm/yyyy], time[hh:mm]

- Weather information is displayed

includes date temperature,

moisture, ...

pass 13/04/2012

[OT-9] Check control buttons is displayed on [Map

view] screen

Precondition:

Look at Weather

information screen

Control buttons are displayed on

[Map view] screen and include:

- Previous message view button is

Pass 9/4/2012



device

displayed as back icon

- Weather Information View

button is displayed as weather icon

- Storm Notification view button is

displayed as storm icon

- Next message view button is

displayed as forward icon

(Control button refers to Figure1-

On-sea Terminal sheet)

View vessel position

[OT-10] Check Vessel's symbol is displayed on [Map

view] screen successfully

Precondition:


1. Look at [Map view]

screen

2. Look at Vessel's position

1. Vessel is displayed on [Map

View] screen as an red point

symbol

2. Position of vessel is displayed

as [longitude-latitude] text, next to

vessel

Pass 13/04/2012

[OT-11] Check auto change vessel icon's position on

[Map view] screen successfullyPrecondition:-

[Map view] screen is displaying

Look at the vessel icon on

map after vessel is moved

- Vessel's icon moves to the

current place of vessel

immediately

Pass 13/04/2012

[OT-12] Check auto change latitude and longitude of

vessel after vessel moved on [Map view]

screen successfully

Precondition:


Look at vessel's latitude and

longitude on [Map view]

screen

- Latitude and longitude are

changed by vessel's current

latitude and longitude

Pass 13/04/2012

[OT-13] Check Vessel's position is displayed on

[Storm Notification] screen successfully

Precondition:

- [Storm Notification] screen is displaying on

desktop of on-sea terminal device

1. Look at [Storm

Notification] screen

2. Look at Vessel's position

1. Vessel is displayed on [Storm

Notification] screen as a red point

symbols

2. Position text of vessel is

displayed as [longitude-latitude]

text, next to vessel icon

Pass 9/4/2012


[OT-14] Check auto update vessel's position

successfully

Precondition:


desktop of on-sea terminal device

Look at the vessel icon on

map after vessel is moved

- Vessel's icon moves to the

current place of vessel

immediately

Pass 13/04/2012

[OT-15] Check auto change latitude and longitude of

vessel after vessel moved on [Storm


successfullyPrecondition:- [Storm

Notification] screen is displaying

Look at vessel's latitude and

longitude on [Storm


- Latitude and longitude are

changed by vessel's current

latitude and longitude

Pass 13/04/2012

View message history

[OT-16] Check display previous message successfully

Precondition:


device

1. Once click on back icon

2. Verify displayed weather

information

1. Display pre-message of current

message successfully

2. Weather information is

displayed with full information

and correct time

Pass 16/4/2012


Precondition:


device

1. Double clicks on back

icon


information

1. Display pre-message of pre-

message successfully



and correct time

Pass 16/4/2012


Precondition:


device

1. 3 clicks on back icon


information


message of previous message

successfully



and correct time

Pass 16/4/2012

[OT-19] Check display last weather message in

message history successfully

Precondition:


2. verify displayed weather

1. Display last weather message in

history


Pass 16/4/2012



device

information displayed with full information

and correct time

[OT-20] Check display current weather message

successfullyPrecondition:- Last weather

message in history is displaying

1. 4 clicks on next icon2.

verify displayed weather

information

1. Displayed weather message is

newest received weather

message2. Weather information is


and correct time

Pass 16/4/2012


successfully

Precondition:

- Fourth weather message in history is

displaying

1. 3 clicks on next icon


information


newest received weather message



and correct time

Pass 16/4/2012


successfully

Precondition:

- Third weather message in history is

displaying

1. Double clicks on next

icon


information





and correct time

Pass 16/4/2012


successfully

Precondition:

- Second weather message in history is

displaying

1. Once click on next icon


information





and correct time

Pass 16/4/2012

[OT-24] Check display previous storm message

successfully

Precondition:


device


2. Verify displayed storm

notification image

1. Display pre-storm message of

successfully

2. Storm notification screen is


and correct time

Pass 16/4/2012


successfullyPrecondition:- [Storm

Notification] screen is displaying on device


icon2. Verify displayed

storm notification image


message successfully2. Storm

notification screen is displayed

with full information and correct

Pass 16/4/2012


time


successfully

Precondition:


device



notification image


message of previous message

successfully



and correct time

Pass 16/4/2012

[OT-27] Check display fourth storm message in


Precondition:


device



notification image

1. Display fourth storm message in

history



and correct time

Pass 16/4/2012

[OT-28] Check display current [Storm Notification]

screen successfully

Precondition:

- Last storm notification image in history is

displaying


2. Verify displayed [Storm


1. Display current [Storm

Notification] screen successfully

2. Current [Storm Notification]

screen is displayed fully and

correctly

Pass 16/4/2012


screen successfully

Precondition:

- Fourth storm notification image in history is

displaying








correctly

Pass 16/4/2012


screen successfullyPrecondition:- Third storm

notification image in history is displaying

1. 2 clicks on next icon2.

Verify displayed [Storm



Notification] screen successfully2.

Current [Storm Notification]


correctly

Pass 16/4/2012


screen successfully

Precondition:

- Second storm notification image in history is








Pass 16/4/2012


displaying correctly

[OT-32] Check display first storm message in message

history successfully

Precondition:




notification image

1. Display first storm image in

storm message history

successfully

2. Storm message image is


and correct time

Pass 16/4/2012

[OT-33] Check display second storm message in


Precondition:



icon


notification image

1. Display second storm image in


successfully



and correct time

Pass 16/4/2012

[OT-34] Check display third storm message in


Precondition:




notification image

1. Display third storm image in


successfully



and correct time

Pass 16/4/2012

[OT-35] Check display fourth storm message in

message history successfullyPrecondition:-

[Map view] screen is displaying on device

1. 4 clicks on back icon2.

Verify displayed storm

notification image

1. Display fourth storm image in


successfully2. Storm message

image is displayed with full

information and correct time

Pass 16/4/2012

[OT-36] Check display fifth storm message in message


Precondition:




notification image

1. Display fifth storm image in


successfully



and correct time

Pass 16/4/2012


[OT-37] Check display [Map view] screen successfully

Precondition:

- Fifth storm notification image in history is

displaying


2. Verify displayed [Map

view] screen

1. Display [Map view] screen

successfully

2. [Map view] is displayed

correctly

Pass 16/4/2012


Precondition:

- Fourth storm notification image in history is

displaying



view] screen


successfully


correctly

Pass 16/4/2012


Precondition:

- Third storm notification image in history is

displaying



view] screen


successfully


correctly

Pass 16/4/2012

[OT-40] Check display [Map view] screen

successfullyPrecondition:- Second storm

notification image in history is displaying

1. Double clicks on next

icon2. Verify displayed

[Map view] screen


successfully2. [Map view] is

displayed correctly

Pass 16/4/2012


Precondition:

- First storm notification image in history is

displaying

1. One click on next icon


view] screen


successfully


correctly

Pass 16/4/2012

View Storm Notification

[OT-44] Check storm notification box is displayed

successfully

Precondition:

- CS sends storm message to vessel

1. Look at the [Map view]

screen

2. Click on [OK] button

1. Display storm notification box,

text is [Bạn có 1 tin báo bão mới],

[Ok] button

2. Storm notification box is closed

Pass 9/4/2012

[OT-45] Check storm notification screen is display on

device successfully

Precondition:

- CS broadcasts storm message to vessel

Look at the [Map view]

screen

- [Storm Notification] screen is

auto displayed on device

- [Storm Notification] screen

includes storm information and

broadcasting storm

sms from CS

pass 9/4/2012


- [Map view] screen is displaying on device storm image

[OT-46] Check storm information is displayed on

[Storm Notification View]

screenPrecondition:- [Storm Notification

View] screen is displaying on device

1. Look at [Map view]

screen2. Verify Storm

Information field

1. Storm Information field is

displayed at the right-bottom of

[Map view] screen2. Storm

Information field includes:-Storm

name is black,bold-DateTime is

black, normalas [Tin phát lúc:

hh:mm dd/mm/yyyy]-Information

titles of storm is displayed as

[Ngày-giờ Vĩ độ Kinh độ Cấp bão

Tốc độ gió] is black and

bold(Storm information displaying

refers to "Figure 1- On-sea

Terminal Screen" sheet)

pass 9/4/2012

[OT-47] Check storm information is visualized on

[Storm Notification View] screen successfully

Precondition:

- [Storm Notification View] screen is

displaying on device

1. Look at Storm Image 1. Storm Information is visualized

on map as storm image and

includes:

- The main storm orbit is

prebroadcasteded by red line

- The eyes of the storm

- The strongly influenced area and

the lightly influenced area

...

(Storm Visualization refers to

"Figure 2- On-sea Terminal

Screen" sheet)

pass 9/4/2012

[OT-48] Check comments of storm image is displayed

successfully

Precondition:

- [Storm Notification view] screen is


1. Look at comments box 1. Comments is displayed at the

right of storm information field

and include:

- Explaination of storm image

(Comments box refers to Fingure

2- On-sea Terminal Screen)

pass 9/4/2012


[OT-49] Check storm information hide button is

displayed on storm information field

successfullyPrecondition:- Storm information

field is displaying on [Storm Notification

view] screen

Look at Storm information

field

Hide button is displayed as a red

triangular at the right-bottom of

storm information field

pass 9/4/2012

[OT-50] Check hide storm information field

successfully

Precondition:

- [Storm Notification view] screen is


Click on coner of storm

information field

Storm information field is hidden pass 9/4/2012

Broadcast SOS Message

[OT-51] Check confirm message box is displayed

successfully

Precondition:


1. Click SOS button on

[Map view] screen

1. Display confirm message box

- Text is [Bạn có muốn gửi tin cầu

cứu]

- [Chắc chắn] button

- [Không] button

Pass 9/4/2012

[OT-52] Check vessel broadcasts SOS message to

coastal station successfully

Precondition:


1. Click on SOS button on

[Map view] screen

2. Click on [Chắc chắn]

button



2. Display notification message

box [Đang gửi tín hiệu SOS],

[OK] button

3. Notification message box is

closed

Pass 9/4/2012

[OT-53] Check when click [không] button in confirm

message box

Precondition:



[Map view] screen

2. Click on [không] button


2. Close confirm message box

Pass 9/4/2012

[OT-54] Check confirm message box is displayed

successfullyPrecondition:- [Weather

information] screen is displaying

1. Click SOS button on

[Map view] screen

1. Display confirm message box -

Text is [Bạn có muốn gửi tin cầu

cứu] - [Chắc chắn] button-

Pass 9/4/2012


[Không] button

[OT-55] Check vessel broadcasts SOS message to

coastal station successfully

Precondition:

- [Weather information] screen is displaying


[Map view] screen

2. Click on [Chắc chắn]

button



2. Display notification message

box [Đang gửi tín hiệu SOS],

[OK] button

3. Notification message box is

closed

Pass 9/4/2012

[OT-56] Check when click [không] button in confirm

message box

Precondition:

- [Weather information] screen is displaying


[Map view] screen

2. Click on [không] button


2. Close confirm message box

Pass 9/4/2012

5.5.2 Coastal Station system



GUI-View

Message

[CSS-1] Check GUI of [Message

View] screen

Precondition:

- [Message View] screen is

displaying on Coastal Station

Screen

Look at this screen [Message View] screen is displayed in

read mode and includes:

- Title

-…

(GUI refers to "Figure 2 - Coastal

Station Screen" sheet)

Pass 5/4/2012

[CSS-2] Check title window is

displayed successfully

Precondition:



Screen

Look at this screen Title of window is [Trạm thu phát ven

biển], text is black.

Pass 5/4/2012


[CSS-4] Check title message is

displayed on [Message View]

screen

Precondition:



Screen

Look at this screen - Title message is displayed under of

title screen

- Text is [Nội dung bản tin], black and

bold

Pass 5/4/2012

[CSS-5] Check notification of SOS

message is displayed on

[Message View] screen

Precondition:

[Message View] screen is


Screen

Look at this screen - Notification of SOS message is

displayed on same line with title

message, right of line

- Text is [[n] bản tin SOS từ tàu]

- Text is bold, and under line

Pass 5/4/2012

[CSS-6] Check message content

textbox is displayed on


Precondition:



Screen

Look at this screen Message content textbox is displayed

under message title and include:

- Time

- Type

- Content

(Message content textbox refers to

"Figure 2 - Coastal Station Screen"

sheet)

Pass 5/4/2012

[CSS-7] Check [Cài đặt] button is

displayed on [Message

View] screen

Precondition:



Screen

Look at this screen - Setting button is displayed at the left

bottom of screen

- Text is [Cài đặt]. Text is black

Pass 5/4/2012

[CSS-8] Check [Cập nhập bản tin]

button is displayed on


Precondition:

Look at this screen - Update button is displayed at the left of

broadcast button

- Text is [Cập nhập bản tin]. Text is

Pass 5/4/2012




Screen

black

[CSS-9] Check [Phát tin] button is

displayed on [Message

View] screen

Precondition:



Screen

Look at this screen - Broadcast button is displayed at the

right bottom of screen

- Text is [Phát bản tin]. Text is black

Pass 5/4/2012

[CSS-10] Check [Lịch sử bản tin]

button is displayed on


Precondition:



Screen

Look at this screen - Messages history view button is

displayed at above of setting button

- Text is [Lịch sử bản tin]. Text is black

Pass 5/4/2012

[CSS-11] Check GUI of setting screen

Precondition:

- Setting screen is displaying

1. Click [Cài đặt] button

2. Look at setting screen

1. Setting screen is displayed over


2. Setting screen includes:

- Title is "cài đặt"

- …

(Setting screen refers to Fingure 3-

Coastal Station Sheet)

Pass 5/4/2012

View Message

[Setting]

[CSS-12] Check [Cài đặt] screen is

displayed on coastal station

Precondition:

- [Message view] screen is

displaying on coastal station

Click [Cài đặt] button Display [Cài đặt] screen Pass 5/4/2012


[CSS-13] Check title of [Cài đặt] screen

is displayed successfully

Precondition:

- [Cài đặt] screen is


Look at [Cài đặt] screen Title of screen is [Cài đặt], text is black. Pass 5/4/2012

[CSS-14] Check connection setting

field is displayed successfully

Precondition:



Look at [Cài đặt] screen - Connection setting is displayed at left

top of [Cài đặt] screen and includes:

+ Title field is [Cài đặt kết nối]

+ [Địa chỉ server] label and textbox

+ [Cổng] label and textbox

Pass 5/4/2012

[CSS-15] Check connection setting of

view message ( Full fill

information)

Precondition:



1. Fill in server address textbox

2. Fill in portal textbox

3. Click enter

1. Filled text is displayed in server

address textbox

2. Filled text is displayed in portal

textbox

3. Server address and portal is saved

successfully

Pass 5/4/2012


view message(Portal is blank)

Precondition:



1. Fill in server address textbox

2. Click enter


address textbox

2. Can't save and display a notification

Pass 5/4/2012


view message(Server address

is blank)

Precondition:



1. Fill in portal textbox

2. Click enter


address textbox

2. Can't save and display a notification

Pass 5/4/2012


view message(all is blank)

Precondition:


Click enter Can't save and display a notification Pass 5/4/2012



[CSS-19] Check message recording

setting field is displayed on

[Cài đặt] screen

Precondition:



Look at [Cài đặt] screen - [Lưu trữ bản tin] field is displayed at

right-top of [Cài đặt] screen and

includes:

+ radio button and value labels, values

are [trong ngày, trong 1 tuần, trong 2

tuần, trong 1 tháng]

Pass 5/4/2012

[CSS-20] Check set message recording

of view message successfully

Precondition:



1. Choose [trong ngày] value of

radio button values

2. Click enter

3. Check message history

1. Display checked radio button

2. Chose value is saved successfully

3. All messages in message history's

time is the set datetime

View message history Pass 5/4/2012



Precondition:



1. Choose [trong 1 tuần] value of

radio button values

2. Click enter






Pass 5/4/2012



Precondition:



1. Choose [trong 2 tuần] value of

radio button values

2. Click enter






Pass 5/4/2012



Precondition:



1. Choose [trong 1 tháng] value of

radio button values

2. Click enter






Pass 5/4/2012

[CSS-24] Check [Thời gian phát] field

is displayed on [Cài đặt]

screen successfully

Precondition:

Look at [Cài đặt] screen - [Thời gian phát] field is display at left-

bottom of [Cài đặt] screen and includes:

+ Time item box

+ [Thêm] button

Pass 5/4/2012




+ [Xóa] button

[CSS-25] Check message broadcast

time setting of view

message(add a broadcast

time)

Precondition:



1. Click [Thêm] button

2. Fill time as hh:mm:ss

3. Click enter

1. Display time input line in time item

box

2. Display input time

3. New time is saved

[Phát tin] function Pass 5/4/2012



message(add a broadcast

time)

Precondition:




2. Fill time with free style

3. Click enter


box


3. Can't save new time and display

notification

Pass 5/4/2012



message(delete a broadcast

time)

Precondition:



1. Choose a time in box

2. Click [Xóa] button

1. Chose time is highlight

2. Chose time is deleted

[Phát tin] function Pass 5/4/2012

[CSS-28] Check delete all time item in

message broadcast time

setting item box

Precondition:



Delete all message broadcast time

setting item

Can't delete all time item in time item

box and display [Bạn không thể xóa.

Phải có ít nhất một giờ trong danh sách

này.] notification box

Pass 5/4/2012

[CSS-29] Check [Thời gian cập nhập

bản tin] field is displayed on

[Cài đặt] screen successfully

Look at [Cài đặt] screen - [Thời gian cập nhập bản tin] field is

display at right-bottom of [Cài đặt]

screen and includes:

Pass 5/4/2012


Precondition:



+ Time item box

+ [Thêm] button

+ [Xóa] button

[CSS-30] Check message auto update


message(add an auto update

time)

Precondition:



2. Fill time as hh:mm:ss

3. Click enter


box


3. Save new time successfully

Pass 5/4/2012



message(add an auto update

time)

Precondition:



2. Fill time with free style

3. Click enter


box


3. Can't save new time and display

notification

[Cập nhập bản tin]

function

Pass 5/4/2012



message(delete an auto

update time)

Precondition:


1. Choose a time in box

2. Click [Xóa] button

1. Chose time is highlight

2. Chose time is deleted

[Cập nhập bản tin]

function

Pass 5/4/2012

[CSS-33] Check delete all time item in

time item box

Precondition:



Delete all time item Can't delete all time item in time item

box and display [Bạn không thể xóa.

Phải có ít nhất một giờ trong danh sách

này.] notification box

Pass 5/4/2012

View message [Update]


successfully(there is a new

message)

Look at message textbox when

time is the set time

Messsage content in textbox is replaced

by new one at this time

Pass 12/4/2012


Precondition:

- Set update time

- [View message] screen is

displaying


successfully(there are more

than 1 new message)

Precondition:

- Set update time


displaying


time is the set time


by newest one at this time

Pass 12/4/2012


successfully(there is not new

message)

Precondition:

- Set update time


displaying


time is the setting time

Information in textbox doesn't changed Pass 12/4/2012

[CSS-37] Check message update when

[Cập nhập bản tin] button is

clicked successfully (There is

a new message)

Precondition:


displaying

Click on [Cập nhập bản tin]

button


by new one at this time

Pass 12/4/2012



clicked successfully (There

are more than 1 new

message)

Precondition:



button


by newest one at this time

Pass 13/4/2012


displaying



clicked successfully(There

isn't new message)

Precondition:


displaying


button

Information in textbox doesn't change Pass 13/4/2012

View Message History

[CSS-40] Check [Message history]

window is displayed

successfully

Precondition:

- [Map view] window is

displaying in Coastal Station

1. Click on [Lịch sử bản tin]

button

[Message history] screen is displayed in

read mode and includes:

- Title label

- Number of recorded message

- Message history table

(GUI refers to "Figure 1 - Coastal

Station Screen" sheet)

Pass 10/4/2012

[CSS-41] Check title of [Lịch sử bản

tin] window is displayed

successfully

Precondition:

- [Lịch sử bản tin] is

displaying

Look at [Lịch sử bản tin] window Window title is [Lịch sử bản tin], text is

black

Pass 10/4/2012

[CSS-43] Check [số các bản tin được

lưu trữ] is displayed

successfully

Precondition:

- [Message history] screen is


Screen

1. Look at [số các bản tin được

lưu trữ] field

2. Click on number at [số các bản

tin được lưu trữ] label

1. [Số các bản tin được lưu trữ] field is

displayed at the left-top of [Message

history] window

- Text of amount of message is [Số các

bản tin được lưu trữ:], text is black

- Number which is displayed [Số các bản

tin được lưu trữ:] field is same with

amount of message list in table

Pass 10/4/2012


2. Can't edit the number

[CSS-44] Check message history table

Precondition:



Screen

Look at message history table - Message history table is displayed in

read mode and includes columns:

+ STT (số thứ tự)

+ Loại

+ Ngày tạo

+ Nội dung

- Text in table is black

Table refers to "Figure 1 - Coastal

Station Screen sheet"

Pass 10/4/2012

[CSS45] Check view message history

in one day is displayed

successfully

Precondition:

- Set message record time of

view message is [trong ngày]

- [Message history] is

displaying

Look at message history table all of received messages in this day is

displayed in message history table

message recording

function

Pass 10/4/2012

[CSS-46] Check view message history

of one week is displayed

successfully

Precondition:


view message is [trong 1

tuần]


displaying

Click on [Lịch sử bản tin] button all of received messages in one week is


Pass 10/4/2012


of two weeks is displayed

successfully

Precondition:



Click on [Lịch sử bản tin] button all of received messages in two weeks is


Pass 10/4/2012


tuần]


displaying


of one month is displayed

successfully

Precondition:



tháng]


displaying

Look at message history screen all of receive messages in one month is


Pass 10/4/2012

[CSS-49] Check information of a

message is displayed in

message table successfully

Precondition:


displaying

1. Look at message history table 1. Message history table is displayed on

read mode and include:

- [Số thứ tự] is auto increase

- [Loại tin] is storm message/ weather

broadcast message

- [Ngày tạo] is message creating time, as

dd/mm/yyyy hh:mm:ss AM(PM)

- [Nội dung] is shortcut of message

content

Pass 10/4/2012

[CSS-50] Check view a message in


Precondition:

- [Message history]screen is

displaying

1. Click on a message in message

history table

2. Verify message's information

1. Message information is displayed

under message history table

2. Title is [Nội dung tin nhắn], Message

time & information is displayed

correctly

Pass 10/4/2012

[CSS-51] Check out of view message

history is successfully

Precondition:


displaying

Click close icon on [Message

history] screen

Close [Message history] and return to

[Map view] screen

Pass 10/4/2012


Broadcast message

[CSS-52] Check coastal station

broadcasts weather message

to vessel successfully(auto)

Precondition:

- [View message] window is

displaying

Look at [View message] screen at

set time

- Current message is broadcasted to

vessel

- Display sound and notification [Đã gửi

bản tin]

Vessel receives

message

Pass 10/4/2012



to vessel successfully(click

button)

Precondition:


displaying

Click [Phát tin] button - Current message is broadcasted to

vessel


bản tin]

Vessel receives

message

Pass 10/4/2012



to vessel when click [Phát

bản tin] button at set auto

time

Precondition:


displaying


vessel twice


bản tin]

Pass 10/4/2012


broadcasts storm message to

vessel successfully(auto)

Precondition:

- [View message] window is

displaying

Look at [View message] screen at

set time

- Current message is broadcasted to

vessel


bản tin]

Pass 10/4/2012



vessel successfully(click


vessel


Pass 10/4/2012


button)

Precondition:


displaying

bản tin]



vessel when click [Phát bản

tin] button at set auto time

Precondition:


displaying


vessel twice


bản tin]

Pass 10/4/2012

[CSS-58] Check CS broadcasts SOS

message to Viewer

successfully

Precondition:

- Increase number of SOS

notification

Look at [View message] screen - Display notification [Đã gửi bản tin] Vessel receives

message

Pass 13/4/2012

Receive message

[CSS-59] Check coastal station system

receives a SOS message from

a vessel successfully

Precondition:


displaying

Look at SOS message notification

field

Number of SOS message notification

increases by one

[OT-51] Pass 13/4/2012


receives 2 SOS messages

from a vessel at the different

time

Precondition:



field


increases by two

[OT-51] Pass 13/04/2012


displaying



from two vessel at the same

time

Precondition:


displaying


field


increases by two

[OT-51] Pass 11/4/2012



from two vessel at the

different time

Precondition:


displaying


field


increases by four

[OT-51] Pass 11/4/2012

5.5.3 Viewer



GUI-Maritime

Information

Visualization

[Viewer-1] Check title of Viewer

window

Precondition:

- Viewer window is

displaying

Look at title of this window Title is [Maritime Information

Visualization], text is black

Pass 2/4/2012

[Viewer-2] Check default screen is

displayed on Viewer window

Look at Viewer widow - Default screen is [Bản đồ tổng quan]

- The visible region of map is Vietnam

Pass 2/4/2012


successfully

Precondition:

- Viewer window is

displaying

land, Vietnam sea, Philippine sea and

China sea.

- Display fullscreen

[Viewer-3] Check tabs is displayed on

viewer window successfully

Precondition:

- Viewer window is

displaying

Look at Viewer widow Default tabs on Viewer window are [Bản

đồ tổng quan] tab and [Tạo tin] tab, and

displayed on tab field

Pass 2/4/2012

[Viewer-4] Check docking bar is

displayed on Viewer window

successfully

Pprecondition:

- Viewer window is

displaying

Look at Viewer widow Docking bars are [Tổng quan] and [Tìm

kiếm], at right of window

Pass 2/4/2012

View all vessels'

position on map

[Viewer-5] Check map is displayed on

[Bản đồ tổng quan] screen

successfully

Precondition:

- [Bản đồ tổng quan] screen is

displaying

Look at [Bản đồ tổng quan] screen The background map contains Vietnam

land, Vietnam sea, Philippine sea and

China sea.

Pass 4/4/2012

[Viewer-6] Check vessel's position is

displayed on map

successfully

Precondition:


displaying

Look at [Bản đồ tổng quan] screen At current time, all registered is displayed

on background screen

Pass 4/4/2012


[Viewer-7] Check background map is

displayed in case of no vessel

Precondition:


displaying

Look at [Bản đồ tổng quan] screen Display only background map Pass 4/4/2012

[Viewer-8] Check automactically update

a vessel position onto the map

(2 minutes)

Precondition:

- A vessel symbol is

displaying onto the map

Look at the vessel symbol on the map The vessel symbol position is changed on

the map

Pass 4/4/2012

[Viewer-9] Check automactically update

two vessel positions onto the

map (2 minutes)

Precondition:

- Two vessel symbols are

displaying on the map

Look at the vessel symbols on the map The vessel symbols position is changed on

the map

Pass 11/4/2012

[Viewer-

10]

Check automactically update

10 vessel positions onto the

map (2 minutes)

Precondition:

- Ten vessels symbols are


Look at the vessel symbols on the map The vessel symbols position is changed on

the map

Untested 11/4/2012

Check view a vessel's information

[Viewer-

11]

Check view a vessel's

information successfully

Precondition:

- At least a vessel symbol is


1. Click once on a vessel symbol

2. Verify displayed information

1. Display vessel's information box

2. Information is displayed includes:

- [Biển kiểm soát] is vessel's license plate

- [Mã số] is vessel's unique ID (link to

vessel's history)

- [Chủ tàu] is vessel owner name

- [Kinh độ] is vessel current position's

Pass 8/4/2012


longitude

- [Vĩ độ] is vessel current position's

latitude

- [Tốc độ] is vessel's velocity

(nautical/hour)

- [Hướng] is vessel's direction

- [Cập nhập lúc] is vessel information

update time(dd/mm/yyyy hh:mm:ss

UTC+7)

[Viewer-

12]

Check close vessel

information box successfully

Precondition:

- Vessel information box is

displaying

Click on close at the right top of vessel

information box

Vessel information box is closed

successfully

Pass 8/4/2012

Check a vessel's voyage

[Viewer-

13]

Check vessel's voyage table is


Precondition:

- Open vessel information

pop up context

Click on link at the unique ID in vessel

information box

Open vessel history in new tab Pass 8/4/2012

[Viewer-

14]

Check title of the vessel

history tab

Precondition:

- Vessel history tab is

displaying

Look at the tab title Title is vessel license plate, text is black Pass 8/4/2012

[Viewer-

15]

Check vessel history screen is


Precondition:


displaying

Look at screen and verify data Vessel history screen is displayed on

readmod and includes:

- Title is [Lịch sử tàu + vessel license

plate]

- [Kết quả] is number of history records

- Choose time from drop-down list to

Pass 8/4/2012


view history

- [Tải dữ liệu] button and [Hiển thị trên

bản đồ] button

- Page drop-down list

- Vessel history table includes Record ID

column, Record time column, Longitude

column, latitude column, velocity column,

direction column

[Viewer-

16]

Check view vessel history in

1 hour successfully(table)

Precondition:


displaying

1. Choose vessel history display time (1 hour)

2. Click on [Tải dữ liệu button]

3. Verify displayed vessel history

1. Chose time is displayed on drop-down

list

2. Display all record had chose time, and

display number displayed record on [Kết

quả] field

3. Time and information of records is

correctly

Pass 8/4/2012

[Viewer-

17]

Check view vessel's voyage

in one month

successfully(image)

Precondition:

- Vessel history in one hour is

displaying

1. Click on [Hiển thị trên bản đồ] button

2. Look at new displayed tab

1. Display new tab is [Lịch sử tàu +

license plate] tab

2. The vessel's voyage in one hour is

displayed and includes:

- Number symbols is number of vessel

history record

- Start and end symbol is bigger

- All symbols is connected by a red line

(Vessel's voyage refers to Figure 3/

Viewer Screen)

Pass 8/4/2012

[Viewer-

18]

Check all vessel history is

displayed successfully(table)

Precondition:


displaying

1. Display all vessel history record

2. Click on [Tải dữ liệu button]

3. Verify displayed vessel history

1. Chose time is displayed on drop-down

list

2. Display all vessel history record, and

display number displayed record on [Kết

quả] field

3. Time and information of records is

correctly

Pass 8/4/2012


[Viewer-

19]

Check close vessel

information box successfully

Precondition:

- Vessel information box is

displaying

Click on close at the right top corner of this

screen

Vessel history screen is closed

successfully

Pass 8/4/2012

[Viewer-

20]

Check all vessel's voyage is

displayed successfully(image)

Precondition:

- All vessel history is

displaying

1. Click on [Hiển thị trên bản đồ] button

2. Look at new displayed tab

1. Display new tab is [Lịch sử tàu [license

plate]] tab

2. The vessel's voyage is displayed and

includes:

- Number symbols is number of vessel

history record

- Start and end symbol is bigger

- All symbols is connected by a red line

(Vessel's voyage refers to Figure 3/

Viewer Screen)

Pass 8/4/2012

[Viewer-

21]

Check vessel's voyage screen

is closed successfully

Precondition:

- Vessel's voyage screen is

displaying

Click on close at the right top corner of this

screen

Vessel's voyage is closed successfully Pass 8/4/2012

Create a message

[Viewer-

22]

Check open [Tạo tin] tab

successfully

Precondition:

- Viewer window is

displaying

Click on [Tạo tin] tab Default screen of this tab is storm

broadcast message creating screen and

includes:

- [Loại bản tin] label

- Message types drop-down list

- Message content creating box

Pass 8/4/2012

[Viewer-

23]

Check storm broadcasting

message creating screen is


Precondition:

1. Click on message types drop down list

2. Choose [Bản tin báo bão]

3. Verify [Bản tin báo bão] input fields

1. Display message types list includes:

[Bản tin báo bão] [Bản tin thời tiết] [Câu

lệnh điều khiển] and [Bản tin khác]

2. Display fields to input content of storm

Pass 8/4/2012


- [Tạo tin] tab is displaying broadcast message

3. Fields refers to Figure5- Viewer screen

sheet

[Viewer-

24]

Check input storm broadcast

message content successfully

Precondition:

- Storm broadcast message

creating screen/default screen

of [Tạo tin] tab is displaying

1. Input storm name in storm name textbox

2. [Vị trí tâm bão 1] fields:

- Choose datetime on datetime field

(dd/mm/yyyy hh:mm:ss)

- Input storm level, Longitude, Latitude,

influence area 1, influence area 2, influence area

3 (inputted data must be interger)






3(inputted data must be interger)













6. Click on [Đồng ý] button

1. Inputted name is displayed in textbox

2. Inputted text is displayed on textbox




Pass 8/4/2012

[Viewer-

25]

Check save storm message to

database succefully

Precondition:

- Previous testcase is finished


2. Choose [Đồng ý] button in confirm message

box


2. Display notification box(successful/

unsuccessfull)

Pass 8/4/2012


[Viewer-

26]

Check notification box is

displayed successfully when

save invalid inputted data in

[Cấp bão] field

Precondition:










3 (inputted data must be interger EXCEPT data

in [Cấp bão] textbox)




















7. Click [Yes] button






6. Display message confirm box includes

message is [Bạn có đồng ý tải bản tin này

lên cơ sở dữ liệu không?], [Yes] button,

[No] button, [Cancel] button

7. Display notification box [Vĩ độ của vị

trí tâm bão 1 phải là số thực]

Pass 8/4/2012

[Viewer-

27]




[Tốc độ gió] field

Precondition:










in [Tốc độ gió] textbox)









Pass 8/4/2012


of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields:





















7. Display notification box [Tốc độ gió

của vị trí tâm bão 1 phải là số thực]

[Viewer-

28]




[Vĩ độ] field

Precondition:











in [Vĩ độ] textbox)




















Pass 8/4/2012














[Viewer-

29]




[Kinh độ] field

Precondition:











in [Kinh độ] textbox)


























7. Display notification box [Kinh độ gió


Pass 8/4/2012






[Viewer-

30]




[Phạm vi ảnh hưởng 1] field

Precondition:











in [Phạm vi ảnh hưởng 1] textbox)





























7. Display notification box [Phạm vi ảnh

hưởng 1 của vị trí tâm bão 1 phải là số

thực]

Pass 8/4/2012

[Viewer-

31]













Pass 8/4/2012


Precondition:



































thực]

[Viewer-

32]





Precondition:



























Pass 8/4/2012


















thực]

[Viewer-

33]




[Cấp bão] field

Precondition:

































7. Display notification box [Cấp bão của

vị trí tâm bão 2 phải là số thực]

Pass 8/4/2012










[Viewer-

34]





Precondition:










































Pass 8/4/2012


7. Click on [Yes] button

[Viewer-

35]




[Vĩ độ] field

Precondition:











































Pass 8/4/2012

[Viewer-

36]




[Kinh độ] field

Precondition:














Pass 8/4/2012





























7. Display notification box [Kinh độ của


[Viewer-

37]





Precondition:





























thực]

Pass 8/4/2012
















[Viewer-

38]





Precondition:

















in [Phạm vi ảnh hưởng 2])




















thực]

Pass 8/4/2012








[Viewer-

39]





Precondition:











































thực]

Pass 8/4/2012


[Viewer-

40]




[Cấp bão] field

Precondition:











































Pass 8/4/2012

[Viewer-

41]





Precondition:



















Pass 8/4/2012


of [Tạo tin] tab is displaying - Choose datetime on datetime field























[Viewer-

42]




[Vĩ độ] field

Precondition:































Pass 8/4/2012














[Viewer-

43]




[Kinh độ] field

Precondition:







































Pass 8/4/2012






[Viewer-

44]





Precondition:











































thực]

Pass 8/4/2012

[Viewer-

45]










Pass 8/4/2012



Precondition:





































thực]

[Viewer-

46]





Precondition:


























Pass 8/4/2012



















thực]

[Viewer-

47]




[Cấp bão] field

Precondition:


































Pass 8/4/2012











[Viewer-

48]





Precondition:










































Pass 8/4/2012



[Viewer-

49]




[Vĩ độ] field

Precondition:











































Pass 8/4/2012

[Viewer-

50]




[Kinh độ] field

Precondition:














Pass 8/4/2012































[Viewer-

51]





Precondition:





























thực]

Pass 8/4/2012
















[Viewer-

52]





Precondition:





































thực]

Pass 8/4/2012








[Viewer-

53]





Precondition:











































thực]

Pass 8/4/2012


[Viewer-

54]

Check notify when input

invalid value in time field of

[Vị trí tâm bão 2]

Precondition:

- All field of storm message

creating screen is inputted

with valid data

1. Input data in datetime field of [Vị trí tâm bão

1]


2], this datetime data is earlier than data in the

datetime field of [Vị trí tâm bão 1]


3]


4]

5. Click [Đồng ý] button


1. Inputted data is displayed in textbox




5. Display confirm message box [Bạn có

đồng ý tải bản tin này lên cơ sở dữ liệu

không?], [Yes] button, [No] button,

[Cancel] button

6. Display notification box [Thời gian của

vị trí tâm bão 1 phải sớm hơn thời gian

của vị trí tâm bão 2]

Pass 8/4/2012

[Viewer-

55]




Precondition:



with valid data


1]


2]





4]










[Cancel] button




Pass 8/4/2012

[Viewer-

56]




Precondition:



with valid data


1]


2]


3]













[Cancel] button




Pass 8/4/2012


[Viewer-

57]

Check weather message

creating screen is displayed

successfully

Precondition:

- Default screen of [Tạo tin]

tab is displaying

Choose [Bản tin thời tiết] value in message type

drop down list

Weather message creating screen is

displayed on read mode and includes:

- Chose value is displayed on message

type field

- Field title is [Bản tin văn bản]

- Text of message name label is [Bản tin

thời tiết], text is red and bold

- Text of message code label is [Mã số:2]

- [Nội dung] label

- Weather message creating textbox

Pass 8/4/2012

[Viewer-

58]

Check create a weather

message successfully(connect

to server successfully)

Precondition:

- Weather message creating

screen is displaying

1. Input data into textbox







không?], [Yes] button, [No] button

3. Display notification box [Bản tin thời

tiết đã được lưu trữ trong cơ sở dữ liệu]

and [OK] button

4. Notification message box is closed

Pass 8/4/2012

[Viewer-

59]

Check notifiy box is


create a weather

message(connect to server

unsuccessfully)

Precondition:

- Weather message creating







2. Display confirm message box, text is

[Bạn có đồng ý tải bản tin này lên cơ sở

dữ liệu không?], [Yes] button and [No]

button

3. Display notification box, text is [Có sự

cố khi kết nối tới máy chủ. Việc tải bản

tin lên cơ sở dữ liệu hiện thời không thực

hiện được] and [OK] button


Pass 8/4/2012

[Viewer-

60]

Check notify box is displayed

successfully when create a

weather message without data

Precondition:

- Weather messsage creating



1. Display notification message box , text

is [Vui lòng nhập tin nhắn gửi đi], [OK]

button


successfully

Pass 8/4/2012



[Viewer-

61]

Check control command

creating screen is displayed

successfully

Precondition:


tab is displaying

Choose [Câu lệnh điều chỉnh] value in message

type drop down list

Control command creating screen is



type field


- Text of message name label is [Câu lệnh

điều chỉnh], text is red and bold



- Control command creating textbox

Pass 8/4/2012

[Viewer-

62]

Check create a control

command

successfully(connect to server

successfully)

Precondition:

- Control command creating









không?], [Yes] button, [No] button

3. Display notification box [Câu lệnh điều

khiển đã được lưu trữ trong cơ sở dữ liệu]

4. Close notification box

Pass 8/4/2012

[Viewer-

63]



create a control command

message(connect to server

unsuccessfully)

Precondition:










button





Pass 8/4/2012

[Viewer-

64]



control command message

without data

Precondition:





1. Display confirm message box , text is



button

2. Display notification box, text is [Câu

lệnh điều khiển dã được lưu trong cơ sở

Pass 8/4/2012


screen is displaying dữ liệu], and [OK] button


[Viewer-

65]

Check other message creating

screen is displayed

successfully

Precondition:


tab is displaying

Choose [Bản tin khác] value in message type

drop down list

Other message creating screen is



type field


- Text of message name label is [Bản tin

khác], text is red and bold



- Other message creating textbox

Pass 14/4/2012

[Viewer-

66]

Check create a message of

other mesage type

successfully(connect to server

successfully)

Precondition:

- Other message creating








không?], [Yes] button, [No] button.

3. Display notification box [Bản tin khác

đã được lưu trong cơ sở dữ liệu]

Pass 14/4/2012

[Viewer-

67]



create a message of other

message type(connect to

server unsuccessfully)

Precondition:

- Other message creting

creating screen is displaying








button.





Pass 14/4/2012

[Viewer-

68]



weather message without data

Precondition:

- Other message creating




1. Display confirm message box , text is



button

2. Display notification box, text is [Vui

Pass 14/4/2012


screen is displaying lòng nhập nội dung tin nhắn gửi đi], and

[OK] button


View SOS notification

[Viewer-

69]

Check SOS message

notification box is displayed

successfully when receive a

SOS message

Precondition:

- [Tổng quan] screen is

displaying

Look at the [Tổng quan] screen Message notification box is displayed at

screen central

- Text is [Nhận được 1 thông tin khẩn cấp

(S.O.S) mới]

- [OK] button

[CSS-59] Pass 13/4/2012

[Viewer-

70]

Check SOS message



SOS message

Precondition:

- [Tạo tin] screen is

displaying

Look at the [Tạo tin] screen Message notification box is displayed at

screen central


(S.O.S) mới]

- [OK] button

[CSS-59] Pass 13/4/2012

[Viewer-

71]

Check SOS message



SOS message

Precondition:

- Vessel history screen is

displaying

Look at vessel history screen Message notification box is displayed at

screen central


(S.O.S) mới]

- [OK] button

[CSS-59] Pass 13/4/2012

[Viewer-

72]

Check SOS message



SOS message

Precondition:

- [Vessel's voyage screen is

Look at vessel's voyage screen Message notification box is displayed at

screen central


(S.O.S) mới]

- [OK] button

[CSS-59] Pass 13/4/2012


displaying

[Viewer-

71]

Check SOS message


successfully when receive 2

SOS messages

Precondition:


displaying

Look at the [Tổng quan] screen Message notification box is displayed at

screen central


(S.O.S) mới]

- [OK] button

[CSS-61] Pass 11/4/2012

[Viewer-

72]

Check SOS message

notification box is closed

successfully

Precondition:

- SOS message notification

box is displaying on screen

Click [OK] button SOS message notification box is closed Pass 4/4/2012

[Viewer-

73]

Check a SOS vessel symbol

is displayed on map


SOS message

Precondition:


displaying

Look at map on [Tổng quan] screen A SOS vessel symbol is displayed on map

as a red symbol, and blinked

[CSS-59] Pass 11/4/2012

[Viewer-

74]

Check 2 SOS vessel symbols

are displayed on map

successfully when receive 2

SOS message

Precondition:


displaying

Look at map on [Tổng quan] screen 2 SOS vessel symbols are displayed on

map as a red symbol, and blinked

[CSS-61] Pass 11/4/2012

5.6 Test Summary Report

5.6.1 Test Execution Summary

5.6.2 Test Results

5.6.3 Summary of Incident Reports Raised During Project

Severity Total

Defect

Open Defect

Assigned Corrected Accepted Total Open

defects

Fatal 0 0 0 0 0

Serious 3 0 3 0 0

Medium 1 0 1 0 0

Cosmetic 4 0 4 0 0

Total (Status) 0 0 0 0 0

Total (W.def) 0 0 0 0 0

Test Execution Summary

Pass Fail Untested Accepted N/A

Number of Test

cases

0 0 0 0 0 0

Onsea Terminal 54 0 0 0 0 54

Coastal Station system 62 0 0 0 0 62

Viewer 75 0 1 0 0 75

CombineV-CS-OT 10 10 0 0 0 10

External Interface 0 0 0 0 0 0

Performance 0 0 0 0 0 0

Data migration 0 0 0 0 0 0

Test coverage

Test coverage 99.5%

Test successful coverage 99.5%

Prepared for MIV

/210 Final Report, Maritime Information Visualization, Version 1.0

Prepared by 6Fingers

5.6.4 Conclusion

5.6.4.1 System Test Success Criteria

# Criteria

1

All the inputs of system testing are baselined and approved by 6Fingers(Common

requirement, ADD, SRS, Design,Software package, System test cases).

2

System testing is over and all known issues (if any) are aware by 6Fingers’ members and

documented in Test summary report.

3 All planned Test Cases have been executed (99.5% test execution coverage)

4

At least 95% executed system test cases have to be passed. (More than 95% test successful

coverage)

5 100% high priority test cases in scope are passed.

6 Only Cosmetic defects can be accepted

6 Installation Guide

6.1 Environment Requirement

Due to all modules of the project are developed on .NET and Java platform, production

environment needs to fulfill these following requirements:

Operating system: Windows 7

Framework: .NET Framework 4.0, Java 7.0

DBMS: SQL Server 2008 R2 Express

6.2 Installation Package

At the glance, the project has these following modules need to be deployed on production

environment

On-sea Terminal

Java application for terminal device (JAR file).

Coastal Station

Set up for coastal station management (EXE file).

6.3 Installation Guide for On-sea Terminal

These following steps show installation guide for MIV On-sea terminal program.

Prepared for MIV



Firstly, open the MIVSetup.exe file.

When the license screen appears, read and click “Tôi đồng ý” button if you want to setup

the program.

On next screen, click “Tiến” button to continue

Prepared for MIV



On next screen, click “Duyệt” button to select destination folder, and finally click “Cài

đặt” button to install.

After installed, open the installed folder

Finally, double click on the MIV_OnseaTerminal.jar file to run the program

6.4 Installation Guide for Database server Install “Microsoft SQL Server” then run “DBServer.exe”

Prepared for MIV



6.5 Installation Guide for Coastal Station

These following steps show installation guide for MIV Viewer program.

Firstly, open the MIVCoastalStation.exe file.

When the license screen appears, read and click “Next” button if you want to setup the program.

On next screen, click “Browse” button to select destination folder, and finally click

“Next” button to install.

Click “Next” to start installation

Prepared for MIV



Installation success, click “Close” to finish

6.6 Installation Guide for Viewer

These following steps show installation guide for MIV Viewer program.

Firstly, open the MIVViewer.exe file.

When the license screen appears, read and click “Next” button if you want to setup the program.

Prepared for MIV



On next screen, click “Browse” button to select destination folder, and finally click

“Next” button to install.

Click “Next” to start installation

Prepared for MIV



Installation success, click “Close” to finish

7 User Manual

7.1 Application Overview

7.1.1 Requirements

In order to use this application, you need to have the following:

.NET Framework 4.0

JRE 7.0

7.1.2 Available Features

The below list is available features for fishers

No. Functions Description

1

View map This use case allows fisher to view the maritime map where he’s on

2

View storm notification This use case allows fisher to view storm notifications broadcasted

by coastal stations. The notifications will be visualized and

displayed in images

3

View weather information This use case allows fisher to view other weather information like

wind power, temperature…The information will be display in text

4

View vessel position The fisher can trace his position by using the terminal. His position

will be displayed inside the map

5

View message history This use case allows fisher to trace the message that was

broadcasted in past, or old message

Prepared for MIV



6

Send SOS notification This use case allows fisher to send SOS notification in case he got a

bad situation.

Table 7-1: Available features for fishers

The below list is available features for operators


1

View message history This use case allows Operator to view history of messages which are

broadcasted and received by this coastal station

2

View broadcasted message This use case allows Operator to view or be alerted whenever the


3

View received message This use case allows Operator to view or be alerted whenever the

coastal station receives a message (except position message) from

vessel

Table 7-2: Available features for operators

The below list is available features for central operators


1

Broadcast messages This use case allows central operator to send messages to all vessels

2

View all vessels’ positions on

map

This use case allows central operator to observe vessel position on

map at a specific time

3

View a vessel’s voyage This use case allows central operator to observe a vessel’s voyage

through an interval of time

4

View a vessel’s information This use case allows central operator to view information of vessel

Table 7-3: Available features for central operators

7.1.3 Roles

To perform certain functions, the user must be assigned a role within the application.

Thus, be sure you are assigned a proper role for this application.

In MIV, the users can be classified into following User Roles as below:

No. Roles Description

1 Operator

A user who has responsibilities for observing coastal station

system and message forwarding between Viewer system and

vessels.

2 Central Operator A user who has responsibilities for vessel management,

observation and salvage.

Table 7-4– Roles for coastal station

Prepared for MIV



7.2 User Manual for Functions

7.2.1 Functions for Fishers

7.2.1.1 View map

When the program is opened, the default screen will be the map.

This map shows the Vietnam sea area map, which can help fishers easier to visualize the sea area.

In the case the fisher want to switch from Weather Information screen to Map, he can click the

“Map Button” on the top-right of the screen

7.2.1.2 View storm notification

When a new storm message arrives, a message box will be displayed to notify the fisher.

Prepared for MIV



After click “ok” button, the storm image will be displayed

If fisher doesn’t understand detail of the storm by image, he can click the button to view more

detail:

7.2.1.3 View weather information

When a new storm message arrives, a message box will be displayed to notify the fisher.

After click “ok” button, the storm image will be displayed.

Prepared for MIV



In the case the fisher want to switch from Map screen to Weather Information, he can click the

“Weather Information Button” on the top-right of the screen

7.2.1.4 View vessel position

When the fisher views the map, the vessel position will be also displayed on the map. It will be an

animating red dot icon, update continuously and the vessel coordinate will be written beside the

dot icon.

Prepared for MIV



7.2.1.5 View message history

The program will store the latest 5 storm messages and 5 weather information messages. If the

fisher want to view the previous message, he can click the button, and click the

to back to the next message

If there is no previous message, the “Previous” button will be gray-scaled:

7.2.1.6 Send SOS notification

There is always a red button at the left-top corner of the program:

If the case the fisher needs help, he can click this button to send “SOS message”.

There will be a confirm dialog:

If fisher click “Chắc chắn” button, the SOS message will be send. The button will

be changed to button. The SOS message will be send until fisher clicks this

button. If fisher click “Không” button, the message will not be send.

7.2.1.7 Notify restricted area

On map will, there is a rounded area call “Restricted area”. The fishers are prohibited to enter this

area.

If the vessel enters this area, a warning will be displayed until it leaves this area

Prepared for MIV



7.2.2 Functions for Operators

7.2.2.1 View broadcasted/received message

Main GUI

7.2.2.2 View message history

Click button , a dialog shows up that lists all current broadcast

messages.

7.2.2.3 Broadcast messages

Click button to broadcast the latest updated message.

If there is no messages to be broadcasted, an inform message pops up.

If there are messages to be broadcasted, the application will broadcast the latest updated message.

When the application finishes broadcasting a message, a message box pops up.

Prepared for MIV



7.2.2.4 Update messages from Database server

Click button to update the latest messages. When updating process finishes, the

program will inform the number of updated messages.

Click “OK”, then the latest message (if there is) will be displayed on the main window.

7.2.2.5 Configuration

Click

7.2.2.5.1 Change server address

In “Cài đặt kế nối” group box, type server IP into “Địa chỉ server” textbox, server port into

“Cổng” texbox, then press Enter key.

Prepared for MIV



The program connects to server with new address. The inform label

displays until connection process finishes. Then the inform label is replaced by

(if success) or (if error).

7.2.2.5.2 Change message storing time

Change the selection in “Lưu trữ bản tin” group box by tick into a radio button.

After you choose one, the current stored message will be updated due to the store time from

database server.

7.2.2.5.3 Change the automatically broadcast time

In “Thời gian phát” group box, you can see the list of time in a day for broadcasting messages

automatically.

To remove a time from this list, select a time and click button. Note that you cannot

remove all items, so if you remove the last item, a message box pops up.

To add a time into this list, click button. A textbox shows up for you to enter a new

time. Note that you must enter a new time in “h:m:s” format (h, m, s stands for hours, minutes,

seconds), then press Enter

Prepared for MIV



If the new time exists, nothing is inserted. Else, then the new time is inserted into the list with

descending order.

7.2.2.5.4 Change the automatically update time

Refer to Change the automatically broadcast time. Do the same thing in “Thời gian cập nhật bản

tin” group box.

7.2.3 Functions for Central Operators

7.2.3.1 Broadcast messages

Step1: Go to tab [Tạo tin]

Step 2: Choose Message type in drop down box [Loại bản tin]

Step 2a: Screen when you choose [Bản tin báo bão]

Step 2b: Screen when you choose other messages

Prepared for MIV



Step 3: Fill the content of message and click [Đồng ý]

Step4: A message box show confirm question. Click [Yes] to commit message to database

Step 5: A Message box will be shown if your message is successfully commit to database

7.2.3.2 View all vessels’ positions on map

All vessel position will be automatically display on tab [Bản đồ tổng quan]

Prepared for MIV



7.2.3.3 View a vessel’s voyage

Step 1: Click on the vessel that you want to see voyage

Step 2: Click to [Bấm vào đây để xem lịch sử đi tàu]

Step 3: Move to tab display the voyage

Step 4: Click [Hiển thị trên bản đồ] to view voyage on map

Prepared for MIV



Step 5: A tab shown vessel voyage

7.2.3.4 View a vessel’s information

Step 1: Click on the any vessel that you want to see information

8 Appendixes

8.1 Messages

This section describes the details of messages used in business rules e.g. error messages,

confirmation messages, etc.

MSG

Code

MSG

Type

Message Title Message Content Button

MSG1 Error InvalidDatetime Bạn đã nhập dữ liệu ngày tháng

không đúng

OK

MSG2 Error InvalidNumber Bạn chỉ được nhập kí tự số OK

Prepared for MIV



MSG3 Error MessageSuccess Bạn đã tạo bản tin thành công OK

MSG4 Inform MessageNotification Có x bản tin mới Xem/Bỏ

qua

miv final report

Technology

miv project

project dependsalargely

guidancethis project

project management plan

necessary information

shore fishing vessels

maritime country

software design