A PROJECT REPORT ON

“Shipping Management System”

Submitted in the partial fulfillment of the requirement for the

award of degree of

MASTER OF COMPUTER APPLICATION

Submitted by: Under the guidance of:

Gaurav Jain Mr. Shailesh Awasthi

0302914041 Sr.Project Leader
MIND Ltd. Noida
.

Submitted to:

KIET SCHOOL OF COMPUTER APPLICATION

KRISHNA INSTITUTE OF ENGINEERING & TECHNOLOGY, GHAZIABAD

UP TECHNICAL UNIVERSITY, LUCKNOW

1
 CERTIFICATE

This is certify that this project entitled “ Shipping Management

System” Which is being submitted by MR. GAURAV JAIN as the partial
fulfillment of the degree of MASTER OF COMPUTER APPLICATION,
U.P. Technical University, Lucknow for the academic year 2003 –
2006. This project is completed under the supervision of MOTHERSON
SUMI INfotech & DESIGN LTD..

INTERNAL EXAMINAR EXTERNAL EXAMINAR

Professor R. Radhakrishnan
Principal,
KIET School of Computer Applications,
Krishna Institute of Engineering and Technology

2
 DECLARATION

I, GAURAV JAIN, hereby declare that the report of the project entitled “
Shipping Management System” has not been presented as a part of
any other academic work to get any degree or certificate except to KIET
School of Computer Applications,Krishna Institute of
Engineering and Technology, Ghaziabad for the fulfillment of the
requirement of the award of degree of MASTER OF COMPUTER
APPLICATION.

Date:
Place: GAURAV JAIN

3
 ACKNOWLEDGEMENT

I would like to express my gratitude to Prof.Radha Krishanan(HOD) for all his

help & support and for guiding me to this Project .

My heartiest thanks to Mr. Arun Tripathi and my college staff Krishna Institute of
Engineering & Technology,Ghaziabad for providing me with an encouraging platform
to develop this project.They helped me in shaping my abilities towards a constructive
goal.

I would like to extend my sincere thanks to our Project Manager,Mr Shailesh

Awashti at Motherson Sumi INfotech and Design Ltd. For guiding me through
the toughest time and leading me to the end of tunnel. Mere words would not suffice
for amount of patience and tolerance he has showed while dealing with a novice like
me.

Thanking my family members and my friends will be to petty an effort .with no

intention of belittling their contribution, I just want to say that it is all their love and
blessings that keeps me going.
I also extend my apologies for any errors or omission ,which are solely my
responsibility.

GAURAV JAIN

4
COMPANY PROFILE
MothersonSumi INfotech and Designs Ltd. (MIND) enables Business Process Automation, Integration
and Optimisation by providing Information Technology Solutions. MIND primarily works in the
domains of manufacturing, transport and logistics, healthcare, education and e-governance. MIND is
technology partner with the following global software leaders: Microsoft (Gold Partner for E-
Commerce Solutions), Oracle and IBM.

MIND is a joint venture of the Sumitomo Wiring Systems Ltd., Japan (www.sws.co.jp, turnover USD
2.4 Billion) and the Motherson Group, India (www.motherson.com, turnover over USD 350 Million -
FY 2004-05).

MIND's headquarters and development centers are located in Noida (near New Delhi), India. MIND
is a CMM Level 5 and an ISO 9001:2000 certified company.

MIND since its inception in 2000 has emerged as a strong world class IT Company with projects
across the globe. MIND has multi-lingual software development capabilities including Japanese and
German.

MIND's projects around the globe

5
Our Vision

To be recognised Globally by our Clients as a preferred partner for Software Design and
Development, IT Services and Support.

Our Mission

To provide the most reliable and cost effective software and support services using appropriate
technologies and expertise and enhance our customers ability to serve their customers better.

Our Objectives

To be a ‘Tier One’ software services company in terms of customer preference - high level of
penetration and retention.

To be an employer of choice in the software industry.

PARTNERS/ALLIANCES >>
Technical Partners

MIND is focused on working with well-established, best-in-class companies to add value to their
offerings and to enhance our technology and products. We engage in a wide variety of alliances with
large and small companies to sustain growth and opportunity.

Enhancing and strengthening it's technical forefront MIND is,

Microsoft Gold Certified Partner

Member of Partner World For Developers (IBM)

6
Member of Oracle Partner Network

Table of Contents

1. Introduction
1.1 Abstract of Project
1.1.1 Title of the Project
1.1.2 Objective

1.2 Problem Specification/Need of Project

2. Feasibility Study
3. Software Requirement Specifications
3.1 Introduction
3.2 Selection of Technology/Specific
Requirements
4. Design
4.1 ER Diagram
4.2 Data Flow Diagram (0 & 1 Level)
4.3 Modules
4.4 Database
4.5 Input-Output form (Screen Layout)
5. Coding
6. Implementation/Technological Environment
7. Testing & Result
8. Enhancement
9. Limitations
10. Conclusion
11. Bibliography

7
 ABSTRACT

PROJECT TITLE……………SHIPPING MANAGEMENT SYSTEM

Modules:-

• PROFILE MANAGEMENT SYSTEM

 Record of Customer Company
 Record of Shipped Company
 Record of Company Branches
 Record of Company Employees

• ORDER MANAGEMENT SYSTEM

 Order Receiving
 Order Loading
 Order Delivery

• ACCOUNT MANAGEMENT SYSTEM

 Order Amount Transaction
 Calculate Employees Salary
 Salary Transaction

