Cargo Logistics

3. SYSTEM ANALYSIS
3.1 STUDY OF CURRENT SYSTEM
Before deciding the scope of the project we have identified many other existing
logistic website such as Maersk Line, SAS Cargo and Lufthansa cargo. Features
that we have noticed about their applications are listed below.

1. Provides facility to ask for quotation without registration.

 Cargo Logistics

2. Provide functionality of booking after registration.

3. Allows customer to select route of their choice.

3.2 PROBLEMS AND WEAKNESS OF CURRENT SYSTEM

Although these applications provide a simple way of placing an order and
quotation following are the remedies of current scenario.

1. Customer may not be aware about all logistic service providers.

 Cargo Logistics

2. Chances thatlogistic service provider known to customer has an access to

all the countries across the world. In such case application fails to satisfy
customers need.
3. There is no such facility wherein a customer can elect transporters
providing services at lowest of the rates. In such cases customers are
forced to pay the desired amounts.

3.3 REQUIREMENT OF NEW SYSTEM

 Cargo Logistics

The new system is required to overcome these problems and to provide a

complete logistic solution where customers can satisfy their needs. The features
that overcome the problems of current scenario are listed below.

1. Provides a portal of a logistic service provider so the customers can select

one transporter of their desire.
2. Customers have the entire list of available route that contain origin and
destination so the client can select route that helps in transporting goods
faster and efficiently.
 Cargo Logistics

3. Customer can see charges of different services of different companies

which help in getting the best deal.

3.4 FEASIBILITY STUDY:

Feasibility study is carried out whenever there is complex problem or opportunity.
it is in fact a preliminary investigation which emphasizes the look before you
leap approach to any important project. A feasibility study is undertaken to
 Cargo Logistics

determine the possibility of either improving existing system or developing a

completely new system. Reasons behind feasibility study are

1. Answer the question whether a new system is to be installed or not?

2. Determine the potential of the existing system.
3. Improve the existing system.
4. Know what should be embedded in the new system.
5. Define the problems and objectives involved in a project.
6. Avoid costly repairs at a later stage when the system is implemented.
7. Avoid crash implementation of a new system.
 Cargo Logistics

8. Avoid the hardware approach.

Technical Feasibility:

Technical feasibility determines whether the work for the project can be done by
current technology, current procedure and available personal. It happens
sometime that after the completion of project new technology arises and customer
needs product to run according to that technology. So Cargo Logistics needs a
large amount of database storage for booking request, available route etc. To
 Cargo Logistics

achieve these goals and to design this application we require following hardware
and software.

Software Platform:

Microsoft Windows XP or later on.

Intel Pentium 3 processor and later on.

512MB RAM (Minimum)

 Cargo Logistics

4 GB Hard disk (Minimum)

Development Tools:

Microsoft Visual Studio 2010

Software Platform:

Web Server: IIS 7

 Cargo Logistics

Database Server: SQL server 2008

Economic Feasibility

The purpose of the economic feasibility assessment is to determine the positive

economic benefits to the organization that the proposed system will provide. It
includes quantification and identification of all the benefits expected. This
assessment typically involves a cost/ benefits analysis.

Behavioral Feasibility
 Cargo Logistics

Behavioral feasibility defines how user responds to the new technology. Motive
behind the behavioral feasibility is to know whether the newly introduced system
is easy to use or not and can every user operate the system easily.

Implementation feasibility

Implementation feasibility defines whether the new system can easily be

implemented in current technology platform.
 Cargo Logistics

3.5 REQUIREMENTS VALIDATION

Name should contain only alphabets

Date format should be DD/MM/YYYY

Email ID must have @ and .

Phone number should contain only digits 1-9.

 Cargo Logistics

Password must be match with re-enter password.

Username must be unique.

 Cargo Logistics

3.6 FUNCTION OF SYSTEM

The system aims at developing a web application for mainly two types of users:-

Logistic Service Provider and Clients (End or ordinary users)

Client

New customer can register him/herself into website.

 Cargo Logistics

Customer can ask for quotation for the goods to be sent.

Order can be placed, edited or deleted online.
Receives documents related to order.

Logistics Service Provider

Transportation Company can register itself to the system.

 Cargo Logistics

Updates schedule of their routes, charges for different supplementary

services such as documentation, packaging, insurance.
Receives quotation request from customers
Receives orders from customers.
Send message on confirmation of order and when goods are actually
delivered.
 Cargo Logistics

3.6.1 Use Cases

Use case diagram shows interaction of user with the system. It

indicates what kind of functionalities user can perform on the
system.

Actors:-Actor is an external factor or user who interacts with the

