CHAPTER 1

INTRODUCTION

1.1 COMPANY PROFILE

Thrifty Technologies is a global services provider delivering technology-driven

business solutions that meet the strategic objectives of our clients. Thrifty Technologies

has 2 ‘Centers of Excellence’ that create solutions around specific needs of industries.

Thrifty delivers unmatched business value to customers through a combination of

process excellence, quality frameworks and service delivery innovation. .

Thrifty Technologies takes charge of the IT needs of the entire enterprise. The

gamut of services extends from Enterprise Application Services (CRM, ERP, e-

Procurement and SCM), to e-Business solutions. Thrifty’s enterprise solutions have

served and continue to serve clients from a range of industries including Energy and

Utilities, Finance, Telecom, and Media and Entertainment. .

In 2002, Thrifty Technologies took a quantum jump in the Business Processing

Outsourcing services. Thrifty Business Processing Outsourcing Solutions complements

the services offered by Thrifty Technologies, making it one of the Business Processing

Outsourcing service players. One of the key challenges for banks and financial services

firms has been to create, retain and leverage upon profitable relationships. To do this,

banks require constant enhancement of their capabilities to:

Gain unique insights from customer data

Process transactions in a straight through manner

Assess risk and take proactive action

1

1.2 OBJECTIVE

Through this system the marine company can communicate with the ship, and

will be able to track status and the stability of the ship. There will be a database

administrator in the company who will be monitoring the ship details through the

system 24 hours. All the data about marine will be maintained in a centralized database

and the administrator will be having the rights to do the data manipulation.

It helps to track the marine details when ever needed.

System reliability is improved by a direct, positive confirmation that a

command was carried out.

The details will be updated and can be viewed at any time.

The status reports can be generated at any time.

Fast processing and accurate computation

2

CHAPTER 2

SYSTEM ANALYSIS

System analysis is done in order to make a feasible study about the existing

problems and to formalize the organization’s requirements. This process forms the

basis of software development and validation by understanding the domain for the

software as well as required function, behavior and performance.

The essential purpose of this phase is to find the need and to define the problem

that needs to be solved .This chapter gives a brief discussion about the detailed study of

the proposed system.

2.1 EXISTING SYSTEM

In order to justify and appreciate the need for the system, we have to study the

existing system. The existing system was developed manually. In this process manually

monitoring the marine records that is huge in size is difficult and also the marine status

has been checked through phone conversation, and it was very difficult to keep track of

the marine status. Beyond doubt this is a very tedious and time consuming task. To

overcome this difficulty, we have to computerize the system in automated manner. At

present no formal existing system exists. The administrator was checking and keeping

track of the details manually.

Drawbacks of the Existing System

Time consuming

Difficulty in tracking details

Tedious and complex

More paper work

Unavailability of data

3

Slow updating and retrieval of information

2.2 PROPOSED SYSTEM

The proposed system “Nautical Telematics System” has been developed using

ASP.NET as front end and SQL as back end. The proposed system overcomes the

drawbacks of the existing system.

Here the administrator will be able to keep track of the marine through the

system. The employee can send the information to the company and also he can view

the updates from the company. The company can keep in track of the marine

throughout its voyage in the sea through this system. In case if any change has to be

done while the marine is moving, that can be informed to the marine by the company

through this system. NTS help the company to keep track of their marines at anytime

and anywhere.

Advantages of the Proposed System

Online Information Access

In many cases, a Telemetric load management solution pays for itself to track

details

System reliability is improved by a direct, positive confirmation that a

command was carried out.

Reduce Complexity.

The cellular data network coverage details will be updated and can be viewed at

any time.

The status reports can be generated at any time.

Faster information retrieval and updating

4

2.3 FEASIBILITY STUDY

The process is to make changes in the current system in order to achieve new

effective system. The feasibility study includes complete initial analysis of all related

system. Therefore the study must be conducted in a manner that will reflect the

economic as well as technical feasibility of the system proposal. Feasibility and risk

analysis are related in many ways. If project risk is great, the feasibility of producing

quality software is reduced. During product engineering, however, we concentrate our

attention on four primary areas of interest. Measure of how beneficial or practical the

development of an information system will be to an organization.

The various feasibility studies are:

Operational Feasibility

Economical Feasibility

Technical Feasibility

2.3.1 Operational Feasibility

The proposed system should use the internet level then the different types of

end users are involved in the system, so it solves the user’s needs and the organization

needs. And it supports the all users environment. Includes people-oriented and social

issues: internal issues, such as manpower problems, labour objections, manager

resistance, organizational conflicts and policies; also external issues, including social

acceptability, legal aspects and government regulations.

2.3.2 Technical Feasibility

In the technical feasibility the system analyst look between the requirements of

the organization, this can enter a large amount of data in the effective time. Output

devices which can produce output in a bulk in an effective time. The choice of

processing unit depends upon the type of processing required in the organization.

5

Technical feasibility is the need of hardware and software, which are needed to

implement the proposed system in the organization. Technical requirements are to be

fulfilled to make the proposed system work. This should be necessarily predetermined

so as to make the system more competent.

2.3.3 Economical Feasibility

Economic feasibility is the most frequently used method for evaluating the

effectiveness of the candidate system that is proposed system, more commonly used as