8
Introduction and overview of project

Introduction

The idea behind building “Shipping Management System” is to have an

automated system between Management and Employees with best co-ordination.
This system is to be built in such way that it should fulfill all the requirements of
Shipping industries to handle their business efficiently. System should be automated
because at present all the work is done by manually in MS Office. That is existing
system is not automated. But in the new system all the work is performs separately
fully automated and coordination between them. The new project is divided into four
parts.

Profile Management System-

In this system keep all the necessary information about the employees, Customer,
shipped company and branches.

Order Management System-

In this system take the order from Customer Company through the main-branch
and the company sub-branches. Branch manager are takes order and forward them
to main-branch. All order is collected on the main-branch and after that organized
them. Allorders that have same destination port and approximate same delivery date
are collect together and load on to the container. Also recorded that one container
has more then one orders product. And also maintain the record of no of containers
are available our company. Then containers aredelivered to the destination port.
After the receiving the full payment dispatching the goods to the shipped company.

Accounting System-

In this system calculate the fare of the transportation of the product accordind the
distance between the source port and destination port in per kilometer and also
calculate salary of employees on the basis of their basic salary, H.R.A, conveyance
allowance.

9
Report System-

In this system show all the reports of the system.

Problem Definition-

“ To analyze, design and develop the Shipping Management System for use
employee as well as management”.

Goals-

• System must benefit the employees

• System must benefit the management
• System should be fully automated
• System should be user friendly
• System should be secure
• System should be upgradable
• System should be easily maintainable
• System should be flexible
• System should be easily adoptable

Objective-

To design form and report, which must be user friendly

• To create and maintain database

• To create master database
• To assign different privileges to various users

Scope-

“Scope of the system is within the organization i.e. all users of the system are
employee and administrator of the company”. Administrator is authorized for

10
 access every form of the system but we give the authentication to the employee
to access authentic form.

Overview-

Project Title : Shipping Management System

Organization : Motherson Sumi INfotech and Design Ltd.
Project Guide : Mr. Shailesh Awasthi
Technology Used : .NET
Language Used : C#.NET
RDBMS : SQL Server 2000
Enviornment : Windows XP

3. Initial study

Introduction:

The “Shipping Management System”is a system used for proper management of

containers in a shipping company.The customer company give their order anywhere
through shipping company branch,telephone and Internet.These order are collected
on the nearest port then all type of product are filled into the container and delivered
to the destination port.At last in the nearest port the container become open and all
product send to their appropriate places.To understand the whole system,it is
necessary to understand the following processes.

Order Receiving Process-

Order collecting process in following steps:

• First of all take the order of the customer company through transported
company branches, telephone and internet.
• Take all the compulsory information about source and destination
company(i.e. company name, contact name, contact title, country, city, full
address, contact no., fax no.)
• Take all the information of the product that is delivered(i.e. product
description, quantity of product)
• Mention the date of receiving date of product and delivery date of the product
• Calculate the fare of goods transportation according to the good acquires to
the container(i.e. area per sqare feet) and destination port distance(i.e. per
km)
• Gives a slip to the customer company representative

11
Order Loading Process-

Order Loading Process in following steps:

• Collect all the goods on to the port

• Now preparing a list of those goods that is to be delivered to the same
destination port and have approximately same delivery date
• Preparing a list of container that in every container puts what kind of
goods(i.e. a container may be exists different orders)
• Date and time of the loading of a container
• Name of the employees who are goes with the container

Order Delivery Process-

Order Delivery Process in following steps:

• Date and time of the dispatching of the goods on the destination port
• Dispatching of the product on that occasion till full fare payment is found
• Take a receipt of delivering goods to the shipped company representative at
the time of dispatching of goods

Existing System-

In the shipping company the company is activated to achieve the following objects:
• To explore the business through found maximum orders
• To develop better coordination between the staff and administrator
• To develop better coordination between the head office and branches
• To develop better coordination between every section of employees

Head office is divided into three sections. First one is Profile management
system, second is order management system,and last one is accounting system.
Each section has their separate employees and an administrator. And our

12
company has branches into the several cities and countries company takes order
through these branches.

The procedure followed for the above services is as under:

• Order Taking- Take the order from customer company through branch
manager directly if order is taken by another city branch then this
information is send to the head office through telephone .

• Profile Management-To maintains the profile of employees customer

company and shipped company there creates a separate department
profile management system.Information of the Customer company and
shipped company are entered into two times.First time at the time of the
order taken when branch manager takes the order from the customer
company.

• Accounting Management-To calculate the working days of the

employees maintain two registers.First one is to maintain the all-
necessary information about employee(i.e. general information,personal
information,educational information)and second one is to records the
absence register to calculate the total working days of the employees.

Drawbacks of Existing System:

• Whole work is manual

• Simple MS-Excel reports are used
• MS-Word is used for publishing
• No flow of information between employees
• Files have to be maintained to keep past record which takes a lot of
space
• Unnecessary money is wasted on stationery

13
Proposed System:

The proposed system is a “Shipping Mangement System”. This system will

remove all the drawbacks and limitations of the existinbg system as describe
below:

• System will be as automated as possible

• System will be fully secure
• No need of publish on notice board
• Save money and time
• Record storing facility is better
• No repetitions in the information flow
• System will generate optimized reports for the use of department
• It is decided to develop the system in c#.net and SQL Server 2000
plateform.The objective is to satisfy all the requirement of the shipping
industries, employees and management and also make it user friendly.

