Your SlideShare is downloading. ×
MIV final report
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

MIV final report

470

Published on

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
470
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. MINISTRY OF EDUCATION AND TRAINING FPT UNIVERSITY Capstone Project Document Maritime Information Visualization 6Fingers Tran Hai Dang – 00606 Ta Duc Tung – 00544Group Pham Quang Hung – 00396Members Ha Thi Tham – 01188 Nguyen Hai Ha – 00740 Duong Hue Linh – 00596Supervisor Mr. Huynh Anh DungExt Supervisor Mr. Nguyen Tat TrungProject code MIV - HaNoi, 04/2012 -
  • 2. Acknowledgements part from the efforts of all team members, the success of any project dependsA 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 cannotsay thank you enough for his tremendous support and help. We feel motivated andencouraged every time we attend his meeting. Without his encouragement and guidancethis project would not have materialized.We are highly indebted to mentor Nguyen Tat Trung for his guidance and constantsupervision as well as for providing necessary information regarding the project & also forhis support in completing the project.We would like to express my gratitude towards our parents for their continuouslyencouragement which help us in completion of this project.Our thanks and appreciations also go to our colleague in developing the project and peoplewho have willingly helped us out with their abilities.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 2Prepared by 6Fingers
  • 3. Preface ietnam is a maritime country with more than 1 million square kilometers ofV 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 thesea including seasonal typhoons which claim over hundred lives and many fishing vesselslost every year, causes of poverty and suffering. Thus, applying advanced technology tosolve this problem, ensuring safety for fishermen is urgently needed.The MIV project aims to develop an additional method of communicating text messageson HF band that along with retaining existing method of communicating (voicetransmitting), using software-modem to modulate and demodulate messages. System willtransfer data from coastal station to vessels and vice-versa.The proposed system consists of the coastal station, vessels, and has the following majorcharacteristics:  Compatible and complement existing communication equipment on fishing vessels  Using advanced digital modulation technique for communication  Visualization Information at both sides (coastal station, vessels)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 3Prepared by 6Fingers
  • 4. Brief ContentsAcknowledgements ................................................................................................................................... 2Preface ..................................................................................................................................................... 3Brief Contents .......................................................................................................................................... 4Definitions and Acronyms ........................................................................................................................ 81 Introduction ..................................................................................................................................... 92 Project Management Plan .............................................................................................................. 123 Software Requirement Specification ............................................................................................... 184 Software Design ............................................................................................................................. 445 Software Testing .......................................................................................................................... 1246 Installation Guide......................................................................................................................... 1917 User Manual ................................................................................................................................ 1978 Appendixes .................................................................................................................................. 209________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 4Prepared by 6Fingers
  • 5. ContentsAcknowledgements ................................................................................................................................... 2Preface ..................................................................................................................................................... 3Brief Contents .......................................................................................................................................... 4Definitions and Acronyms ........................................................................................................................ 81 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 ................................................................................................. 122 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 ................................................................................................ 173 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 5Prepared by 6Fingers
  • 6. 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 ................................................................... 444 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 ............................................................ 1235 Software Testing .......................................................................................................................... 124 5.1 Requirements for Test .................................................................................... 124________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 6Prepared by 6Fingers
  • 7. 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 ............................................................................................. 1916 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 .......................................................................... 1957 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 ................................................................ 2068 Appendixes .................................................................................................................................. 209 8.1 Messages ...................................................................................................... 209________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 7Prepared by 6Fingers
  • 8. Definitions and AcronymsAcronym DefinitionMIV Maritime Information VisualizationPM Project ManagerPTL Project Technical LeaderTL Team LeaderQA Quality Assurance OfficerDV DeveloperURD User Requirement DocumentSRS Software Requirement SpecificationADD Architecture Design DocumentDDD Detail Design DocumentTP Test PlanTC Test CaseSC Source CodeCM Configuration ManagerUC Use caseUI User InterfaceGUI Graphical User InterfaceAT Acceptance TestIT Integration TestST System TestUT Unit TestTR Test ReportUAT User Acceptance TestCS Coastal StationCO Central Operator Table 0-1: Definitions and Acronyms________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 8Prepared by 6Fingers
  • 9. 1 Introduction1.1 Literature review1.1.1 Coastal Station SystemIn Vietnam, weather forecast information, storm alerting, meteorological information andother rescue information are transmitted to fishing vessels by Coastal Station System. Inorder to update the information, fishing vessels need to continuously listen to messagesbroadcasted from coastal stations. On the other hand, whenever there is any issueconcerning about safety, rescuing… vessels need to alert coastal stations.1These station need to be online 24 hours per day, 7 days per week on the frequency of7.903 KHz. In this case, station staff will transmit messages by talking and listen torescuing information from fishing vessels.2Advantages Disadvantages  Easy to use  Anti-interference  In many urgent cases, sailor cannot hear the message clearly, which lead to misunderstanding and damaging1.1.2 Viettel Coastal and Islands Base Transceiver Station (BTS) SystemFrom the beginning of 08 – 2009, Viettel Corporation set up a system of BTSs alongVietnam’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 mobilephone signal is very good. However, out of this range, especially from 61 nautical awayfrom BTS, signal is very weak, cannot use.3Advantages Disadvantages  Can use cell phone  Narrow range  Cannot cover full range of South – East Asia Sea1.1.3 Movimar SystemMovimar System is a very high-end system which is set up by Vietnamese Governmentand French Government with the investment of €13.9 million and implement period is 3years, 2011 – 2013. System will be deployed in 28 provinces in Vietnam. In the target ofMovimar project, about 3000 vessels will be equipped satellite communicating device.Moreover, about 150 navy vessels will be equipped with supporting device, prepared forcommunicating and processing rescuing information.4After finishing the project, fishing vessels will be able to automatically receive weatherinformation transmitted from coastal station. Along with this, coastal station can1 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>________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 9Prepared by 6Fingers
  • 10. continuously monitor fishing vessels’ position and take action immediately whenemergency come.5Advantages Disadvantages  High technology  High capital investment  Guarantees a high quality of  Number of monitored vessel is only communicating and rescuing 2850  Technology dependency (depend on France)1.2 Project IdeaAlong with retaining existing method of communicating (voice transmitting), the mainpurpose 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 Station5 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ắnthiế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>________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 10Prepared by 6Fingers
  • 11.  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 Vessel1.3 General view Visualization Viewer Visualization Text Data HF Coastal Station Tex HF tD ata Visualization Database Data Text Synchronize Visualization HF Text Data HF Visualization Text Data HF Coastal Station Database Figure 1-3: General view________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 11Prepared by 6Fingers
  • 12. 1.4 Proposal and Project’s BenefitsImplementing this system will improve communication efficiency between coastal stationand 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 ConstraintsThe system will be deployed on both Coastal Station and Fishing Vessels. MIV systemwill work only when Coastal Station is equipped with necessary hardware and an Internetline. Device equipment is also applied to fishing vessels except that no Internet line isneeded 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 idea2 Project Management Plan2.1 Project Overview2.1.1 Core Business Cases and ApproachThe 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 accident2.1.2 Project Milestones and DeliverablesNo Stage Committed Actual Deviation________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 12Prepared by 6Fingers
  • 13. 1 Project Management Plan 02 – Feb – 12 02 – Feb – 12 0 day2 SRS v1.0 07 – Feb – 12 09 – Feb – 12 2 days3 Detailed design v1.0 09 – Mar – 12 15 – Mar – 12 6 days4 Final package 20 – Mar – 12 30 – Mar – 12 10 days5 Test report v1.0 22 – Mar – 12 03 – April – 12 12 days6 User Manual v1.0 30 – Mar – 12 04 – April – 12 5 days Table 2-1: Project milestones and deliverables2.2 Boundaries of the SystemThe system under development of this Capstone Project will include:  The software installer  User manual  SRS  Design documents  Test documents  Source code2.3 Development EnvironmentBelow is the list of hardware and software requirements needed for developmentenvironment: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 device2.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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 13Prepared by 6Fingers
  • 14. 2.4 Project Organization2.4.1 Software Process ModelThe process model used for developing this project is iterative and incrementaldevelopment model.6 Figure 2-1: Iterative and incremental modelWe have only approximately 3 months for doing everything of this project and not everymember has experience for the similar systems before. Besides, the beginning the problemdefinition is not totally clear and we need to clarify it in iterative model. The iterative waylead us to reduce the misunderstand requirements and make sure project runs in the rightway. 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 somesteps in parallel. Working in parallel some steps can help us to reduce effort and projectcan be delivered on only 3 months.2.4.2 Roles and ResponsibilitiesProject Instructor  Mr. Huynh Anh Dung  Mr. Nguyen Tat TrungProject team member DangTH (PM) TungTD HungPQ ThamHT HaNH LinhDH (CM, DV) (DV) (DV) (DV) (Tester) Figure 2-2: Project Team Organization6 Wikipedia. (Jan 28, 2012). “Iterative and incremental development”. Wikipedia.org. Feb 3, 2012<http://en.wikipedia.org/wiki/Iterative_and_incremental_development>________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 14Prepared by 6Fingers
  • 15. 2.5 Project Management Plan2.5.1 Tasks2.5.1.1 Create Software Requirements SpecificationDescription: create SRSOutput: SRS documentDeliverables: deliver SRS document before Feb 7, 2012Resources needed: 6 people in 2 days for brainstorming, 2 people in 5 days for doing SRSRisks: because there is no actual user, and the requirements come from all the teammembers, misunderstandings may happen regularly2.5.1.2 Create Software Design DescriptionDescription: create design for overall systemsOutput: SDDDeliverables: deliver with SDD before Mar 9, 2012Resources needed: 6 people in 2 days for brainstorming, 2 people in 26 days for doingSDDDependencies and Constraints: depends on the completion of SRSRisks: SRS may not be detailed enough to capture the business rules, causing the detaileddesign to be inappropriate or will be changed much in the future2.5.1.3 CodingDescription: implement the system to reflect the requirementsOutput: source code of the project, unit test reportsDeliverables: executable programs and source code before Feb 23, 2012Resources needed: all developers in 30 daysDependencies and Constraints: depends on the completion of SRS, SDDRisks: 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 protocol2.5.1.4 System TestDescription: perform system test for the systemOutput: system test reportDeliverables: Software Test Documentation before Apr 2, 2012Resources needed: 2 people in 39 daysDependencies and Constraints: Coding is finishedRisks: 39 days may be too short to check whole system works well or not2.5.2 Task Sheet: Assignments and TimetableRefer to the Master Plan document.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 15Prepared by 6Fingers
  • 16. 2.6 Risk ManagementID Risk Description Probability Effect Status Action Contingency1 User Get Involvement: requirement Its quite difficult from other Tolerabl to communicate Very high Occurred sources like e and get news or involvement from internet users2 Testing: Create Unable to test in a simulation Very high Serious Occurred deployed environment environment3 Hardware Borrow FPT Purchase availability: Technology Lack of devices Research Very high Serious Occurred such as text-to- Institute speech modem, GPS device4 New Technology: Prepare Request Android, Map knowledge for support from API, Encoding- new friends or decoding Very high Serious Potential technologies someone that algorithm by materials is expert of and internet that new technology5 Resource OJT can help We have may Experience: us to get more experienced Team member In- experience in colleagues in Not lack of software Moderate significa software software relevant development nt engineering engineering to experience ask and get advice6 Project Project Ask many Management Manager experienced skill: prepares Project Moderate Serious Potential Project Manager knowledge Manager lacks of project from text book when getting management skill in library trouble Table 2-2: Risk Management________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 16Prepared by 6Fingers
  • 17. 2.7 Coding ConventionsThe following rules follow the standard rules for developing applications using .NET andC#.2.7.1 Naming ConventionsRefer to .NET Naming Guidelines.72.7.2 Coding StylesRefer to FxCop rules and Code Analysis for Managed Code Warnings.82.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 doesnt 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>________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 17Prepared by 6Fingers
  • 18. 3 Software Requirement Specification3.1 High Level Requirements3.2 Domain Model3.2.1 Diagram Viewer DatabaseServer CoastalStation OnSeaTerminal Normal Normal Normal Push to service Query from Broadcast to Message Message Message creates view view Storm Storm Storm creates Push to service Notify to Broadcast to view Message Message Message Central view Operator Operator Fisher view Position Position Position view Query from service Push to Send to Message Message Message view creates view SOS SOS SOS Notify to service Push to Send to Message Message Message Diagram 3-1: Domain Model Diagram3.2.2 Domain Object DescriptionObject DescriptionVessel The vessel has an unique ID that registered with MIV systemMessage 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 positionViewer The central system which is responsible for creating broadcasting messages and visualize information received from vesselsDatabase 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 18Prepared by 6Fingers
  • 19. Object Description to vessels and receiving messages from vesselsOn-sea Terminal The software system on vessels for visualizing information received from coastal station and sending messages back to coastal stationCentral Operator Person who uses Viewer software to broadcast message or monitor vessels on mapFisher Person who is the owner of a vessel and also the user of on-sea terminal deviceOperator Person who uses Coastal Station software to observe broadcasted & received messages at each coastal station Table 3-1: Domain Object Description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 19Prepared by 6Fingers
  • 20. 3.3 Business process flow3.3.1 Storm message broadcasting process Storm Message Broadcasting Coastal Station Central Operator Database System On-seaTerminal Fisher System Message Creating Start Create storm message Save storm Message into Message Saving Database Notify Coastal Station Message Broadcasting Encode Message Broadcast message Decode Message Receiving message Visualize information View storm Message Viewing message End Diagram 3-2: Storm message broadcasting process________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 20Prepared by 6Fingers
  • 21. 3.3.2 Normal message broadcasting process Normal Message Broadcasting Coastal Station Central Operator Database System On-seaTerminal Fisher System Message Creating Start Create message Message Saving Save Message into Database Loop: Get message from database Message Broadcasting Encode Message Broadcast message Decode Message Receiving message Display information View message Message Viewing End Diagram 3-3: Normal message broadcasting process________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 21Prepared by 6Fingers
  • 22. 3.3.3 Position message sending (from vessel) process Position Message Sending (From Vessel) Message Creating & Sending Coastal Station On-seaTerminal Database System Viewer Central Operator System Start Loop: Send position message Message Receiving Receive message Decode Message Message Saving Save Message into Database Loop: update Message Visualizing position from database Visualize information View map Message Viewing End Diagram 3-4 Position message sending (from vessel) process________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 22Prepared by 6Fingers
  • 23. 3.3.4 SOS message sending (from vessel) process SOS Message Sending (From Vessel) Coastal Station Fisher On-seaTerminal Database System Viewer Central Operator System Start Message Creating Press “SOS” Create SOS button message Encode SOS Message Sending message Send SOS message Message Receiving Receive message Decode Message Save Message into Database Message Saving Notify Viewer Message Visualizing Visualize information Message Viewing View map End Diagram 3-5 SOS message sending (from vessel) process________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 23Prepared by 6Fingers
  • 24. 3.4 Use cases and Actors3.4.1 On-sea Terminal System3.4.1.1 Diagram Diagram 3-6: On-sea Terminal UCs3.4.1.2 Description of ActorsActor Name Description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 24Prepared by 6Fingers
  • 25. Actor Name DescriptionFisher 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 description3.4.1.3 Description of Use casesUse case Name DescriptionView map This use case allows fisher to view the maritime map where he’s onView storm notification This use case allows fisher to view storm notifications broadcasted by coastal stations. The notifications will be visualized and displayed in imagesView weather information This use case allows fisher to view other weather information like wind power, temperature…The information will be display in textView vessel position The fisher can trace his position by using the terminal. His position will be displayed inside the mapView forbidden area warning This use case allows fisher to be warned when vessel is going to enter a forbidden areaSend SOS notification This use case allows fisher to send SOS notification in case he got a bad situation.Auto send position message to This use case allows position of vessel to be sent back to CoastalCoastal Station Station for tracking automaticallyReceive messages from This use case allows messages broadcasted from Coastal Station toCoastal Station be received and be informed to fisher Table 3-3: On-sea Terminal Use cases description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 25Prepared by 6Fingers
  • 26. 3.4.2 Coastal Station System3.4.2.1 Diagram Diagram 3-7 Coastal Station UCs________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 26Prepared by 6Fingers
  • 27. 3.4.2.2 Description of ActorsUsecase Name DescriptionOperator 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 description3.4.2.3 Description of Use casesUse case Name DescriptionView message history This use case allows Operator to view history of messages which are broadcasted and received by this coastal stationView broadcasted message This use case allows Operator to view or be alerted whenever the coastal station broadcasts a message to vesselsView received message This use case allows Operator to view or be alerted whenever the coastal station receives a message (except position message) from vesselBroadcast message to This use case allows Operator to send message to Transceivervessels device, then it will be broadcasted to vessels via HF bandReceive messages from This use case allows message sent from vessels to be received byvessels Transceiver device, then to be push into PC’s COM ports to process.Commit message into This use case allows message received from vessels to be inserteddatabase and stored into Maritime database in Database Server Table 3-5: Coastal Station System Use case description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 27Prepared by 6Fingers
  • 28. 3.4.3 Viewer System3.4.3.1 Diagram Diagram 3-8: Viewer System UCs3.4.3.2 Description of ActorsActor Name DescriptionCentral Operator A user who has responsibilities for vessel management, observation and salvage Table 3-6: Station System Actors description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 28Prepared by 6Fingers
  • 29. 3.4.3.3 Description of Use casesUse case Name DescriptionCreate broadcast messages This use case allows central operator to send messages to all vesselsView all vessels’ positions This use case allows central operator to observe vessel position onon map map at a specific timeView a vessel’s voyage This use case allows central operator to observe a vessel’s voyage through an interval of timeView a vessel’s information This use case allows central operator to view information of vesselAuto update vessels’ This use case allows all vessels position to be updated after aposition specified interval of time Table 3-7: Station System Use cases description3.5 Functional Requirements3.5.1 Use cases Description3.5.1.1 On-sea Terminal Use case Description3.5.1.1.1 UC1: View mapName View mapDescription 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-screenActor Fisher3.5.1.1.2 UC2: View storm notificationName View storm notificationDescription 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 areaActor Fisher3.5.1.1.3 UC3: View weather informationName View weather informationDescription This use case allows fisher to view the weather information broadcasted by coastal station. The information contains temperature, moisture ... and________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 29Prepared by 6Fingers
  • 30. will be displayed in text form. The frame of weather information will be located at right-bottom of the mapActor Fisher3.5.1.1.4 UC4: View vessel positionName View vessel positionDescription 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 continuouslyActor Fisher3.5.1.1.5 UC5: View message historyName View message historyDescription This use case allows fisher to view 5 latest messages broadcasted from coastal stationActor Fisher3.5.1.1.6 UC6: Send SOS notificationName Send SOS notificationDescription 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 FisherTrigger User press [SOS] buttonPost 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 StationName Auto send position message to Coastal StationDescription This use case allows fisher to send the current position of vessel to Coastal Station automatically. The position is generated according to GPS deviceActor FisherPre condition Computer must connect to GPS device and transceiver device________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 30Prepared by 6Fingers
  • 31. 3.5.1.1.8 UC8: Receive message from Coastal StationName 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 FisherPre condition Computer must connect to transceiver devicePost condition Inform user about message (in text form or visualized form)3.5.1.1.9 UC9: View forbidden area warningName View forbidden area warningDescription This use case allows fisher to be warned when vessel enters into a defined forbidden area. Warning mean may be by text and/or soundActor FisherPre condition Computer must connect to GPS device3.5.1.2 Coastal Station System3.5.1.2.1 UC10: View message historyName View message historyDescription 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 OperatorTriggerPre-conditionPost-condition3.5.1.2.2 UC11: View broadcasted messageName View broadcasted messageDescription This use case allows Operator to view or be alerted whenever the coastal station broadcasts a message to vessels________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 31Prepared by 6Fingers
  • 32. Actor OperatorTrigger A message has just been broadcasted to vesselsPre-condition Computer must connect to transceiver device3.5.1.2.3 UC12: View received messageName View received messageDescription This use case allows Operator to view or be alerted whenever the coastal station received a message from vessels (except for position message)Actor OperatorTrigger A message has just been received by the coastal stationPre-condition Computer must connect to transceiver devicePost-condition The message will be commit to save into database server3.5.1.2.4 UC13: Broadcast messages to vesselsName Broadcast messages to vesselsDescription This use case allows Operator to broadcast the latest message to vessels through audio portActor OperatorTrigger User click button [Phát bản tin]Pre-condition Computer must connect to transceiver devicePost-condition The message will be commit to save into database server3.5.1.2.5 UC14: Update messages from databaseName Update messages from databaseDescription This use case allows Operator to update the latest broadcast messages from database serverActor OperatorTrigger User click button [Cập nhật bản tin]Pre-condition Computer must connect to database serverPost-condition The latest message will be displayed into GUI________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 32Prepared by 6Fingers
  • 33. 3.5.1.2.6 UC15: Receive messages from vesselsName Update messages from databaseDescription 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 OperatorPre-condition Computer must connect to transceiver device through audio port (mic port)Post-condition The content of received message will be displayed into GUI3.5.1.3 Viewer Use cases Description3.5.1.3.1 UC16: Create broadcast messagesName Create broadcast messagesDescription 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 OperatorTrigger 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 serverPost-condition The message will be saved into database server3.5.1.3.2 UC17: View all vessels’ positions on mapName View all vessels’ positions on mapDescription 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.Actor Central OperatorPre-condition Internet connection is available for map downloading________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 33Prepared by 6Fingers
  • 34. Business RulesBR DescriptionCodeBR1 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 voyageName View a vessel’s voyageDescription This use case allows central operator to observe a vessel’s voyage on a time interval.Actor Central OperatorTrigger User click to a vessel’s position on the map of main screen.Pre-condition There is at least a vessel displayed on the mapBusiness RulesBR DescriptionCodeBR5 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 informationName View a vessel’s informationDescription This use case allows central operator view the information of a registered vessel, including an unique ID, current position, weight, etc.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 34Prepared by 6Fingers
  • 35. Actor Central OperatorTrigger User points mouse to the vessel position on the map and clickPre-condition There is at least one vessel displayed on the mapPost-condition Information of vessel is displayed in a pop up context3.5.1.3.5 UC20: Auto update vessel positionName Auto update vessel positionDescription This use case allows Central Operator not need to update vessel position manually. The application will update those information automatically each period of time.Actor Central OperatorTrigger User points mouse to the vessel position on the map and clickPre-condition There is at least one vessel displayed on the mapPost-condition Information of vessel is displayed in a pop up context3.5.2 Screen Description3.5.2.1 Viewer screen3.5.2.1.1 SC1 – Map view screenMaritime Information Visualization - O X Quản lý Tạo bản tin Lịch sử đi tàu X Đ I Ề U K H I Ể N T Ì M K I Ế M Figure 3-1: Map view screen________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 35Prepared by 6Fingers
  • 36. Field name Control Editable Mandatory Description TypeWindow 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 description3.5.2.1.2 SC2 – SOS notification screenMaritime Information Visualization - O X Quản lý Tạo bản tin Lịch sử đi tàu X Đ I Ề U K H I Ể N T Ì M K I Ế M Figure 3-2: SOS notification screenField name Control Editable Mandatory Description TypeSOS 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 36Prepared by 6Fingers
  • 37. 3.5.2.1.3 SC3 – Vessel information view screenMaritime Information Visualization - O X Quản lý Tạo bản tin Lịch sử đi tàu X Đ I Ề Biển kiểm soát: U 103QN K H Kinh độ: 123.456 I Ể Vĩ độ: N 14.362 T Ì M Các thông tin khác K I Ế M Figure 3-3: Vessel information view screenField name Control Editable Mandatory Description TypeInformation Context No Context shows vessel informationContext when user click to vessel symbol in map view area Table 3-10: Vessel information view screen description3.5.2.1.4 SC4 – Vessel voyage view screen Maritime Information Visualization - O X Quản lý Tạo bản tin Lịch sử đi tàu X Đ I Ề U K H I Ể N T Ì M K I Ế M Figure 3-4: Vessel voyage view screen________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 37Prepared by 6Fingers
  • 38. Field name Control Editable Mandatory Description TypeVessel voyage UI No The line draws a vessel voyage control from a start point to an ending point Table 3-11: Vessel voyage view Screen description3.5.2.1.5 SC5 – Storm message creating screenMaritime Information Visualization - O X Quản lý Tạo bản tin X Đ Bản tin báo bãoBản tin báo bão I Ề Bản tin thời tiết biển U Vị trí tâm bão 1: 11/02/2012 06:00 Bản tin cảnh báo K H Bản tin khẩn I Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150 Các bản tin khác Ể N Vị trí tâm bão 2: 11/02/2012 10:00 T Ì Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150 Phạm vi ảnh hưởng 3: 320 M K Vị trí tâm bão 3: 11/02/2012 10:00 I Ế M Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150 Phạm vi ảnh hưởng 3: 320 Vị trí tâm bão 4: 11/02/2012 10:00 Vĩ độ: 22.123 Kinh độ: 123.456 Phạm vi ảnh hưởng 1: 90 Phạm vi ảnh hưởng 2: 150 Phạm vi ảnh hưởng 3: 320 Đồng ý Figure 3-5: Storm message creating screenField name Control Editable Mandatory Description TypeTab title Text No Yes Text: “Tạo bản tin”Message type Drop-down Yes Yes List of message type listMessage 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 38Prepared by 6Fingers
  • 39. 3.5.2.2 Coastal Station System Screen3.5.2.2.1 SC6 – Message history screenLịch sử bản tin - O XSố các bản tin được lưu trữ: 1 STT Loại Thời gian nhận Thời gian phát Ghi chú Bản tin thời tiết 1 14:00:00 10/02/2012 16:00:00 10/02/2012 biển Figure 3-6: Message history screenField name Control Editable Mandatory Description TypeTitle Text No Yes Text: “Lịch sử bản tin”Amount of Text No Yes Color: redmessages Text Length: 255Message history Table No Yes Table of message records Table 3-13: Message history view screen description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 39Prepared by 6Fingers
  • 40. 3.5.2.2.2 SC7 – Message view screenCoastal Station - O X Phát bản tin 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ập nhật bản tin Phát bản tin Cài đặt Lịch sử các bản tin Figure 3-7: Message view screenField name Control Editable Mandatory Description TypeMessage 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] text No Yes Text: “Cập nhật bản tin”button The system will connect to database to update new messages[Phát bản tin] Button No Yes Text: “Phát bản tin”button Functionality: Broadcast the message to vessels manually[Lịch sử bản tin] Button No Yes Text: “Lịch sử bản tin”button Functionality: show the SC6 –________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 40Prepared by 6Fingers
  • 41. Field name Control Editable Mandatory Description Type Message history screen Table 3-14: Message view screen description3.5.2.3 On-sea Terminal screen3.5.2.3.1 SC8 – Map view screen Figure 3-8: Map view screenField name Control Editable Mandatory Description TypeBackground 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 Image No Yes A symbol at the point as realsymbol vessel positionVessel position text No Yes The text as real vessel positiontext putted near Vessel position symbol________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 41Prepared by 6Fingers
  • 42. Field name Control Editable Mandatory Description TypeWeather textbox Textbox No Yes The textbox containing information of weather, putted at the below right cornerSOS button Button No Yes Text: “SOS” User will use this button in case of urgency Table 3-15: Map view Screen3.5.2.3.2 SC9 – Storm (on map) view screen Figure 3-9: Storm view screenField name Control Editable Mandatory Description TypeStorm 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 42Prepared by 6Fingers
  • 43. 3.6 Nonfunctional Requirements3.6.1 User access and security3.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/s3.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 ScalabilityThe system will be able to scale to support additional vessels, coastal stations or viewersystems.3.6.7 MaintainabilityThe 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 43Prepared by 6Fingers
  • 44. 3.7 Other Requirements Language: Vietnamese3.8 Requirement Completeness CriteriaThe 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 Completeness Remain Use case functions/features Communication from 6, 7, 8, 13, via UHF/VHF via HF band Coastal Station to On-sea 15 band Terminal, and vice-versa Read/write data from/into 6, 7, 8, 13, 100% transceiver through audio 15 port Read position from GPS 4 100% device Divide a message into 6, 7, 8, 13, 100%Capstone multiple packages and 15project assemble them Visualize vessel position 18, 19 100% information using Google Earth API Visualize storm information 1, 2 100% on map (On-sea Terminal) Visualize vessel position on 1, 4 100% map (On-sea Terminal) Remote to manage Maritime 14, 16, 19, 100% database 20 Availability to work with a to be system with more than 100 developedRelease to Coastal Station and about in futuremarket and 20000 vesselsgo live Communication via HF to be tested & deployed in future Table 3-17: Requirement Completeness Criteria4 Software Design4.1 Design Overview4.1.1 System Context4.1.1.1 Diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 44Prepared by 6Fingers
  • 45. Diagram 4-1: System Context Diagram4.1.1.2 System Context DescriptionObject DescriptionOn-land systemCentral operator User of Viewer application, responsible for - Monitoring vessel positions, voyages - Create weather messages, storm messagesOperator User of Coastal Station application, responsible for - Monitoring messages to be broadcasted to vessels, received from vessels - Broadcasting messages to vesselsViewer Windows application for monitoring vessel positions, vessel voyages, creating messagesCoastal Station Windows application for monitoring broadcasted messages, received messages. It connects to radio station hardware for that tasksDatabase server Windows application that connects to SQL Server for managing Maritime databaseLand-sea CommunicationRadio station Hardware at each coastal station for broadcasting messages, receive messages through HF waveTransceiver Hardware at each vessel for receiving messages, send messages through________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 45Prepared by 6Fingers
  • 46. Object Description HF waveOn-sea SystemFisher User of On-sea Terminal application, responsible for monitoring their own vessel position on map, being alerted about storm, weather informationOn-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 Description4.2 Architecture Overview4.2.1 Diagram4.2.1.1 On-land System4.2.1.1.1 Database Server Diagram 4-2: Database Server ArchitectureNo Package Name Description1 UI (Console) Console display, informs user about connections or database altering activities2 Controller Main controller3 From-Client Remote Manage processes when Viewer or________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 46Prepared by 6Fingers
  • 47. No Package Name Description Coastal Station remotes to server4 To-Client Remote Manage processes when server remotes to Viewer / Coastal Station clients5 SQL Database Access Connects to SQL Database Server (default: local host), control data flow from/to SQL Database Server6 Configuration Contains application setting up parameters7 Common Struct Common objects for binding data8 Exception Management Exception management Table 4-2: Database Server Architecture Description4.2.1.1.2 Viewer Diagram 4-3: Viewer Architecture DiagramNo Package Name Description1 GUI Display graphical interface2 Controller Main controller3 Boast cast Messages Creator Create “Boast cast” Messages________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 47Prepared by 6Fingers
  • 48. No Package Name Description4 Google Earth Handler Prepare display data and control Google Earth API5 Server Connection Connect to database server, read data from/write data into database server6 Common Struct Common objects for binding data7 Math Helper Provide math functions8 Logs Management Log files management9 Exception Management Exceptions management10 Configuration Contains application setting up parameters Table 4-3: Viewer Architecture Description4.2.1.1.3 Coastal Station Diagram 4-4: Coastal Station ArchitectureNo Package Name Description1 GUI Display graphical interface2 Controller Main controller3 Server Connection Connect to database server, read data from/write data into database server________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 48Prepared by 6Fingers
  • 49. No Package Name Description4 Transceiver Connection Connect to transceiver, receive data from / send data to transceiver5 Error Correction Algorithm Algorithm to correct errors, eliminate noises generated through land-sea HF communication6 Audio Decode/Encode Modem Transform text into audio, audio into text7 Configuration Contains application setting up parameters8 Common Struct Common objects for binding data9 Exception Management Exception management Table 4-4 Coastal Station Architecture Description4.2.1.2 On-sea Terminal Presentation Layer Common Layer GUI Common Struct <<uses>> Business Layer <<uses>> <<uses>> Audio Soft- Exception Data correction Controller Modem Management «uses» Data Access Layer Utility Tranceiver connection Diagram 4-2: On Sea Terminal ArchitectureNo Package Name Description1 GUI Display graphical interface to fisher2 Controller Control the main program, process data3 Transceiver Connection Connect to transceiver, receive data from / send data to transceiver4 Error Correction Algorithm to check the correctness of data, generated by audio noise through land-sea HF communication, correct it if________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 49Prepared by 6Fingers
  • 50. No Package Name Description possible5 Audio Soft-modem Convert audio data from analog to digital and digital to analog, communicate with the device audio in/out port6 Common Struct Common message type receive/broadcast from/to coastal stations7 Exception Management Manage exception of on-sea terminal program8 Utilization Contains utilization function for the program Table 4-2 On-sea Terminal Architecture Description4.3 Detailed Design Description4.3.1 On-land System4.3.1.1 Database Server4.3.1.1.1 Class diagram4.3.1.1.1.1 Diagram Diagram 4-5: Database server – class diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 50Prepared by 6Fingers
  • 51. 4.3.1.1.1.2 Class Description4.3.1.1.1.2.1 Server class4.3.1.1.1.2.1.1 AttributesNo Name Type Description1 Port int2 dbConnectManager MaritimeDAL4.3.1.1.1.2.1.2 Methods4.3.1.1.1.2.1.2.1 ConfigConnectionMethod name void ConfigConnection() Setup connection so that server can listen if there is any client connect toDescription server, using SOAPParameters voidReturn void4.3.1.1.1.2.1.2.2 CloseConnectionMethod name void CloseConnection()Description Close connectionParameters voidReturn void4.3.1.1.1.2.1.2.3 StartPositionMessageThreadMethod name void StartPositionMessageThread()Description Create a queue to manage all vessel position updating into Maritime databaseParameters voidReturn void4.3.1.1.1.2.1.2.4 AddViewerClientMethod name void AddViewerClient(string clientID)Description add clientID string into list of Viewer client ID client ID, generated by Viewer clientParameters clientID: string applicationReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 51Prepared by 6Fingers
  • 52. 4.3.1.1.1.2.1.2.5 AddCoastalStationClientMethod name void AddCoastalStationClient (string clientID)Description add clientID string into list of CoastalStation client ID client ID, generated by CoastalStationParameters clientID: string client applicationReturn void4.3.1.1.1.2.1.2.6 RemoveViewerClientMethod name void RemoveViewerClient(string clientID) remove clientID string from list of Viewer client ID, usually be called whenDescription Viewer client disconnects to server client ID, generated by Viewer clientParameters clientID: string applicationReturn void4.3.1.1.1.2.1.2.7 RemoveCoastal StationClientMethod name void RemoveCoastalStationClient(string clientID) Remove clientID string from list of CoastalStation client ID, usually be calledDescription when CoastalStation disconnects to server clientID, generated by CoastalStationParameters clientID: string client applicatonReturn void4.3.1.1.1.2.1.2.8 AddPositionMessageIntoQueueMethod name void AddPositionMessageIntoQueue(VesselPosition positionRecord) Add position message update calling function into a queue so that they willDescription process in order, prevent Maritime database connection conflicts position information to be insertedParameters positionRecord: VesselPosition into databaseReturn void4.3.1.1.1.2.1.2.9 PopPositionMessageFromQueueMethod name VesselPosition PopPositionMessageFromQueue()Description Pop position record of vessel from queue to be processedParameters void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 52Prepared by 6Fingers
  • 53. Return the popped VesselPosition, null if the queue is empty4.3.1.1.1.2.1.2.10 InsertBroadcastMessageMethod name void InsertBroadcastMessage(BroadcastMessage message) Insert broadcast message into Maritime database. It calls MaritimeDALDescription method to insert.Parameters message: BroadcastMessage message to be insertedReturn void4.3.1.1.1.2.1.2.11 InsertSOSMessageMethod name void InsertSOSMessage(SOSMessage message) Insert SOS message into Maritime database. It calls MaritimeDAL method toDescription insert.Parameters message: SOSMessage message to be insertedReturn void4.3.1.1.1.2.1.2.12 GetVesselLastestInfoMethod name List<VesselPosition> GetVesselLastestInfo()Description Connect to Maritime database, then get latest position records of all vesselsParameters voidReturn list of position records, null if there is no information4.3.1.1.1.2.2 TransporterDelegateIt is not a class. We just use it to group these following delegates.4.3.1.1.1.2.2.1 NewStormMessageHandlerMethod name void NewStormMessageHandler (BroadcastMessage message) delegate for CoastalStation client to be able to register a handler for processingDescription a new storm messageParameters message: BroadcastMessage new storm messageReturn void4.3.1.1.1.2.2.2 NewSOSMessageHandlerMethod name void NewSOSMessageHandler(SOSMessage message)Description Delegate for Viewer client to be able to register a handler for processing a new________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 53Prepared by 6Fingers
  • 54. SOS messageParameters message: SOSMessage new SOS messageReturn void4.3.1.1.1.2.3 ConfigIniFileManager class4.3.1.1.1.2.3.1 AttributesNo Name Type Description1 fileName string name of .ini configuration file2 port int server listening port3 dbConnectionString string connection string to Maritime database4.3.1.1.1.2.3.2 Methods4.3.1.1.1.2.3.2.1 ReadMethod name void Read (string filename)Description Open ini file, read values, then save into its membersParameters filename: string file path to be readReturn void4.3.1.1.1.2.3.2.2 SaveMethod name void Save(string filename)Description Open ini file, write its members’ value into fileParameters filename: string file path to be writtenReturn void4.3.1.1.1.2.4 MaritimeDAL class4.3.1.1.1.2.4.1 AttributesNo Name Type Description1 connectionString string connection string to connect into Maritime database________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 54Prepared by 6Fingers
  • 55. 4.3.1.1.1.2.4.2 Methods4.3.1.1.1.2.4.2.1 OpenMethod name bool Open(string connectionString)Description Open connection to Maritime database connection string to MaritimeParameters connectionString: string databaseReturn bool4.3.1.1.1.2.4.2.2 CloseMethod name void Close()Description Close connection to Maritime databaseParameters voidReturn void4.3.1.1.1.2.4.2.3 GetBroadcastMessageMethod name List<BroadcastMessage> GetBroadcastMessage(DateTime fromDateTime)Description Get the broadcast message which has created date time after fromDateTimeParameters fromDateTime: DateTime created date time of messageReturn list of broadcast message, null if there is no messages4.3.1.1.1.2.4.2.4 GetVesselInfoByVesselIDMethod name Vessel GetVesselInfoByVesselID(int vesselID)Description Get vessel information from Maritime database by vessel ID vessel ID (primary key of VesselParameters vesselID: int table in Maritime database)Return Vessel object, null if there is no information4.3.1.1.1.2.4.2.5 GetVoyageByVesselIDMethod name List<VesselPosition> GetVoyageByVesselID(int vesselID)Description Get voyage of a vessel that has vesselID vessel ID (primary key of VesselParameters vesselID: int table in Maritime database)Return list of position records of this vessel, null if there is no information________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 55Prepared by 6Fingers
  • 56. 4.3.1.1.1.2.4.2.6 InsertBroadcastMessageMethod name void InsertBroadcastMessage(BroadcastMessage message)Description Insert broadcast message into Maritime databaseParameters message: BroadcastMessage message to be insertedReturn void4.3.1.1.1.2.4.2.7 InsertSOSMessageMethod name void InsertSOSMessage(SOSMessage message)Description Insert SOS message into Maritime databaseParameters message: SOSMessage message to be insertedReturn void4.3.1.1.1.2.4.2.8 InsertPositionMessageMethod name void InsertPositionMessage(VesselPosition positionRecord)Description Insert position information into Maritime databaseParameters positionRecord: VesselPosition position record to be insertedReturn void4.3.1.1.1.2.4.2.9 GetVesselLastestPositionMethod name List<VesselPosition> GetVesselLastestPosition()Description Get list of the latest position records of all vesselsParameters voidReturn list of position records, null if there is no information4.3.1.1.1.2.5 ICoastalStationRemote interface4.3.1.1.1.2.5.1 AttributesThis interface has no attributes.4.3.1.1.1.2.5.2 Methods4.3.1.1.1.2.5.2.1 RegisterCoastalStationTransporter void RegisterCoastalStationTransporter(string clientID,Method name CoastalStationTransporter csTransporter) Inform server that CoastalStation client is connected and allow server toDescription remote CoastalStation client through transporter object________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 56Prepared by 6Fingers
  • 57. client ID string, generated by clientID: string CoastalStation applicationParameters transporter object to be used in csTransporter: CoastalStationTransporter remote from server to CoastalStation clientReturn void4.3.1.1.1.2.5.2.2 UnregisterCoastalStationTransporterMethod name void UnregisterCoastalStationTransporter(string clientID) Inform server that CoastalStation client is disconnected and server cannot useDescription transporter object to remote client ID string, generated byParameters clientID: string CoastalStation applicationReturn void4.3.1.1.1.2.5.2.3 GetBroadcastMessageMethod name List<BroadcastMessage> GetBroadcastMessage(DateTime fromDateTime)Description Get the broadcast message which has created date time after fromDateTimeParameters fromDateTime: DateTime created date time of messageReturn list of broadcast message, null if there is no messages4.3.1.1.1.2.5.2.4 GetVesselInfoByIDMethod name Vessel GetVesselInfoByID(int vesselID)Description Get vessel information from Maritime database by vessel ID vessel ID (primary key of VesselParameters vesselID: int table in Maritime database)Return Vessel object, null if there is no information4.3.1.1.1.2.5.2.5 CommitPositionMessageFromVesselMethod name void CommitPositionMessageFromVessel(VesselPosition positionRecord)Description Commit vessel position information to Database ServerParameters positionRecord: VesselPosition position record to be committedReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 57Prepared by 6Fingers
  • 58. 4.3.1.1.1.2.5.2.6 CommitSOSMessageFromVesselMethod name void CommitSOSMessageFromVessel(SOSMessage message)Description commit SOS message to Database ServerParameters message: SOSMessage message to be committedReturn void4.3.1.1.1.2.6 IViewerRemote interface4.3.1.1.1.2.6.1 AttributesThis interface has no attributes.4.3.1.1.1.2.6.2 Methods4.3.1.1.1.2.6.2.1 RegisterViewerTransporter void RegisterViewerTransporter(string clientID, ViewerTransporterMethod name vTransporter) Inform server that Viewer client is connected and allow server to remoteDescription Viewer client through transporter object client ID string, generated by ViewerParameters clienID: string application transporter object to be used in vTransporter: ViewerTransporter remote from server to Viewer clientReturn void4.3.1.1.1.2.6.2.2 UnregisterViewerTransporterMethod name void UnregisterViewerTransporter(string clientID) Inform server that Viewer client is disconnected and server cannot useDescription transporter object to remote client ID string, generated by ViewerParameters clientID: string applicationReturn void4.3.1.1.1.2.6.2.3 GetVesselLastestInfoMethod name List<VesselPosition> GetVesselLastestInfo()Description Get list of the latest position records of all vesselsParameters voidReturn list of position records, null if there is no information________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 58Prepared by 6Fingers
  • 59. 4.3.1.1.1.2.6.2.4 GetVoyageByVesselIDMethod name List<VesselPosition> GetVoyageByVesselID(int vesselID)Description Get voyage of a vessel that has vesselID vessel ID (primary key of VesselParameters vesselID: int table in Maritime database)Return list of position records of this vessel, null if there is no information4.3.1.1.1.2.6.2.5 GetVesselInfoByIDMethod name Vessel GetVesselInfoByID(int vesselID)Description Get vessel information from Maritime database by vessel ID vessel ID (primary key of VesselParameters vesselID: int table in Maritime database)Return Vessel object, null if there is no information4.3.1.1.1.2.6.2.6 CommitBroadcastMessageMethod name void CommitBroadcastMessage(BroadcastMessage message)Description Commit broadcast message to Database ServerParameters message: BroadcastMessage message to be committedReturn void4.3.1.1.1.2.6.2.7 GetLastestStormMessageMethod name BroadcastMessage GetLastestStormMessage()Description Get the latest storm message in Maritime databaseParameters voidReturn BroadcastMessage with type of Storm, null if there is no information________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 59Prepared by 6Fingers
  • 60. 4.3.1.1.2 Sequence Diagram4.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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 60Prepared by 6Fingers
  • 61. 4.3.1.1.2.2 Start position message thread Diagram 4-8: Database Server – Start position message thread sequence diagram4.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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 61Prepared by 6Fingers
  • 62. 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 diagram4.3.1.1.2.5 Insert position message from vessel Diagram 4-13: Database server – Insert position message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 62Prepared by 6Fingers
  • 63. 4.3.1.1.2.6 Insert Broadcast message from Viewer Diagram 4-14: Database server – Insert broadcast message sequence diagram4.3.1.1.2.7 Insert SOS message from vessels Diagram 4-15: Database server – Insert SOS message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 63Prepared by 6Fingers
  • 64. 4.3.1.1.2.8 Insert storm message from Viewer Diagram 4-16: Database server – Insert storm message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 64Prepared by 6Fingers
  • 65. 4.3.1.2 Viewer4.3.1.2.1 Class Diagram4.3.1.2.1.1 Diagram Diagram 4-17: Viewer – class diagram4.3.1.2.1.2 Class Description4.3.1.2.1.2.1 MainController class4.3.1.2.1.2.1.1 AttributesNo Name Type Description1 autoUpdateData AutoUpdateData Manages automatically updating message from database________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 65Prepared by 6Fingers
  • 66. No Name Type Description2 serverConnectManager ServerConnectManager Connects to database & manages database data altering3 searchForm SearchForm Application search GUI Form4 mainForm MainForm Application main GUI Form5 overViewForm overViewForm Application overview GUI Form6 createMeesagesForm CreateMeesagesForm Application create new broadcast messages GUI Form7 vesselManager VesselManager Management Vessel list4.3.1.2.1.2.1.2 Methods4.3.1.2.1.2.1.2.1 AutoBroadcastMessageMethod name void ControlGetData() Synchronize threads during time the application get data from data base. It isDescription called by AutoUpdateData when time interval is reached.Parameters voidReturn void4.3.1.2.1.2.1.2.2 ControlUpdateDataMethod name void ControlUpdateData() Synchronize threads during time the application get update data to GUI. It isDescription called by AutoUpdateData when it finished get data from database.Parameters voidReturn void4.3.1.2.1.2.1.2.3 ControlDisplayVesselMethod name void ControlDisplayVessel() Display Vessels as layers on GoogleEarth API. It is called byDescription ControlUpdateData.Parameters void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 66Prepared by 6Fingers
  • 67. Return void4.3.1.2.1.2.1.2.4 ControlDisplayTyphoonMethod name void ControlDisplayTyphoon() Display Typhoon as a layer on GoogleEarth API. It is called byDescription ControlUpdateData after it calls ControlDisplayVessel().Parameters voidReturn void4.3.1.2.1.2.1.2.5 ControlDisplaySOSMethod name void ControlDisplaySOS() Display SOS messages as layers on GoogleEarth API. It is called byDescription ControlUpdateData after it calls ControlDisplayTyphoon ().Parameters voidReturn void4.3.1.2.1.2.1.2.6 ConfigParametersMethod name void ConfigPagrameters()Description Configuration parametersParameters voidReturn void4.3.1.2.1.2.2 ServerConnectManager class4.3.1.2.1.2.2.1 AttributesNo Name Type Description1 ServerIP string IP of server2 ServerPort int Port of server3 eventHandler IServerConnectManager Handle event from database4.3.1.2.1.2.2.2 Methods4.3.1.2.1.2.2.2.1 ConnectMethod name bool Connect()Description Make a connection to database to get data.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 67Prepared by 6Fingers
  • 68. Parameters voidReturn true if connect success, false if fail4.3.1.2.1.2.2.2.2 CommitMessagesMethod name bool CommitMessages(string message)Description Commit Broadcast messages to database.Parameters message : string Content of messageReturn true if connect success, false if fail4.3.1.2.1.2.2.2.3 GetVesselLatestInfoMethod name Vessel GetVesselLatestInfo()Description Get VesselLatestInfo from databaseParameters voidReturn New List<Vessel>4.3.1.2.1.2.2.2.4 GetVesselHistoryMethod name Vessel GetVesselHistory()Description Get VesselHistory from databaseParameters voidReturn New List<Vessel>4.3.1.2.1.2.2.2.5 GetVesselOwnerMethod name Owner GetVesselOwner()Description Get VesselOwner from databaseParameters voidReturn New Owner object4.3.1.2.1.2.2.2.6 GetLatestTyphoonMessageMethod name Owner GetLatestTyphoonMessage()Description Get TyphoonMessage from databaseParameters voidReturn New Typhoon object________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 68Prepared by 6Fingers
  • 69. 4.3.1.2.1.2.3 AutoUpdateData class4.3.1.2.1.2.3.1 AttributesNo Name Type Description1 Interval int Interval of Auto Update Data2 CallBackFunction object Callback when update data finished4.3.1.2.1.2.3.2 Methods4.3.1.2.1.2.3.2.1 StartMethod name void Start()Description Start AutoUpdateDataParameters voidReturn void4.3.1.2.1.2.3.2.2 StopMethod name void Stop()Description Stop AutoUpdateDataParameters voidReturn void4.3.1.2.1.2.3.2.3 AutoUpdateLatestInfoMethod name void AutoUpdateLatestInfo()Description Get VesselLatestInfo from database and add to List<vessel>Parameters voidReturn void4.3.1.2.1.2.3.2.4 AutoUpdateTyphoonMethod name void AutoUpdateTyphoon()Description Get Typhoon data from database and add to object TyphoonParameters voidReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 69Prepared by 6Fingers
  • 70. 4.3.1.2.1.2.4 VesselManager class4.3.1.2.1.2.4.1 AttributesNo Name Type Description1 VesselList List<Veseel> List of Vessel4.3.1.2.1.2.4.2 Methods4.3.1.2.1.2.4.2.1 AddVesselMethod name bool AddVessel(Vessel vessel)Description Add vessel to list VesselParameters vessel:Vessel vessel object to add in List<Vessel>Return true if vessel is added success, fall if fail4.3.1.2.1.2.4.2.2 RemoveVesselMethod name bool RemoveVessel(int index)Description Remove vessel from list VesselParameters index: int Index of vessel in List<Vessel>Return true if vessel is remove success, fall if fail4.3.1.2.1.2.4.2.3 EditVesselMethod name bool EditVessel(int index)Description Edit vessel from list VesselParameters index: int Index of vessel in List<Vessel>Return true if vessel is edit success, fall if fail4.3.1.2.1.2.4.2.4 CountMethod name int Count()Description Return number of vessels in List<Vessel>Parameters voidReturn number of vessels in list4.3.1.2.1.2.4.2.5 ToTableMethod name Datatable Totable()Description Return a Table of vessels in List<Vessel>________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 70Prepared by 6Fingers
  • 71. Parameters voidReturn Datatable of List<Vessel>4.3.1.2.1.2.4.2.6 FindByVesselNoMethod name Vessel FindByVesselNo (string vesselNo)Description Return a vessel in List<Vessel> base on vessel numberParameters vesselNo: string Number of vesselReturn New Vessel object4.3.1.2.1.2.4.2.7 FindByVesselIDMethod name Vessel FindByVesselID (int ID)Description Return a vessel in List<Vessel> base on vessel IDParameters ID:int ID of vesselReturn New Vessel object4.3.1.2.1.2.4.2.8 FindByVesselOwnerMethod name Vessel FindByVesselOwner (string name)Description Return a vessel in List<Vessel> base on name of ownerParameters name: string Name of ownerReturn New Vessel object4.3.1.2.1.2.5 Vessel class4.3.1.2.1.2.5.1 AttributesNo Name Type Description1 VesselID int Id of vessel2 VesselOwner string Owner of vessel3 VesselHistoryID int HistoryId of vessel4 VesselNumber string Number of vessel5 VesselType enum Type of vessel6 VesselLat float Latitude of vessel7 VesselLng float Longtitude of vessel________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 71Prepared by 6Fingers
  • 72. No Name Type Description8 VesselHeading float Heading of vessel9 VesselSpeed float Speed of vessel10 Vesse LastReceiveData Datetime Last Receive data of vessel11 VesselSOS bool Vessel being transmits SOS messages12 VesselApiID int ID in GoogleEarth API13 VesselIsNew bool Vessel is new14 VesselIsRead bool Vessel is displayed4.3.1.2.1.2.5.2 Methods4.3.1.2.1.2.5.2.1 EqualsMethod name bool Equals (Vessel vessel)Description Compare 2 vesselsParameters vessel: Vessel Vessel to compareReturn true if 2 vessel is equals, fail if not4.3.1.2.1.2.6 MathHelper class4.3.1.2.1.2.6.1 Attributes4.3.1.2.1.2.6.2 Methods4.3.1.2.1.2.6.2.1 Distance2pointMethod name Float Distance2point(GLatLng g1, GLatLng g2)Description Calculate distance of 2 point g1:GLatLng Position 1Parameters g2: GLatLng Position 2Return Distance of 2 point4.3.1.2.1.2.6.2.2 PointsOfCircleMethod name GLatLng PointsOfCircle(Circle circle,double angle)Description Calculate position of a point in circle________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 72Prepared by 6Fingers
  • 73. circle: Circle Circle to calculateParameters angle: double Angle at the center of circleReturn New GLatLng object4.3.1.2.1.2.6.2.3 FindTangentsMethod name GLatLng[] FindTangents (Circle c1,Circle c2)Description Calculate tangents of 2 circle c1: Circle Circle 1Parameters c2: Circle Circle 2Return New array GLatLng[] objects4.3.1.2.1.2.7 GLatLng class4.3.1.2.1.2.7.1 AttributesNo Name Type Description1 EarthRadiusInKilometers float Earth Radius2 Longitude float Longitude3 Latitude float Latitude4.3.1.2.1.2.7.2 Methods4.3.1.2.1.2.7.2.1 DegreeToRadianMethod name float DegreeToRadian(float deg)Description Calculate radian of a degreeParameters deg: float Angle in degreeReturn Angle in radian4.3.1.2.1.2.7.2.2 RadianToDegreeMethod name float RadianToDegree(float rad)Description Calculate degree of a radianParameters rad: float Angle in radianReturn Angle in degree________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 73Prepared by 6Fingers
  • 74. 4.3.1.2.1.2.7.2.3 DistanceToMethod name float DistanTo(GLatLng endPoint)Description Calculate distance of this point to another pointParameters endPoint : GLatLng End point to calculateReturn Distance of this point to another point4.3.1.2.1.2.7.2.4 BearingToMethod name float BearingTo(GLatLng endPoint)Description Calculate bearing of this point to another pointParameters endPoint: GLatLng End point to calculateReturn Bearing of this point to another point4.3.1.2.1.2.8 GoogleEarthCommands class4.3.1.2.1.2.8.1 AttributesNo Name Type Description1 IconScale1 float Icon scale when display2 IconScale2 float Icon scale when click3 SOSIconScale1 float Icon SOS when display4 SOSIconScale1 float Icon SOS when click5 DefaultRange float Default range on GoogleEarth API6 CenterLat float Center point latitude7 CenterLng floar Center point longitude4.3.1.2.1.2.8.2 Methods4.3.1.2.1.2.8.2.1 DrawCircleMethod name void DrawCircle (Circle circle)Description Draw a circle on GoogleEarthParameters circle:Circle Circle to drawReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 74Prepared by 6Fingers
  • 75. 4.3.1.2.1.2.8.2.2 DrawLineMethod name void DrawLine (GLatLng p1,GLatLng p2)Description Draw a line on GoogleEarth p1: GLatLng Begin positionParameters p2: GLatLng End positionReturn void4.3.1.2.1.2.8.2.3 DrawTyphoonMethod name void DrawLine (Typhoon typhoon)Description Draw a typhoon on GoogleEarthParameters typhoon: Typhoon Typhoon to drawReturn void4.3.1.2.1.2.8.2.4 SetVesselApiIDMethod name void SetVesselApiID (int ID)Description Set ApiID of a vesselParameters ID: int ID of VesselReturn Void4.3.1.2.1.2.8.2.5 DrawVesselMethod name void DrawVessel (Vessel vessel)Description Draw a vessel on Google EarthParameters vessel:Vessel Vessel to drawReturn Void4.3.1.2.1.2.8.2.6 UpdateVesselMethod name void UpdateVessel (Vessel vessel)Description Update vessel on Google EarthParameters vessel :Vessel Vessel to updateReturn Void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 75Prepared by 6Fingers
  • 76. 4.3.1.2.1.2.8.2.7 ChangeIconMethod name void ChangeIcon (object obj)Description Change Icon of a layer on Google EarthParameters obj:object Object need to be change IconReturn Void4.3.1.2.1.2.8.2.8 DeleteVesselMethod name void DeleteVessel (Vessel vessel)Description Delete a vessel on Google EarthParameters vessel:Vessel Vessel to deleteReturn Void4.3.1.2.1.2.8.2.9 DeleteAllMethod name void DeleteAll ()Description Delete all layers on Google EarthParameters VoidReturn Void4.3.1.2.1.2.8.2.10 SetVesselDescriptionMethod name void SetVesselDescription(Vessel vessel)Description Set description for Vessel on Google Earth Vessel should be displayedParameters vessel: Vessel descriptionReturn Void4.3.1.2.1.2.8.2.11 SOSVisualizationMethod name void SOSVisualization (Vessel vessel)Description Set Display SOS Vessel on Google EarthParameters vessel: Vessel Vessel in trobleReturn Void4.3.1.2.1.2.8.2.12 CreateLookAtMethod name void CreateLookAt (int alt,float lat,float lng)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 76Prepared by 6Fingers
  • 77. Description Create “look at” at a position alt: int Altitude of “look at”Parameters lat: float Latitude of position lng: float Longitude of positionReturn Void4.3.1.2.1.2.8.2.13 CreatePlaceMarkMethod name void CreatePlaceMark (GLatLng p)Description Create a place mark on GoogleEarthParameters p: GLatLng Point to create place markReturn Void4.3.1.2.1.2.8.2.14 DeletePlaceMarkMethod name void DeletePlaceMark (PlaceMark pm)Description Delete a place mark on GoogleEarthParameters pm:PlaceMark PlaceMark to deleteReturn Void4.3.1.2.1.2.9 MainForm class4.3.1.2.1.2.9.1 AttributesNo Name Type Description1 GeIsReady bool Loading GoogleEarth is finished4.3.1.2.1.2.9.2 Methods4.3.1.2.1.2.9.2.1 UpdateDataMethod name void UpdateData ()Description Updata data to GUIParameters voidReturn void4.3.1.2.1.2.9.2.2 DrawLayersMethod name void DrawLayers ()________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 77Prepared by 6Fingers
  • 78. Description Call methods drawing in GoogleEarthCommand for drawing on Google EarthParameters voidReturn void4.3.1.2.1.2.9.2.3 GeReadyMethod name void GeReady ()Description Callback function of GoogleEarth API, set GeIsReady to trueParameters voidReturn void4.3.1.2.1.2.9.2.4 GeFailedMethod name void GeFailed ()Description Callback function of GoogleEarth API, set GeIsReady to falseParameters voidReturn void4.3.1.2.1.2.9.2.5 SetApiIDMethod name void SetApiID ()Description Callback function of GoogleEarth API, set ApiID of VesselParameters voidReturn void4.3.1.2.1.2.9.2.6 VesselClickMethod name void VesselClick (int vesselID)Description Callback function of GoogleEarth API, a vessel is click on GoogleEarthParameters vesselID: int ID of vessel clickedReturn void4.3.1.2.1.2.9.2.7 ShowShipHistoryMethod name void ShowShipHistory (int vesselID)Description Callback function of GoogleEarth API, vessel should be show its historyParameters vesselID: int ID of vessel clicked________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 78Prepared by 6Fingers
  • 79. Return void4.3.1.2.1.2.9.2.8 SetPlaceMarkLocationMethod name void SetPlaceMarkLocation(float lat,float lng)Description Callback function of GoogleEarth API, PlaceMark is “relocation” lat: float New latitude of PlaceMarkParameters lng: float New longitude of PlaceMarkReturn void4.3.1.2.1.2.10 SearchingForm class4.3.1.2.1.2.10.1 AttributesNo Name Type Description1 ResultData Datatable Result data4.3.1.2.1.2.10.2 Methods4.3.1.2.1.2.10.2.1 btnSearch_ClickMethod name void btnSearch_Click (object sender, EventArgs e)Description Button Search clicked Default arguments of delegate for sender: object event handlerParameters Default arguments of delegate for e: EventArgs event handlerReturn void4.3.1.2.1.2.10.2.2 createMenuMethod name void createMenu ()Description Create menu for SearchingFormParameters voidReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 79Prepared by 6Fingers
  • 80. 4.3.1.2.1.2.11 OverviewForm class4.3.1.2.1.2.11.1 Attributes4.3.1.2.1.2.11.2 Methods4.3.1.2.1.2.11.2.1 FillDataMethod name void FillData ()Description Display data to GUIParameters voidReturn void4.3.1.2.1.2.11.2.2 CreateMenuMethod name void CreateMenu ()Description Create menu for OverviewFormParameters voidReturn void4.3.1.2.1.2.12 CreateMessagesForm class4.3.1.2.1.2.12.1 Attributes4.3.1.2.1.2.12.2 Methods4.3.1.2.1.2.12.2.1 btnOK_ClickMethod name void btnOK_Click (object sender, EventArgs e)Description Button OK Clicked Default arguments of delegate for sender: object event handlerParameters Default arguments of delegate for e: EventArgs event handlerReturn void4.3.1.2.1.2.12.2.2 checkInputDoubleMethod name bool checkInputDouble(string input)Description Check input string is a doubleParameters input: string Input should be checkedReturn True if input is double, fall if not________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 80Prepared by 6Fingers
  • 81. 4.3.1.2.1.2.12.2.3 checkInputMethod name bool checkInput(string input)Description Check inputParameters input:string Input should be checkedReturn True if input has length >04.3.1.2.2 Sequence Diagram4.3.1.2.2.1 Start program Diagram 4-18: Viewer – Start program sequence diagram4.3.1.2.2.2 Update VesselLatestInfo________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 81Prepared by 6Fingers
  • 82. Diagram 4-19: Viewer – Update Vessel Latest Information sequence diagram4.3.1.2.2.3 Display Vessel History Diagram 4-20: Viewer – Display Vessel History sequence diagram4.3.1.2.2.4 S.O.S Messages process________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 82Prepared by 6Fingers
  • 83. Diagram 4-21: Viewer – SOS Messages Process sequence diagram4.3.1.2.2.5 Searching vessel information Diagram 4-22: Viewer – Searching Vessel Information sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 83Prepared by 6Fingers
  • 84. 4.3.1.3 Coastal Station4.3.1.3.1 Class Diagram4.3.1.3.1.1 Diagram Diagram 4-23: Coastal Station – Class Diagram4.3.1.3.1.2 Class Description4.3.1.3.1.2.1 MainController class4.3.1.3.1.2.1.1 AttributesNo Name Type Description1 serverConnectManager ServerConnectManager Connects to database & manages database data altering2 transceiverConnectManager TransceiverConnectManager Connects to transceiver & read/write data into transceiver3 iniConfigManager ConfigIniFileManager Read/write initial configuration settings of application4 mainForm MainForm Application main GUI Form5 updateTimer AutoRunTimer Manages automatically updating message from database________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 84Prepared by 6Fingers
  • 85. No Name Type Description6 broadcastTimer AutoRunTimer Manages automatically broadcasting messages to vessels4.3.1.3.1.2.1.2 Methods4.3.1.3.1.2.1.2.1 AutoBroadcastMessageMethod name void AutoBroadcastMessage() Automatically broadcast messages to vessels. It is called by AutoRunTimerDescription when time interval is reached.Parameters voidReturn void4.3.1.3.1.2.1.2.2 Broadcast MessageMethod name void BroadcastMessage(BroadcastMessage message) Broadcast a message to vessels, actually implementing through:Description - Encode message - Modulate message - Send data to transceiverParameters message: BroadcastMessage Message to be broadcastedReturn void4.3.1.3.1.2.1.2.3 HandleStormMessageMethod name void HandleStormMessage(BroadcastMessage message)Description process storm message: broadcast it immediately and display it into GUIParameters message: BroadcastMessage storm message to be broadcastedReturn void4.3.1.3.1.2.1.2.4 GetBroadcastMessageMethod name BroadcastMessage GetBroadcastMessage()Description Get broadcast message from Database Server.Parameters voidReturn BroadcastMessage, null if there is no messages or error________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 85Prepared by 6Fingers
  • 86. 4.3.1.3.1.2.1.2.5 ReconfigParametersMethod name void ReconfigParameters(object parameter)Description Change parameters due to new valueParameters parameter: object value of parameters to be updatedReturn void4.3.1.3.1.2.1.2.6 ShowMessageHistoryMethod name void ShowMessageHistory()Description Show MessageHistoryForm as a modal formParameters voidReturn void4.3.1.3.1.2.2 MessageHistoryForm class4.3.1.3.1.2.2.1 AttributesThis 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 Methods4.3.1.3.1.2.2.2.1 ShowDialogMethod name DialogResult ShowDialog() Show dialog as a modal dialog form. This method is inherit fromDescription System.Windows.Forms in C#Parameters voidReturn value of type System.Windows.Forms.DialogResult (C#)4.3.1.3.1.2.3 MainForm class4.3.1.3.1.2.3.1 AttributesThis 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.3.2 Methods4.3.1.3.1.2.3.2.1 InformBroadcastMessageMethod name void InformBroadcastMessage(BroadcastMessage message) display message onto GUI and inform this message to have just beenDescription broadcastedParameters message: BroadcastMessage Message to have been broadcasted________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 86Prepared by 6Fingers
  • 87. Return void4.3.1.3.1.2.3.2.2 btnMessageBroadcast_ClickedMethod name void btnMessageBroadcast_Clicked(object sender, EventArgs e) Delegate for event handler when Broadcast message button is clicked. ThisDescription method is generated by Visual Studio 2010 tool Default arguments of delegate for sender: object event handlerParameters Default arguments of delegate for e: EventArgs event handlerReturn Void4.3.1.3.1.2.3.2.3 InformNewBroadcastMessageMethod name void InformNewBroadcastMessage(BroadcastMessage message) Display message onto GUI and inform this message to have just updated fromDescription Database Server message that have been updatedParameters message: BroadcastMessage from Database ServerReturn void4.3.1.3.1.2.3.2.4 btnConfigSetting_ClickedMethod name void btnConfigSetting_Clicked(object sender, EventArgs e) Delegate for event handler when Config Setting button is clicked. This methodDescription is generated by Visual Studio 2010 tool. It call ShowDialog() method of SettingForm. Default argument of delegate for sender: object event handlerParameters Default argument of delegate for e: EventArgs event handlerReturn void4.3.1.3.1.2.3.2.5 btnMessageHistoryShow_ClickedMethod name void btnMessageHitoryShow_Clicked(object sender, EventArgs e)DescriptionParameters sender: object Default argument of delegate for________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 87Prepared by 6Fingers
  • 88. event handler Default argument of delegate for e: EventArgs event handlerReturn void4.3.1.3.1.2.4 SettingForm class4.3.1.3.1.2.4.1 AttributesThis 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.4.2 Methods4.3.1.3.1.2.4.2.1 ShowDialogMethod name void ShowDialog()Description Display SettingForm as a modal formParameters voidReturn void4.3.1.3.1.2.4.2.2 Setting ParameterChangedMethod name void SettingParameterChanged(object parameter) Event handler when user change setting parameters. It changes value ofDescription relative members of FileIniConfigManager.Parameters parameter: object parameter value has changedReturn void4.3.1.3.1.2.5 ConfiglniFileManager class4.3.1.3.1.2.5.1 AttributesNo Name Type Description1 filename string filename to be read/written2 serverIP string server IP address3 serverPort int server listening port4 broadcastTimecodeList object list of time code for automatically broadcasting5 updateTimecodeList object list of time code for automatically updating________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 88Prepared by 6Fingers
  • 89. 4.3.1.3.1.2.5.2 Methods4.3.1.3.1.2.5.2.1 ReadMethod name void Read(string filename)Description It opens .ini file and reads the file and save it into its attributesParameters filename: string file path to be readReturn void4.3.1.3.1.2.5.2.2 WriteMethod name void Write(string filename)Description It opens .ini file and writes attributes’ value into this fileParameters filename: string file path to be writtenReturn void4.3.1.3.1.2.6 ErrorCorrectManager class4.3.1.3.1.2.6.1 AttributesThis class has no attributes.4.3.1.3.1.2.6.2 Methods4.3.1.3.1.2.6.2.1 EncodeMethod name byte[] Encode(byte[] source)Description Encode data before sending, using xxx algorithmParameters source: byte[] data to be encoded in bytesReturn encoded data in bytes4.3.1.3.1.2.6.2.2 DecodeMethod name byte[] Decode(byte[] source)Description Decode data after receiving, using Viterbi decoding algorithmParameters source: byte[] data to be decoded in bytesReturn decoded data in bytes4.3.1.3.1.2.7 AudioModem class4.3.1.3.1.2.7.1 AttributesThis class has no attributes.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 89Prepared by 6Fingers
  • 90. 4.3.1.3.1.2.7.2 Methods4.3.1.3.1.2.7.2.1 ModulateMethod name byte[] Modulate(byte[] source) Embed source data into audio so that it can be transferred using HFDescription communication, using AFSK algorithmParameters source: byte[] data to be modulatedReturn modulated data in bytes4.3.1.3.1.2.7.2.2 DemodulateMethod name byte[] Demodulate (byte[] source)Description Get embedded data in audio stream after receiving it from transceiverParameters source: byte[] data to be demodulatedReturn demodulated data in bytes4.3.1.3.1.2.8 AutoRunTimer class4.3.1.3.1.2.8.1 AttributesNo Name Type Description1 timecodeList object list of time code for processing2 callbackFunction object delegate function for when a call is active by timer3 timer System.Timers.Timer timer for calling callbackFunction when time code is reach4.3.1.3.1.2.8.2 Methods4.3.1.3.1.2.8.2.1 SetupWithTimecodeList void SetupWithTimecodeList(TimecodeList timecodes, ElapsedEventHandlerMethod name callbackFunction) Setup with list of timecode. It saves the list of timecode and starts runningDescription timer list of time code when timer callsParameters timecodes: TimecodeList callback function callbackFunction: callback function called when time ElapsedEventHandler code reachesReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 90Prepared by 6Fingers
  • 91. 4.3.1.3.1.2.8.2.2 ConfigNextIntervalMethod name void ConfigNextInterval() It changes time interval for the next call so that the next call is called at theDescription 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 voidReturn void4.3.1.3.1.2.8.2.3 StopMethod name void Stop()Description Stop timer.Parameters voidReturn void4.3.1.3.1.2.9 TransceiverConnectManager class4.3.1.3.1.2.9.1 AttributesNo Name Type Description1 audioDevice object audio port2 MessageReceiveHandler ITransceiverConnectManager handler for processing when receiving data4.3.1.3.1.2.9.2 Methods4.3.1.3.1.2.9.2.1 ConnectMethod name void Connect()Description It looks for audio input/output ports and opens stream to these devices.Parameters voidReturn void4.3.1.3.1.2.9.2.2 SendMethod name void Send(byte[] data) It checks connections to audio output device and send data to audio stream toDescription transceiverParameters data: byte[] pointer to data to be sent________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 91Prepared by 6Fingers
  • 92. Return void4.3.1.3.1.2.9.2.3 CloseMethod name void Close() It cancels audio streams between audio ports and close connections to theseDescription portsParameters voidReturn void4.3.1.3.1.2.10 ServerConnectManager class4.3.1.3.1.2.10.1 AttributesNo Name Type Description1 serverIP string server IP address2 serverPort int server listening port3 eventHandler IServerConnectManager handler for errors, connection status (disconnected, connected)4.3.1.3.1.2.10.2 Methods4.3.1.3.1.2.10.2.1 ConnectMethod name void Connect(string serverIP, int serverPort)Description It opens connection to Database Server serverIP: string server IP addressParameters serverPort: int server listening portReturn void4.3.1.3.1.2.10.2.2 CommitPositionMessageMethod name void CommitPositionMessage(VesselPosition positionRecord) It checks for connection to Database Server, then inserts a new positionDescription message of a vessel into Maritime databaseParameters positionRecord: VesselPosition record of a vessel’s positionReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 92Prepared by 6Fingers
  • 93. 4.3.1.3.1.2.10.2.3 CommitSOSMessageMethod name void CommitSOSMessage(SOSMessage message) It checks for connection to Database Server, then inserts a new SOSMessageDescription of a vessel into Maritime database message generated and sent fromParameters message: SOSMessage vessel when vessel needs helpReturn void4.3.1.3.1.2.10.2.4 GetBroadcastMessageMethod name List<BroadcastMessage> GetBroadcastMessage(DateTime fromDateTime)Description It gets the broadcast messages which were created after fromDateTimeParameters fromDateTime: DateTime created date time of messageReturn list of BroadcastMessage, null if there is no available messages4.3.1.3.1.2.11 IServerConnectManager interface4.3.1.3.1.2.11.1 AttributesThis interface has no attributes.4.3.1.3.1.2.11.2 Methods4.3.1.3.1.2.11.2.1 HandleErrorMessageMethod name void HandleErrorMessage(string errorDetail) It handles error message when errors is generated from server connection andDescription remotingParameters errorDetail: string error descriptionReturn void4.3.1.3.1.2.11.2.2 ServerDisconnectedMethod name void ServerDisconnected() Handler in case of that the connection changes from connected intoDescription disconnectedParameters voidReturn void4.3.1.3.1.2.11.2.3 ServerConnectedMethod name ServerConnected________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 93Prepared by 6Fingers
  • 94. Handler in case of that the connection changes from disconnected intoDescription connectedParameters voidReturn void4.3.1.3.1.2.12 IMainFormEventHandler interface4.3.1.3.1.2.12.1 AttributesThe interface has no attributes.4.3.1.3.1.2.12.2 Methods4.3.1.3.1.2.12.2.1 GetLatestBroadcastMessageMethod name Broadcastmessage GetLastestBroadcastMessage()Description Get the latest broadcast message from Database ServerParameters voidReturn Broadcastmessage4.3.1.3.1.2.12.2.2 ShowMessageHistoryMethod name void ShowMessageHistory()Description Show the MessageHistoryFormParameters voidReturn void4.3.1.3.1.2.13 ITransceiverConnectManager interface class4.3.1.3.1.2.13.1 Attributes4.3.1.3.1.2.13.2 Methods4.3.1.3.1.2.13.2.1 MessageReceivedMethod name void MessageReceived(byte[] data) Handler for processing data when transceiver receives data through audioDescription input portParameters data: byte[] data in bytes to be processedReturn void4.3.1.3.1.2.13.2.2 HandleErrorMessageMethod name void HandleErrorMessage(string errorDetail)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 94Prepared by 6Fingers
  • 95. Handler in case of error is generated while connecting to audio input/outputDescription ports and reading/sending dataParameters errorDetail: string error contentReturn void4.3.1.3.2 Sequence Diagram4.3.1.3.2.1 Start program Diagram 4-24: Coastal Station – Start program Sequence Diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 95Prepared by 6Fingers
  • 96. 4.3.1.3.2.2 Broadcast messages4.3.1.3.2.2.1 Automatically broadcastingDiagram 4-25: Coastal Station – Automatically broadcast message sequence diagram4.3.1.3.2.2.2 Manually broadcasting Diagram 4-26: Coastal Station – Manually broadcast message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 96Prepared by 6Fingers
  • 97. 4.3.1.3.2.2.3 Broadcast messages Diagram 4-27: Coastal Station – Broadcast message sequence diagram4.3.1.3.2.3 Receive messages (from vessels) Diagram 4-28: Coastal Station – Receive message (from vessel) sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 97Prepared by 6Fingers
  • 98. 4.3.1.3.2.4 Handle Storm messages (received from database server) Diagram 4-29: Coastal Station – Handle storm message sequence diagram4.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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 98Prepared by 6Fingers
  • 99. 4.3.1.3.2.5.2 Manually updating Diagram 4-31: Coastal Station – Manually update message sequence diagram4.3.1.3.2.6 Configure application parametersDiagram 4-32: Coastal Station – Configure application parameters sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 99Prepared by 6Fingers
  • 100. 4.3.1.3.2.7 Show message history Diagram 4-33: Coastal Station – Show message history sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 100Prepared by 6Fingers
  • 101. 4.3.2 On-sea Terminal4.3.2.1 Class Diagram4.3.2.1.1 Diagram Diagram 4-34: On-sea Terminal – Class Diagram4.3.2.1.2 Class description4.3.2.1.2.1 MainProgram class4.3.2.1.2.1.1 AttributesNo Name Type Description1 Draw_State int The current drawing state of the program(map/text information)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 101Prepared by 6Fingers
  • 102. No Name Type Description2 messageQueue ArrayList<String> Store new messages received3 stormMessageQueue Queue<StormMesage> Store last 5 new storm messages4 weatherInfoMessageQ Queue<WeatherInfoMessage> Store last 5 new weather text ueue message5 updatingThread Thread A thread which run continuously, update data of the program.6 messageDisplayer MessageDisplayer Use java graphics API to draw messages content4.3.2.1.2.1.2 Methods4.3.2.1.2.1.2.1 paintComponentMethod name void paintComponent() When the screen of the program reload, this method will be call to paint all theDescription screen, background, messages contentParameters voidReturn void4.3.2.1.2.1.2.2 bindMessageDataMethod name void bindMessageData() Check and process new message received, push it to message queue of theDescription programParameters voidReturn void4.3.2.1.2.1.2.3 drawMapMethod name void drawMap()Description Switch the program draw state to draw map and storm messagesParameters voidReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 102Prepared by 6Fingers
  • 103. 4.3.2.1.2.1.2.4 drawWeatherInfoMethod name void drawWeatherInfo()Description Switch the program draw state to draw weather information text messageParameters voidReturn void4.3.2.1.2.2 MessageDisplayer class4.3.2.1.2.2.1 AttributesNo Name Type Description1 mapBackground Image The map of the Vietnam sea area2 weatherInfoBackground Image The background to draw text message3 mapWidth int The width of the background to draw4 mapHeight int The height of the background to draw4.3.2.1.2.2.2 Methods4.3.2.1.2.2.2.1 getScreenXMethod name int getScreenX(float longitude)Description Convert from geographical longitude to screen dimensionParameters longitude:float Real longitudeReturn The converted x-dimension4.3.2.1.2.2.2.2 getScreenYMethod name int getScreenX(float latitude)Description Convert from geographical latitude to screen dimensionParameters latitude:float Real latitudeReturn The converted y-dimension4.3.2.1.2.2.2.3 drawMapBackground void drawMapBackground(int screenWidth, int screenHeight, GraphicMethod name graphics)Description Draw Vietnam sea mapParameters screenWidth: int Width of the map________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 103Prepared by 6Fingers
  • 104. scrreenHeight:int Height of the map The JPanel Graphics which is use to Graphic:Graphics drawReturn void4.3.2.1.2.2.2.4 drawWeatherInfoBackground void drawWeatherInfoBackground(int screenWidth, int screenHeight, GraphicMethod name graphics)Description Draw background image to draw text message content screenWidth: int Width of the background scrreenHeight:int Height of the backgroundParameters The JPanel Graphics which is used Graphic:Graphics to drawReturn void4.3.2.1.2.2.2.5 drawStormMethod name void drawStorm(StormMessage message, Graphics graphic)Description Visualize storm data to screen message:StormMessage The StormMessage to be drawedParameters The JPanel Graphics which is used Graphic:Graphics to drawReturn void4.3.2.1.2.2.2.6 drawWeatherInfoMethod name void drawWeatherInfo(WeatherInfoMessage message, Graphics graphic)Description Draw text message data to screen The WeatherInfoMessage to be message:WeatherInfoMessage drawedParameters The JPanel Graphics which is used Graphic:Graphics to drawReturn void4.3.2.1.2.2.2.7 drawObjectMethod name void drawObject(Image object, int x, int y, Graphics graphic)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 104Prepared by 6Fingers
  • 105. Description Draw a object to screen Object:Image Object image to be drawed x:int x dimension to be drawedParameters y:int y dimension to be drawed The JPanel Graphics which is used Graphic:Graphics to drawReturn void4.3.2.1.2.3 Updating thread class4.3.2.1.2.3.1 AttributesName Type DescriptionmainProgram MainProgram The mainprogram, which this thread will update data while running4.3.2.1.2.3.2 Methods4.3.2.1.2.3.2.1 runMethod name void run()Description While running, the thread will update data continuouslyParameter voidReturn void4.3.2.1.2.4 Vessel class4.3.2.1.2.4.1 AttributesName Type Descriptionframes Image The Image array, which is used to draw vessel icon as animationcurrentFrame Image The current Image frame of animationcurrent Float Current longitude of the vesselcurrentY Float Current latitude of the vessel4.3.2.1.2.4.2 Methods4.3.2.1.2.4.2.1 updateMethod name void update(float lat, float lon, long timer)________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 105Prepared by 6Fingers
  • 106. Description Update the vessel location and frame of animation lat:float New latitude to be updated lon:float New longitude to be updatedParameter Current time, use to update animation timer:long frameReturn void4.3.2.1.2.5 IComPortListener interface4.3.2.1.2.5.1 AttributesThis interface has no attribute4.3.2.1.2.5.2 Methods4.3.2.1.2.5.2.1 comPortCallbackMethod name void comPortCallback() The callback interface of mainprogram, which is called when new messageDescription receivedParameter data:string New message dataReturn void4.3.2.1.2.6 TranceiverConnection interface4.3.2.1.2.6.1 AttributesThis interface has no attribute4.3.2.1.2.6.2 Methods4.3.2.1.2.6.2.1 connectMethod name void connect()Description Connect to the com port, then listen data continuouslyParameter voidReturn void4.3.2.1.2.6.2.2 modulateToSoundMethod name void modulateToSound(String data)Description Send string data as amateur radio analog signalParameter Data: String Data to be sent________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 106Prepared by 6Fingers
  • 107. Return void4.3.2.1.2.6.2.3 comPortCallbackMethod name void comPortCallback()Description Listen to comport and send push new received data to main programParameter Data: StringReturn void4.3.2.1.2.7 MaritimeMessage class4.3.2.1.2.7.1 AttributesName Type Descriptioncontent String Raw data of the message4.3.2.1.2.7.2 Methods4.3.2.1.2.7.2.1 getMessageTypeMethod name int getMessageType(String message)Description Return the type of the message (storm message/ weatherinfo message)Parameter message: StringReturn 0 if StormMessage, 1 if WeatherInfoMessage4.3.2.1.2.7.2.2 messageRegisteredMethod name boolean messageRegistered(String message)Description Check if the message has already been received and processedParameter message:String Raw data of the messageReturn true if message has already been received, otherwise false4.3.2.1.2.8 StormEye class4.3.2.1.2.8.1 AttributesName Type Descriptiontime String Time forecasted of the storm eyelevel int Level of the storm________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 107Prepared by 6Fingers
  • 108. Name Type DescriptionwindPower int The power/velocity of the storm windlatitude float Latitude of the storm eyeLongitude float Longitude of the storm eyeInfluence1 float The strongest influence areaInfluence2 float The next strong influence areaInfluence3 float The weakest influence area4.3.2.1.2.8.2 MethodsThis class has no method4.3.2.1.2.9 StormMessage class4.3.2.1.2.9.1 AttributesName Type DescriptionstormEyes StormEye[] The 4 forecasted storm eyes4.3.2.1.2.9.2 Methods4.3.2.1.2.9.2.1 processDataMethod name void processData(String message)Description Process data to get information about 4 forecasted storm eyesParameter message:String Raw data of the messageReturn void4.3.2.1.2.10 WeatherInfo class4.3.2.1.2.10.1 AttributesName Type DescriptionweatherInfo weatherInfo The content of the weather information text message4.3.2.1.2.10.2 Methods4.3.2.1.2.10.2.1 processDataMethod name void processData(String message)Description Process data to get content of the message________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 108Prepared by 6Fingers
  • 109. Parameter message:String Raw data of the messageReturn void4.3.2.1.2.11 SOSMessage class4.3.2.1.2.11.1 AttributesThis class has only attribute inherited from super class MaritimeMessage4.3.2.1.2.11.2 Methods4.3.2.1.2.11.2.1 packageDataMethod name void packageData(float lat, float lon, float bearing, float speed)Description Create a SOSMessage to send to the coastal station lat: float Latitude of the vessel lon: float Longitude of the vesselParameter bearing: float Bearing of the vessel speed: float Speed of the vessselReturn void4.3.2.1.2.12 PositionMessage class4.3.2.1.2.12.1 AttributesThis class has only attribute inherited from super class MaritimeMessage4.3.2.1.2.12.2 Methods4.3.2.1.2.12.2.1 packageData void packageData(float lat, float lon, float bearing, float speed)Method nameDescription Create a PositionMessage to send to the coastal station lat: float Latitude of the vessel lon: float Longitude of the vesselParameter bearing: float Bearing of the vessel speed: float Speed of the vessselReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 109Prepared by 6Fingers
  • 110. 4.3.2.1.2.13 InvalidMessageException4.3.2.1.2.13.1 AttributesName Type Descriptionmessage string The exception description4.3.2.1.2.13.2 Methods4.3.2.1.2.13.2.1 getMessageMethod name String getMessage()Description Return the description of the exceptionParameter voidReturn The description of the exception4.3.2.1.2.14 DataCorrection class4.3.2.1.2.14.1 AttributesThis class has no attribute4.3.2.1.2.14.2 Methods4.3.2.1.2.14.2.1 isCorrectMethod name boolean isCorrect(String message)Description Check if a message data has been changed by noise or notParameter message:String Content of the messageReturn True if data is correct, false if it has been changed4.3.2.1.2.14.2.2 correctDataMethod name correctData(String[] messages)Description Get true message data from several error-detected messagesParameter message: String[] Error-detected messages arrayReturn void________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 110Prepared by 6Fingers
  • 111. 4.3.2.2 Sequence Diagram4.3.2.2.1 Start program Diagram 4-35: On-sea Terminal – Start Program sequence diagram4.3.2.2.2 Process received data Diagram 4-36: On-sea Terminal – Received Data Process sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 111Prepared by 6Fingers
  • 112. 4.3.2.2.3 Draw storm Diagram 4-37: On-sea Terminal – Draw Storm sequence diagram4.3.2.2.4 Draw text messageDiagram 4-38: On-sea Terminal – Draw Text Message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 112Prepared by 6Fingers
  • 113. 4.3.2.2.5 Send position message Diagram 4-39: On-sea Terminal – Send Position Message sequence diagram4.3.2.2.6 Send SOS message Diagram 4-40: On-sea Terminal – Send SOS Message sequence diagram________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 113Prepared by 6Fingers
  • 114. 4.4 Database Design4.4.1 Database Diagram Diagram 4-41: Database Diagram4.4.2 Table design description4.4.2.1 OwnerThis table contains static (not frequently changed) information of vessel owners.No Field name Field type Null Key Description Primary key1 OwnerID int No Yes Auto increment2 OwnerName nvarchar(50) Yes Owner’s name Registered id number of each3 IDNumber Varchar(20) No Vietnamese, provided by government.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 114Prepared by 6Fingers
  • 115. 4.4.2.2 VesselThis table contains static information of vessels.No Field name Field type Null Key Description Primary key1 VesselID int No Yes Auto increment Registered id number of each vessel,2 VesselNumber varchar(50) No provided by government. Foreign key3 OwnerID int Yes Vessel owner ID4.4.2.3 Vessel HistoryThis table contains dynamic information of vessel with time log.No Field name Field type Null Key Description Primary key1 VesselHistoryID int No Yes Auto increment Foreign key2 VesselID int No Vessel ID The time when position messages3 CreatedDateTime datetime2(7) No are created (from on-sea terminal) Longitude of vessel (got from GPS)4 Longitude float No when position message is generated Latitude of vessel (got from GPS)5 Latitude float No when position message is generated Speed of vessel at the time position6 Speed smallint Yes message is generated Angle from north-intending vertex7 TrueHeading smallint Yes to velocity vertex of vessel at the time position is generated4.4.2.4 Vessel Latest InformationThis table contains information of the newest positions of vessels. The structure of this table isalmost the same with Vessel History table.No Field name Field type Null Key Description1 VesselID int No Yes Primary key The time when position2 CreatedDateTime datetime2(7) No messages are created (from on- sea terminal) Longitude of vessel (got from3 Longitude float No GPS) when position message is generated Latitude of vessel (got from4 Latitude float No GPS) when position message is generated Speed of vessel at the time5 Speed smallint Yes position message is generated Angle from north-intending6 TrueHeading smallint Yes vertex to velocity vertex of________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 115Prepared by 6Fingers
  • 116. vessel at the time position is generated4.4.2.5 Message TypeThis table contains information of broadcast message type. The kinds of message types are listed inBroadcast Message Structure.No Field name Field type Null Key Description Primary key1 TypeID int No Yes Auto increment2 TypeName nvarchar(50) No Name of message type4.4.2.6 Broadcast MessageThis table contains all broadcast message created and committed to database server by Viewersystem.No Field name Field type Null Key Description Primary key1 MessageID int No Yes Auto increment Foreign key2 TypeID int Yes Message type ID The time when broadcast message3 CreatedDateTime datetime2(7) Yes is created (at Viewer application) Content of message, in defined structures4 Description Nvarchar(500) Yes Reference to Broadcast Message Structure to see kinds of message structure4.4.2.7 SOS MessageThis table contains information of SOS messages from vessels.4.4.3 Broadcast Message StructureThe message structure depends on the message type.4.4.3.1 Storm MessageThe fields will be separated by ‘;’ character in the message (for example “a;b;c”)MessageID MessageType StormNameInteger 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+Time2 StormLevel2 WindPower2 Latitude2 Longitude2 Radius2.1 Radius2.2 Radius2.3“dd/mm-hh” Integer Integer Real number Real number Real number Real number Real number+Time3 StormLevel3 WindPower3 Latitude3 Longitude3 Radius3.1 Radius3.2 Radius3.3“dd/mm-hh” Integer Integer Real number Real number Real number Real number Real number+Time4 StormLevel4 WindPower4 Latitude4 Longitude4 Radius4.1 Radius4.2 Radius4.3“dd/mm-hh” Integer Integer Real number Real number Real number Real number Real numberNo Data Description________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 116Prepared by 6Fingers
  • 117. No Data Description1 MessageID The id of the message broadcasted2 MessageType Type of the message: Storm, SOS, Position, Text-weather message3 Storm name Name of the storm4 Time1-4 Time of the four predicted storm eyes5 StormLevel1-4 Level of the four predicted storm eyes6 WindPower1-4 Power/velocity of the four predicted storm eyes7 Latitude1-4 Latitude of the four predicted storm eyes8 Longitude1-4 Longitude of the four predicted storm eyes9 Radius1.1-4.1 The strongest influence area radius of the four predicted storm eyes10 Radius1.2-4.2 The next strong influence area radius of the four predicted storm eyes11 Radius1.3-4.3 The weakest influence area radius of the four predicted storm eyes4.4.3.2 Weather MessageThe fields will be separated by ‘;’ character in the message ( for example “a;b;c”)MessageID MessageType ContentInteger Integer StringNo Data Description1 MessageID The id of the message broadcasted2 MessageType Type of the message: Storm, SOS, Position, Text-weather message3 Content The weather information broadcasted by the coastal stations4.4.3.3 Position MessageThe fields will be separated by ‘;’ character in the message ( for example “a;b;c”)MessageID MessageType Latitude Longitude Heading Speed________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 117Prepared by 6Fingers
  • 118. Integer Integer Real number Real number Real number Real numberNo Data Description1 MessageID The id of the message broadcasted2 MessageType Type of the message: Storm, SOS, Position, Text-weather message3 Latitude Latitude of the vessel4 Longitude Longitude of the vessel5 Heading Heading of the vessel6 Speed Speed of the vessel4.4.3.4 SOS MessageThe fields will be separated by ‘;’ character in the message ( for example “a;b;c”)MessageID MessageType Latitude Longitude Heading SpeedInteger Integer Real number Real number Real number Real numberNo Data Description1 MessageID The id of the message broadcasted2 MessageType Type of the message: Storm, SOS, Position, Text-weather message3 Latitude Latitude of the vessel4 Longitude Longitude of the vessel5 Heading Heading of the vessel6 Speed Speed of the vessel4.5 Algorithm4.5.1 Error Detection & Correction Algorithm4.5.1.1 IntroductionBroadcasting message via HF band has big challenge of noise and low speed, so we have to face upwith two problems: loss bits and wrong bits. We can use check sum to detect loss bits andconvolutional 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 ViterbiDecoding to new version that it can combine many wrong packets to one correct packet. At theterminal sides the more packet with the same content the more concise percent the final packet we________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 118Prepared by 6Fingers
  • 119. have. Using this extended version we can detect and correct many bits, we have tested onsimulation: base on about 10 wrong packets still find correct one and rarely did we fail on testing. Figure 4-1: Encoding Decoding ModelNo Item Description1 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 detection4.5.1.2 Protocol EncodingAX.25 is a data link layer protocol derived from the X.25 protocol suite and designed foruse by amateur radio operators. It is used extensively on amateur packet radio networks.Flag Address Control PID Info FCS Flag01111110 N * 8 bits 8 bits 8 bits N * 8 bits 16 bits 01111110 Table 4-5: The original frame of AX.25 ProtocolSince we see that many fields on this frame are redundant for our system, and MIV needs to fillraw data (Info field) into some fields like address or PID to maximize the capacity of originalinformation in a packet. We simplify above frame to: Flag 0 Packet ID Info FCS Flag 1 Flag 201111101 16 bits N * 8 bits 16 bits 01111110 01111111 Table 4-6: The customized Protocol for MIV systemBase on the name we can understand that Flag fields are the one that mark the beginning andending of the packet. Info field contains raw data; FCS field is the sum of packet ID and the lengthof info in bytes.4.5.1.3 Convolutional Encoding AlgorithmYou 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 wereceive an input bit, we change the current state to the next state and output a couple of bits basedon two tables below: Current State Input = 0 Input = 1________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 119Prepared by 6Fingers
  • 120. 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 tableFor example, if we have raw data bit string like 01011100101002, after finishing this decodingalgorithm, 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 inputbits 0 to assure that expectation. The truth is that two additional input bit 0 are good enough for thatcriteria; but the length of input bit is divided by 8 and we want the length of output bits has thesame 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 120Prepared by 6Fingers
  • 121. 4.5.1.4 Viterbi Decoding AlgorithmPerhaps the single most important concept to understand the Viterbi algorithm is the trellisdiagram. The figure below shows the trellis diagram for our example for a 13-bit message: Diagram 4-43: Trellis diagram for Viterbi decoding algorithmThe four possible states of the encoder are depicted as four rows of horizontal dots. Thereis one column of four dots for the initial state of the encoder and one for each time instantduring the message. For a 13-bit message with four additional bits, there are 17 timeinstants in addition to t = 0, which represents the initial condition of the encoder. The solidlines 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 outputtable discussed above: Diagram 4-44: Next state diagramRemember that dotted lines represent cases where the encoder input is a zero, and solidlines 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 121Prepared by 6Fingers
  • 122. Each time we receive a pair of channel symbols, were going to compute a metric tomeasure the "distance" between what we received and all of the possible channel symbolpairs we could have received. The distance is computed by simply counting how many bitsare different between the received channel symbol pair and the possible channel symbolpairs. 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 timedimension and j for state dimension). So the formulation for F is: Diagram 4-46: Function F at time t = 5However, because of many wrong packets with the same original content, the probabilitythat we have more than one optimal path is very small and nearly impossible. All abovedescribes 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 manybits from many packet at the same time we can detect and correct many bits, we havetested 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________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 122Prepared by 6Fingers
  • 123. Diagram 4-47: Viterbi decoding algorithm flow chart4.5.2 Software Modem – Sound Modem4.5.2.1 IntroductionA Softmodem, or software modem, is a modem with minimal hardware capacities,designed to use a host computers resources (mostly CPUpower and RAM but sometimeseven audio hardware) to perform most of the tasks performed by dedicated hardware in atraditional modem.In MIV project, the software modem willutilize computer sound card for modulatingand demodulating4.5.2.2 ModulationModulation is the process of encoding digitaldata into analog signal. Func modulate Input byte[] Output short[]Output from modulate function will be usedas raw data for sound card. Sound card willplay the sound represented by that raw data.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 123Prepared by 6Fingers
  • 124. 4.5.2.3 DemodulationDemodulation 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 Testing5.1 Requirements for Test5.1.1 Feature to be tested5.1.1.1 Viewer system5.1.1.1.1 Manage messageFeature name Manage message Allows CO to create a new storm message, weather message, controlDescription command and other message and save in the server database5.1.1.1.2 View all vessels’ positions on mapFeature name View all vessels’ positions on mapDescription Allows CO to view all vessels’ positions on [Map view] screen5.1.1.1.3 View vessel’s voyageFeature name View vessel’s voyageDescription Allows CO to observe a vessel’s voyage on a time interval5.1.1.1.4 View SOS notificationFeature name View SOS notificationDescription Allows CO to view vessels’ SOS symbols on map when had SOS notification5.1.1.1.5 View vessel’s informationFeature name View vessel’s information Allows CO to view the information of a registered vessel, including unique ID,Description current position, direction, etc5.1.1.1.6 View vessel’s informationFeature name View vessel’s information________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 124Prepared by 6Fingers
  • 125. Allows CO to view the information of a registered vessel, including unique ID,Description current position, direction, etc5.1.1.1.7 Performance testFeature name Performance testDescription Map load and display time, each click event time5.1.1.2 CS system5.1.1.2.1 View messages historyFeature name View messages history Allows Operator to view history of messages which are broadcasted andDescription received by this CS: broadcasted message, and received message5.1.1.2.2 View broadcast messageFeature name View broadcast message Allows Operator to view or be alerted whenever the coastal station broadcastsDescription a message to vessels5.1.1.2.3 View receive messageFeature name View receive message Allows Operator to view or be alerted whenever the coastal station receivedDescription SOS messages from vessels5.1.1.2.4 Broadcast a message to all vesselFeature name Broadcast a message to all vesselDescription Allows Operator to send messages to all vessels5.1.1.2.5 Update messageFeature name Update messageDescription Allows CS system to auto update/ or be updated by Operator5.1.1.2.6 CS settingFeature name CS setting Allows Operator to set up CS system as: connection, message historyDescription recording time, broadcast time, message updating time________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 125Prepared by 6Fingers
  • 126. 5.1.1.2.7 Performance testFeature name Performance testDescription Send and receive message time5.1.1.3 On-sea Terminal5.1.1.3.1 View mapFeature name View map Allows fisher to view the maritime map at his position. The map containsDescription Asian maritime map, name of the famous places. The map will be full-screen5.1.1.3.2 View storm notificationFeature name View storm notification Allows fisher to view the storm notification broadcasted by CS. TheDescription notification will be displayed in image. In contains the eyes of the storm, the strongly influenced area and the lightly influenced area5.1.1.3.3 View weather informationFeature name View weather information Allows fisher to view the weather information broadcasted by CS. The information contains temperature, moisture ... and will be displayed in textDescription form. The frame of weather information will be located at right-bottom of the map5.1.1.3.4 View vessel positionFeature name View vessel position Allows fisher to view the position of his vessel. The position will be displayedDescription inside the map, with a vessel icon. The position will be updated continuously5.1.1.3.5 View messages historyFeature name View message historyDescription Allows fisher to view 5 latest messages broadcasted from CS5.1.1.3.6 Send SOS NotificationFeature name Send SOS Notification Allows fisher to send SOS notification in bad situation. He can push a buttonDescription inside the On-sea terminal device, and the notification will be sent to the rescue team________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 126Prepared by 6Fingers
  • 127. 5.1.1.3.7 Performance testFeature name Performance testDescription Send and receive message time5.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 distance5.2 Test strategy5.2.1 Test types5.2.1.1 Function TestingFunction testing of the target-of-test should focus on any requirements for test that can betraced directly to use cases or business functions and business rules. The goals of thesetests are to verify proper data acceptance, processing, and retrieval, and the appropriateimplementation of the business rules. This type of testing is based upon black boxtechnique that is verifying the application and its internal processes by interacting with theapplication via the Graphical User Interface (GUI) and analyzing the output or results.5.2.1.2 User Interface TestingUser Interface (UI) testing verifies a user’s interaction with the software. The goal of UItesting is to ensure that the User Interface provides the user with the appropriate access andnavigation through the functions of the target-of-test. In addition, UI testing ensures thatthe objects within the UI function as expected and conform to fishers, operators or CO.5.2.1.3 Performance testingPerformance profiling is a performance test in which broadcast time, SOS transferringtime, and other time-sensitive requirements are measured and evaluated. The goal ofPerformance Profiling is to verify performance requirements have been achieved.Performance profiling is implemented and executed to profile and tune a target-of-testsperformance behaviors as a function of conditions such as distance or hardwareconfigurations.________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 127Prepared by 6Fingers
  • 128. 5.2.2 Test Environment5.2.2.1 Test Viewer configurationHardware Intel® Core™ 2 Duo CPU T6600 @ 2.20GHz  Windows 7Software  SQL server 2008 Express5.2.2.2 Test CS configurationHardware Intel® Core™ 2 Duo CPU T6600 @ 2.20GHz  Windows 7Software  .NET 4.05.2.2.3 Test vessel configurationHardware Intel® Core™ 2 Duo CPU T6600 @ 2.20GHz  Windows 7Software  Jre 75.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 image5.3 DeliverablesNo Deliverables Delivered Date Delivered by Delivered to1 Test Plan 08 – 02 – 2012 LinhDH MIV team2 System Test case 09 – 02 – 2012 LinhDH MIV team3 Defect Update daily LinhDH MIV team4 Test report 03 – 04 – 2012 LinhDH MIV team________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 128Prepared by 6Fingers
  • 129. 5.4 Checklist5.4.1 Checklist of ValidationQuestion Yes No N/A1. Does a failure of validation on every field cause a sensible user error xmessage?2. Is the user required to fix entries which have failed validation tests? x3. Have any fields got multiple validation rules and if so are all rules being xapplied?4. If the user enters an invalid value and clicks on the OK button (i.e. does notTAB off the field) is the invalid entry identified and highlighted correctly withan error message? x5. Is validation consistently applied at screen level unless specifically requiredat field level? x6. For all numeric fields check whether negative numbers can and should beable to be entered. x7. For all numeric fields check the minimum and maximum values and alsosome mid-range values allowable? x8. For all character/alphanumeric fields check the field to ensure that there is acharacter limit specified and that this limit is exactly correct for the specifieddatabase size? x9. Do all mandatory fields require user input? x10. If any of the database columns dont allow null values then thecorresponding screen fields must be mandatory. (If any field which initially wasmandatory has become optional then check whether null values are allowed inthis field.) x5.4.2 Submission checklistQuestion Yes N/ATABLES AND FIGURESDoes every table column, including the stub column, have a heading? xAre all tables referred to in text? xAre the elements in the figures large enough to remain legible after thefigure has been reduced to the width of a journal column or page? x________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 129Prepared by 6Fingers
  • 130. Is lettering in a figure no smaller than 8 points and no larger than 14points? xAre the figures being submitted in a file format acceptable to thepublisher? xHas the figure been prepared at a resolution sufficient to produce a high-quality image? xAre all figures numbered consecutively with Arabic numerals? xAre all figures and tables mentioned in the text and numbered in the orderin which they are mentioned? xREFERENCESAre references cited both in text and in the reference list? xDo the text citations and reference list entries agree both in spelling andin date? xAre journal titles in the reference list spelled out fully? xAre the references (both in the parenthetical text citations and in thereference list) ordered alphabetically by the authors’ surnames? xAre inclusive page numbers for all articles or chapters in books providedin the reference list? xAre references to studies included in your meta-analysis preceded by anasterisk? xFORMATHave you checked the journal’s website for instructions to authorsregarding specific formatting requirements for submission? xIs the entire manuscript—including quotations, references, author note,content footnotes, and figure captions—double-spaced? Is the manuscriptneatly prepared? xAre the margins at least 1 in. (2.54 cm)? xAre the title pages, abstracts, references, appendices, content footnotes,tables, and figures on separate pages (with only one table or figure perpage)? Are the figure captions on the same page as the figures? Aremanuscript elements ordered in sequence, with the text pages between theabstract and the references? xAre all pages numbered in sequence, starting with the title page? xPARAGRAPHS AND HEADINGS________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 130Prepared by 6Fingers
  • 131. Is each paragraph longer than a single sentence but not longer than onemanuscript page? xDo the levels of headings accurately reflect the organization of the paper? xDo all headings of the same level appear in the same format? x________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 131Prepared by 6Fingers
  • 132. 5.5 Test cases5.5.1 Onsea Terminal Inter-test case ID Test Case Description Test Case Procedure Expected Output Result Test date Dependence View Map [OT-1] Check [Map view] screen is displayed on Look at [MIV] application Default screen is [Map view] pass 9/4/2012 device successfully screen. screen Precondition: - Open application on on-sea terminal device [OT-2] Check Asian maritime map is displayed on Look at [Map view] screen Asian maritime map is displayed pass 9/4/2012 [Map view] screen successfully full screen on [Map view] screen Precondition: successfully - [Map view] screen is displaying on device [OT-3] Check name of famous place is displayed on Look at Asian maritime Name of famous place is displayed pass 9/4/2012 Asia maritime map successfully map on Asian maritime map as: Hà Precondition: Nội, TP. Hồ Chí Minh… - [Map view] screen is displaying on device [OT-4] Check control buttons is displayed on [Map Look at [Map view] screen Control buttons are displayed on pass 9/4/2012 view] screenPrecondition:- [Map view] screen [Map view] screen and include:- is displaying on device 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) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 132Prepared by 6Fingers
  • 133. [OT-5] Check SOS button is displayed on [Map view] Look at [Map view] screen SOS button is displayed at the left- pass 9/4/2012 screen successfully top of [Map view] screen Precondition: (SOS button icon refers to - [Map view] screen is displaying Figure1- On-sea Terminal screen sheet) View weather information [OT-6] Check weather information screen is 1. Click on weather icon 1. [Map view] screen is replaced pass 9/4/2012 displayed on device successfully 2. Look at weather by weather information screen Precondition: information screen 2. Weather Information screen - [Map view] screen is displaying on desktop includes: of on-sea terminal device - Title - DateTime - Control buttons - Content of weather broadcast message … (Weather Information screen refers to Figure 2- On-sea Terminal sheet) [OT-7] Check weather information view icon is Look at weather Weather information view icon is pass 9/4/2012 highlighted on weather information information view icon highlighted screenPrecondition:- Weather information screen is displaying on device [OT-8] Check weather information is displayed on Look at weather - Title is [Bản tin dự báo thời tiết] pass 13/04/2012 [Map view] screen information screen - [dd/mm/yyyy], time[hh:mm] Precondition: - Weather information is displayed - Weather information screen is displaying on includes date temperature, device moisture, ... [OT-9] Check control buttons is displayed on [Map Look at Weather Control buttons are displayed on Pass 9/4/2012 view] screen information screen [Map view] screen and include: Precondition: - Previous message view button is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 133Prepared by 6Fingers
  • 134. - Weather information screen is displaying on displayed as back icon device - 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 Vessels symbol is displayed on [Map 1. Look at [Map view] 1. Vessel is displayed on [Map Pass 13/04/2012 view] screen successfully screen View] screen as an red point Precondition: 2. Look at Vessels position symbol - [Map view] screen is displaying 2. Position of vessel is displayed as [longitude-latitude] text, next to vessel [OT-11] Check auto change vessel icons position on Look at the vessel icon on - Vessels icon moves to the Pass 13/04/2012 [Map view] screen successfullyPrecondition:- map after vessel is moved current place of vessel [Map view] screen is displaying immediately [OT-12] Check auto change latitude and longitude of Look at vessels latitude and - Latitude and longitude are Pass 13/04/2012 vessel after vessel moved on [Map view] longitude on [Map view] changed by vessels current screen successfully screen latitude and longitude Precondition: - [Map view] screen is displaying [OT-13] Check Vessels position is displayed on 1. Look at [Storm 1. Vessel is displayed on [Storm Pass 9/4/2012 [Storm Notification] screen successfully Notification] screen Notification] screen as a red point Precondition: 2. Look at Vessels position symbols - [Storm Notification] screen is displaying on 2. Position text of vessel is desktop of on-sea terminal device displayed as [longitude-latitude] text, next to vessel icon ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 134Prepared by 6Fingers
  • 135. [OT-14] Check auto update vessels position Look at the vessel icon on - Vessels icon moves to the Pass 13/04/2012 successfully map after vessel is moved current place of vessel Precondition: immediately - [Storm Notification] screen is displaying on desktop of on-sea terminal device [OT-15] Check auto change latitude and longitude of Look at vessels latitude and - Latitude and longitude are Pass 13/04/2012 vessel after vessel moved on [Storm longitude on [Storm changed by vessels current Notification] screen Notification] screen latitude and longitude successfullyPrecondition:- [Storm Notification] screen is displaying View message history [OT-16] Check display previous message successfully 1. Once click on back icon 1. Display pre-message of current Pass 16/4/2012 Precondition: 2. Verify displayed weather message successfully - Weather information screen is displaying on information 2. Weather information is device displayed with full information and correct time [OT-17] Check display previous message successfully 1. Double clicks on back 1. Display pre-message of pre- Pass 16/4/2012 Precondition: icon message successfully - Weather information screen is displaying on 2. Verify displayed weather 2. Weather information is device information displayed with full information and correct time [OT-18] Check display previous message successfully 1. 3 clicks on back icon 1. Display pre-message of pre- Pass 16/4/2012 Precondition: 2. Verify displayed weather message of previous message - Weather information screen is displaying on information successfully device 2. Weather information is displayed with full information and correct time [OT-19] Check display last weather message in 1. 4 clicks on back icon 1. Display last weather message in Pass 16/4/2012 message history successfully 2. verify displayed weather history Precondition: 2. Weather information is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 135Prepared by 6Fingers
  • 136. - Weather information screen is displaying on information displayed with full information device and correct time [OT-20] Check display current weather message 1. 4 clicks on next icon2. 1. Displayed weather message is Pass 16/4/2012 successfullyPrecondition:- Last weather verify displayed weather newest received weather message in history is displaying information message2. Weather information is displayed with full information and correct time [OT-21] Check display current weather message 1. 3 clicks on next icon 1. Displayed weather message is Pass 16/4/2012 successfully 2. Verify displayed weather newest received weather message Precondition: information 2. Weather information is - Fourth weather message in history is displayed with full information displaying and correct time [OT-22] Check display current weather message 1. Double clicks on next 1. Displayed weather message is Pass 16/4/2012 successfully icon newest received weather message Precondition: 2. Verify displayed weather 2. Weather information is - Third weather message in history is information displayed with full information displaying and correct time [OT-23] Check display current weather message 1. Once click on next icon 1. Displayed weather message is Pass 16/4/2012 successfully 2. Verify displayed weather newest received weather message Precondition: information 2. Weather information is - Second weather message in history is displayed with full information displaying and correct time [OT-24] Check display previous storm message 1. Once click on back icon 1. Display pre-storm message of Pass 16/4/2012 successfully 2. Verify displayed storm successfully Precondition: notification image 2. Storm notification screen is - [Storm Notification] screen is displaying on displayed with full information device and correct time [OT-25] Check display previous storm message 1. Double clicks on back 1. Display pre-message of pre- Pass 16/4/2012 successfullyPrecondition:- [Storm icon2. Verify displayed message successfully2. Storm Notification] screen is displaying on device storm notification image notification screen is displayed with full information and correct ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 136Prepared by 6Fingers
  • 137. time [OT-26] Check display previous storm message 1. 3 clicks on back icon 1. Display pre-message of pre- Pass 16/4/2012 successfully 2. Verify displayed storm message of previous message Precondition: notification image successfully - [Storm Notification] screen is displaying on 2. Storm notification screen is device displayed with full information and correct time [OT-27] Check display fourth storm message in 1. 4 clicks on back icon 1. Display fourth storm message in Pass 16/4/2012 message history successfully 2. Verify displayed storm history Precondition: notification image 2. Storm notification screen is - [Storm Notification] screen is displaying on displayed with full information device and correct time [OT-28] Check display current [Storm Notification] 1. 4 clicks on next icon 1. Display current [Storm Pass 16/4/2012 screen successfully 2. Verify displayed [Storm Notification] screen successfully Precondition: Notification] screen 2. Current [Storm Notification] - Last storm notification image in history is screen is displayed fully and displaying correctly [OT-29] Check display current [Storm Notification] 1. 3 clicks on next icon 1. Display current [Storm Pass 16/4/2012 screen successfully 2. Verify displayed [Storm Notification] screen successfully Precondition: Notification] screen 2. Current [Storm Notification] - Fourth storm notification image in history is screen is displayed fully and displaying correctly [OT-30] Check display current [Storm Notification] 1. 2 clicks on next icon2. 1. Display current [Storm Pass 16/4/2012 screen successfullyPrecondition:- Third storm Verify displayed [Storm Notification] screen successfully2. notification image in history is displaying Notification] screen Current [Storm Notification] screen is displayed fully and correctly [OT-31] Check display current [Storm Notification] 1. 1 clicks on next icon 1. Display current [Storm Pass 16/4/2012 screen successfully 2. Verify displayed [Storm Notification] screen successfully Precondition: Notification] screen 2. Current [Storm Notification] - Second storm notification image in history is screen is displayed fully and ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 137Prepared by 6Fingers
  • 138. displaying correctly [OT-32] Check display first storm message in message 1. Once click on back icon 1. Display first storm image in Pass 16/4/2012 history successfully 2. Verify displayed storm storm message history Precondition: notification image successfully - [Map view] screen is displaying on device 2. Storm message image is displayed with full information and correct time [OT-33] Check display second storm message in 1. Double clicks on back 1. Display second storm image in Pass 16/4/2012 message history successfully icon storm message history Precondition: 2. Verify displayed storm successfully - [Map view] screen is displaying on device notification image 2. Storm message image is displayed with full information and correct time [OT-34] Check display third storm message in 1. 3 clicks on back icon 1. Display third storm image in Pass 16/4/2012 message history successfully 2. Verify displayed storm storm message history Precondition: notification image successfully - [Map view] screen is displaying on device 2. Storm message image is displayed with full information and correct time [OT-35] Check display fourth storm message in 1. 4 clicks on back icon2. 1. Display fourth storm image in Pass 16/4/2012 message history successfullyPrecondition:- Verify displayed storm storm message history [Map view] screen is displaying on device notification image successfully2. Storm message image is displayed with full information and correct time [OT-36] Check display fifth storm message in message 1. 5 clicks on back icon 1. Display fifth storm image in Pass 16/4/2012 history successfully 2. Verify displayed storm storm message history Precondition: notification image successfully - [Map view] screen is displaying on device 2. Storm message image is displayed with full information and correct time ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 138Prepared by 6Fingers
  • 139. [OT-37] Check display [Map view] screen successfully 1. 5 clicks on next icon 1. Display [Map view] screen Pass 16/4/2012 Precondition: 2. Verify displayed [Map successfully - Fifth storm notification image in history is view] screen 2. [Map view] is displayed displaying correctly [OT-38] Check display [Map view] screen successfully 1. 4 clicks on next icon 1. Display [Map view] screen Pass 16/4/2012 Precondition: 2. Verify displayed [Map successfully - Fourth storm notification image in history is view] screen 2. [Map view] is displayed displaying correctly [OT-39] Check display [Map view] screen successfully 1. 3 clicks on next icon 1. Display [Map view] screen Pass 16/4/2012 Precondition: 2. Verify displayed [Map successfully - Third storm notification image in history is view] screen 2. [Map view] is displayed displaying correctly [OT-40] Check display [Map view] screen 1. Double clicks on next 1. Display [Map view] screen Pass 16/4/2012 successfullyPrecondition:- Second storm icon2. Verify displayed successfully2. [Map view] is notification image in history is displaying [Map view] screen displayed correctly [OT-41] Check display [Map view] screen successfully 1. One click on next icon 1. Display [Map view] screen Pass 16/4/2012 Precondition: 2. Verify displayed [Map successfully - First storm notification image in history is view] screen 2. [Map view] is displayed displaying correctly View Storm Notification [OT-44] Check storm notification box is displayed 1. Look at the [Map view] 1. Display storm notification box, Pass 9/4/2012 successfully screen text is [Bạn có 1 tin báo bão mới], Precondition: 2. Click on [OK] button [Ok] button - CS sends storm message to vessel 2. Storm notification box is closed [OT-45] Check storm notification screen is display on Look at the [Map view] - [Storm Notification] screen is broadcasting storm pass 9/4/2012 device successfully screen auto displayed on device sms from CS Precondition: - [Storm Notification] screen - CS broadcasts storm message to vessel includes storm information and ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 139Prepared by 6Fingers
  • 140. - [Map view] screen is displaying on device storm image [OT-46] Check storm information is displayed on 1. Look at [Map view] 1. Storm Information field is pass 9/4/2012 [Storm Notification View] screen2. Verify Storm displayed at the right-bottom of screenPrecondition:- [Storm Notification Information field [Map view] screen2. Storm View] screen is displaying on device 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) [OT-47] Check storm information is visualized on 1. Look at Storm Image 1. Storm Information is visualized pass 9/4/2012 [Storm Notification View] screen successfully on map as storm image and Precondition: includes: - [Storm Notification View] screen is - The main storm orbit is displaying on device 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) [OT-48] Check comments of storm image is displayed 1. Look at comments box 1. Comments is displayed at the pass 9/4/2012 successfully right of storm information field Precondition: and include: - [Storm Notification view] screen is - Explaination of storm image displaying on device (Comments box refers to Fingure 2- On-sea Terminal Screen) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 140Prepared by 6Fingers
  • 141. [OT-49] Check storm information hide button is Look at Storm information Hide button is displayed as a red pass 9/4/2012 displayed on storm information field field triangular at the right-bottom of successfullyPrecondition:- Storm information storm information field field is displaying on [Storm Notification view] screen [OT-50] Check hide storm information field Click on coner of storm Storm information field is hidden pass 9/4/2012 successfully information field Precondition: - [Storm Notification view] screen is displaying on device Broadcast SOS Message [OT-51] Check confirm message box is displayed 1. Click SOS button on 1. Display confirm message box Pass 9/4/2012 successfully [Map view] screen - Text is [Bạn có muốn gửi tin cầu Precondition: cứu] - [Map view] screen is displaying - [Chắc chắn] button - [Không] button [OT-52] Check vessel broadcasts SOS message to 1. Click on SOS button on 1. Display confirm message box Pass 9/4/2012 coastal station successfully [Map view] screen 2. Display notification message Precondition: 2. Click on [Chắc chắn] box [Đang gửi tín hiệu SOS], - [Map view] screen is displaying button [OK] button 3. Click on [OK] button 3. Notification message box is closed [OT-53] Check when click [không] button in confirm 1. Click on SOS button on 1. Display confirm message box Pass 9/4/2012 message box [Map view] screen 2. Close confirm message box Precondition: 2. Click on [không] button - [Map view] screen is displaying [OT-54] Check confirm message box is displayed 1. Click SOS button on 1. Display confirm message box - Pass 9/4/2012 successfullyPrecondition:- [Weather [Map view] screen Text is [Bạn có muốn gửi tin cầu information] screen is displaying cứu] - [Chắc chắn] button- ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 141Prepared by 6Fingers
  • 142. [Không] button [OT-55] Check vessel broadcasts SOS message to 1. Click on SOS button on 1. Display confirm message box Pass 9/4/2012 coastal station successfully [Map view] screen 2. Display notification message Precondition: 2. Click on [Chắc chắn] box [Đang gửi tín hiệu SOS], - [Weather information] screen is displaying button [OK] button 3. Click on [OK] button 3. Notification message box is closed [OT-56] Check when click [không] button in confirm 1. Click on SOS button on 1. Display confirm message box Pass 9/4/2012 message box [Map view] screen 2. Close confirm message box Precondition: 2. Click on [không] button - [Weather information] screen is displaying5.5.2 Coastal Station system Inter-test case ID Test Case Description Test Case Procedure Expected Output Result Test date Dependence GUI-View Message [CSS-1] Check GUI of [Message Look at this screen [Message View] screen is displayed in Pass 5/4/2012 View] screen read mode and includes: Precondition: - Title - [Message View] screen is -… displaying on Coastal Station (GUI refers to "Figure 2 - Coastal Screen Station Screen" sheet) [CSS-2] Check title window is Look at this screen Title of window is [Trạm thu phát ven Pass 5/4/2012 displayed successfully biển], text is black. Precondition: - [Message View] screen is displaying on Coastal Station Screen ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 142Prepared by 6Fingers
  • 143. [CSS-4] Check title message is Look at this screen - Title message is displayed under of Pass 5/4/2012 displayed on [Message View] title screen screen - Text is [Nội dung bản tin], black and Precondition: bold - [Message View] screen is displaying on Coastal Station Screen [CSS-5] Check notification of SOS Look at this screen - Notification of SOS message is Pass 5/4/2012 message is displayed on displayed on same line with title [Message View] screen message, right of line Precondition: - Text is [[n] bản tin SOS từ tàu] [Message View] screen is - Text is bold, and under line displaying on Coastal Station Screen [CSS-6] Check message content Look at this screen Message content textbox is displayed Pass 5/4/2012 textbox is displayed on under message title and include: [Message View] screen - Time Precondition: - Type [Message View] screen is - Content displaying on Coastal Station (Message content textbox refers to Screen "Figure 2 - Coastal Station Screen" sheet) [CSS-7] Check [Cài đặt] button is Look at this screen - Setting button is displayed at the left Pass 5/4/2012 displayed on [Message bottom of screen View] screen - Text is [Cài đặt]. Text is black Precondition: [Message View] screen is displaying on Coastal Station Screen [CSS-8] Check [Cập nhập bản tin] Look at this screen - Update button is displayed at the left of Pass 5/4/2012 button is displayed on broadcast button [Message View] screen - Text is [Cập nhập bản tin]. Text is Precondition: ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 143Prepared by 6Fingers
  • 144. [Message View] screen is black displaying on Coastal Station Screen [CSS-9] Check [Phát tin] button is Look at this screen - Broadcast button is displayed at the Pass 5/4/2012 displayed on [Message right bottom of screen View] screen - Text is [Phát bản tin]. Text is black Precondition: [Message View] screen is displaying on Coastal Station Screen [CSS-10] Check [Lịch sử bản tin] Look at this screen - Messages history view button is Pass 5/4/2012 button is displayed on displayed at above of setting button [Message View] screen - Text is [Lịch sử bản tin]. Text is black Precondition: [Message View] screen is displaying on Coastal Station Screen [CSS-11] Check GUI of setting screen 1. Click [Cài đặt] button 1. Setting screen is displayed over Pass 5/4/2012 Precondition: 2. Look at setting screen [Message View] screen - Setting screen is displaying 2. Setting screen includes: - Title is "cài đặt" -… (Setting screen refers to Fingure 3- Coastal Station Sheet) View Message [Setting] [CSS-12] Check [Cài đặt] screen is Click [Cài đặt] button Display [Cài đặt] screen Pass 5/4/2012 displayed on coastal station Precondition: - [Message view] screen is displaying on coastal station ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 144Prepared by 6Fingers
  • 145. [CSS-13] Check title of [Cài đặt] screen Look at [Cài đặt] screen Title of screen is [Cài đặt], text is black. Pass 5/4/2012 is displayed successfully Precondition: - [Cài đặt] screen is displaying on coastal station [CSS-14] Check connection setting Look at [Cài đặt] screen - Connection setting is displayed at left Pass 5/4/2012 field is displayed successfully top of [Cài đặt] screen and includes: Precondition: + Title field is [Cài đặt kết nối] - [Cài đặt] screen is + [Địa chỉ server] label and textbox displaying on coastal station + [Cổng] label and textbox [CSS-15] Check connection setting of 1. Fill in server address textbox 1. Filled text is displayed in server Pass 5/4/2012 view message ( Full fill 2. Fill in portal textbox address textbox information) 3. Click enter 2. Filled text is displayed in portal Precondition: textbox - [Cài đặt] screen is 3. Server address and portal is saved displaying on coastal station successfully [CSS-16] Check connection setting of 1. Fill in server address textbox 1. Filled text is displayed in server Pass 5/4/2012 view message(Portal is blank) 2. Click enter address textbox Precondition: 2. Cant save and display a notification - [Cài đặt] screen is displaying on coastal station [CSS-17] Check connection setting of 1. Fill in portal textbox 1. Filled text is displayed in server Pass 5/4/2012 view message(Server address 2. Click enter address textbox is blank) 2. Cant save and display a notification Precondition: - [Cài đặt] screen is displaying on coastal station [CSS-18] Check connection setting of Click enter Cant save and display a notification Pass 5/4/2012 view message(all is blank) Precondition: - [Cài đặt] screen is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 145Prepared by 6Fingers
  • 146. displaying on coastal station [CSS-19] Check message recording Look at [Cài đặt] screen - [Lưu trữ bản tin] field is displayed at Pass 5/4/2012 setting field is displayed on right-top of [Cài đặt] screen and [Cài đặt] screen includes: Precondition: + radio button and value labels, values - [Cài đặt] screen is are [trong ngày, trong 1 tuần, trong 2 displaying on coastal station tuần, trong 1 tháng] [CSS-20] Check set message recording 1. Choose [trong ngày] value of 1. Display checked radio button View message history Pass 5/4/2012 of view message successfully radio button values 2. Chose value is saved successfully Precondition: 2. Click enter 3. All messages in message historys - [Cài đặt] screen is 3. Check message history time is the set datetime displaying on coastal station [CSS-21] Check set message recording 1. Choose [trong 1 tuần] value of 1. Display checked radio button Pass 5/4/2012 of view message successfully radio button values 2. Chose value is saved successfully Precondition: 2. Click enter 3. All messages in message historys - [Cài đặt] screen is 3. Check message history time is the set datetime displaying on coastal station [CSS-22] Check set message recording 1. Choose [trong 2 tuần] value of 1. Display checked radio button Pass 5/4/2012 of view message successfully radio button values 2. Chose value is saved successfully Precondition: 2. Click enter 3. All messages in message historys - [Cài đặt] screen is 3. Check message history time is the set datetime displaying on coastal station [CSS-23] Check set message recording 1. Choose [trong 1 tháng] value of 1. Display checked radio button Pass 5/4/2012 of view message successfully radio button values 2. Chose value is saved successfully Precondition: 2. Click enter 3. All messages in message historys - [Cài đặt] screen is 3. Check message history time is the set datetime displaying on coastal station [CSS-24] Check [Thời gian phát] field Look at [Cài đặt] screen - [Thời gian phát] field is display at left- Pass 5/4/2012 is displayed on [Cài đặt] bottom of [Cài đặt] screen and includes: screen successfully + Time item box Precondition: + [Thêm] button ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 146Prepared by 6Fingers
  • 147. - [Cài đặt] screen is + [Xóa] button displaying on coastal station [CSS-25] Check message broadcast 1. Click [Thêm] button 1. Display time input line in time item [Phát tin] function Pass 5/4/2012 time setting of view 2. Fill time as hh:mm:ss box message(add a broadcast 3. Click enter 2. Display input time time) 3. New time is saved Precondition: - [Cài đặt] screen is displaying on coastal station [CSS-26] Check message broadcast 1. Click [Thêm] button 1. Display time input line in time item Pass 5/4/2012 time setting of view 2. Fill time with free style box message(add a broadcast 3. Click enter 2. Display input time time) 3. Cant save new time and display Precondition: notification - [Cài đặt] screen is displaying on coastal station [CSS-27] Check message broadcast 1. Choose a time in box 1. Chose time is highlight [Phát tin] function Pass 5/4/2012 time setting of view 2. Click [Xóa] button 2. Chose time is deleted message(delete a broadcast time) Precondition: - [Cài đặt] screen is displaying on coastal station [CSS-28] Check delete all time item in Delete all message broadcast time Cant delete all time item in time item Pass 5/4/2012 message broadcast time setting item box and display [Bạn không thể xóa. setting item box Phải có ít nhất một giờ trong danh sách Precondition: này.] notification box - [Cài đặt] screen is displaying on coastal station [CSS-29] Check [Thời gian cập nhập Look at [Cài đặt] screen - [Thời gian cập nhập bản tin] field is Pass 5/4/2012 bản tin] field is displayed on display at right-bottom of [Cài đặt] [Cài đặt] screen successfully screen and includes: ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 147Prepared by 6Fingers
  • 148. Precondition: + Time item box - [Cài đặt] screen is + [Thêm] button displaying on coastal station + [Xóa] button [CSS-30] Check message auto update 1. Click [Thêm] button 1. Display time input line in time item Pass 5/4/2012 time setting of view 2. Fill time as hh:mm:ss box message(add an auto update 3. Click enter 2. Display input time time) 3. Save new time successfully Precondition: - Setting screen is displaying [CSS-31] Check message auto update 1. Click [Thêm] button 1. Display time input line in time item [Cập nhập bản tin] Pass 5/4/2012 time setting of view 2. Fill time with free style box function message(add an auto update 3. Click enter 2. Display input time time) 3. Cant save new time and display Precondition: notification - Setting screen is displaying [CSS-32] Check message auto update 1. Choose a time in box 1. Chose time is highlight [Cập nhập bản tin] Pass 5/4/2012 time setting of view 2. Click [Xóa] button 2. Chose time is deleted function message(delete an auto update time) Precondition: - Setting screen is displaying [CSS-33] Check delete all time item in Delete all time item Cant delete all time item in time item Pass 5/4/2012 time item box box and display [Bạn không thể xóa. Precondition: Phải có ít nhất một giờ trong danh sách - [Cài đặt] screen is này.] notification box displaying on coastal station View message [Update] [CSS-34] Check message auto update Look at message textbox when Messsage content in textbox is replaced Pass 12/4/2012 successfully(there is a new time is the set time by new one at this time message) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 148Prepared by 6Fingers
  • 149. Precondition: - Set update time - [View message] screen is displaying [CSS-35] Check message auto update Look at message textbox when Messsage content in textbox is replaced Pass 12/4/2012 successfully(there are more time is the set time by newest one at this time than 1 new message) Precondition: - Set update time - [View message] screen is displaying [CSS-36] Check message auto update Look at message textbox when Information in textbox doesnt changed Pass 12/4/2012 successfully(there is not new time is the setting time message) Precondition: - Set update time - [View message] screen is displaying [CSS-37] Check message update when Click on [Cập nhập bản tin] Messsage content in textbox is replaced Pass 12/4/2012 [Cập nhập bản tin] button is button by new one at this time clicked successfully (There is a new message) Precondition: - [View message] screen is displaying [CSS-38] Check message update when Click on [Cập nhập bản tin] Messsage content in textbox is replaced Pass 13/4/2012 [Cập nhập bản tin] button is button by newest one at this time clicked successfully (There are more than 1 new message) Precondition: - [View message] screen is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 149Prepared by 6Fingers
  • 150. displaying [CSS-39] Check message update when Click on [Cập nhập bản tin] Information in textbox doesnt change Pass 13/4/2012 [Cập nhập bản tin] button is button clicked successfully(There isnt new message) Precondition: - [View message] screen is displaying View Message History [CSS-40] Check [Message history] 1. Click on [Lịch sử bản tin] [Message history] screen is displayed in Pass 10/4/2012 window is displayed button read mode and includes: successfully - Title label Precondition: - Number of recorded message - [Map view] window is - Message history table displaying in Coastal Station (GUI refers to "Figure 1 - Coastal Station Screen" sheet) [CSS-41] Check title of [Lịch sử bản Look at [Lịch sử bản tin] window Window title is [Lịch sử bản tin], text is Pass 10/4/2012 tin] window is displayed black successfully Precondition: - [Lịch sử bản tin] is displaying [CSS-43] Check [số các bản tin được 1. Look at [số các bản tin được 1. [Số các bản tin được lưu trữ] field is Pass 10/4/2012 lưu trữ] is displayed lưu trữ] field displayed at the left-top of [Message successfully 2. Click on number at [số các bản history] window Precondition: tin được lưu trữ] label - Text of amount of message is [Số các - [Message history] screen is bản tin được lưu trữ:], text is black displaying on Coastal Station - Number which is displayed [Số các bản Screen tin được lưu trữ:] field is same with amount of message list in table ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 150Prepared by 6Fingers
  • 151. 2. Cant edit the number [CSS-44] Check message history table Look at message history table - Message history table is displayed in Pass 10/4/2012 Precondition: read mode and includes columns: - [Message history] screen is + STT (số thứ tự) displaying on Coastal Station + Loại Screen + Ngày tạo + Nội dung - Text in table is black Table refers to "Figure 1 - Coastal Station Screen sheet" [CSS45] Check view message history Look at message history table all of received messages in this day is message recording Pass 10/4/2012 in one day is displayed displayed in message history table function successfully Precondition: - Set message record time of view message is [trong ngày] - [Message history] is displaying [CSS-46] Check view message history Click on [Lịch sử bản tin] button all of received messages in one week is Pass 10/4/2012 of one week is displayed displayed in message history table successfully Precondition: - Set message record time of view message is [trong 1 tuần] - [Message history] is displaying [CSS-47] Check view message history Click on [Lịch sử bản tin] button all of received messages in two weeks is Pass 10/4/2012 of two weeks is displayed displayed in message history table successfully Precondition: - Set message record time of view message is [trong 2 ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 151Prepared by 6Fingers
  • 152. tuần] - [Message history] is displaying [CSS-48] Check view message history Look at message history screen all of receive messages in one month is Pass 10/4/2012 of one month is displayed displayed in message history table successfully Precondition: - Set message record time of view message is [trong 1 tháng] - [Message history] is displaying [CSS-49] Check information of a 1. Look at message history table 1. Message history table is displayed on Pass 10/4/2012 message is displayed in read mode and include: message table successfully - [Số thứ tự] is auto increase Precondition: - [Loại tin] is storm message/ weather - [Message history] screen is broadcast message displaying - [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 [CSS-50] Check view a message in 1. Click on a message in message 1. Message information is displayed Pass 10/4/2012 history successfully history table under message history table Precondition: 2. Verify messages information 2. Title is [Nội dung tin nhắn], Message - [Message history]screen is time & information is displayed displaying correctly [CSS-51] Check out of view message Click close icon on [Message Close [Message history] and return to Pass 10/4/2012 history is successfully history] screen [Map view] screen Precondition: - [Message history] screen is displaying ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 152Prepared by 6Fingers
  • 153. Broadcast message [CSS-52] Check coastal station Look at [View message] screen at - Current message is broadcasted to Vessel receives Pass 10/4/2012 broadcasts weather message set time vessel message to vessel successfully(auto) - Display sound and notification [Đã gửi Precondition: bản tin] - [View message] window is displaying [CSS-53] Check coastal station Click [Phát tin] button - Current message is broadcasted to Vessel receives Pass 10/4/2012 broadcasts weather message vessel message to vessel successfully(click - Display sound and notification [Đã gửi button) bản tin] Precondition: - [View message] screen is displaying [CSS-54] Check coastal station Click [Phát tin] button - Current message is broadcasted to Pass 10/4/2012 broadcasts weather message vessel twice to vessel when click [Phát - Display sound and notification [Đã gửi bản tin] button at set auto bản tin] time Precondition: - [View message] screen is displaying [CSS-55] Check coastal station Look at [View message] screen at - Current message is broadcasted to Pass 10/4/2012 broadcasts storm message to set time vessel vessel successfully(auto) - Display sound and notification [Đã gửi Precondition: bản tin] - [View message] window is displaying [CSS-56] Check coastal station Click [Phát tin] button - Current message is broadcasted to Pass 10/4/2012 broadcasts storm message to vessel vessel successfully(click - Display sound and notification [Đã gửi ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 153Prepared by 6Fingers
  • 154. button) bản tin] Precondition: - [View message] screen is displaying [CSS-57] Check coastal station Click [Phát tin] button - Current message is broadcasted to Pass 10/4/2012 broadcasts storm message to vessel twice vessel when click [Phát bản - Display sound and notification [Đã gửi tin] button at set auto time bản tin] Precondition: - [View message] screen is displaying [CSS-58] Check CS broadcasts SOS Look at [View message] screen - Display notification [Đã gửi bản tin] Vessel receives Pass 13/4/2012 message to Viewer message successfully Precondition: - Increase number of SOS notification Receive message [CSS-59] Check coastal station system Look at SOS message notification Number of SOS message notification [OT-51] Pass 13/4/2012 receives a SOS message from field increases by one a vessel successfully Precondition: - [View message] screen is displaying [CSS-60] Check coastal station system Look at SOS message notification Number of SOS message notification [OT-51] Pass 13/04/2012 receives 2 SOS messages field increases by two from a vessel at the different time Precondition: - [View message] screen is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 154Prepared by 6Fingers
  • 155. displaying [CSS-61] Check coastal station system Look at SOS message notification Number of SOS message notification [OT-51] Pass 11/4/2012 receives 2 SOS messages field increases by two from two vessel at the same time Precondition: - [View message] screen is displaying [CSS-62] Check coastal station system Look at SOS message notification Number of SOS message notification [OT-51] Pass 11/4/2012 receives 2 SOS messages field increases by four from two vessel at the different time Precondition: - [View message] screen is displaying5.5.3 Viewer Inter-test case ID Test Case Description Test Case Procedure Expected Output Result Test date Dependence GUI-Maritime Information Visualization [Viewer-1] Check title of Viewer Look at title of this window Title is [Maritime Information Pass 2/4/2012 window Visualization], text is black Precondition: - Viewer window is displaying [Viewer-2] Check default screen is Look at Viewer widow - Default screen is [Bản đồ tổng quan] Pass 2/4/2012 displayed on Viewer window - The visible region of map is Vietnam ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 155Prepared by 6Fingers
  • 156. successfully land, Vietnam sea, Philippine sea and Precondition: China sea. - Viewer window is - Display fullscreen displaying [Viewer-3] Check tabs is displayed on Look at Viewer widow Default tabs on Viewer window are [Bản Pass 2/4/2012 viewer window successfully đồ tổng quan] tab and [Tạo tin] tab, and Precondition: displayed on tab field - Viewer window is displaying [Viewer-4] Check docking bar is Look at Viewer widow Docking bars are [Tổng quan] and [Tìm Pass 2/4/2012 displayed on Viewer window kiếm], at right of window successfully Pprecondition: - Viewer window is displaying View all vessels position on map [Viewer-5] Check map is displayed on Look at [Bản đồ tổng quan] screen The background map contains Vietnam Pass 4/4/2012 [Bản đồ tổng quan] screen land, Vietnam sea, Philippine sea and successfully China sea. Precondition: - [Bản đồ tổng quan] screen is displaying [Viewer-6] Check vessels position is Look at [Bản đồ tổng quan] screen At current time, all registered is displayed Pass 4/4/2012 displayed on map on background screen successfully Precondition: - [Bản đồ tổng quan] screen is displaying ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 156Prepared by 6Fingers
  • 157. [Viewer-7] Check background map is Look at [Bản đồ tổng quan] screen Display only background map Pass 4/4/2012 displayed in case of no vessel Precondition: - [Bản đồ tổng quan] screen is displaying [Viewer-8] Check automactically update Look at the vessel symbol on the map The vessel symbol position is changed on Pass 4/4/2012 a vessel position onto the map the map (2 minutes) Precondition: - A vessel symbol is displaying onto the map [Viewer-9] Check automactically update Look at the vessel symbols on the map The vessel symbols position is changed on Pass 11/4/2012 two vessel positions onto the the map map (2 minutes) Precondition: - Two vessel symbols are displaying on the map [Viewer- Check automactically update Look at the vessel symbols on the map The vessel symbols position is changed on Untested 11/4/2012 10] 10 vessel positions onto the the map map (2 minutes) Precondition: - Ten vessels symbols are displaying on the map Check view a vessels information [Viewer- Check view a vessels 1. Click once on a vessel symbol 1. Display vessels information box Pass 8/4/2012 11] information successfully 2. Verify displayed information 2. Information is displayed includes: Precondition: - [Biển kiểm soát] is vessels license plate - At least a vessel symbol is - [Mã số] is vessels unique ID (link to displaying on the map vessels history) - [Chủ tàu] is vessel owner name - [Kinh độ] is vessel current positions ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 157Prepared by 6Fingers
  • 158. longitude - [Vĩ độ] is vessel current positions latitude - [Tốc độ] is vessels velocity (nautical/hour) - [Hướng] is vessels direction - [Cập nhập lúc] is vessel information update time(dd/mm/yyyy hh:mm:ss UTC+7) [Viewer- Check close vessel Click on close at the right top of vessel Vessel information box is closed Pass 8/4/2012 12] information box successfully information box successfully Precondition: - Vessel information box is displaying Check a vessels voyage [Viewer- Check vessels voyage table is Click on link at the unique ID in vessel Open vessel history in new tab Pass 8/4/2012 13] displayed successfully information box Precondition: - Open vessel information pop up context [Viewer- Check title of the vessel Look at the tab title Title is vessel license plate, text is black Pass 8/4/2012 14] history tab Precondition: - Vessel history tab is displaying [Viewer- Check vessel history screen is Look at screen and verify data Vessel history screen is displayed on Pass 8/4/2012 15] displayed successfully readmod and includes: Precondition: - Title is [Lịch sử tàu + vessel license - Vessel history tab is plate] displaying - [Kết quả] is number of history records - Choose time from drop-down list to ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 158Prepared by 6Fingers
  • 159. 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- Check view vessel history in 1. Choose vessel history display time (1 hour) 1. Chose time is displayed on drop-down Pass 8/4/2012 16] 1 hour successfully(table) 2. Click on [Tải dữ liệu button] list Precondition: 3. Verify displayed vessel history 2. Display all record had chose time, and - Vessel history tab is display number displayed record on [Kết displaying quả] field 3. Time and information of records is correctly [Viewer- Check view vessels voyage 1. Click on [Hiển thị trên bản đồ] button 1. Display new tab is [Lịch sử tàu + Pass 8/4/2012 17] in one month 2. Look at new displayed tab license plate] tab successfully(image) 2. The vessels voyage in one hour is Precondition: displayed and includes: - Vessel history in one hour is - Number symbols is number of vessel displaying history record - Start and end symbol is bigger - All symbols is connected by a red line (Vessels voyage refers to Figure 3/ Viewer Screen) [Viewer- Check all vessel history is 1. Display all vessel history record 1. Chose time is displayed on drop-down Pass 8/4/2012 18] displayed successfully(table) 2. Click on [Tải dữ liệu button] list Precondition: 3. Verify displayed vessel history 2. Display all vessel history record, and - Vessel history tab is display number displayed record on [Kết displaying quả] field 3. Time and information of records is correctly ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 159Prepared by 6Fingers
  • 160. [Viewer- Check close vessel Click on close at the right top corner of this Vessel history screen is closed Pass 8/4/2012 19] information box successfully screen successfully Precondition: - Vessel information box is displaying [Viewer- Check all vessels voyage is 1. Click on [Hiển thị trên bản đồ] button 1. Display new tab is [Lịch sử tàu [license Pass 8/4/2012 20] displayed successfully(image) 2. Look at new displayed tab plate]] tab Precondition: 2. The vessels voyage is displayed and - All vessel history is includes: displaying - Number symbols is number of vessel history record - Start and end symbol is bigger - All symbols is connected by a red line (Vessels voyage refers to Figure 3/ Viewer Screen) [Viewer- Check vessels voyage screen Click on close at the right top corner of this Vessels voyage is closed successfully Pass 8/4/2012 21] is closed successfully screen Precondition: - Vessels voyage screen is displaying Create a message [Viewer- Check open [Tạo tin] tab Click on [Tạo tin] tab Default screen of this tab is storm Pass 8/4/2012 22] successfully broadcast message creating screen and Precondition: includes: - Viewer window is - [Loại bản tin] label displaying - Message types drop-down list - Message content creating box [Viewer- Check storm broadcasting 1. Click on message types drop down list 1. Display message types list includes: Pass 8/4/2012 23] message creating screen is 2. Choose [Bản tin báo bão] [Bản tin báo bão] [Bản tin thời tiết] [Câu displayed successfully 3. Verify [Bản tin báo bão] input fields lệnh điều khiển] and [Bản tin khác] Precondition: 2. Display fields to input content of storm ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 160Prepared by 6Fingers
  • 161. - [Tạo tin] tab is displaying broadcast message 3. Fields refers to Figure5- Viewer screen sheet [Viewer- Check input storm broadcast 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 24] message content successfully 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox Precondition: - Choose datetime on datetime field 3. Inputted text is displayed on textbox - Storm broadcast message (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox creating screen/default screen - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox of [Tạo tin] tab is displaying influence area 1, influence area 2, influence area 3 (inputted data must be interger) 3. [Vị trí tâm bão 2] 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) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button [Viewer- Check save storm message to 1. Click on [Đồng ý] button 1. Display confirm message box Pass 8/4/2012 25] database succefully 2. Choose [Đồng ý] button in confirm message 2. Display notification box(successful/ Precondition: box unsuccessfull) - Previous testcase is finished ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 161Prepared by 6Fingers
  • 162. [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 26] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Cấp bão] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Cấp bão] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Vĩ độ của vị (dd/mm/yyyy hh:mm:ss) trí tâm bão 1 phải là số thực] - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 27] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Tốc độ gió] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này in [Tốc độ gió] textbox) lên cơ sở dữ liệu không?], [Yes] button, ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 162Prepared by 6Fingers
  • 163. of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Tốc độ gió (dd/mm/yyyy hh:mm:ss) của vị trí tâm bão 1 phải là số thực] - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 28] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Vĩ độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Vĩ độ] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Vĩ độ của vị (dd/mm/yyyy hh:mm:ss) trí tâm bão 1 phải là số thực] - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] fields: - Choose datetime on datetime field ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 163Prepared by 6Fingers
  • 164. (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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 29] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Kinh độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Kinh độ] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Kinh độ gió (dd/mm/yyyy hh:mm:ss) của vị trí tâm bão 1 phải là số thực] - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] fields: - Choose datetime on datetime field (dd/mm/yyyy hh:mm:ss) - Input storm level, Longitude, Latitude, ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 164Prepared by 6Fingers
  • 165. influence area 1, influence area 2, influence area 3 (inputted data must be interger) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 30] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 1] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Phạm vi ảnh hưởng 1] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Phạm vi ảnh (dd/mm/yyyy hh:mm:ss) hưởng 1 của vị trí tâm bão 1 phải là số - Input storm level, Longitude, Latitude, thực] influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 31] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 2] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 165Prepared by 6Fingers
  • 166. Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Phạm vi ảnh hưởng 2] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Phạm vi ảnh (dd/mm/yyyy hh:mm:ss) hưởng 2 của vị trí tâm bão 1 phải là số - Input storm level, Longitude, Latitude, thực] influence area 1, influence area 2, influence area 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 32] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 3] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger EXCEPT data message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying in [Phạm vi ảnh hưởng 3] textbox) lên cơ sở dữ liệu không?], [Yes] button, 3. [Vị trí tâm bão 2] fields: [No] button, [Cancel] button - Choose datetime on datetime field 7. Display notification box [Phạm vi ảnh (dd/mm/yyyy hh:mm:ss) hưởng 3 của vị trí tâm bão 1 phải là số - Input storm level, Longitude, Latitude, ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 166Prepared by 6Fingers
  • 167. influence area 1, influence area 2, influence area thực] 3(inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 33] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Cấp bão] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Cấp bão của - Input storm level, Longitude, Latitude, vị trí tâm bão 2 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Cấp bão] textbox) 4. [Vị trí tâm bão 3] 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) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 167Prepared by 6Fingers
  • 168. 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 34] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Tốc độ gió] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Tốc độ gió - Input storm level, Longitude, Latitude, của vị trí tâm bão 2 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Tốc độ gió] textbox) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 168Prepared by 6Fingers
  • 169. 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 35] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Vĩ độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Vĩ độ của vị - Input storm level, Longitude, Latitude, trí tâm bão 2 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Vĩ độ] textbox) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 36] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Kinh độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 169Prepared by 6Fingers
  • 170. creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Kinh độ của - Input storm level, Longitude, Latitude, vị trí tâm bão 2 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Kinh độ] textbox) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 37] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 1] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 1 của vị trí tâm bão 2 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger EXCEPT data in [Phạm vi ảnh hưởng 1] textbox) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 170Prepared by 6Fingers
  • 171. 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 38] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 2] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 2 của vị trí tâm bão 2 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger EXCEPT data in [Phạm vi ảnh hưởng 2]) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] fields: - Choose datetime on datetime field ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 171Prepared by 6Fingers
  • 172. (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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 39] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 3] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 3 của vị trí tâm bão 2 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger EXCEPT data in [Phạm vi ảnh hưởng 3] textbox) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 172Prepared by 6Fingers
  • 173. [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 40] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Cấp bão] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Cấp bão của - Input storm level, Longitude, Latitude, vị trí tâm bão 3 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Cấp bão] textbox) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 41] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Tốc độ gió] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 173Prepared by 6Fingers
  • 174. of [Tạo tin] tab is displaying - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Tốc độ gió - Input storm level, Longitude, Latitude, của vị trí tâm bão 3 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Tốc độ gió] textbox) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 42] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Vĩ độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Vĩ độ của vị - Input storm level, Longitude, Latitude, trí tâm bão 3 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] fields: - Choose datetime on datetime field (dd/mm/yyyy hh:mm:ss) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 174Prepared by 6Fingers
  • 175. - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Vĩ độ] textbox) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 43] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Kinh độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Kinh độ của - Input storm level, Longitude, Latitude, vị trí tâm bão 3 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Kinh độ] textbox) 5. [Vị trí tâm bão 4] fields: - Choose datetime on datetime field (dd/mm/yyyy hh:mm:ss) - Input storm level, Longitude, Latitude, ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 175Prepared by 6Fingers
  • 176. influence area 1, influence area 2, influence area 3 (inputted data must be interger) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 44] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 1] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 1 của vị trí tâm bão 3 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Phạm vi ảnh hưởng 1] textbox) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 45] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 176Prepared by 6Fingers
  • 177. [Phạm vi ảnh hưởng 2] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 2 của vị trí tâm bão 3 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Phạm vi ảnh hưởng 2]) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 46] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 3] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 1] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 3 của vị trí tâm bão 3 phải là số ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 177Prepared by 6Fingers
  • 178. influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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 EXCEPT data in [Phạm vi ảnh hưởng 3] textbox) 5. [Vị trí tâm bão 4] 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) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 47] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Cấp bão] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Cấp bão của - Input storm level, Longitude, Latitude, vị trí tâm bão 4 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 178Prepared by 6Fingers
  • 179. 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Cấp bão] textbox) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 48] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Tốc độ gió] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Tốc độ gió - Input storm level, Longitude, Latitude, của vị trí tâm bão 4 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Tốc độ gió] textbox) 6. Click on [Đồng ý] button ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 179Prepared by 6Fingers
  • 180. 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 49] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Vĩ độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Vĩ độ của vị - Input storm level, Longitude, Latitude, trí tâm bão 4 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Vĩ độ] textbox) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 50] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Kinh độ] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 180Prepared by 6Fingers
  • 181. creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Kinh độ của - Input storm level, Longitude, Latitude, vị trí tâm bão 4 phải là số thực] influence area 1, influence area 2, influence area 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Kinh độ] textbox) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 51] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 1] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 1 của vị trí tâm bão 4 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] fields: ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 181Prepared by 6Fingers
  • 182. - 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) 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Phạm vi ảnh hưởng 1] textbox) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 52] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 2] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 2] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 2 của vị trí tâm bão 4 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] fields: - Choose datetime on datetime field (dd/mm/yyyy hh:mm:ss) ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 182Prepared by 6Fingers
  • 183. - Input storm level, Longitude, Latitude, influence area 1, influence area 2, influence area 3 (inputted data must be interger EXCEPT data in [Phạm vi ảnh hưởng 2]) 6. Click on [Đồng ý] button 7. Click on [Yes] button [Viewer- Check notification box is 1. Input storm name in storm name textbox 1. Inputted name is displayed in textbox Pass 8/4/2012 53] displayed successfully when 2. [Vị trí tâm bão 1] fields: 2. Inputted text is displayed on textbox save invalid inputted data in - Choose datetime on datetime field 3. Inputted text is displayed on textbox [Phạm vi ảnh hưởng 3] field (dd/mm/yyyy hh:mm:ss) 4. Inputted text is displayed on textbox Precondition: - Input storm level, Longitude, Latitude, 5. Inputted text is displayed on textbox - Storm broadcast message influence area 1, influence area 2, influence area 6. Display message confirm box includes creating screen/default screen 3 (inputted data must be interger) message is [Bạn có đồng ý tải bản tin này of [Tạo tin] tab is displaying 3. [Vị trí tâm bão 1] fields: lên cơ sở dữ liệu không?], [Yes] button, - Choose datetime on datetime field [No] button, [Cancel] button (dd/mm/yyyy hh:mm:ss) 7. Display notification box [Phạm vi ảnh - Input storm level, Longitude, Latitude, hưởng 3 của vị trí tâm bão 4 phải là số influence area 1, influence area 2, influence area thực] 3 (inputted data must be interger) 4. [Vị trí tâm bão 3] 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) 5. [Vị trí tâm bão 4] 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 EXCEPT data in [Phạm vi ảnh hưởng 3] textbox) 6. Click on [Đồng ý] button 7. Click on [Yes] button ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 183Prepared by 6Fingers
  • 184. [Viewer- Check notify when input 1. Input data in datetime field of [Vị trí tâm bão 1. Inputted data is displayed in textbox Pass 8/4/2012 54] invalid value in time field of 1] 2. Inputted data is displayed in textbox [Vị trí tâm bão 2] 2. Input data in datetime field of [Vị trí tâm bão 3. Inputted data is displayed in textbox Precondition: 2], this datetime data is earlier than data in the 4. Inputted data is displayed in textbox - All field of storm message datetime field of [Vị trí tâm bão 1] 5. Display confirm message box [Bạn có creating screen is inputted 3. Input data in datetime field of [Vị trí tâm bão đồng ý tải bản tin này lên cơ sở dữ liệu with valid data 3] không?], [Yes] button, [No] button, 4. Input data in datetime field of [Vị trí tâm bão [Cancel] button 4] 6. Display notification box [Thời gian của 5. Click [Đồng ý] button vị trí tâm bão 1 phải sớm hơn thời gian 6. Click [Yes] button của vị trí tâm bão 2] [Viewer- Check notify when input 1. Input data in datetime field of [Vị trí tâm bão 1. Inputted data is displayed in textbox Pass 8/4/2012 55] invalid value in time field of 1] 2. Inputted data is displayed in textbox [Vị trí tâm bão 3] 2. Input data in datetime field of [Vị trí tâm bão 3. Inputted data is displayed in textbox Precondition: 2] 4. Inputted data is displayed in textbox - All field of storm message 3. Input data in datetime field of [Vị trí tâm bão 5. Display confirm message box [Bạn có creating screen is inputted 3], this datetime data is earlier than data in the đồng ý tải bản tin này lên cơ sở dữ liệu with valid data datetime field of [Vị trí tâm bão 2] không?], [Yes] button, [No] button, 4. Input data in datetime field of [Vị trí tâm bão [Cancel] button 4] 6. Display notification box [Thời gian của 5. Click [Đồng ý] button vị trí tâm bão 2 phải sớm hơn thời gian 6. Click [Yes] button của vị trí tâm bão 3] [Viewer- Check notify when input 1. Input data in datetime field of [Vị trí tâm bão 1. Inputted data is displayed in textbox Pass 8/4/2012 56] invalid value in time field of 1] 2. Inputted data is displayed in textbox [Vị trí tâm bão 4] 2. Input data in datetime field of [Vị trí tâm bão 3. Inputted data is displayed in textbox Precondition: 2] 4. Inputted data is displayed in textbox - All field of storm message 3. Input data in datetime field of [Vị trí tâm bão 5. Display confirm message box [Bạn có creating screen is inputted 3] đồng ý tải bản tin này lên cơ sở dữ liệu with valid data 4. Input data in datetime field of [Vị trí tâm bão không?], [Yes] button, [No] button, 4], this datetime data is earlier than data in the [Cancel] button datetime field of [Vị trí tâm bão 3] 6. Display notification box [Thời gian của 5. Click [Đồng ý] button vị trí tâm bão 3 phải sớm hơn thời gian 6. Click [Yes] button của vị trí tâm bão 4] ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 184Prepared by 6Fingers
  • 185. [Viewer- Check weather message Choose [Bản tin thời tiết] value in message type Weather message creating screen is Pass 8/4/2012 57] creating screen is displayed drop down list displayed on read mode and includes: successfully - Chose value is displayed on message Precondition: type field - Default screen of [Tạo tin] - Field title is [Bản tin văn bản] tab is displaying - 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 [Viewer- Check create a weather 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 8/4/2012 58] message successfully(connect 2. Click on [Đồng ý] button 2. Display confirm message box [Bạn có to server successfully) 3. Click on [Yes] button đồng ý tải bản tin này lên cơ sở dữ liệu Precondition: 4. Click on [OK] button không?], [Yes] button, [No] button - Weather message creating 3. Display notification box [Bản tin thời screen is displaying tiết đã được lưu trữ trong cơ sở dữ liệu] and [OK] button 4. Notification message box is closed [Viewer- Check notifiy box is 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 8/4/2012 59] displayed successfully when 2. Click on [Đồng ý] button 2. Display confirm message box, text is create a weather 3. Click on [Yes] button [Bạn có đồng ý tải bản tin này lên cơ sở message(connect to server 4. Click on [OK] button dữ liệu không?], [Yes] button and [No] unsuccessfully) button Precondition: 3. Display notification box, text is [Có sự - Weather message creating cố khi kết nối tới máy chủ. Việc tải bản screen is displaying tin lên cơ sở dữ liệu hiện thời không thực hiện được] and [OK] button 4. Notification message box is closed [Viewer- Check notify box is displayed 1. Click on [Đồng ý] button 1. Display notification message box , text Pass 8/4/2012 60] successfully when create a 2. Click on [OK] button is [Vui lòng nhập tin nhắn gửi đi], [OK] weather message without data button Precondition: 2. Notification message box is closed - Weather messsage creating successfully ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 185Prepared by 6Fingers
  • 186. screen is displaying [Viewer- Check control command Choose [Câu lệnh điều chỉnh] value in message Control command creating screen is Pass 8/4/2012 61] creating screen is displayed type drop down list displayed on read mode and includes: successfully - Chose value is displayed on message Precondition: type field - Default screen of [Tạo tin] - Field title is [Bản tin văn bản] tab is displaying - Text of message name label is [Câu lệnh điều chỉnh], text is red and bold - Text of message code label is [Mã số:3] - [Nội dung] label - Control command creating textbox [Viewer- Check create a control 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 8/4/2012 62] command 2. Click on [Đồng ý] button 2. Display confirm message box [Bạn có successfully(connect to server 3. Click on [Yes] button đồng ý tải bản tin này lên cơ sở dữ liệu successfully) 4. Click on [OK] button không?], [Yes] button, [No] button Precondition: 3. Display notification box [Câu lệnh điều - Control command creating khiển đã được lưu trữ trong cơ sở dữ liệu] screen is displaying 4. Close notification box [Viewer- Check notifiy box is 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 8/4/2012 63] displayed successfully when 2. Click on [Đồng ý] button 2. Display confirm message box, text is create a control command 3. Click on [Yes] button [Bạn có đồng ý tải bản tin này lên cơ sở message(connect to server dữ liệu không?], [Yes] button and [No] unsuccessfully) button Precondition: 3. Display notification box, text is [Có sự - Control command creating cố khi kết nối tới máy chủ. Việc tải bản screen is displaying tin lên cơ sở dữ liệu hiện thời không thực hiện được] and [OK] button [Viewer- Check notify box is displayed 1. Click [Đồng ý] button 1. Display confirm message box , text is Pass 8/4/2012 64] successfully when create a 2. Click [Yes] button [Bạn có đồng ý tải bản tin này lên cơ sở control command message 3. Click on [OK] button dữ liệu không?], [Yes] button and [No] without data button Precondition: 2. Display notification box, text is [Câu - Control command creating lệnh điều khiển dã được lưu trong cơ sở ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 186Prepared by 6Fingers
  • 187. screen is displaying dữ liệu], and [OK] button 3. Close notification box [Viewer- Check other message creating Choose [Bản tin khác] value in message type Other message creating screen is Pass 14/4/2012 65] screen is displayed drop down list displayed on read mode and includes: successfully - Chose value is displayed on message Precondition: type field - Default screen of [Tạo tin] - Field title is [Bản tin văn bản] tab is displaying - Text of message name label is [Bản tin khác], text is red and bold - Text of message code label is [Mã số:4] - [Nội dung] label - Other message creating textbox [Viewer- Check create a message of 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 14/4/2012 66] other mesage type 2. Click on [Đồng ý] button 2. Display confirm message box [Bạn có successfully(connect to server 3. Click on [Yes] button đồng ý tải bản tin này lên cơ sở dữ liệu successfully) không?], [Yes] button, [No] button. Precondition: 3. Display notification box [Bản tin khác - Other message creating đã được lưu trong cơ sở dữ liệu] screen is displaying [Viewer- Check notifiy box is 1. Input data into textbox 1. Inputted data is displayed in textbox Pass 14/4/2012 67] displayed successfully when 2. Click on [Đồng ý] button 2. Display confirm message box, text is create a message of other 3. Click on [Yes] button [Bạn có đồng ý tải bản tin này lên cơ sở message type(connect to dữ liệu không?], [Yes] button and [No] server unsuccessfully) button. Precondition: 3. Display notification box, text is [Có sự - Other message creting cố khi kết nối tới máy chủ. Việc tải bản creating screen is displaying tin lên cơ sở dữ liệu hiện thời không thực hiện được] and [OK] button [Viewer- Check notify box is displayed 1. Click on [Đồng ý] button 1. Display confirm message box , text is Pass 14/4/2012 68] successfully when create a 2. Click on [Yes] button [Bạn có đồng ý tải bản tin này lên cơ sở weather message without data 3. Click on [OK] button dữ liệu không?], [Yes] button and [No] Precondition: button - Other message creating 2. Display notification box, text is [Vui ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 187Prepared by 6Fingers
  • 188. screen is displaying lòng nhập nội dung tin nhắn gửi đi], and [OK] button 3. Close notification box View SOS notification [Viewer- Check SOS message Look at the [Tổng quan] screen Message notification box is displayed at [CSS-59] Pass 13/4/2012 69] notification box is displayed screen central successfully when receive a - Text is [Nhận được 1 thông tin khẩn cấp SOS message (S.O.S) mới] Precondition: - [OK] button - [Tổng quan] screen is displaying [Viewer- Check SOS message Look at the [Tạo tin] screen Message notification box is displayed at [CSS-59] Pass 13/4/2012 70] notification box is displayed screen central successfully when receive a - Text is [Nhận được 1 thông tin khẩn cấp SOS message (S.O.S) mới] Precondition: - [OK] button - [Tạo tin] screen is displaying [Viewer- Check SOS message Look at vessel history screen Message notification box is displayed at [CSS-59] Pass 13/4/2012 71] notification box is displayed screen central successfully when receive a - Text is [Nhận được 1 thông tin khẩn cấp SOS message (S.O.S) mới] Precondition: - [OK] button - Vessel history screen is displaying [Viewer- Check SOS message Look at vessels voyage screen Message notification box is displayed at [CSS-59] Pass 13/4/2012 72] notification box is displayed screen central successfully when receive a - Text is [Nhận được 1 thông tin khẩn cấp SOS message (S.O.S) mới] Precondition: - [OK] button - [Vessels voyage screen is ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 188Prepared by 6Fingers
  • 189. displaying [Viewer- Check SOS message Look at the [Tổng quan] screen Message notification box is displayed at [CSS-61] Pass 11/4/2012 71] notification box is displayed screen central successfully when receive 2 - Text is [Nhận được 2 thông tin khẩn cấp SOS messages (S.O.S) mới] Precondition: - [OK] button - [Tổng quan] screen is displaying [Viewer- Check SOS message Click [OK] button SOS message notification box is closed Pass 4/4/2012 72] notification box is closed successfully Precondition: - SOS message notification box is displaying on screen [Viewer- Check a SOS vessel symbol Look at map on [Tổng quan] screen A SOS vessel symbol is displayed on map [CSS-59] Pass 11/4/2012 73] is displayed on map as a red symbol, and blinked successfully when receive a SOS message Precondition: - [Tổng quan] screen is displaying [Viewer- Check 2 SOS vessel symbols Look at map on [Tổng quan] screen 2 SOS vessel symbols are displayed on [CSS-61] Pass 11/4/2012 74] are displayed on map map as a red symbol, and blinked successfully when receive 2 SOS message Precondition: - [Tổng quan] screen is displaying ________________________________________________________________________Final Report, Maritime Information Visualization, Version 1.0 Page | 189Prepared by 6Fingers
  • 190. 5.6 Test Summary Report5.6.1 Test Execution SummaryTest Execution Summary Number of Test Pass Fail Untested Accepted N/A cases 0 0 0 0 0 0Onsea Terminal 54 0 0 0 0 54Coastal Station system 62 0 0 0 0 62Viewer 75 0 1 0 0 75CombineV-CS-OT 10 10 0 0 0 10External Interface 0 0 0 0 0 0Performance 0 0 0 0 0 0Data migration 0 0 0 0 0 0Test coverageTest coverage 99.5%Test successful coverage 99.5%5.6.2 Test Results5.6.3 Summary of Incident Reports Raised During ProjectSeverity Total Open Defect Defect Assigned Corrected Accepted Total Open defectsFatal 0 0 0 0 0Serious 3 0 3 0 0Medium 1 0 1 0 0Cosmetic 4 0 4 0 0Total (Status) 0 0 0 0 0Total (W.def) 0 0 0 0 0
  • 191. Prepared for MIV5.6.4 Conclusion5.6.4.1 System Test Success Criteria# Criteria All the inputs of system testing are baselined and approved by 6Fingers(Common1 requirement, ADD, SRS, Design,Software package, System test cases). System testing is over and all known issues (if any) are aware by 6Fingers’ members and2 documented in Test summary report.3 All planned Test Cases have been executed (99.5% test execution coverage) At least 95% executed system test cases have to be passed. (More than 95% test successful4 coverage)5 100% high priority test cases in scope are passed.6 Only Cosmetic defects can be accepted6 Installation Guide6.1 Environment RequirementDue to all modules of the project are developed on .NET and Java platform, productionenvironment needs to fulfill these following requirements: Operating system: Windows 7 Framework: .NET Framework 4.0, Java 7.0 DBMS: SQL Server 2008 R2 Express6.2 Installation PackageAt the glance, the project has these following modules need to be deployed on productionenvironment 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 TerminalThese following steps show installation guide for MIV On-sea terminal program. Page 191/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 192. Prepared for MIVFirstly, open the MIVSetup.exe file.When the license screen appears, read and click “Tôi đồng ý” button if you want to setupthe program.On next screen, click “Tiến” button to continue Page 192/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 193. Prepared for MIVOn next screen, click “Duyệt” button to select destination folder, and finally click “Càiđặt” button to install.After installed, open the installed folderFinally, double click on the MIV_OnseaTerminal.jar file to run the program6.4 Installation Guide for Database serverInstall “Microsoft SQL Server” then run “DBServer.exe” Page 193/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 194. Prepared for MIV6.5 Installation Guide for Coastal StationThese 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 Page 194/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 195. Prepared for MIVInstallation success, click “Close” to finish6.6 Installation Guide for ViewerThese 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. Page 195/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 196. Prepared for MIVOn next screen, click “Browse” button to select destination folder, and finally click“Next” button to install.Click “Next” to start installation Page 196/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 197. Prepared for MIVInstallation success, click “Close” to finish7 User Manual7.1 Application Overview7.1.1 RequirementsIn order to use this application, you need to have the following: .NET Framework 4.0 JRE 7.07.1.2 Available FeaturesThe below list is available features for fishersNo. Functions Description View map This use case allows fisher to view the maritime map where he’s on1 View storm notification This use case allows fisher to view storm notifications broadcasted by coastal stations. The notifications will be visualized and2 displayed in images View weather information This use case allows fisher to view other weather information like3 wind power, temperature…The information will be display in text View vessel position The fisher can trace his position by using the terminal. His position4 will be displayed inside the map View message history This use case allows fisher to trace the message that was5 broadcasted in past, or old message Page 197/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 198. Prepared for MIV Send SOS notification This use case allows fisher to send SOS notification in case he got a6 bad situation. Table 7-1: Available features for fishersThe below list is available features for operatorsNo. Functions Description View message history This use case allows Operator to view history of messages which are1 broadcasted and received by this coastal station View broadcasted message This use case allows Operator to view or be alerted whenever the2 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) from3 vessel Table 7-2: Available features for operatorsThe below list is available features for central operatorsNo. Functions Description Broadcast messages This use case allows central operator to send messages to all vessels1 View all vessels’ positions on This use case allows central operator to observe vessel position on2 map map at a specific time View a vessel’s voyage This use case allows central operator to observe a vessel’s voyage3 through an interval of time View a vessel’s information This use case allows central operator to view information of vessel4 Table 7-3: Available features for central operators7.1.3 RolesTo 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 A user who has responsibilities for observing coastal station1 Operator system and message forwarding between Viewer system and vessels. A user who has responsibilities for vessel management,2 Central Operator observation and salvage. Table 7-4– Roles for coastal station Page 198/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 199. Prepared for MIV7.2 User Manual for Functions7.2.1 Functions for Fishers7.2.1.1 View mapWhen 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 screen7.2.1.2 View storm notificationWhen a new storm message arrives, a message box will be displayed to notify the fisher. Page 199/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 200. Prepared for MIVAfter click “ok” button, the storm image will be displayedIf fisher doesn’t understand detail of the storm by image, he can click the button to view moredetail:7.2.1.3 View weather informationWhen 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. Page 200/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 201. Prepared for MIVIn 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 screen7.2.1.4 View vessel positionWhen the fisher views the map, the vessel position will be also displayed on the map. It will be ananimating red dot icon, update continuously and the vessel coordinate will be written beside thedot icon. Page 201/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 202. Prepared for MIV7.2.1.5 View message historyThe program will store the latest 5 storm messages and 5 weather information messages. If thefisher want to view the previous message, he can click the button, and click the to back to the next messageIf there is no previous message, the “Previous” button will be gray-scaled:7.2.1.6 Send SOS notificationThere 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 willbe changed to button. The SOS message will be send until fisher clicks thisbutton. If fisher click “Không” button, the message will not be send.7.2.1.7 Notify restricted areaOn map will, there is a rounded area call “Restricted area”. The fishers are prohibited to enter thisarea.If the vessel enters this area, a warning will be displayed until it leaves this area Page 202/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 203. Prepared for MIV7.2.2 Functions for Operators7.2.2.1 View broadcasted/received messageMain GUI7.2.2.2 View message historyClick button , a dialog shows up that lists all current broadcastmessages.7.2.2.3 Broadcast messagesClick 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. Page 203/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 204. Prepared for MIV7.2.2.4 Update messages from Database serverClick button to update the latest messages. When updating process finishes, theprogram 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 ConfigurationClick7.2.2.5.1 Change server addressIn “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. Page 204/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 205. Prepared for MIVThe program connects to server with new address. The inform labeldisplays until connection process finishes. Then the inform label is replaced by (if success) or (if error).7.2.2.5.2 Change message storing timeChange 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 fromdatabase server.7.2.2.5.3 Change the automatically broadcast timeIn “Thời gian phát” group box, you can see the list of time in a day for broadcasting messagesautomatically.To remove a time from this list, select a time and click button. Note that you cannotremove 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 newtime. Note that you must enter a new time in “h:m:s” format (h, m, s stands for hours, minutes,seconds), then press Enter Page 205/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 206. Prepared for MIVIf the new time exists, nothing is inserted. Else, then the new time is inserted into the list withdescending order.7.2.2.5.4 Change the automatically update timeRefer to Change the automatically broadcast time. Do the same thing in “Thời gian cập nhật bảntin” group box.7.2.3 Functions for Central Operators7.2.3.1 Broadcast messagesStep1: 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 Page 206/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 207. Prepared for MIVStep 3: Fill the content of message and click [Đồng ý]Step4: A message box show confirm question. Click [Yes] to commit message to databaseStep 5: A Message box will be shown if your message is successfully commit to database7.2.3.2 View all vessels’ positions on mapAll vessel position will be automatically display on tab [Bản đồ tổng quan] Page 207/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 208. Prepared for MIV7.2.3.3 View a vessel’s voyageStep 1: Click on the vessel that you want to see voyageStep 2: Click to [Bấm vào đây để xem lịch sử đi tàu]Step 3: Move to tab display the voyageStep 4: Click [Hiển thị trên bản đồ] to view voyage on map Page 208/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 209. Prepared for MIVStep 5: A tab shown vessel voyage7.2.3.4 View a vessel’s information Step 1: Click on the any vessel that you want to see information8 Appendixes8.1 MessagesThis section describes the details of messages used in business rules e.g. error messages,confirmation messages, etc.MSG MSG Message Title Message Content ButtonCode Type Error InvalidDatetime Bạn đã nhập dữ liệu ngày tháng OKMSG1 không đúng Error InvalidNumber Bạn chỉ được nhập kí tự số OKMSG2 Page 209/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers
  • 210. Prepared for MIV Error MessageSuccess Bạn đã tạo bản tin thành công OKMSG3 Inform MessageNotification Có x bản tin mới Xem/BỏMSG4 qua Page 210/210 Final Report, Maritime Information Visualization, Version 1.0 Prepared by 6Fingers

×