MIV final report

677 views

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
677
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

MIV final report

  1. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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. 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

×