Limitation:

Any system cannot be fullproof. Likewise the proposed system can also face
certain drawbacks. There can be security breach. If some malicious user gets
access the password then the system become vulnerable.

Conclusion:

From the observation made in the initial analysis, it can be recommended that
one can develop such a system and justify that the initial study could be
followed by the feasibility analysis phase. In the next chapter, the different
feasibility analysis are performed.

14
FEASIBILITY STUDY

15
 The English word feasible means capable of being carried out
successfully. An event is said to be feasible if it is considered possible
and practicable.

The feasibility study depends on the result of the initial

investigation; the survey is expanded to a more detailed feasibility
study. As we have learned in the above proceedings, a feasibility study
is a test of a system proposal according to its workability to meet user
need, and effective use of the resources provided to user by the
developer of the software.

The main objective of the feasibility study is not to solve the

problem but to acquire a sense of its scope. During the study, the
problem definition is crystallization and aspects of the problem to be
including in the system are determined.

The result of the feasibility study is a formal proposal. This is

simply a report a formal document detailing the nature and scope of
the proposed solution. The proposal summarized what is going to be
done.

The FS is an investigation into how possible a proposed

scheme might be, and whether it is capable of being carried out
successfully. This is usually assessed on four standard criteria for
feasibility but other considerations may be relevant and necessary
depending on the specific nature of the project and its environment. It
refers to the phase where the proposed system is tested whether it is
really required in the present working conditions or not. It is a very
important step in system development as its result determines
whether the system has to be developed or not developed or not. The
standard assessment criteria and typical questions they address are: -

 Technical feasibility - can we do this project?

 Social feasibility - do we want this project?

16
  Economic feasibility - can we afford this project?
 Operational feasibility - can we handle the outcome of this
project?

TECHNICAL FEASIBILITY :-

The Proposed System Is Technically Feasible Since:

 The proposed system is capable of providing adequate

responses.
 The proposed system being modular, can add more features in
future.
 As far as the software and hardware is concerned, the proposed
 System is completely reliable with data security.
 Technology is available to make it work.
 It is possible to achieve the proposal within the performance
criteria.
 There are sufficient skilled technologists available to staff this
project.
 Proposed tasks are new for the company.

SOCIAL FEASIBILITY : -

The Proposed System Is Socially Feasible Since:

 Proposed system is physically possible and there are no

negatives
 Repercussions and impacts on people in and outside the
company.
 The proposal will influence working practices in a favorable way
and improve working conditions for employees.
 The proposed system will not effect employment directly. If
vacant
 Post will be created there is provision to fulfill them.
 It considers the social cost, human issues, cost to the
environment, society and company culture.

ECONOMIC FEASIBILITY :-

17
 The Proposed System Is Economically Feasible Since:

 The cost of the hardware and software is quite affordable.

 Long term financial profit on the amount of time and effort can
be saved.
 The manpower cost will be reduced.
 Improved quality of work by better information system and
faster decision-making will be possible.
 System implementation Improves efficiency in terms of
processing time.
 The proposed system is beneficial and will balance the capital
outlay.

OPERATIONAL FEASIBILITY :-

The Proposed System Is Operationally Feasible Since:

 The proposed system is approved by CEO, controller of programs

and meets producer’s requirements.
 Since the new system is going to ease the workload of the
 Users the proposed system will help in improving the total
performance.
 Users are active part of the system and supportive to the
 System because the implementation of the system means lesser
workload and convenient mode of working for them.
 Company can cope with the change that will result.
 Company has enough resources to make the end-product worth
while in future.
 If the project needs additional time, the company is able to
retrain/redistribute existing staff or recruit additional manpower.

Feasibility report :-

18
 In my opinion the report is: -

“The PROJECT is adequate feasible to implement and execute

the project”

The culmination of the feasibility study is a feasibility report

directed to management; it evaluates the impact of the proposed
changes on the areas(s) in question. The report is a formal document
for management use; brief enough and sufficiently no technical to be
understandable, yet detailed enough to provide the basic for system
design.
There is no standard format for preparing feasibility report. Analysts
usually decide on a standard format that suits the particular user and
system. Most reports, however, begins with a summary of finding and
recommendations, followed by documented details. Starting with
summary information highlight the essence of the report, giving
management the option of reviewing the details later.

 Cover latter formally presents the report and brief indicates to

management the nature, general finding, and recommendation
to be considered.

 Table of contents specifies the location of the various parts of

the report.

 Overview is a narrative explanation of the purpose and scope of

the project

 Detailed finding outline the method used in the present system.

 Economic justification details point by point.

 Recommendations and conclusions suggest to management the

most beneficial and cost-effective system.

19
 Analysis

System Analysis:-

Requirement analysis phase of the project concern with what is done in the project,
this phase stress on "what" rather than "how". This phase is very important in product
development as it gives the direction to the development of the software product by
clearly defining the inputs of the users and the clients. Requirements gathering involve
the study of the needs of users, clients, and the previous system.

In the project to get the clear understand required to study the help for this project
and the entire tool, which is used to develop the project. To see the functionality then
require to learn visual basic 6.0, Oracle 8i.

Software Development Life Cycle

Introduction
This discusses the concepts behind the design of software life cycle models (SLCMs). It
provides you with the basic building blocks of a model and gives examples of their use.
Armed with this information you can:

1. Create a custom SLCM for your project

2. Tailor an existing SLCM
3. Evaluate a SLCM