system.
 Cargo Logistics

Use Case:-Set of scenarios that describes how actor uses the system.

Use Case Diagrams:

Cargo Logistics
 Cargo Logistics

Figure 3.6.1 Use Case (Client Management)

Cargo Logistics
 Cargo Logistics

Figure 3.6.2 Use Case (Transporter Management)

Cargo Logistics
 Cargo Logistics

Figure 3.6.3 Use Case (Order Management)

Cargo Logistics
 Cargo Logistics

Figure 3.6.4 Use Case (Freight Management)

3.7 DATA MODELLING

 Cargo Logistics

Data modeling is a process used to define and analyze

data requirements needed to support the business processes within the scope
of corresponding information systems in organizations. Therefore, the process of
data modeling involves professional data modelers working closely with business
stakeholders, as well as potential users of the information system.

For any application database is crucial part. Bad data modelling leads to poor
design of database design which ultimately results in poor application.
 Cargo Logistics

3.7.1 E-R Diagram

In software engineering, an entityrelationship model (ER model)

is a data model for describing the data or information aspects of a
business domain or its process requirements, in an abstract way that
lends itself to ultimately being implemented in a database such as
a relational database.
 Cargo Logistics

An entity-relationship model is a systematic way of describing and

defining a business process. The process is modeled as components
(entities) that are linked with each other byrelationships that express
the dependencies and requirements between them, such as: one
building may be divided into zero or more apartments, but one
apartment can only be located in one building. Entities may have
various properties (attributes) that characterize them. Diagrams
created to represent these entities, attributes, and relationships
 Cargo Logistics

graphically are called entityrelationship diagrams.An ER model is

typically implemented as a database. In the case of a relational
database, this stores data in tables, which represent the entities.
Some data fields in these tables point to indexes in other tables;
such pointers represent the relationships.

Three types of data models schemas are used in software

engineering
 Cargo Logistics

Conceptual Model

Logical Data Model

Physical Data Model

E-R Notations
Cargo Logistics

Entity

Relationship
Cargo Logistics

Attribute

Multivalued Attribute
Cargo Logistics

Key Attribute
Cargo Logistics

Composite Attribute
 Cargo Logistics

Weak Entity

E-R Diagram:
Cargo Logistics
 Cargo Logistics

Figure 3.7.1 E-R Diagram

3.7.2. Activity Diagram

Activity diagrams are graphical representations of workflows of

stepwise activities and actions with support for choice, iteration and
concurrency. In the Unified Modeling Language, activity diagrams
are intended to model both computational and organizational
 Cargo Logistics

processes (i.e. workflows) Activity diagrams show the overall flow

of control.
Cargo Logistics
 Cargo Logistics

Figure 3.7.2 Transporter Registration

Cargo Logistics
Cargo Logistics

Figure 3.7.3 Add Route

Cargo Logistics
Cargo Logistics
 Cargo Logistics

Figure 3.7.4 Activity Diagram (Booking Request)

Cargo Logistics
 Cargo Logistics

Figure 3.7.5 Activity Diagram (Booking Confirmation)

Cargo Logistics
 Cargo Logistics

Figure 3.7.6 Activity Diagram (Quotation Request)

3.7.3 Data Dictionary

The various table created in the projects in SQLServer are as

shownbelow. The fields with their data types and the description are
 Cargo Logistics

given. These tables are created according to the entities in the

project. Suppose there are various screens in the project. Thus a table
is formed which contains various information about all the screens.
Similarly tests are performed on the modules. Thus a table is created
in which all the information is stored about the various tests
performed in the module.

This helps when a query is to be fired in the SQL Server.Suppose we

want information about the bugs the query can be generated for the
 Cargo Logistics

bug severity table and subsequently the required fields can be

fetched into the forms of the projects.

Here are the tables used in the project, with their primary and
foreign keys specified and their relationship.

1) Login Details: Stores the information about user to get login.

 Cargo Logistics

Field Name Data Type Allow Null Comment

Email_id Varchar(30) No ID of client/transporter for login

Password Varchar(20) No Login password

User_type Varchar(30) No To check If it is client/transporter

Type_of_freight Varchar(20) Yes To check whether airline or

 Cargo Logistics

shipping company

2) Customer Details:It stores information about the customer who request for
booking and also provides information about company details.

Field Name Data Type Allow Null Comment

 Cargo Logistics

Cust_id Int No ID of client

Comp_name Varchar(30) No Name of Company

Comp_name Varchar(30) Yes Type of company

 Cargo Logistics

Address Varchar(30) No Address of company

City Varchar(30) No Name of city

Country Varchar(30) No Name of country

 Cargo Logistics

