Danmarks Tekniske Universitet & Visma Consulting ... Ibrahim Nemli DTU & Visma Consulting Optimering

  • View
    228

  • Download
    0

Embed Size (px)

Text of Danmarks Tekniske Universitet & Visma Consulting ... Ibrahim Nemli DTU & Visma Consulting...

Studerende: Ibrahim Nemli

Studienummer: s093477

DTU Vejleder: Carsten Witt

Virksomhedsvejledere: Sren Lund, Mikael Grnfeldt & Klaus Mogensen

Virksomhed: Visma Consulting, Hellerup

Afsluttende eksamensnummer: IMM-B.Eng-2012-25

Afleveringsdato: 28-01-2013

Danmarks Tekniske Universitet & Visma Consulting, Hellerup

Projekt rapport Optimering af fartjs kommunikationsmodul konfiguration Optimizing fishing vessel communication module configuration

Ibrahim Nemli DTU & Visma Consulting Optimering af fartjs kommunikationsmodul konfiguration IMM-B.Eng-2012-25

S i d e | 2

Technical University of Denmark

Informatics and Mathematical Modelling

Building 321, DK-2800 Kongens Lyngby, Denmark

Phone +45 45 25 33 51, Fax +45 45 88 26 73

reception@imm.dtu.dk

www.imm.dtu.dk

http://www.imm.dtu.dk/

Ibrahim Nemli DTU & Visma Consulting Optimering af fartjs kommunikationsmodul konfiguration IMM-B.Eng-2012-25

S i d e | 3

Summary This is a report about optimizing and making a user-friendly interaction with a configuration for a system called communication unit which is a part of vTrack. vTrack is a software program developed and maintained by Visma Consulting at Hellerup in the department of Fishery Solutions1. The main objectives of this software are to track and monitor fishing vessels for the country concerned. The communication unit starts up by reading a configuration file (written in xml) which is quite long and messy. From the information in this file it initializes some processes (as threads) and starts to perform different kind of tasks as specified in the configuration. The aim in this project is to get rid of this xml file by mapping the data into a database and then making a graphical environment to maintain the configuration in a convenient way. The project has been achieved by splitting the project into sub projects: Subproject 1 database modelling In this subproject a database architecture has been developed which makes is possible to map the data in the configuration file to database. Subproject 2 integration and unit testing After developing the database the communication unit has to be integrated with the database so it reads the configuration from it and initializes the correct processes as it did with the xml file. That no functionalities have been corrupted during this switchover has to be validated by performing unit tests for the developed source code. Subproject 3 environment Finally as the last part of the project an environment (a web application) is needed to make it possible to interact with the data stored in the database and manipulate it regarding to the CRUD principles (create, read, update, delete). Those changes should immediate take effect on communication unit without restarting it from scratch. This is also an optimizing since any changes on the configuration file (the xml file) caused a manual restart of the communication unit. Subproject 4 xml parser This subproject came up while discussing at the company. This is a small program which is able to parse the configuration file and convert it to SQL statements. Furthermore this program gives you the opportunity to save the statements into a SQL file and run it directly on a database. This project has been made in collaboration with Visma Consulting at Hellerup and Technical University of Denmark (DTU). The rest of this report has been writing in Danish language.

1 http://www.fisherysolution.com/

http://www.fisherysolution.com/

Ibrahim Nemli DTU & Visma Consulting Optimering af fartjs kommunikationsmodul konfiguration IMM-B.Eng-2012-25

S i d e | 4

Forord Jeg er en IT-diplomingenir studerende fra DTU, Danmarks Tekniske Universitet, der skal skrive et eksamensprojekt (bachelor), med det forml at opn en B. Eng grad i IT. I dette projekt arbejdes der med et skaldt Vessel Monitoring System (VMS) som er i stand til at kunne overvge fiskefartjer i det land, det er installeret i. VMSen er opbygget af forskellige enheder og en af disse enheder er kommunikationsenheden, som vedtager al kommunikation mellem de eksterne datakilder, f.eks. de overvgende fiskefartjer, og systemet selv. Denne enhed startes op ved at indlse konfigurationsparametre fra en fil, sledes at den kan oprette forbindelser til de korrekte datakilder. Ulempen ved denne lsning er, at der kommunikationsenheden skal genstartes nr der modificeres i filen, hvilket giver kommunikationsnedetid. En anden ulempe er, at filen er efterhnden s stor og kompleks, at den er svr at overskue. Denne opgave har til forml at udvikle en arkitektur der vil gre det muligt, at kunne persistere data fra konfigurationsfilen i en database. Dernst skal kommunikationsenheden ndres, s den lser konfigurationen fra databasen. S snart der sker ndringer i konfigurationsparametrene, skal disse indlses af kommunikationsenheden. Endelig skal der udvikles et grafisk brugerinterface hvori de gemte data i databasen kan modificeres p en brugervenlig mde. Dette vil srge for at kommunikationsenheden ikke genstartes hver gang der ndres i parametrene manuelt. Projekt udfres i et samarbejde med vejledere fra DTU og Visma Consulting, Hellerup. Ibrahim Nemli s093477 Hellerup, januar 2013

Ibrahim Nemli DTU & Visma Consulting Optimering af fartjs kommunikationsmodul konfiguration IMM-B.Eng-2012-25

S i d e | 5

Indholdsfortegnelse

Summary ............................................................................................................................................................ 3

Forord ................................................................................................................................................................ 4

1 Projekt indledning og problemformulering ............................................................................................... 9

2 Vision ....................................................................................................................................................... 10

3 vTrack systemarkitektur .......................................................................................................................... 10

4 Foranalyse ................................................................................................................................................ 11

4.1 Kommunikationsenheden ............................................................................................................... 11

4.1.1 Analyse af vTrack.xml .............................................................................................................. 11

4.1.2 Opstart af kommunikationsenheden ...................................................................................... 14

4.2 Prsentationsenheden ................................................................................................................... 18

4.3 Konklusion ....................................................................................................................................... 20

5 Features ................................................................................................................................................... 21

5.1 Database .......................................................................................................................................... 21

5.2 Kommunikationsenheden ............................................................................................................... 21

5.3 Milj ................................................................................................................................................. 21

5.4 vTrack Xml Parser ............................................................................................................................ 21

6 Kravspecifikation ..................................................................................................................................... 22

6.1 Funktionelle krav ............................................................................................................................. 22

6.2 Non-funktionelle krav ...................................................................................................................... 34

7 Produkt karakteristika ............................................................................................................................. 35

8 Lsningsstrategi ....................................................................................................................................... 37

9 Projekt planlgning ................................................................................................................................. 39

9.1 Tidsplan............................................................................................................................................ 45

10 Arbejdsgang ......................................................................................................................................... 46

11 Status rapporter .................................................................................................................................. 46

12 Afgrnsning......................................................................................................................................... 46

13 Intro .....................................................................................