20
Definition
A software life cycle model (SLCM) is a representation of the major components of
the software development work and their interrelationship in a graphical framework that
can be easily understood and communicated. Just as the WBS partitions the deliverable
into its component parts so the SLCM apportions the work to be done into manageable
work units.

You must have a defined SLCM for your project to:

• Define the work to be performed

• Divide up the work into manageable pieces
• Determine project milestones at which project performance can be evaluated
• Define the sequence of work units
• Provide a framework for definition and storage of the deliverables produced by the
project
• Communicate your development strategy to project stakeholders

A SLCM achieves this by:

• Providing a simple graphical representation of the work to be performed

• Allowing focus on important features of the work, downplaying excessive detail
• Providing a standard work unit hierarchy for progressive decomposition of the work
into manageable chunks
• Providing for changes (tailoring) at low cost

21
Classifying Life Cycle processes
In planning software development you need to consider the complete exercise as a
process. To effectively manage it you need to break it up into component sub processes.
Figure shown below present the 3 main classes of the software development process and
gives examples of the members of each class.

Software life cycle process classification:

Software Development process
1. Project Support Processes

• Project Management
• Quality Management
• Configuration Management

Development processes

• Concept
• Requirement
• Design
• Coding
• Testing
• Installation
• Maintenance
• Retirement

22
2. Integral processes

• Planning
• Training
• Review
• Problem Resolution
• Risk Management
• Document Management
• Interview
• Joint Session
• Technical Investigation
• Test

Project Support processes are involved with the management of the software
Development exercise. They are performed throughout the life of the project.
Development processes embody all work that directly contributes to the development of
the project deliverable. They are typically interdependent.
Integral Processes are common processes that are performed in the context of more than
one development activity. For example, the review process is performed in the context of
requirement definition, design and coding.

Describing a process
Processes are described in terms of a series of work units. Work units are logically
related chunks of work. For example, all preliminary design effort is naturally chunked
together.

23
Figure described the components of a work unit.

Figure component of a work unit

Work Work Unit Work Flow Output

Flow
Input
Entry Statement of Exit
Criteria work Criteria

Out In
Feedback
A work unit is described in terms of:

Work Flow input/output. Workflow is the work products that flow from one work
unit to the next. For example, in figure, the design specification flows from the output of
the design work unit to the input of the code work unit. Workflow is the deliverables
from the work unit. All work units must have a deliverables. The life cycle model should
provide detailed description of the format and content of all deliverables.

Entry Criteria are the conditions that must exit before a work unit can commence.
Statement of works (SOW). The SOW describing the work to be performed on the
work flow inputs to create the outputs.

Exit Criteria. The conditions that must exit for the work to be deemed complete.

Feedback paths

24
Feedback paths are the paths by which work performed in one work unit impact work
either in progress of completed in a preceding work unit.

Example of feedback path.

Requirement Design spec. Test Units

Spec. Design Code

For example the model described as above figure allows for the common situation where
the act of coding often uncovers inconsistencies and omissions in the design. The issues
raised by programmers then require rework of the base lined design document.
Defining feedback paths provides a mechanism for iterative development of work
products. That is, it allows for the real world fact that specifications and code are seldom
complete and correct at their first approval point. The feedback path allows for planning,
quantification and control of the rework effort.
Implementing feedback paths on your project requires the following procedures:

• A procedure to raise issues or defects with lined deliverables.

• A procedure to review issues and approve rework of base lined
Deliverables.
• Allocation of budget for rework in each project phase.

25
Example
Figure provides a phase level life cycle model for a software development project
Figure A generic project model

Requirement System Test System Development

Capture Planning Planning

Preliminary Integration Integration Maintenance

design test Testing And
Planning Enhancement

Detailed Unit test Unit testing

design planning

Coding

Main workflow

Feedback path

26
Project scope and activities

One thing we that the scope of the project depends upon the need. Necessity is the mother
of invention. Everything whatever is being made or has already been made is just because
of need. When we face a situation in which we require something which is not available
with us, we try to invent that thing. Before the advent of computer, we know that each
and every task is being performed under manual systems. It is tedious to work in the
manual system as than of computer system. One can handle his work very efficiently,
speedily and timely with the help of computer. If the manual system were continued
today then a person would always be busy with entering, deleting and updating the
records.
Everything is revolving around the mouse button and just a click solves many
problems within seconds. No need to maintain heavy registers. There is no requirement
of keeping big records. Everything is automatic.
So one can easily anticipate the future of this project after going through the needs
mentioned above. One thing we know that the scope of the project depends upon the need
and it was felt that computerization of the existing manual system will save the time of
concerned person and it will enhance the efficiency of his work. Now we can easily say
that the future of the project is quite bright in time to come.

Activity Summary

The following are the major tasks or activities associated with this project.
They are described in detail in the following sections:

• Project Initiation

27
 • Analysis of Software Requirement
• Developing a Prototype
• Functionality Designing

• Coding
• Testing
• Data Migration
• Documentation
• Implementation
• Training

Project Initiation

This task brings together the project team and client for a walk through
of the project objectives and plan. The project team will review the statement
of work, assumption and project procedures, thereby consolidating agreement
about project goals, activities, roles, responsibilities and project management
practices. Also reviewed during this task are the resource requirements.

The purpose of the on-site project initiation is to:

• Refining the project scopes, deliverables and schedule.

• Define and lay down the standards for the proposed system
• Refine issue resolution and escalation procedures, and
• Periodic Status reporting