Pin_code Varchar(20) No Pin code of area

Cp_name Varchar(30) No Contact person name

Cp_phone Varchar(30) No Phone no of contact person

 Cargo Logistics

Cpalt_mail Varchar(30) Yes Email id of contact person

Fax_no Varchar(30) Yes Faxno of contact person

Email_id Varchar(20) Yes Email of contact person

 Cargo Logistics

3) Booking Details: Stores information about booking request and its status.

Field Name Data Type Allow Null Comment

Transport_id Int Yes ID of client

Cust_id Varchar(50) No Name of Company

 Cargo Logistics

Booking_id Varchar(10) No Type of company

Type_of_freight Varchar(20) Yes Address of company

Source_add Varchar(100) No Address from where goods

need to send

Source_country Varchar(30) No Country from where goods

will be sent
 Cargo Logistics

Source _city Varchar(30) No City from where goods will

be sent

Source_pincode Varchar(20) No City from where goods will

be sent

Des_add Varchar(100) Yes Address where goods will

be sent
 Cargo Logistics

Des_country Varchar(30) Yes Country where goods will

be sent

Des_city Varchar(30) Yes City where goods will be

sent

Des_pincode Varchar(20) No Pincode of destination

Type_of_container Varchar(50) No Type of container required

 Cargo Logistics

by client

Insurance Varchar(10) No Insurance required or not

Packaging Varchar(10) No Packaging needed or

Status Varchar(10) No Indicate whether the order

has been confirmed by
transporter or not.
 Cargo Logistics

4) Goods Details: Stores information of goods at the time of booking placed by

customer.

Field Name Data Type Allow Null Comment

Goods_id Varchar(20) No ID of goods

 Cargo Logistics

Booking_id Varchar(10) No Booking id associated with

goods

Type_of_goods Varchar(50) No Type of goods (chemical,

garments)

Quantity Int No Quantity of goods

Value Float No Value of goods for

 Cargo Logistics

insurance purpose

Height Float No Height of goods

Length Float No Length of goods

Weight Float No Weight of goods

Volume Float no Total volume of goods

 Cargo Logistics

5) Consigner Details: Information about the receiving party is stored in this table.

Field Name Data Type Allow Null Comment

Booking_id Varchar(10) No ID of client

Consigner_id Int No Name of Company

 Cargo Logistics

Commodity_name Varchar(50) No Type of company

Country Varchar(30) Yes Address of company

City Varchar(30) No City of commodity

Address Varchar(100) No Address of commodity

Pin_zip_code Varchar(30) No Pin/zip code of address

 Cargo Logistics

Cp_name Varchar(50) No Name of contact person

Phone_no Varchar(30) No Phone no of contact

person

Email_id Varchar(50) No Email Id of contact

person

Fax Varchar(50) Yes Fax no of contact person

 Cargo Logistics

6) Payment Details: Contains transaction of amount done at the time of booking.

Field Name Data Type Allow Null Comment

Cust_id Varchar(50) No ID of client who made

the payment
 Cargo Logistics

Date Date No Date on which payment

is made

Payment_mode Varchar(50) No Payment mode like debit

card, credit card or net
banking

Transaction_id Int No Transaction ID

 Cargo Logistics

generated on payment

Bank Varchar(50) No Bank through which

payment is made

Amount Int No Amount paid

Card_no Int No Card number of card

holder
 Cargo Logistics

Card_holder_name Varchar(50) No Name of card holder

7) Country Master: List of all the countries around the world.

Field Name Data Type Allow Null Comment

 Cargo Logistics

Country_Id Varchar(5) No ISO code of country

Country_name Varcar(50) No Name of country

8) City Master: List major cities around the world.

 Cargo Logistics

Field Name Data Type Allow Null Comment

Country_Id Varchar(5) No ISO code of country

City_name Varcar(50) No Name of the city

9) Airport Master: List of major airports around the world.

 Cargo Logistics

Field Name Data Type Allow Null Comment

Country_Id Varchar(5) No ISO code of country

Airport_name Varcar(80) No Name of Airport

10) Port master: List of all the ports around the world.
 Cargo Logistics

Field Name Data Type Allow Null Comment

Country_Id Varchar(5) No ISO code of country

Port_name Varcar(50) No Name of Company

11) Airline Details:List of all airlines.

 Cargo Logistics

Field Name Data Type Allow Null Comment

Airline_id(primary Int No Unique ID of each Airline

key)

Company_name Varchar(30) No Name of airline

Country Varchar(30) No Country associated with

airport
 Cargo Logistics

City Varchar(30) No City associated with airport