cost/benefit analysis. The procedure is to determine the benefit and savings that are

expected from the candidate system and compare them with the coast, if the benefit

over weight cost then the decision is made to design and implement the system,

otherwise further justification in the proposed system will have it be made, if it has

chance to improve.

Cost estimate for a system we consider several elements. Hardware, Personnel,

Facility, Operation, Supply cost etc. The Economical feasibility must satisfy the needs

of the technical feasibility and the operational feasibility. It involves the economic

feasibility of developing and implementing the proposed system. Economic Feasibility

means, the project benefit of the proposed system outweigh.

6

CHAPTER 3

SYSTEM SPECIFICATION

3.1 HARDWARE REQUIREMENTS

Processor Pentium IV-Class,2.1 GHz or Above

RAM 1 GB.(Min 512)

Hard Disk Space Ultra SCSI Controller 40 GB Hard Disk

CD-ROM Drive or DVD-ROM 52x CD ROM Required

Video 800x600,256 colors Recommended: High Color

16-bit

Mouse Microsoft Mouse or Compatible pointing device

Monitor 17” Color Monitor

Network Interface Card 10\100 TX LAN

Network LAN

7

3.2 SOFTWARE REQUIREMENTS

Operating System Microsoft Windows XP Professional - Service

Pack 2.

Package Microsoft Visual Studio .NET 2005.

Database Microsoft SQL Server 2000

Third Party Tool Infragistics Net Advantage 2006 Volume 3 – with

AJAX.

Web Browser Microsoft Internet Explorer Version 6.0 and above.

Web Server IIS 5.0

Language Design – Active Server Pages .NET (ASP.NET –

2.0)

Code - Visual Basic .NET.(VB.NET)

Scripting Languages Java Script – Client Side.

8

CHAPTER 4

SOFTWARE DESCRIPTION

4.1 FRONT END

4.1.1 Asp .NET

ASP.NET aims for performance benefits over other script-based

technologies (including Classic ASP) by compiling the server-side code to one or

more DLL files on the web server This compilation happens automatically the first

time a page is requested (which means the developer need not perform a separate

compilation step for pages). This feature provides the ease of development offered

by scripting languages with the performance benefits of a compiled binary.

However, the compilation might cause a noticeable delay to the web user when the

newly-edited page is first requested from the web server.

The ASPX and other resource files are placed in a virtual host on an Internet

Information Services server (or other compatible ASP.NET servers; see Other

Implementations, below). The first time a client requests a page, the .NET

framework parses and compiles the file(s) into a .NET assembly and sends the

response; subsequent requests are served from the DLL files. By default ASP.NET

will compile the entire site in batches of 1000 files upon first request. If the

compilation delay is causing problems, the batch size or the compilation strategy

may be tweaked.

9

Asp .NET Compared To Asp Classics

Compiled code means applications run faster with more design time errors

trapped at the development stage.

Significantly improved run-time error handling, making use of exception

handling using try-catch blocks.

Similar metaphors to Windows applications such as controls and events.

ASP.NET leverages the multi-language capabilities of the .NET CLR,

allowing web pages to be coded in VB.NET, C#, J#, Delphi.NET, Chrome

etc.

Ability to cache the whole page or just parts of it to improve performance.

Ability to use the code-behind development model to separate business

logic from presentation.

Web Server Controls: these are controls introduced by ASP.NET for

providing the UI for the web form. These controls are state managed

controls and are WYSIWYG controls.

If an ASP.NET application leaks memory, the ASP.NET runtime unloads

the AppDomain hosting the erring application and reloads the application in

a new AppDomain.

Ability to use the code-behind development model to separate business

logic from presentation.

Microsoft Dotnet Framework

The Microsoft .NET Framework is a software framework and it includes a

large library of coded solutions to prevent common programming problems and a

virtual machine that manages the execution of programs written specifically for the

framework. The .NET Framework is a key Microsoft offering and is intended to be

used by most new applications created for the Windows platform. The coded solutions

that form the framework's Base Class Library cover a large range of programming

needs in a number of areas, including user interface, data access, database connectivity,

cryptography, web application development, numeric algorithms, and network

10

communications. The class library is used by programmers, who combine it with their

own code to produce applications.

Fig 4.1.1 Microsoft Dotnet Framework

Principal Design Features

Interoperability 

Because interaction between new and older applications is commonly

required, the .NET Framework provides means to access functionality that is

implemented in programs that execute outside the .NET environment. Access to

COM components is provided in the System Runtime.

11

Common Runtime Engine 

The Common Language Runtime (CLR) is the virtual machine

component of the .NET framework. All .NET programs execute under the

supervision of the CLR, guaranteeing certain properties and behaviors in the

areas of memory management, security, and exception handling.

Language Independence 

The .NET Framework introduces a Common Type System, or CTS. The

CTS specification defines all possible data types and programming constructs

supported by the CLR and how they may or may not interact with each other.

Because of this feature, the .NET Framework supports the exchange of

instances of types between programs written in any of the .NET languages. This

is discussed in more detail in Microsoft .NET Languages.

Base Class Library 

The Base Class Library (BCL), part of the Framework Class Library

(FCL), is a library of functionality available to all languages using the .NET

Framework. The BCL provides classes which encapsulate a number of common