The project initiation will also be used to finalize reporting and issue resolution
procedures. As a starting point in the discussion following is proposed

Analysis of Software Requirements

28
 A complete understanding of software requirements is essential to the success
of a software development effort. The requirement analysis task is a process of
discovery, refinement, modeling and specification.

Both Synergy employees and team members will take an active role in
requirement analysis and specification.

• Conduct needs analysis

• Draft preliminary software specification

Developing a prototype

In this phase Synergy Business Pvt Ltd.. team will be developing a

prototype based on the specification collected during the previous phase. The
major deliverable of the task is demo to project manager. After the prototype is
complete, the Synergy project Manager will review the feedback results with
Senior Technical Manager and augment with any specification missing during
the previous activity.

Design

Software design is an iterative process through which requirements are

translated into a "blueprint" for constructing the software. Design is

29
represented as level that can be directly traced to specific data, functional and
behavioral requirements. The activities are:

• Review preliminary software specification

• Develop functional specification

Development

The Synergy Business Pvt Ltd. team will decide the structure of data,
software architecture, and procedural details of implementation. Team will also
decides how the design will be translated into a programming language and
how testing will be performed.

Synergy Business Pvt Ltd. team will develop code for all the modules using
appropriate tools. Each code will be documented using a standard format. This
format will include general comments at the beginning of the code, as well as
comments wherever required.

Testing

Software testing is a critical element of software quality assurance and

represents the ultimate review of specification, design and coding. The
increasing visibility of software as system element and the attendant "costs"
associated with a software failure has motivated Beehive for well planned,
through testing. This task includes:

• Developing unit test plans using product specifications

• Developing integration test plans using product specifications

30
 • Review modular code
• Test component modules to product specifications and modify
code
• Integration Testing
• Test module integration
• Identify anomalies to specifications and modify code

Documentation

Since this application is business critical it must be fully documented.

MSSL team members will:

• Develop Help specification

• Develop user manual specifications
• Develop Help system
• Develop user manuals

Implementation

Beehive team with the help of project Manager will develop an

implementation strategy and methodology. The team will secure resource and
install the software.

In the implementation phase, the software developed is installed or combined

with the other software at the client side or at the firm itself if the software was
developed from the in-house operations of the firm. The software has now
been readied to be used by the prospective users.

Training

31
 Synergy team will develop training specification for users and support
staff and conduct training for both end users and support staff.

• Develop training specifications for end users

• Develop training specification for support staff
• Conduct training

Project Plan

Project Tasks

The project would consists of the following tasks:

• Designing Software specifications

• Developing a prototype
• Development
• Testing
• Data migration
• Documentation
• Implementation
• Training

Risk Management

32
 Risk is defined as exposure to the chance of injury or loss, a hazard or
dangerous chance. Using certain defined risk management techniques Beehive
plan to alleviate this chance. This plan is broken down into four distinct
phases:

• Identification
• Analysis
• Mitigation
• Monitoring

When risks are analyzed, it is important to quantify the level of uncertainty and
the degree of loss associated with each risk. To accomplish this following
categories of risks are considers:

• Project Risk
• Technical Risk
• Business Risk
• Implementation Risk

Project Risk

These risks threaten the project plan. If the project risks become real, it is
likely that the project schedule will slip and cost will increase. The major risk
appeared are:

• Poor requirements
• Poor estimation
• Lack of Budgets

33
 • Faulty assumptions
• Timely availability of skills/expertise required for the project

Technical Risk

These risks threaten the quality and timelines of the software to be

produced. If a technical risk becomes a reality, implementation may become
difficult or impossible. Technical risks identify

• Potential design

• Implementation
• Interfacing with existing system
• Maintenance problems
• Bandwidth issues in case of Internet connection
• Internet related communication issue

Business Risk

These risks threaten the viability of the software to be built. Business risks
often jeopardize the project or the product. The reasons are:

• Market risk
• Strategic risk
• Management risk
• Budget risk

34
 The risk management strategy is intended to identify critical areas and
risk events, both technical and non-technical, and take necessary action to
mitigate them before they can become problems, causing serious cost,
schedule, or performance impacts. This program will make use of modeling
and simulation, technology demonstrations, and prototype testing to handle
risk.

DATA FLOW DIAGRAM :

Login :

35
 Password
validation

Check validation

Input emp Invalid pass Invalid

Employee login id pass
password &password message

Empid
&password valid

Open
menu
page

36
Order Recieved

37
 order

Full of Order
Create
containe inform
r order
ation
Creating
customer
Less of Order info
contain
er Create
custom
er
Create
Order not exist new
order

Order
Customer profile
incompl Valid customer id
ete exist

Customer not
exist
Creating Order info
Order exist customer account info
product info
shipped profile

Input Customer not exist

order Create
informat custome
ion r

Creating customer

Valid customer id
Customer profile
Order info
account info
product info
shipped profile

38
 Order Loading:

Order load

Order load
Order info Order
id

Display
selected
order
informatio
n

39
 Order Delivery:

Place with Existing

Less Of Container
Container
Checking
Check
Order And Loading
Order Type
Of Container

Full Of Place with New

Container Container
Reports Generate
Container Database

Delivered Delivery of
Reports Container

40
Entity-Relationship Model
The entity-relationship (E-R) data model perceives the real world as consisting of
basic objects, called entities, and relationships among these objects. It was
developed to facilitate database design by allowing specification of an enterprise
schema, which represents the overall logical structure of a database.

Basic Concepts