Address Varchar(30) No Address of airport

Pin_zip_no Varchar(30) No Pin/zip code of airport

Cp_name Varchar(30) No Name of contact person of

Airline
 Cargo Logistics

Phone_no Varchar(30) No Phone no of contact person

Alteml_id Varchar(30) Yes Alternate email id of

contact person

Fax_no Varchar(30) No Fax number

Email_id Varchar(30) No Login ID for Airline

company
 Cargo Logistics

12) Air Route: List of all available routes from all the logistic service provider.

Field Name Data Type Allow Null Comment

Airline_id Int No Unique ID of Airline

Route_id(primary Varchar(10) No Unique ID of route

 Cargo Logistics

key)

O_cntry_id Varchar(5) No Origin country of route

Origin Varchar(100) No Origin airport of route

Int_des1_id Varchar(5) No Intermediate country of

route
 Cargo Logistics

Int_dest1 Varchar(100) No Intermediate airport

Charges Float No Transportation charges

from origin to
intermediate destination

Int_des2_id Varchar(5) No Intermediated destination

2
 Cargo Logistics

Int_dest2 Varchar(100) No Intermediate Airport 2

Charges1 Float No Transportation Charges

from intermediate
destination1 to 2

Dest_cntry_id Varchar(50) No Destination country of

route
 Cargo Logistics

Destination Varchar(100) No Destination airport

Charges 2 Float No Charges from int_dest2 to

destination

13) Avb_a _country: List of all the countries where service is available.
 Cargo Logistics

Field Name Data Type Allow Null Comment

Country_Id Varchar(5) No ISO code of country

Country_name Varcar(50) No Name of Country

 Cargo Logistics

14) Charge Airline: Stores information about different type of charges of all the
airlines.

Field Name Data Type Allow Null Comment

Airline_id Int No Unique ID of airline

Pkg_chrg Int No Packaging charges

 Cargo Logistics

Doc_chrg Int No Documentation charges

Insr_chrg Int No Insurance charges

Max_allowed_wt Int No Maximum non chargeable

weight

Chrg_wt Int No Charges on extra weight

 Cargo Logistics

15) Shipping company details: Master table for all the shipping companies.

Field Name Data Type Allow Null Comment

Ship_co_id Int No Unique ID of shipping

company
(primary key)
 Cargo Logistics

Company_name Varchar(30) No Name of Company

Country Varchar(30) No Country associated with

Port

City Varchar(30) No City associated with Port

Address Varchar(30) No Address of Port

 Cargo Logistics

Pin_zip_no Varchar(30) No Pin code of port

Cp_name Varchar(30) No Name of contact person

Phone_no Varchar(30) No Phone number of contact

person

Alteml_id Varchar(30) Yes Alternate Email ID

 Cargo Logistics

Fax_no Varchar(30) No Fax number

Email_id Varchar(30) No Login ID for Shipping

company

16) Sea route: Master table of all the routes by all the shipping company.
 Cargo Logistics

Field Name Data Type Allow Null Comment

Ship_co_id Int No Unique ID of client

Route_id(primary Varchar(10) No Unique ID of route

key)

O_date Date No Departure Date

 Cargo Logistics

O_country_id Varchar(5) No Origin country of route

Origin Varchar(100) No Origin Port of route

Int_des_cntry_1 Varchar(5) No Intermediate country of

route

Int_dest_1 Varchar(100) No Intermediate Port

 Cargo Logistics

Charges Float No Transportation charges

from origin to
intermediate destination

Int_des_cntry2 Varchar(5) No Intermediated destination

2

Int_dest_2 Varchar(100) No Intermediate Port 2

 Cargo Logistics

Charges1 Float No Transportation Charges

from intermediate
destination1 to 2

D_date Date No Arrival date

Des_cntry Varchar(50 No Destination country of

route
 Cargo Logistics

Destination Varchar(100) No Destination Port

Charges2 Float No Transportation Charges

from intermediate
destination2 to destination

17) Avb_sea_country: List of countries where service is available by shipping

company.
 Cargo Logistics

Field Name Data Type Allow Null Comment

Country_Id Varchar(5) No ISO code of country

Country_name Varcar(50) No Name of country

 Cargo Logistics

18) Chrg_Ship: Master table that stores information of different type of charges
of all the shipping company.

Field Name Data Type Allow Null Comment

Ship_co_id Int No Unique ID of Shipping

company

Pkg_chrg Int No Packaging charges

 Cargo Logistics

Doc_chrg Int No Documentation charges

Ins_chrg Int No Insurance charges

Max_allowed_wt Int No Maximum non chargeable

weight