functions, including file reading and writing, graphic rendering, database

interaction and XML document manipulation.

Simplified Deployment 

The .NET framework includes design features and tools that help

manage the installation of computer software to ensure that it does not interfere

with previously installed software, and that it conforms to security

requirements.

12

Security 

The design is meant to address some of the vulnerabilities, such as

buffer overflows, that have been exploited by malicious software.

Additionally, .NET provides a common security model for all applications.

Portability 

The design of the .NET Framework allows it to theoretically be platform

agnostic, and thus cross-platform compatible. Microsoft's commercial

implementations of the framework cover Windows, Windows CE.In addition,

Microsoft submits the specifications for the Common Language Infrastructure

(which includes the core class libraries, Common Type System, and the

Common Intermediate Language, the C# language, and the C++/CLI language

to both ECMA and the ISO, making them available as open standards.

4.2 BACK END

4.2.1 Microsoft Sql Server 2000

The following is a list of the new features provided in SQL Server 2000:

User-defined functions

Indexed views

Distributed partitioned views

INSTEAD OF and AFTER triggers

New data types

Cascading RI constraints

Multiple SQL Server instances

XML support

Log shipping

13

The rest of this section takes a closer look at each of these new features and

provides a reference to subsequent chapters where more information about the new

feature can be found

User-Defined Functions

SQL Server has always provided the ability to store and execute SQL code

routines via stored procedures. In addition, SQL Server has always supplied a number

of built-in functions. Functions can be used almost anywhere an expression can be

specified in a query. This was one of the shortcomings of stored procedures—they

couldn't be used inline in queries in select lists, where clauses, and so on. Perhaps you

want to write a routine to calculate the last business day of the month. With a stored

procedure, you have to exec the procedure, passing in the current month as a parameter

and returning the value into an output variable, and then use the variable in your

queries. If only you could write your own function that you could use directly in the

query just like a system function. In SQL Server 2000, you can.

Indexed Views

Views are often used to simplify complex queries, and they can contain joins

and aggregate functions. However, in the past, queries against views were resolved to

queries against the underlying base tables, and any aggregates were recalculated each

time you ran a query against the view. In SQL Server 2000 Enterprise or Developer

Edition, you can define indexes on views to improve query performance against the

view. When creating an index on a view, the result set of the view is stored and indexed

in the database. Existing applications can take advantage of the performance

improvements without needing to be modified.

Distributed Partitioned Views

SQL Server 7.0 provided the ability to create partitioned views using the

UNION ALL statement in a view definition. It was limited, however, in that all the

tables had to reside within the same SQL Server where the view was defined. SQL

14

Server 2000 expands the ability to create partitioned views by allowing you to

horizontally partition tables across multiple SQL Servers. The feature helps you scale

out one database server to multiple database servers, while making the data appear as if

it comes from a single table on a single SQL Server. In addition, partitioned views are

now able to be updated.

Instead of and After Triggers

In versions of SQL Server prior to 7.0, a table could not have more than one

trigger defined for INSERT, UPDATE, and DELETE. These triggers only fired after

the data modification took place. SQL Server 7.0 introduced the ability to define

multiple AFTER triggers for the same operation on a table. SQL Server 2000 extends

this capability by providing the ability to define which AFTER trigger fires first and

which fires last.

SQL Server 2000 also introduces the ability to define INSTEAD OF triggers.

INSTEAD OF triggers can be specified on both tables and views. (AFTER triggers can

still only be specified on tables.) If an INSTEAD OF trigger is defined on a table or

view, the trigger will be executed in place of the data modification action for which it is

defined. The data modification is not executed unless the SQL code to perform it is

included in the trigger definition.

Text in Row Data

In previous versions of SQL Server, text and image data was always stored on a

separate page chain from where the actual data row resided. The data row contained

only a pointer to the text or image page chain, regardless of the size of the text or image

data. SQL Server 2000 provides a new text in row table option that allows small text

and image data values to be placed directly in the data row, instead of requiring a

separate data page. This can reduce the amount of space required to store small text and

image data values, as well as reduce the amount of I/O required to retrieve rows

containing small text and image data values.

15

Multiple Sql Server Instances

Previous versions of SQL Server supported the running of only a single instance

of SQL Server at a time on a computer. Running multiple instances or multiple versions

of SQL Server required switching back and forth between the different instances,

requiring changes in the Windows registry. (The SQL Server Switch provided with 7.0

to switch between 7.0 and 6.5 performed the registry changes for you.)

SQL Server 2000 provides support for running multiple instances of SQL

Server on the same system. This allows you to simultaneously run one instance of SQL

Server 6.5 or 7.0 along with one or more instances of SQL Server 2000.

16

CHAPTER 5

PROJECT DESIGN

5.1 PROBLEM DEFINITION

Project Design is a process through which requirements are translated into a

representation of software. In this phase the software development process, the

software's overall structure and its nuances are defined.

A software development model is created. The logical system of the product is

developed in this phase. It is the phase where quality is fostered. It identifies the

software components, specifies relationships among components define program

structure and provides a blueprint for implementation.

5.2 OVERVIEW OF THE PROJECT

This is a marine based telematics system designed to give marine operators

access or navigation, maintenance and emergency services via web-based application

so that the ship and the response centers details can be maintained and updated

frequently. It helps to track, manage, monitor and control all assets in sea.

Through this system the marine company can communicate with the ship, and

will be able to track status and the stability of the ship. There will be a database

administrator in the company who will be monitoring the ship details through the

system 24 hours. All the data about marine will be maintained in a centralized database

and the administrator will be having the rights to do the data manipulation.

17

5.3 MODULE DESCRIPTION

The different modules that have been used in Nautical Telematics system are:

Login module

Login Status Module

Registration Module

Port Of Call List (PCL)

Message Module

Pre arrival Notification of security (PANS)

Stability maintenance Module

Checklist Module

Status Module

Cargo Displacement Module

Brief description on the modules:

Login Module

In this module the login details will be maintained .Only the administrator will

be able to do the manipulation of data that is the insert, update delete, view, search can

be done.

Login Status Module

This module will be maintaining the login status that is the login timing details

of each employee. Through this the company will be able to monitor each employee

working time.

Registration Module

In this module all the Registration details will be maintained. Here also the

administrator only will be doing all data manipulation that is the insert, update, delete,

search, and view. The employee can do only the inserting of data to the system.

There are 5 sub modules in this registration module. They are:

Employee Registration

18

Cargo registration

Port registration

Ship Registration

Port Of Call List (Pcl)

This module will be used for maintaining details of the departure time and date

of the ship, the ports that have been visited by the ship, and also the arrival date and

time of the ship to the destination port. Through this module the company and the port

will be keeping track of the ship.

Pre Arrival Notification Security (Pans)

This module will be used by the ship to intimate the port authorities the arrival

of the vessel at least 24 hours prior to take all the security measures. Here all the

departure and the arrival date and time will be maintained.

Message Module

This module will be maintaining all the message that will be sending from the

ship to the company .Here the current latitude and longitude description also the wind

direction, wind force , distance travelled, distance to go and also about the fuel used

and remaining fuel everything will be maintained.

There are 3 sub modules in this Message module, They are:

Departure Message

Noon message

Arrival message

Stability Maintenance Module

This module is used keep track of the stability of the ship while it’s navigating

through the sea. Here all the details of the navigation path will be described

Status Module

19

This Module is used to maintain the status of the ship while it’s navigating

through the sea, and also here in this module it will be having all the details of the ports

where the ship visited.

Check List Module

In this module it will be maintaining all the safety measures that have to be

checked and used in the ship while it’s navigating.

There are 3 sub modules in this checklist module, they are:

Communication Checklist

Emergency Checklist

Anchor and the Anchorage

Cargo Displacement Module

This module will maintain all the details of the cargo agent and the goods that

have been taken by the ship. It will maintain the bill of lading agreement which have to

be passed before taking the ship from the port. Here all the Good details and also the

ports to which that have to be unloaded will be there.

5.4 DATA FLOW DIAGRAM

20

Level 0:

Figure 5.4.1 Level-0 DFD

Level 1:

Figure 5.4.2 Level 1 - DFD for Admin

21

Figure 5.4.3 Level 1 - DFD for Employee

22

Level 2:

Figure 5.4.4 Level 2 DFD for Admin and Employee

23

5.5. ER-DIAGRAM

Figure 5.5.1 Entity Relationship Diagram

24

5.6 TABLE RELATIONSHIP DIAGRAM

25

Figure 5.6.1 Table Relationship Diagram

5.7 DATABASE DESIGN

5.7.1 Company Details Table

Table Name : Compdet

Primary Key : Compid

Field Name Data Type Description

Compid Int(5) Company Id

Compname Varchar(20) Company Name

Proprietor Varchar(20) Owner Name

Address Varchar(50) Company Address

Port of Registry Varchar(20) Registered port for the ship

Totnoship Int(5) Total no: of ship in the

port

Totemp Int(5) Total number of

employees

Phone Int(15) Phone number

Mailed Varchar(20) Email

Table 5.7.1 Company Details Table

26

5.7.2 PORT DETAILS TABLE

Table Name : Portdet

Primary Key : Portid

Field Name Data Type Description

Portid Int(10) Port Number

Portname Varchar(30) Name of Port

Address Varchar(50) Address

Location Varchar(20) Situated Location

Pilotage Varchar(20) Pilotage Name

Commnid Varchar(10) Communication id

Mail id Varchar(20) Email id

Fax Int(15) Fax Number

Prevport Varchar(20) Previous Port

Nextport Varchar(20) Next Port

Table 5.7.2 Port Details Table

27

5.7.3 CARGO AGENT DETAILS TABLE

Table Name : Cargoagentdet

Primary Key : Agentid

Field Name Data Type Description

Agentid Int(5) Agent id

Agentname Varchar(20) Agent Name

Commnid Varchar(10) Communication id

Country Varchar(20) Country Name

State Varchar(20) Name of The State

Address Varchar(50) Agent Address

Phone Int(15) Phone Number

Fax Int(15) Fax Number

Mail id Varchar(20) Email id

Message Varchar(1000) Message area

Status Varchar(100) Status Check

Table 5.7.3 Cargo Agent Details Table

28

5.7.4 LOGIN DETAILS TABLE

Table Name : logindet

Primary Key : Loginid

Foreign Key : SSN, Portid, Agentid

Field Name Data Type Description

Loginid Int(10) Login Id

SSN Int(10) Security Number

Portid Int(10) Port id

Agentid Int(5) Communication Id

Username Varchar(20) All username

Password Varchar(20) Password

Department Varchar(20) Employees department

Position Varchar(20) Employees position

Table 5.7.4 Login Details Table

29

5.7.5 SHIP DETAILS TABLE

Table Name : Shipdet

Primary Key : Shipid

Foreign Key : Portid, Compid, Cargoid

Field Name Data Type Description

Shipid Int(10) Ship Number

Shipname Varchar(20) Name of the ship

Reg No Int(10) Ship Registration number

Totnoemp Int(100) Total number of emp in

ship

Portid Int(10) Port number

Compid Int(5) Company Name

Proprietor Varchar(20) Owner Name

DOB Datetime Date of Build

Length Int(10) Length of Ship

Breadth Int(10) Breadth “ “

Depth Int(10) Depth “ “

Freeboard Int(10) Cargo freeboard

Gross Tonnage Int(10) Gross weight

Dwt Int(10) Dead weight

Lwt Int(10) Light weight

Cargoid Int(10) Cargo id number

Security Level Varchar(10) Security Levels

Mail id Varchar(20) Email id

Table 5.7.5 Ship Details Table

30

5.7.6 MANUFACTURER DETAILS TABLE

Table Name : Mandet

Primary Key : Manuid

Foreign Key : Compid, Shipid

Field Name Data Type Description

Manuid Int(5) Manufacturer id

Manuname Varchar(20) Manufacturer name

Compid Int(5) Company id

Shipid Int(5) Ship id

Totnoship Int(5) Total no: of ship

Table 5.7.6 Manufacturer Details Table

31

5.7.7 EMPLOYEE DETAILS TABLE

Table Name : Empdet

Primary Key : SSN

Foreign Key : Shipid

Field Name Data Type Description

SSN Int(10) Security Number

Empname Varchar(20) Employee Name

Emptype Varchar(20) Employee Type

Username Varchar(20) Employee username

Password Varchar(20) Employee password

Ship name Varchar(20) Name of the ship

Shipid int(10) Ship Number

DOB Datetime Date of Birth

POB Varchar(20) Place Of Birth

Pass No Varchar(10) Passport Number

DOJ Datetime Date Of Joining

Department Varchar(20) Department Name

Designation Varchar(20) Position

Pass Expiry Datetime Pass Expiry Date

Nationality Varchar(20) Nationality Type

Address Varchar(100) Employee Address

City Varchar(60) Name of City

State Varchar(50) Name of State

Pincode Int(6) Pin code Number

Phoneno Int(15) Residence Number

Mobile Int(15) Mobile Number

Email id Varchar(20) Email

Table 5.7.7 Employee Details Table

5.7.8 CARGO DETAILS TABLE

32

Table Name : cargodet

Primary Key : Cargoid

Foreign Key : Agentid, Portid, Shipid

Field Name Data Type Description

Cargoid Int(10) Cargo id number

Agentid Int(5) Agent id

Portid int(10) Cargo delivery Port id

Shipid int(10) Ship id

Billoflade Varchar(10) Bill of lading Agreement

Dwt Int(10) Dead weight

Lwt Int(10) Light weight

Table 5.7.8 Cargo Details Table

5.7.9 PORT OF CALL LIST TABLE

33

Table Name : Pcldet

Primary Key : PCLid

Foreign Key : Shipid, SSN

Field Name Data Type Description

PCLid Int(10) PCL id

Shipid Varchar(20) Ship Number

Nationality Varchar(20) Nationality

Supervisor Varchar(100) Supervisor Name

Start Varchar(50) Start From

End Varchar(50) End Place

Previous Varchar(50) Previous Port

Next Varchar(50) Next Port

Visited Integer Ports Visited

To Go Integer Ports to go

Cancelled Integer Ports Cancelled

Reason Varchar(100) Cancelled Reason

Arrived Datetime Arrived Date

Departed Datetime Arrived Time

SSN Int(10) Security Number

Table 5.7.9 Port of Call List Table

5.7.10 NOON MESSAGE TABLE

34

Table Name : Noonmsgdet

Primary Key : Noonid

Foreign Key : Shipid, Portid, Agentid, SSN

Field Name Data Type Description

Noonid Int(10) Noon id

Shipid Int(5) Shipid

Date DateTime Report Date

Curr Lat Varchar(50) Latitude

Curr Long Varchar(50) Longitude

From Varchar(20) From Position

Till Ptn Varchar(20) Till Position

Tot Hrs Datetime Total Hours

Engine rpm Int(10) Engine Rotation

Dist made Int(100) Distance Made

Hrs Rem Datetime Remaining Hours

Speed Int(100) Engine Speed

Fuel Used Int(100) Fuel Used

Rem Fuel Int(100) Remaining Fuel

Fuel other Int(100) Other Purposes

Fuel Back Int(100) Fuel Back

Wind Dir Varchar(20) Wind Direction

Wind Force Int(10) Wind Force

Bcargo Int(10) Basic Cargo Wt

Dcargo Int(10) Displacement Carg

Acargo Int(10) After Displacement

Air temp Varchar(20) Air Temperature

Sea Temp Varchar(20) Sea Temperature

Table 5.7.10 Noon Message Table

5.8 INPUT DESIGN

35

Input design is the method by which valid data are accepted from the user. The

valid data turn is stored as operational data in the database. Incorrect input data are the

most common cause of errors in the data processing. The input design is carried out in

such a way that the input screens are user friendly. The goals of designing input design

are to make input data entry as easy and error free. Input screen takes care to filter the

valid data from being becoming an operational data at data entry phase.

This is achieved by providing proper checks and validation procedures and

certain features to users. Input design is the part of the overall system design that

careful attention and is the most expensive phase. It is the point of most contact for the

users with the system and so it is prone to errors.

Objectives of Input Design

Produce close effective method input

High level accuracy

Free of ambiguity

Several Stages of Input Design

Data recording

Data verification

Data correction

Transmitting data to the system

The input design involves in converting the originated inputs into a system

based format. The aim of input design is to make the data entry easier, logical error

free. It helps to filter errors in the input data or otherwise it would enter into the

database. It involves procedures for capturing data, verifying it and then passing them

on to the further processing. After choosing the input medium, attention is given to the

careful design of the input stages for error handling and validation procedures.

5.9 OUTPUT DESIGN

36

The output design defines the output required and the format in which it is to be

produced. Care must be given to present the right information. The outputs generated

can be classified into three main categories:

Screen Output

Output to be stored as files in storage media.

Hardcopy of the output.

The screen output displays the generated output on the screen. The results of

most of the queries are displayed on the screen. The provision of generated output to be

stored in the file is for future reference and to take hard copies of the same and it is

used to provide the information to the management and when ever situation demands.

Sample report is referred in appendix.

The output is the most important and direct source of information to the user.

Efficient, output design should improve the systems relationship with the user and

helps in decision making. A major form of output is a hard copy from the printer.

Printouts should be designed around the output requirement to the user. The standard

that is maintained for output design is clear. Output provides a permanent copy of the

results for the later consultation.

CHAPTER 6

37

SYSTEM TESTING

Software testing is the process used to help identify the correctness,

completeness, security and quality of developed software.It is the process of checking

whether the developed system is working according to the original objectives and

requirements. Testing of the application has to be done at various stages of

development of the application to find and fix bugs at an earlier stage and get an error

free, high quality product as output of the process.

6.1 UNIT TESTING

A unit test is a procedure used to validate that a particular module of source

code is working properly. The test case is written for all functions and methods so that

whenever a change causes a regression, it can be quickly identified and fixed. Unit

testing is done to test and validate the functionality defined for each screen.

6.2 INTEGRATION TESTING

Integration testing is the phase of software testing in which individual software

modules are combined and tested as a group. Integration testing takes as its input

modules that have been checked out by unit testing, groups them in larger aggregates,

applies tests, and delivers as its output the integrated system ready for system testing.In

order to ensure that links across screens within a sub-system or module are established

properly, an integration/link testing is to be done. Link testing will not cover

functionality across different sub-systems but ensures the navigation between screens.

6.3 USER INTERFACE TESTING

38

The tests are designed to include the following:

Data displayed is properly intended.

Page conforms to standard layout.

All default values are displayed properly.

Dates are displayed in correct format.

6.4 TEST CASES

39

UNIT TEST LOG

PROJECT NAME: NAUTICAL TELEMATICS SYSTEM

Screen name: Login Details Page

Object

Name

Test

Id

Test Case

Description

Action Expected

Result

Actual

Results

Status

User name Tc001 To check if the

usernames are valid

and methods to verify

username validation

are available.

Type

user

name in

text box

The unique user

name should be

available in

database otherwise,

error message

should be

displayed.

Same as

expected

PASS

Password Tc002 To check if the

password does not

appear to the user as

it is being typed and

methods to verify

password validation

are available.

Type

password

in

password

box.

Password should

be available in

database otherwise,

error message

should be

displayed.

Same as

expected PASS

Submit Tc003 To check the

username and

password are

available based on the

type in the database

and if authentic move

over to user page.

Click on

Ok

button

Home page of the

appropriate user /

error message

stating invalid

username or

password

Same as

expected PASS

Table 6.4.1 Test Cases for Login

UNIT TEST LOG

40

PROJECT NAME: NAUTICAL TELEMATICS SYSTEM

Screen name: Registration Details Page

Object

Name

Test Id Test Case

Description

Action Expected

Result

Actual

Results

Status

Search

Type

Tc101 To check if the type

of search is selected

and the

corresponding details

are available

Select

from the

drop down

list box

Based on the selected

value the details

should be retrieved

from the database and

should be displayed.

Same as

expected

PASS

Search

Details

Tc102 To check whether the

details displayed

based on the type of

search chosen by the

user

Select

from the

drop down

list box of

search

Based on the type of

search the details

should be retrieved

from the database and

should be displayed.

Same as

expected PASS

Signup Tc103 To check whether the

personal details of the

user given gets

inserted into the

database

Click on

ok button

The personal details

given by the user

should get inserted in

the database and also

perform validation

for wrong inputs

Same as

expected

PASS

Send

Mail

Tc105 To check whether the

mail has been send.

Click on

send mail

button

Based on the selected

employee the mails

have to be sent.

Same as

expected PASS

Table 6.4.2 Test Cases for Registration

CHAPTER 7

41

SYSTEM IMPLEMENTATION

7.1 IMPLEMENTATION

Implementation is a process of converting the software developed in the

development environment to its operational environment. The developed software

undergoes many changes in the operational environment in terms of hardware and

software specification .The software should be developed to accommodate changes that

could happen during the post implementation period. The profiling is done to ensure

that the system works accurately and effectively before the live operations commences.

The proper implementation involves the conversion of critical files to the operational

environment, ensures that they are error free, and minimizes the maintenance task.

The Implementation Plan Consists of the Following

Testing the developed system with sample data.

Direction and correction of errors.

Making necessary changes in the system

Checking the reports with that of the existing system

Training and involvement of the user personal.

The two major task of preparing for implementation are educating and training

the users and testing of the system.

CHAPTER 8

42

CONCLUSION & FUTURE ENHANCEMENTS

8.1 CONCLUSION

The Nautical Telematics System project is to computerize the manual acting.

It developed in the conventional style of ASP.NET with the help of back end tool as

Sql. This system helps the marine company to keep track of the marine anywhere at

any time. Moreover this system is user friendly .The data manipulation by the

administrator also can be done when ever needed. A good amount of user-friendly

features have been incorporated into the system for the user to achieve maximum

benefit. Further expansion of the system also can be done in future if needed. The

application can be enhanced in future with the needs of the organization since Sql is the

backend and is portable. The database and the information can be update to the latest

forthcoming versions.

8.2 FUTURE ENHANCEMENTS

There are also possibilities for enhancing and further developing the project

with customized reports according to the latest information’s and needs of the

company. Thus the system can be altered in accordance with the future requirements

and advancements. System performance evaluation must be monitored not only to

determine whether or not they perform as plan but also to determine if they should have

to meet changes in the information needed for the company.

CHAPTER 9

43

APPENDIX

9.1 SOURCE CODE

Cargo Agent Registration

using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.Data.SqlClient;

public partial class Cargo_Agent : System.Web.UI.Page

{

SqlConnection con = new SqlConnection("database = nts;server=.;uid=sa");

//Database Connectivity

SqlCommand cmd = new SqlCommand();

SqlDataAdapter da = new SqlDataAdapter();

DataTable dt = new DataTable();

DataSet ds = new DataSet();

SqlDataReader dr;

public void msgbox(string msg)

{

Response.Write("<script type='text/javascript'>alert('" + msg + "')</script>");

}

protected void Page_Load(object sender, EventArgs e)

{

}

44

protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{

}

protected void Button2_Click(object sender, EventArgs e)

{

con.Open();

cmd.Connection = con;

try

{

cmd.CommandText = "insert into cargodet values('" + TextBox3.Text + "','" +

TextBox2.Text + "','" + TextBox1.Text + "','" + TextBox7.Text + "','" + TextBox8.Text

+ "','" + DropDownList2.SelectedItem + "','" + TextBox6.Text + "','" + TextBox5.Text

+ "','" + DropDownList3.SelectedItem + "')";

if ((TextBox3.Text == "") || (TextBox2.Text == "") || (TextBox1.Text == "") ||

(TextBox7.Text == "") || (TextBox8.Text == "") || (TextBox6.Text == "") ||

(TextBox5.Text == ""))

{

TextBox8.Text = "";

msgbox("NULL VALUES NOT ALLOWED...");

}

else

{

cmd.ExecuteNonQuery();

msgbox("DATA SAVED SUCCESSFULLY...");

}

}

catch (Exception)

{

msgbox("ERROR OCCURED,UNABLE TO SAVE");

}

finally

{

}

45

con.Close();

}

protected void Button4_Click(object sender, EventArgs e)

{

Response.Redirect("Ship Registration.aspx");

}

protected void Button3_Click(object sender, EventArgs e)

{

Response.Redirect("Port Registration.aspx");

}

protected void Button8_Click(object sender, EventArgs e)

{

con.Open(); //Update

cmd.Connection = con;

try

{

cmd.CommandText = "update cargodet set agentname ='" + TextBox3.Text +

"',address='" + TextBox2.Text + "',phoneno='" + TextBox1.Text + "',website='" +

TextBox7.Text + "',state='" + DropDownList2.SelectedItem + "',fax='" +

TextBox6.Text + "',emailid='" + TextBox5.Text + "',country='" +

DropDownList3.SelectedItem + "' where agentid='" + TextBox8.Text + "'";

if ((TextBox3.Text == "") || (TextBox2.Text == "") || (TextBox1.Text == "") ||

(TextBox7.Text == "") || (TextBox8.Text == "") || (TextBox6.Text == "") ||

(TextBox5.Text == ""))

{

TextBox8.Text = "";

msgbox("NULL VALUES NOT ALLOWED...");

}

else

{

cmd.ExecuteNonQuery();

msgbox("DATA UPDATED SUCCESSFULLY...");

}

46

}

catch (Exception)

{

msgbox("ERROR OCCURED,UNABLE TO UPDATE ");

}

finally

{

}

con.Close();

}

}

Employee Registration

using System;

using System.Data;

using System.Configuration;

using System.Collections;

using System.Web;

using System.Web.Security;

using System.Web.UI;

using System.Web.UI.WebControls;

using System.Web.UI.WebControls.WebParts;

using System.Web.UI.HtmlControls;

using System.Data.SqlClient;

using System.Collections.Generic;

using System.ComponentModel;

using System.Drawing;

using System.Text;

public partial class Employee_Registration : System.Web.UI.Page

{

SqlConnection con = new SqlConnection("database = nts;server=.;uid=sa");

//Database Connectivity

47

SqlCommand cmd = new SqlCommand();

SqlDataAdapter da = new SqlDataAdapter();

DataTable dt = new DataTable();

DataSet ds = new DataSet();

SqlDataReader dr;

public void msgbox(string msg)

{

Response.Write("<script type='text/javascript'>alert('" + msg + "')</script>");

}

protected void Page_Load(object sender, EventArgs e)

{

con.Open();

cmd.Connection = con;

cmd.CommandText = "select shipsign from shipdet";

dr = cmd.ExecuteReader();

if (!IsPostBack)

{

while (dr.Read())

{

DropDownList4.Items.Add(dr.GetValue(0).ToString());

}

}

con.Close();

}

protected void ImageButton1_Click(object sender, ImageClickEventArgs e)

{

Response.Redirect("Ship Registration.aspx");

}

protected void Button3_Click(object sender, EventArgs e)

{

cmd.Connection = con;

con.Open(); //Insert in to Database

try

48

{

cmd.CommandText = "insert into empdet values('" +

DropDownList7.SelectedItem + "','" + DropDownList9.SelectedItem + "','" +

TextBox8.Text + "','" + DropDownList8.SelectedItem + "','" + TextBox7.Text + "','" +

TextBox13.Text + "','" + TextBox10.Text + "','" + DropDownList4.SelectedItem + "','"

+ DropDownList6.SelectedItem + "','" + DropDownList5.SelectedItem + "','" +

DropDownList3.SelectedItem + "','" + TextBox9.Text + "','" + TextBox14.Text + "','" +

TextBox6.Text + "','" + TextBox1.Text + "','" + DropDownList2.SelectedItem + "','" +

DropDownList1.SelectedItem + "','" + TextBox5.Text + "','" + TextBox2.Text + "','" +

TextBox3.Text + "')";

if ((TextBox8.Text == "") || (TextBox7.Text == "") || (TextBox13.Text == "") ||

(TextBox10.Text == "") || (TextBox9.Text == "") || (TextBox14.Text == "") ||

(TextBox6.Text == "") || (TextBox1.Text == "") || (TextBox5.Text == "") ||

(TextBox2.Text == "") || (TextBox8.Text == "") || (TextBox3.Text == ""))

{

TextBox10.Text = "";

msgbox("NULL VALUES NOT ALLOWED");

}

else

{

cmd.ExecuteNonQuery();

msgbox("DATA SAVED SUCCESSULLY...");

}

}

catch (Exception)

{

msgbox("ERROR OCCURED,UNABLE TO SAVE");

}

finally

{

}

9.2 SCREEN SHOTS

49

9.2.1 Login Page

Figure 9.2.1 Login Page

9.2.2 Employee Registration

50

Figure 9.2.2 Employee Registration Page

9.2.3 Port Registration

51

Figure 9.2.3 Port Registration Page

52

9.2.4. Cargo Agent Registration

Figure 9.2.4 Cargo Agent Registration Page

53

9.3.5 Ship Registration

Figure 9.3.5 Ship Registration Page

54

9.3.6 Pre Arrival Notification

Figure 9.3.6 Pre Arrival Notification Page

9.3.7 Departure Message

55

Figure 9.3.7 Departure Message Page

9.3.8 Noon Message

56

Figure 9.3.8 Noon Message Page

CHAPTER 10

57

REFERENCES

BOOK REFERENCES

C# Programming Bible: Wiley Publications by Jeff Ferguson, Brian Patterson,

Jason Beres, Pierre Boutquin, and Meeta Gupta.Website:www.wileyindia.com

Software Engineering A Practitioner's Approach: TATA McGraw Hill

Series Fifth Edition by Roger S.Pressman, Ph.D.

Software Testing Guide Book: SofTReL Publications by Ajitha Kruthiventy,

Amrish Shah, Ashna Datye, Bharathy J, Deepa M G, James M, Jayapradeep J,

Jeffin Jacob M.

The Complete Reference Visual Basic 6: TATA McGraw Hill Edition by

Noel Jorke.

The Unified Modeling Language User Guide: Addison Wesley, 1998 by

Grady Booch, James Rumbaugh and Ivar Jacobson.Website:www.uml.org.

Designing using Asp.net and C# Programming: Cegonsoft Ltd & Maze Net

Solutions.

Asp.net Cookbook: O’Reilly publication, August 2004 by Michel A. Kittel,

Geooffrey T. LeBlond.

Developing Web Applications with VB.net and Asp.net: Wiley Computer

publishing, 2002 by John Alexander, Billy Hollis.

WEB REFERENCES

http://www.dotnetspider.com.

http://www.w3schools.com.

http://www.codeproject.com.

http://www.uml.org.

http://forums.asp.net

http://www.gotdotnet.com

58