Entity Sets
An entity is a ‘thing’ or ‘object’ in the real world that is distinguishable from
all other objects. An entity has a set of properties, and the values for some
set of properties may uniquely identify an entity.
An entity may be concrete, such as person or a book, or it may be
abstract, such as a loan or a holiday, or a concept.
An entity set is asset of entities of the same type that share the same
properties, or attributes.
Attributes

An entity is represented by a set of attributes. Attributes are descriptive

properties possessed by each member of an entity set. It can be
characterized by the following attribute types.
• Single-valued attributes-Attributes which have single value for a
particular entity
• Multivalued attributes-Attributes which have asset of values for a
specific entity.
• Derived attributes-Attributes that can be derived from the values of
related attributes or entities.

Relationship Sets

A relationship is an association among several entities.

A relationship set is a set of relationships of the same type.

Primary Key
A primary key allows us to identify asset of attributes that suffice to
distinguish entities from each other.

41
Entity-Relationship Diagrams (E-R Diagrams)

An E-R Diagram can express the overall logical structure of a database

graphically.
E-R Diagrams are simple and clear-qualities that may well account in large part
of the widespread use of the E-R Model.
Such a diagram consists of the following major components:

• Rectangles, which represent entity sets

Entity set
E

• Ellipses, which represent attributes

A Attribute
• Diamonds, which represent relationship sets

R Relationship set

• Lines, which link attributes to entity sets and entity sets to relationship sets
Links

• Double ellipses, which represent multivalued attributes

A Multivalued Attribute

• Dashed Ellipses, which denote derived attributes

A Derived Attribute

42
 branch_i
d
ee_prof
ie
eg_prof
b_profil ie
b_profile e eg_profile
eg_prof
ile
ee_profil
b_prof
il
e
cust_i eg_profi
ep_prof
d eg_profil e eg_profil
ie
e emp_ent e
ee_prof
emp_sale cal emp_psa
eg_profil ile
c l
e
emp sal
cust_id emp_entcal pass
emp_salec emp_psal
file ep_profile
emp_ent
emp sal pass
cal
cust_id
emp_sale emp_atte
order
c nd
_info emp_psal
salary
emp_dsal

Calcula
emp_attend
salary te
order _info salary

Sal_lo
ad

emp_dsal
Sal_load
order
_info
order_load
order _info
order_produ order_lo
ct ad
order_de
liv
order_load

order _info
order_deliv
order_deliv

order_product

account_info
order account_info
acc_tran
_info
account_in
fo

acc_tran

43

Ee_
E.R Diagram:

Order delivery—

ide

product_quantity
Order_id

dat_of_dil

bl_id
pay status

pro_name Order Delivery

44
ORDER LOADING:

ide Cont_id

Order_id
Load_date

Ship_id Order Load

Order_sta

order amount:

45
 ide
to_amount

order_id pai_amount

bl_id order Amount rest_amount

Order Information:

46
 Order_i Dest_po
ide rt
d

Bl_id Sour_po
rt

Cust_id T_amou
nt
B_id Ord_stat
Order information us

S_country
O_date

D_country
D_date
P_status

Order Product:

47
 Count_i
ide
d
Count_si
Order_id
ze

Pro_nam
Bl_id
e

Book_si Pro_qua
ze n
Order Product

Data Dictionary:

48
 The tables used in container order management system are:

• Table Name : ord_dil

Primary key : ide

Field Name Field Type Description

ide numeric(9) Id of order delivery

order_id varchar(50) Order id

bl_id varchar(50) Bill id

pre_name varchar(50) Name of the product

product_quanti numeric(9) Quantity of trhe product

dat_of_dil datetime(8) Date of the delivery

pay_status varchar(50) Status of the payment

•Table Name: ord_load

Primary key : ide
Field Name Field Type Description

Ide numeric(9) Id of the order loading

order_id varchar(50) Order id

cont_id varchar(50) Container id

Ship_id varchar(50) Ship id

order_sta varchar(50) Order status

Load_date datetime(8) Date of the loading of

product

• Table Name: ord_amount

49
 Primary key : ide

Field Name Field Type Description

Ide numeric(9) Id of the order amount

order_id varchar(50) Order id

bl_id varchar(50) Bill id

to_amount money(8) Total amount

pai_amount money(8) Paid amount

Rest_amount money(8) Rest amount

50
 • Table Name: ord_info
Primary key : ide

Field Name Field Type Description

ide numeric(9) Id of the order information

order_id numeric(9) Order id

bl_id varchar(50) Bill id

cust_id varchar(50) Customer company id

b_id varchar(50) Branch id

s_country varchar(50) Source country

d_country varchar(50) Destination country

sour_port varchar(50) Source port of the source

country
dest_port varchar (50) Destination port of the
destination country
ord_status varchar (50) Status of the order

t_amount money (8) Fare of the product

transportation
p_status varchar(50) Status of the payment

o_date datetime(8) Date of the order receiving

d_date datetime(8) Date of the order must be

deliver

51
 • Table Name: ord_product
Primary key : ide

Field Name Field Type Description

ide numeric(9) Id of the order information

order_id numeric(9) Order id

bl_id numeric(9) Bill id

book_size numeric(9) Part of the container is book

cont_id varchar(50) Container id

cont_size numeric(9) Container size

pro_name varchar(50) Product name

pro_quan int (4) Product quantity

• Table Name: emp_logpass

Primary key : ide

52
Field Name Field Type Description

id Varchar(50) Id of the administrator