Chrg_wt Int No Charges on extra weight

 Cargo Logistics

19) Complaint Table: Stores complains made by client.

Field Name Data Type Allow Null Comment

Date Date No Date on which complaint

 Cargo Logistics

is registered

Type_of_freight Varchar(50) No Whether the transporter is

airline or shipping
company

Transporter Varchar(50) No Name of company

Booking_id Varchar(10) No Booking ID associated

 Cargo Logistics

with complaint

Complaint_type Varchar(30) No Type of complaint for

example delay, damaged
etc

Description Varchar(500) No Description of complaint

 Cargo Logistics

20) Confirm_booking: Booking that has been confirmed is stored in the table
and status changes when customers make payment.

Field Name Data Type Allow Null Comment

Confirmation_id Int No Confirmation ID of booking.

Confirmation_date Date No Date on which order was

confirmed.
 Cargo Logistics

Dispatch date Date No Date on which goods will be

dispatched.

Booking_id Varchar(10) No Booking ID associated with

complaint

Transporter_id Varchar(50) No ID of a transporter who is

responsible for order
 Cargo Logistics

Type Varchar(50) No Whether transporter in airline or

shipping company

Client_id Int No ID of client who had placed an

order

Is_viewed_or_not Int No Whether the confirmation

message is viewed by customer or
 Cargo Logistics

not.

21) Quotation Request: Master table for all the quotation request.

Field Name Data Type Allow Null Comment

 Cargo Logistics

Request_no Int No Request Number of

quotation

Type_of_freight Varchar(20) No Whether the transporter is

airline or shipping
company

Transporter Varchar(50) No Name of company

 Cargo Logistics

Origin Varchar(10) No Origin of order

Destination Varchar(30) No Location where goods is to

be sent

Type_of_goods Varchar(20) No Type of goods such as

machinery, electronics etc.

Weight Float No Weight of goods

 Cargo Logistics

Volume Float No Volume of goods

Company Varchar(50) No Quotation request maker

Contact_person Varchar(50) No Contact person

Email_id Varchar(50) No Email ID of contact person

Phone_no Varchar(20) No Phone number of contact

 Cargo Logistics

person

Fax_no Varchar(20) Yes Fax number of contact

person
 Cargo Logistics

3.8 FUNCTIONAL AND BEHAVIOURAL MODELLING

 Cargo Logistics

All functional models really do is describe the computational structure of the

system. On the other hand, this system even though it may have many Use
Cases should only have one functional model, yet this may be composed of
many functional diagrams. Furthermore, the activity of creating a functional
model is commonly known as functional modelling.

Behavioral models are used to describe the overall behavior of a system. Two
types of behavioral model are:
 Cargo Logistics

Data processing models that show how data is processed as it moves

through the system.
State machine models that show the systems response to events.

These models show different perspectives so both of them are required to describe
the systems behavior.

3.8.1 Context Diagram and Data Flow Diagram

 Cargo Logistics

System context diagrams show a system, often software-based, as a

whole and its inputs and outputs from/to external factors.

System Context Diagrams represent all external entities that may

interact with a system. Such a diagram pictures the system at the
center, with no details of its interior structure, surrounded by all its
interacting systems, environments and activities. The objective of
the system context diagram is to focus attention on external factors
 Cargo Logistics

and events that should be considered in developing a complete set

of systems requirements and constraints.

System Context Diagrams are used early in a project to get

agreement on the scope under investigation. Context diagrams are
typically included in a requirements document. These diagrams
must be read by all project stakeholders and thus should be written
in plain language, so the stakeholders can understand items within
the document.
 Cargo Logistics

Level-0:
Cargo Logistics
 Cargo Logistics

Figure 3.8.1 Context Flow Diagram

Level-1 DFD:
Cargo Logistics
 Cargo Logistics

Figure 3.8.2 Data Flow Diagram for Booking (Level -1)

Cargo Logistics
 Cargo Logistics

Figure 3.8.3 Data Flow Diagram Quotation (Level-1)

Cargo Logistics
 Cargo Logistics

Figure 3.8.4 Route and charges update (Level-1)

3.9 MAIN MODULE OF THE SYSTEM

Client: Client is a person who is willing to send goods or who asks for quotation
to the logistic service provider.
 Cargo Logistics

Logistics Service Provider: It is an entity or commodity who provide logistic

services. It also contains process of updating routes , charges of different services.

Registration: Registration process contains providing necessary information for

successful registration in the system,

Booking: It comprises the entire process of booking including placing order,

response from logistic service provider, and payment.
 Cargo Logistics

Quotation: Quotation asking process includes simple quotation request.

Response of this is in the form of mail.