Professional Documents
Culture Documents
Submitted to:
1
CERTIFICATE
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
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.
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.
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.
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.
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
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
Modules:-
8
Introduction and overview of project
Introduction
In this system keep all the necessary information about the employees, Customer,
shipped company and branches.
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-
Problem Definition-
“ To analyze, design and develop the Shipping Management System for use
employee as well as management”.
Goals-
Objective-
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-
3. Initial study
Introduction:
• 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-
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.
• 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 .
13
Proposed System:
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.
16
Economic feasibility - can we afford this project?
Operational feasibility - can we handle the outcome of this
project?
TECHNICAL FEASIBILITY :-
SOCIAL FEASIBILITY : -
ECONOMIC FEASIBILITY :-
17
The Proposed System Is Economically Feasible Since:
OPERATIONAL FEASIBILITY :-
Feasibility report :-
18
In my opinion the report is: -
the project”
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.
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:
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.
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.
• 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.
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.
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:
25
Example
Figure provides a phase level life cycle model for a software development project
Figure A generic project model
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 project initiation will also be used to finalize reporting and issue resolution
procedures. As a starting point in the discussion following is proposed
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.
Developing a prototype
Design
29
represented as level that can be directly traced to specific data, functional and
behavioral requirements. The activities are:
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
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
Implementation
Training
31
Synergy team will develop training specification for users and support
staff and conduct training for both end users and support staff.
Project Plan
Project Tasks
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
• 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.
Login :
35
Password
validation
Check validation
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
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:
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
Relationship Sets
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)
Entity set
E
A Attribute
• Diamonds, which represent relationship sets
R Relationship set
• Lines, which link attributes to entity sets and entity sets to relationship sets
Links
A Multivalued Attribute
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
44
ORDER LOADING:
ide Cont_id
Order_id
Load_date
order amount:
45
ide
to_amount
order_id pai_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:
49
Primary key : ide
50
• Table Name: ord_info
Primary key : ide
51
• Table Name: ord_product
Primary key : ide
52
Field Name Field Type Description
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
.
58
6 .Edit Administrator Password:
59
7 .Delete Administrator Password:
60
8. New Employee Password:
61
Through this form employee can change the password:
62
10. Delete Employee:
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
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
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.
USER TRAINING:
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.
Parallel systems
Direct conversion
Pilot systems
Systems phase-in
PARALLEL SYSTEMS :-
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 :-
72
TOOLS/ENVIORNMENT REQUIRED
Software Requirements
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.
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:-
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 :
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.
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.
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
79