password Varchar(50) administrator Password
con_pass Varchar(50) Confirmation Password

FORM DESIGN :

53
1. Home page:

This is the main form of the project Shipping Management System.Through this form
administrator and employees ( profile System,Order Management System and
Accounting System)are login into the project.Administrator can use the whole project
i.e.total project is visible.But employeescan access only their authorizes forms else forms
are invisible.

54
2. Administrator Login:

In this form the administrator must be enter their administrator id and password.If
administrator id and passward are correct administrator will enter into project.This form
is made for security purpose of the project i.e.unauthorized person can not be entering the
project.

55
3. Employee Login:

In this form the employee must be enter their employee id and password.If employee id
and passward are correct employee will enter into project.This form is made for security
purpose of the project i.e.unauthorized person can not be entering the project.

56
4. Menu form:

This is the menu form of the project.This is the MDI form of the project.through this
form we can traverse whole project.

57
 .

5. Create Administrator Password:

Through this form administrator can create the password.

58
 6 .Edit Administrator Password:

Through this form administrator can change the password.

59
 7 .Delete Administrator Password:

Through this form administrator can delete the password.

60
8. New Employee Password:

Through this form employee can create the password:

9. Change Employee Password:

61
Through this form employee can change the password:

62
10. Delete Employee:

Through this form employee can delete the password:

11. Main Order Form:

63
Through this form we can give the order of container.Order is two types.First is full of
container and second is partial container.In the partial container more then one order take
places into a single container.

64
12. Full Container:

`In this form we fill the entries to book the full container.Set the Status of the order i.e.
order load ,order pending,order delivery and also set the status of the payment i.e.
complete payment,partial payment and at the delivery time payment.

65
13. Order Load:

In this form first we choose the entry from combobox and select them,then all the other
entries are evaluating automatically and set the status of the order Load.

66
14. Partial Order Form:

In this form we fill the entries to book the container.Set the Status of the order i.e. order
load ,order pending,order delivery and also set the status of the payment i.e. complete
payment,partial payment and at the delivery time payment.

67
 CODING

“Design specification” contains program specification as one of its topic. Programmers

for the development of software use this. In this stage, the actual coding / writing of the
programs are done.

This is very important part of application development stage. In the coding part the actual
programs are written for the functions which are performed in the application. This part is
particular for programmer which write the function actions programs.

After completion of the coding stage the application development stages go in the testing
phase.

Note: - The coding Part of the project is not included in this project
documentation.

68
 IMPLEMENTATION

A crucial phase in the system life cycle is the successful

implementation of the new system design. Implementation includes all
those activities that
take place to convert from the old system to the new one. The new
system may be completely new, replacing an existing manual or
automated system or it may be major modification to an existing
system. In either case , proper implementation becomes necessary so
that a reliable system based
“The requirements of the organization can be provided.
Successful implementation may not guarantee improvement in
the organization using the new system, but improper
installation will prevent it. It has been observed that even the
best system can’t show good result if the analysts managing
the implementation do not attend to every important details.
This is an area where the systems analysts need to work with
utmost care.”
This system will be implemented using C#.Net as front end and SQL
SERVER 2000 as back end and Windows XP Professional as the
platform.
For the successful implementation of a system, the training of the
users of the system plays an important role. Because even well
designed system can succeed or fail because of the way the are

operated and used. Therefore, the quality of the training received by

the personnel involved with the system in various capacities helps or
hinders and may even prevent the successful implementation of
management information system. Those who are directly or indirectly

69
related with the system development work must know in detail what
their roles will be, how they can make efficient use of the system and
what the system will or will not do for them. Therefore both system
operators and users need training.

SYSTEMS OPERATORS TRAINING :-

Running of the system successfully depend on the personnel working

in the computer center. They are responsible for providing the
necessary support. Their training must ensure that they are able to
handle all possible operations, routine and extra- ordinary in nature.
Operators training should include such fundamentals as how to turn
the equipment on and use it, how to power off and knowledge of what
constitutes normal operation. The operators should also be trained on
different type of malfunctioning, how to recognize them and what
steps should be taken whenever they arise. As part of their training,
operators should be given both a troubleshooting list that identifies
possible problems and remedies for them, as well as the names and
telephone numbers of individuals to
Contact when unexpected or unusual problem arise. Training also
involves familiarization with run procedures, which involves working
through the sequence of activities needed to use a new system on an
ongoing basis.

USER TRAINING:

User may be trained on use of equipment, particularly in the case

where, for example, a micro-computer is in use and the individual
involved is both operator and user. In such cases, users must be given
training on how to operate the system also. Questions that may be
trivial to the analyst, such as how to turn on a terminal, how to insert
a diskette into a micro-computer, or when it is safe to turn off the
equipment without danger of data loss, are significant problems to
new users who are not familiar with computers. This is also the case
with our system. In most of the cases, user training deals with the

operation of the system itself, with proper attention given to data

handling techniques.

70
 It is imperative that users be properly trained in methods of entering
transactions, editing data, formulating inquiries, deleting and inserting
of records. No training is complete without familiarizing users with
simple systems maintenance activities. Weakness in any aspect of
training may lead to awkward situations that cause user frustration
and errors. In our project also it is necessary to train users on how to
commit the transactions.Training of operators and users can be
organized in several different ways. Most important ways to train users
are Vendor and in-service training In-house training.

Often the best source of training on equipment is the vendor who

supplies the equipment. Most vendors offer extensive educational
programs as part of their services. In the case of our project too, we’ll
provide training to the users of our project. Conversion is also
important in the implementation phase. Conversion is the process of
changing from the old system to the new one. It must be properly
planned and executed. Four methods of conversion are common in
use. They are:

 Parallel systems

 Direct conversion

 Pilot systems

 Systems phase-in

Each method should be considered in the light of the opportunities that

it offers and problems that it may create. However, it may be possible
that sometimes, we may be forced to apply one method over others,
even though other methods may be more beneficial. In general,
systems conversion should be accomplished in shortest possible time.
Long conversion periods create problems for all persons involved
including both analysts and users.

PARALLEL SYSTEMS :-

The most secure method of converting from an old to new system is to

run both systems in parallel. Under this approach, users continue to

71
operate the old system in the usual manner but they also start using
the new system. This method is the safest one.

DIRECT CONVERSION :-

This method converts from the old system to the new system abruptly,
sometimes over a weekend or even midnight. The old system is used
until a planned conversion day, when it is replaced by the new system.
There are not parallel activities.

PILOT SYSTEM :-

Pilot approach is often preferred in the case of the new system which
involves new techniques or some drastic changes in organization
performance. In this method, a working version of the system is
implemented in one part of the organization, such as a single work
area or department.

PHASE-IN METHOD :-

This method is used when it is not possible to install a new system

throughout an organization all at once. It allows some users to take
advantage of the new system early. Also it allows training and
installation without unnecessary use of resources. The project
developed by us should be implemented using the parallel systems
conversion method.

72
 TOOLS/ENVIORNMENT REQUIRED

Tools and Environment used in this project are as under: -

Software Requirements

 Operating system : Windows XP Professional

 Framework : Microsoft Visual Studio .Net
2003
 Back End : Sql-Server 2000
 Server : Internet Information Server
(IIS) 6.0
 Language : C#.Net

Hardware Requirements

 Pentium IV Processer
 128 MB RAM
 10 GB. Hdd.
 1.5 GHz Processor
 LAN card
 Printer

73
 TESTING PHASE

Program is individually tested using some test/dummy data. This activity produces
“tested programs”.

To ensure that system serves it purpose it has to be thoroughly tested. Testing can be
done at two levels.

Some of the commonly used Strategies for Testing are as

follows:-

Unit Testing

Module Testing

Subsystem Testing

System Testing

Acceptance Testing

The testing phase is vital too the system. System testing is done to
check if all the parts of the system are working correctly and if all the
goals are achieved. Although testing is of many types, we have used
only three type of testing, which are as follows:-

74
 Unit testing:-

Also known as modular testing in this we tested each of the

modules of our system individually with simulated data.

 System Testing:-
System testing is designed to uncover weaknesses that were not
found in earlier tests. This includes forced system failure and
validation of the total system as it will be implemented by its users
in the operational environment.Generally,it begins with low volumes
of transactions based on live data. The volume is increased until the
maximum level for each transaction type is reached. The total
system is also tested for recovery and fallback after various major
failures to ensure that no data are lost during the emergency; all
this is done with the old system still in operation. After the
candidate system passes the test, the old system is discontinued.
In this we tested the whole system with voluminous simulated data
and the system perform efficiently under the maximum possible
load.

 Acceptance Testing :-

75
 The user and management accepted the system because it fulfilled
the requirements of them and provides good visual interface so that
the user can operate it without any inconvenience.

SYSTEM TESTING :

 PREPRODUCTION TESING (IN PROCESS) :

Internal tests are performed on prepared components. This activity is

carried out side along with production of components. This is a
necessary activity as it avoids smaller problems getting converted into
bigger one if they are deducted in early stages.

 POST PRODUCTION TESING :

This testing is done after the production is over. This is divided in to

two categories.

 ALPHA TESTING (ONSITE TESTING) :

This testing is normally performed at the site where same people

involved in the production carry out the production. The focus of this
testing is to test the interrelationship of various components and
synchronization among them. This testing also focuses on efficiency
related issues.

 BETA TESTING :

The system is given to the users and the users of the previous the
version of the system. These user works on this system to give their
feedback about the system. This testing mainly focuses upon on the
acceptance level of the users and any operating difficulties experienced
by the users.

Testing Result Performed in the project:-

76
All the testing are performed during the testing stage by the project
member, me and project head. All the test i.e. Unit, System and
acceptance test are successfully give results which fulfill user
requirements.

All the functions which are defined in our application are work very
well.
The results are very good which fulfill the user requirement.

77
 CONCLUSION

This project is not the end of path for our carrier. This is the first online
project designed by me and as I think this is the learning experience for me.
For any project development a person must be equipped with high skill in
analysis as well as in designing. The position where we are the learning
stage and from the cooperation of my Respected Teachers, I am simply able
to give the end of this project.

This project is running successfully by the use of .Net Framework

Environment and Sql-server as Back end. All the technologies are latest and
easy to under stand.

78
 BIBLIOGRAPHY

.NET:
*ASP.NET Used
Writer: Stephen walther
*Black book asp.net AND c#.
*Wrox professional
Writer: Mr. Karliwatson, Jon D.Reid
Publication: Wrox

DBMS:
*Fundamentals of Database System
Writer: Mr. Elmasri and Mr. Navathe
Publication: BPB
*An Introduction to Database System
Writer: Mr.Bipin C Desai
Publication: Galgotia

SQL:
*Oracle Developing 2000

Writer: Mr. Ivan Bayross

Publication: BPB
* Sql-server the complete Reference

79