CMS

Document Sample
CMS Powered By Docstoc
					                                                    Appendix 1

    CARGO MANAGEMENT SYSTEM

               A PROJECT REPORT

                     Submitted by

           ASHVIN JADAV(04CE08)
      DHARMENDRA SHUDRA(10CE08)

       In fulfillment for the award of the degree

                          Of

       BACHELOR OF ENGINEERING

                          in

          Computer Science & Engineering




B.H. GARDI COLLEGE OF ENGG. & TECH. – RAJKOT.

  Gujarat Technological University, Ahmedabad

                    December, 2011
                                                            Appendix 2

          B. H. GARDI COLLEGE OF ENGG. & TECH. – RAJKOT.

                 COMPUTER SCIENCE & ENGINEERING


                                    2011


                             CERTIFICATE


                                                        Date:


This is to certify that the dissertation entitled “CARGO MANAGEMENT

SYSTEM” has been carried out by ASHVIN JADAV(04CE08) and

DHARMENDRA SHUDRA(10CE08) under my guidance in fulfillment of the

degree of Bachelor of Engineering in Computer Science & Engineering (7th

Semester/8th Semester) of Gujarat    Technological University, Ahmedabad

during the academic year 2011-12.




Guides:




                                                   Head of the Department
                              ACKNOWLEDGEMENT



       Every work that completes successfully stands on the constant encouragement, goodwill
and support of the people. Through this, we would like to express our gratitude to all those who
have contributed to accomplish our project successfully.




       It is a pleasure to acknowledge our debt to all the people involved, directly or indirectly,
in the development of this project, undertaken at Computer Science & Technology
Department. This experience will definitely help us in our future endeavours of work.




       I take this opportunity to express our immense gratitude to Ms. Nafisha Mamati Madam
who has played the role as an Project Guidance faculty for me at the B. H. Gardi College Of
Engg. & Tech. for being a constant source of inspiration right from seeking project to the
successful completion of project and also guiding us throughout our project.




       I would like to take the opportunity to thank our Head of the Department Mr. Hitesh
Nimbark Sir, and Mr. Parvesh Sir who has constantly inspired us for project.




I express my sincere thanks to Ms. Nafisha Mamati Madam who has played the role as an
Internal Guidance faculty for me and all other faculties of our department for being a constant
source of inspiration right from seeking project to the successful completion of project and also
guiding us throughout our project. Finally I would also like to thanks my Project Partners
without whom the project would not be possible to complete in given scheduled time and to all
my college mates who help anyway in providing help whenever I needed related to the project.
                                ABSTRACT



      The online application software for managing transportation and goods
arrangement for Cargo Management Company. These programs feature modules
for tracking and managing every aspect of vehicle maintenance, fuel costing,
routing and mapping, warehousing, communications, traveler and cargo handling,
carrier selection and management, accounting etc.



      The Online Cargo Management System performs order management tasks to
maintain data associated with an order. This system provides the user interface
module through which the customers can easily access the system. The user
interface includes an input mechanism to specify one or more orders.



      The system is helpful to manage the online shipping orders, to arrange the
goods into containers, to decide optimal route of transportation, to optimize the
cost of the shipment, on time delivery of goods to the desired destination.
                                               Appendix 3

                       LIST OF FIGURES



Figure No         Figure Description             Page No

Fig 3.1     The Water Fall Model                    8

Fig 5.1     .NET 2.0 Framework Architecture         15

Fig 7.1     Use Case Diagram(Display Module)        39

Fig 7.2     Class Diagram                           40

Fig 7.3     E-R Diagram                             41

Fig 7.4     System Activity Diagram                 42

Fig 7.5     Context Diagram                         43

Fig 7.6     Control Flow Diagram                    44
                                           Appendix 4
                    LIST OF TABLES
Table No      Table Description               Page No

Table 3.1     Roles and Responsibilities        11

Table 7.4.1   Functional Requirement            27
                                                                                  Appendix 5

      LIST OF SYMBOLS, ABBREVIATIONS AND NOMENCLATURE




Symbol Name
Symbols used in DFD:

(1) Process: People, procedure or devices that use or produce data. The physical component is
    not defined.




(2) External entity: An external entity such as an employee, team leader, and HR person are
    essentially physical entities external to the software system which interact with the system
    by inputting data to the system or by consuming the data produced by the system.




(3) Data Flow: A data flow symbol represents the data flow occurring between two processes
    or between, an external entity and a process in the direction of the data flow arrow.




(4) Data store: A data store represents a logical file. The direction of data flow arrow shows
    whether data is being read from or written into a data store.
(5) Output: The output symbol is used when a hard copy is produced such as report.




Abbreviation

Asp.net     Asp.net server pages

CSS         Cascading Style Sheets

JS          JavaScript

HTML        Hyper Text Mark up Language

AJAX        Asynchronous JavaScript and XML

IT          Information Technology
                                                        Appendix 6

                                    TABLE OF CONTENTS


                 Acknowledgement                                 i
                 Abstract                                       ii
                 List of Figures                                iii
                 List of Tables                                 iv
                 List of Abbreviations                          v
                 Table of Contents                              vii

INTRODUCTION TO PROJECT

Chapter : 1 Introduction                                        1

1.1      Project Summary                                        1
1.2      Purpose : Goals and Objectives                         1
1.3      Scope                                                  3


BRIEF HISTORY OF THE WORK
Chapter : 2      Overview                                       5
2.1       The Overall Description                               6


LITERATURE SERVEY                                               8
Chapter : 3 Project Management
3.1      Project Planning                                       8
      3.1.1 Project Development & Approach                      8
      3.1.2 Project Plan                                       10
Chapter : 4 System Requirement study
      4.1 User Characteristics                                 12
      4.2 H/W and S/W Requirements                             12
      4.3 Constraints                                          13
      4.3.1 User Interface                                 13
      4.3.2 Assumptions and Dependencies                   13
      4.3.3 Safety and Security                            14


Chapter : 5 Technology and Literature Reviews              15
   5.1 Common Language Runtime                             16
   5.2 Introduction about ASP.NET                          16

WORKING / IMPLEMENTATION OF THE PROJECT WORK /SIMULATION
Chapter : 6 Implementation planning and Details            23
   6.1 Implementation Environment                          23

   6.2 Program/Modules Specification                       23

   6.3 Security Features                                   24

   6.4 Coding Standards                                    24

RESULT ANALYSIS
Chapter : 7 System Analysis                                26
   7.1 Study of Current System                             26
   7.2 Problem and weakness of Current System              26
   7.3 Requirement of new System                           26
      7.3.1 User Requirement
      7.3.2 System Requirement
            7.3.2.1 Functional Requirements
            7.3.2.2 Non-Functional Requir
   7.4 Requirement Validation                              38
   7.5 Function of System                                  39
      7.5.1 Use Case Diagram
   7.6 Data Modeling                                       40
      7.6.1 Class diagram
      7.6.2 E-R Diagram
      7.6.3 Activity Diagram
   7.7 Functional and Behavioral Modeling   43
      7.7.1 Context Diagram
      7.7.2 Control Flow Diagram
   7.8 Main Modules of new System           45


CONCLUSION

Chapter : 8 Conclusion                      48

APPENDICES

LIST OF REFERENCES                          49
    CARGO MANAGEMENT SYSTEM

               A PROJECT REPORT

                     Submitted by

           ASHVIN JADAV(04CE08)
        DHARMESH SHUDRA(10CE08)

       In fulfillment for the award of the degree

                          Of

       BACHELOR OF ENGINEERING

                          in

          Computer Science & Engineering




B.H. GARDI COLLEGE OF ENGG. & TECH. – RAJKOT.

  Gujarat Technological University, Ahmedabad

                    December, 2011
                              INTRODUCTION TO PROJECT

Chapter :1 Introduction
1.1    Project Summary


The online application software for managing transportation operations of all types: shippers,
airlines, trucks, trains, transportation rental agencies, etc. These programs feature modules for
tracking and managing every aspect of vehicle maintenance, fuel costing, routing and mapping,
warehousing, communications, traveler and cargo handling, carrier selection and management,
accounting etc.

The Online Cargo Management System performs order management tasks to maintain data
associated with an order. This system provides the user interface module through which the
customers can easily access the system. The user interface includes an input mechanism to
specify one or more orders.

The system is helpful to manage the online shipping orders, to arrange the goods into containers,
to decide optimal route of transportation, to optimize the cost of the shipment, on time delivery
of goods to the desired destination.



1.2    Purpose :Goals and Objectives


The main aim of the Online Cargo Management System is to provide cost effective
alternatives to help customers to get better cargo services. It helps to the warehouse management
to handle their customers’ needs effectively and efficiently.

It also helps to warehouse management to manage transportation routes, delivery time, on-time
shipment, available resources etc.
    The system provides cost effective alternatives to help
    customers to get better cargo services. It helps to the
    warehouse management to handle their customers’
    needs effectively and efficiently. It also helps to
C   warehouse management to manage transportation
    routes, delivery time, on-time shipment, available
A
    resources etc.
R

G

O
                     The system will help to arrange goods into containers
                     according to weight, volume and shipment. The system
M                    will manage details of the products that are to be
                     delivered. To arrange boxes in an optimal way special
A
                     code has been designed. Boxes are arranged in such a
N                    way that a container can carry maximum goods.

A

G

E
    The system will help to decide medium of
M
    transportation according to the requirements. It will
E   also help to decide optimal route of transportation to
    reach the desired destination. It will also help to
N
    reduce number of trips of shipment. It will help to
T   optimize the cost of shipment
1.3    Scope


The main aim of Online Cargo Management System is to provides cost effective alternatives to
help customers to get better cargo services. The services offered by this system are:

        User and Customer verification

       The system will verify the user based on their given logged on information and they will
       be given appropriate rights based on their id. The customers will be verified by their id,
       password and registration number.

        Online booking

       The requester is logged into the retrieval system and an interface of the retrieval system is
       provided to the logged-in requestor to allow same to search for items of documentation
       relating to such requester and such cargo based on indicia associated with each item.

        Order verification and Management

       The order given by the verified customer will be verified by checking the goods
       availability in warehouse. The search results include a number of items of documentation,
       and an identification of a number of particular ones of the items in the set of search
       results is received from the requester. The retrieval system creates a merged electronic
       document containing all of the identified items of documentation and the created merged
       document is delivered from the retrieval system to one of the requester and a destination
       selected by the requester.

        Goods arrangement in a container

       The goods arrangement in a container is that of orthogonally packing a subset of some
       given rectangular-shaped boxes into a rectangular container of fixed dimensions. Each
       box has an associated profit and the problem is to choose a subset of the boxes that fits
       into a single container so that maximum profit is loaded. If the profit of a box is set to its
       volume, this problem corresponds to the minimization of wasted space. An optimal
       filling of a container reduces the shipping costs as well as increasing the stability and
       support of the load.
Finds optimal route

Usually the need to choose the best route between two points is limited by the
information presented, in form of maps and operation hours for each route. This system
offers new complexity results for optimal route planning. We develop systems that take
in account stops, time, distance, fuel, bridge heights, low underpass and commercial
vehicle restrictions and etc.

Estimates the effective cost

It optimizes the effective cost through proper goods arrangement in a container and by
finding the optimal route.

Generates various reports

The retrieval system creates a merged electronic document containing all of the identified
items of documentation and the created merged document is delivered from the retrieval
system to one of the requester and a destination selected by the requester.
                               BRIEF OVERVIEW OF THE WORK


Chapter : 2 Overview
A storage system, or more correctly, a "cargo system" follows up after all cargo moved in the
ports, from its unloading from the ship to its being handed over to the customer (import cargo) or
from its entrance into the port until its loading onto the ship (export cargo).

The system follows all movement of import and export cargo at the various locations. It covers
the following subjects:




1. Input and maintenance of all import manifests.

2. Receipt of cargo to warehouses (loose and containerized).

3. Movement of cargo from location to location within the warehouse.

4. Report on damage.

5. Information center (including customer display terminal).

6.Handling of separated cargo (secondary manifest on international forwarders).

7. Dangerous cargo.

8. Unstuffing of containers.

9. Direct delivery.

10. Input of release documents.

11. Release of cargo (accompanied by gate pass or accompanying documents).

12. Weighing in (all weighing on scales is handled by the system - import,

    exp0r, containers).

13. Unclaimed goods.
14. Input of export cargo into the warehouses (storage documents).

15. Input of export documents.

16. Containerizing of cargo.

17. Loading of cargo on the ship.

18. Cancellation of export.

19. Communication with associated systems.


2.1 The Overall Description
       The Online Cargo Management System provides cost effective alternatives to help
customers to get better cargo services. The services offered by this system are:

User and Customer verification

       The system will verify the user based on their given logged on information and they will
be given appropriate rights based on their id. The customers will be verified by their id, password
and registration number.

Online booking

       The requester is logged into the retrieval system and an interface of the retrieval system is
provided to the logged-in requestor to allow same to search for items of documentation relating
to such requester and such cargo based on indicia associated with each item.

Order verification

       The order given by the verified customer will be verified by checking the goods
availability in warehouse. The search results include a number of items of documentation, and an
identification of a number of particular ones of the items in the set of search results is received
from the requester. The retrieval system creates a merged electronic document containing all of
the identified items of documentation and the created merged document is delivered from the
retrieval system to one of the requester and a destination selected by the requester.
Goods arrangement in a container

       The goods arrangement in a container is that of orthogonally packing a subset of some
given rectangular-shaped boxes into a rectangular container of fixed dimensions. Each box has
an associated profit and the problem is to choose a subset of the boxes that fits into a single
container so that maximum profit is loaded. If the profit of a box is set to its volume, this
problem corresponds to the minimization of wasted space. An optimal filling of a container
reduces the shipping costs as well as increasing the stability and support of the load.

Finds optimal route

       Usually the need to choose the best route between two points is limited by the
information presented, in form of maps and operation hours for each route. This system offers
new complexity results for optimal route planning. We develop systems that take in account
stops, time, distance, fuel, bridge heights, low underpass and commercial vehicle restrictions and
etc.

Estimates the effective cost

       It optimizes the effective cost through proper goods arrangement in a container and by
finding the optimal route.

Generates various reports

       The retrieval system creates a merged electronic document containing all of the identified
items of documentation and the created merged document is delivered from the retrieval system
to one of the requester and a destination selected by the requester.
                               LITERATURE SERVEY

Chapter : 3 Project Management


3.1   Project Planning

3.1.1 Project Development Approach
The software process model used to develop this system is “Waterfall Model”




                                 Fig 3.1 The Water Fall Model
The model consists of six distinct stages, namely:

 1.    In the requirements analysis phase

            (a) The problem is specified along with the desired service objectives (goals)

            (b) The constraints are identified

  2.     In the specification phase the system specification is produced from the detailed
definitions of (a) and (b) above. This document should clearly define the product function.

  3.     In the system and software design phase, the system specifications are translated into a
software representation. The software engineer at this stage is concerned with:

         Data structure
         Software architecture
         Algorithmic detail and
         Interface representations

 The hardware requirements are also determined at this stage along with a picture of the overall
system architecture. By the end of this stage should the software engineer should be able to
identify the relationship between the hardware, software and the associated interfaces. Any faults
in the specification should ideally not be passed ‘down stream’

  4.     In the implementation and testing phase stage the designs are translated into the software
domain

         Detailed documentation from the design phase can significantly reduce the coding effort.
         Testing at this stage focuses on making sure that any errors are identified and that the
         software meets its required specification.

  5.     In the integration and system testing phase all the program units are integrated and tested
to ensure that the complete system meets the software requirements. After this stage the software
is delivered to the customer [Deliverable – The software product is delivered to the client for
acceptance testing.]

  6.         The maintenance phase the usually the longest stage of the software. In this phase the
software is updated to:

            Meet the changing customer needs
            Adapted to accommodate changes in the external environment
            Correct errors and oversights previously undetected in the testing phases

3.1.2 Project Plan

            Project management approach basically consists of the following 5 steps:

       1. Grouping work in to packages, which acquires the property of the project. These means
             that the work so grouped are related to each other, contribute to the same goals and can
             be bound by definite time, cost and performance targets.
       2. Entrusting the whole project to a single responsibility center known as the project
             manager, for coordinating, directing and controlling the project.
       3. Supporting and servicing the project internally within the organization by through total
             projectization, and external through vendors and contractors.
       4. Building up a commitment through negotiation, coordinating and directing towards
             goals through schedules, budgets and contracts.
       5.     Ensuring adherence to goals through continuous monitoring and control using schedule
             budget and contracts as the basis.
ROLES & RESPONSIBILITIES


         ROLE                  NAME                      RESPONSIBILITY

                                                    Defining scope

                                                    Providing required resources

      Project Guide       Ms. Nafisha Mamti         Project tracking and monitoring.

                                                    Analysis and Effort Estimation.

                                                    Coordination between teams.

                                                    Analysis

                                                    Designing

                                                    Coding
                        1)Dharmendra
                                                    Reporting to Project Guide
    Candidates’s Name
                        2)Ashvin                    Documentation

                                                    Coding

                                                    Reporting to Project Guide

                                                    Testing & maintenance



                          Table 3.1 Roles & Responsibilities
Chapter :4 System Requirement study
4.1 User Characteristics

   Three types of users interact with the system:
   1. Super Administrator: The supreme Administrator will have all rights of the system and
       his main job will be to manage clients and employees. He will have all kinds of reports
       regarding shipments and products stored in warehouse.
   2. Employee: The employee of cargo company will manage orders, products and
       shipments. His main job will be to deliver ordered products to destination on time.
   3. Client User: The client companies will register and can place orders for their stored
       products.
4.2 Hardwares and Softwares Requirements

       Hardware Requirements :

              Client Side:   Minimal requirement for best performance

                                     RAM – 128 MB or Higher
                                     Any GUI based terminal having at least 800*600 screen
                                     resolution
                                     Internet Connection with speed up to 100 Kbps or above,
              Server Side: Minimal requirement for best performance

                                     RAM –256 MB or Higher,
                                     Processor : Pentium 4 or higher.
       Software Requirements :

              Client Side:

                                     Platform-Windows 95,98,2000,XP .
                                     Web Browser – Internet Explorer, Mozilla firefox
                                            or any other web browser.
                                     Client side scripting : .NET with c#.
               Server Side:

                                      Platform -Windows 95,98,2000,XP.
                                      Web Server : IIS
                                      MySQL Server 2005.
                                      Server side scripting : ASP.NET with c#.


4.3 Constraints

4.3.1 User Interface
Although, the user interface is implemented within the context of the problem domain, the
interface itself represents a critically important Subsystem for the most modern application.
Because a wide variety of user interface development environment already exist, the design of
GUI element is not necessary. Reusable classes (with appropriate attributes and operations)
already exist for windows, icons, mouse operations and wide variety of other interaction
functions. The implementer needs only instantiate objects that have appropriate characteristics
for the problem domain.


The user interface design process encompasses four distinct framework activities:
        User, task and environment analysis and modeling.
        Interface design.
        Interface construction.
        Interface validation.


4.3.2   ASSUMPTIONS AND DEPENDENCIES:
The project was started with the assumption that we would be given the necessary support in the
form of hardware and software resources. Our project depends a lot on the inputs.
   •    All the access rights and permissions are given to the Administrator.
   •    No one can enter the system without having a login and password.
   •    All the connections during accessing system are run without fail.
4.3.3 Safety and Security
Security is a very wide-reaching term during every step of application building process you
must, without doubt, be aware of how mischievous end users might attempt to bypass your
lockout measures.
Not every page that you build with ASP.Net is meant to be open and accessible to every one on
the Internet. Some times you want to build pages or section of an application that are accessible
to only a select group of your choosing. For this reasons you need the security measures.
Security can help to protect data behind your application from fraudulent use. We must take step
to ensure that no one can take over the application or gain access to its resources.
We can take different action to protect our application and resources.


Two types of security measures are:
Authentication
        Authentication is a process that determines the identity of user.
Authorization
    Authorization is a process of determining weather and authenticated user is permitted access
to any part of an application. Or access only to specified data sets that the application provides.
ASP.Net provides many different types of authentication measures to use within applications
including basic authentication, digest authentication, forms authentications, integrated windows
authentication. Different authentication modes are established through settings that can be
applied to the application web.config file or with servers IIS.
Chapter :5 Technology and Literature Review


       Diagnostic Center is an essential Medical Management Tool. It also includes some part
hospital management such ward allocation, I.C.U., and O.T. which are the parts of the hospitals.
                                                                                  diagnostic
It combines the features of patient management which includes their registration, diagnost test,
ward allocation, and also for the O.T. allocation if needed and it is not dependent on the
availability of the other software. It should run on Windows based platform.

                                                         are:-
       The following technologies & Designing tools used are:
                        STUDIO-2008(Front End)
       MICROSOFT VISUAL STUDI
                  2005(Back
       SQL Server-2005(Back End)



We are not having any past work system. We are designing this project for the first time. So we
are free to use any technology that we want .Online Recruitment is a web application developed
                                                  server-2005
using ASP.Net using C# used as front end with Sql server 2005 used as back end.




                             Fig 5.1 .NET 2.0 Framework Architecture
The .NET Framework is a set of objects and blueprints from Microsoft for building applications.
The .NET Framework provides the underlying functionality of ASP.NET. All applications
developed under the .NET framework including ASP.NET applications, have certain key feature
that ensure compatibility, security, and stability.

5.1 Common Language Runtime
The Common Language Runtime (CLR) is an environment that manages the execution of code.
In other words, it runs and maintains any code that you write. With the .NET framework and
CLR you still write code and compile it. However, instead of compiling it into something that
computer understands, you compile it into a language called the Microsoft Intermediate
Language (MSIL). This language is shorthand way of representing all the code you have written.
ASP.NET pages are compiled into MSIL as well. When you compile to MSIL, your application
produces something called metadata. This is descriptive information about your application. It
tells what the application can do, where it belongs, and so on.

5.2 Introduction about ASP.NET

ASP.NET, the latest version of Active Server Pages, is Microsoft’s technology for building
dynamic pages, database-driven Web sites. Active Server Pages is one of the most popular
languages for building scalable, interactive Web sites. Several of the highest traffic Web sites on
the Internet employs Active Server Pages. Examples include Dell Online, Barnes and Noble, 1-
800-flowers, and the Microsoft site itself.

Easy Programming Model

ASP.NET makes building real world Web applications dramatically easier. ASP.NET server
controls enable an HTML-like style of declarative programming that let you build great pages
with far less code than with classic ASP. Displaying data, validating user input, and uploading
files are all amazingly easy. Best of all, ASP.NET pages work in all browsers -- including
Netscape, Opera, AOL, and Internet Explorer.

Flexible Language Options

ASP.NET lets you leverage your current programming language skills. Unlike classic ASP,
which supports only interpreted VBScript and JScript, ASP.NET now supports more than 25
.NET languages (including built-in support for VB.NET, C#, and JScript.NET -- no tool
required), giving you unprecedented flexibility in your choice of language.

Great Tool Support

You can harness the full power of ASP.NET using any text editor -- even Notepad! But Visual
Studio 2005 adds the productivity of Visual Basic-style development to the Web. Now you can
visually design ASP.NET Web Forms using familiar drag-drop-double-click techniques, and
enjoy full-fledged code support including statement completion and color-coding. VS.NET also
provides integrated support for debugging and deploying ASP.NET Web applications.

The Professional version of Visual Studio 2005 delivers life-cycle features to help organizations
plan, analyze, design, build, test, and coordinate teams that develop ASP.NET Web applications.
These include UML class modeling, database modeling (conceptual, logical, and physical
models), testing tools (functional, performance and scalability), and enterprise frameworks and
templates, all available within the integrated Visual Studio .NET environment.

Rich Class Framework

Application features that used to be hard to implement, or required a 3rd-party component, can
now be added in just a few lines of code using the .NET Framework. The .NET Framework
offers over 4500 classes that encapsulate rich functionality like XML, data access, file upload,
regular expressions, image generation, performance monitoring and logging, transactions,
message queuing, SMTP mail, and much more!

Compiled execution

ASP.NET is much faster than classic ASP, while preserving the "just hit save" update model of
ASP. However, no explicit compile step is required! ASP.NET will automatically detect any
changes, dynamically compile the files if needed, and store the compiled results to reuse for
subsequent requests. Dynamic compilation ensures that your application is always up to date,
and compiled execution makes it fast.
Rich output caching:

         ASP.NET output caching can dramatically improve the performance and scalability of
your application. When output caching is enabled on a page, ASP.NET executes the page just
once, and saves the result in memory in addition to sending it to the user. When another user
requests the same page, ASP.NET serves the cached result from memory without re-executing
the page. Output caching is configurable, and can be used to cache individual regions or an
entire page. Output caching can dramatically improve the performance of data-driven pages by
eliminating the need to query the database on every request.

Web-Farm Session State

ASP.NET session state lets you share session data user-specific state values across all machines
in your Web farm. Now a user can hit different servers in the web farm over multiple requests
and still have full access to her session. And since business components created with the .NET
Framework are free-threaded, you no longer need to worry about thread affinity.

Memory Leak, DeadLock and Crash Protection:

ASP.NET automatically detects and recovers from errors like deadlocks and memory leaks to
ensure       your      application     is     always      available     to        your    users.
For example, say that your application has a small memory leak, and that after a week the leak
has tied up a significant percentage of your server's virtual memory. ASP.NET will detect this
condition, automatically start up another copy of the ASP.NET worker process, and direct all
new requests to the new process. Once the old process has finished processing its pending
requests, it is gracefully disposed and the leaked memory is released. Automatically, without
administrator intervention or any interruption of service, ASP.NET has recovered from the error.

Dynamic update of running application:

ASP.NET now lets you update compiled components without restarting the web server. In the
past with classic COM components, the developer would have to restart the web server each time
he deployed an update. With ASP.NET, you simply copy the component over the existing DLL
-- ASP.NET will automatically detect the change and start using the new code.
Easy Migration Path:

You do not have to migrate your existing applications to start using ASP.NET. ASP.NET runs
on IIS side-by-side with classic ASP on Windows 2000 and Windows XP platforms. Your
existing ASP applications continue to be processed by ASP.DLL, while new ASP.NET pages are
processed by the new ASP.NET engine. You can migrate application by application, or single
pages. And ASP.NET even lets you continue to use your existing classic COM business
components. ASP.Net represents a radical departure from previous versions of Active Server
Pages.




Following are some of the significant new features of ASP.NET 2.0 Framework:

ASP.NET uses compiled code written in Common Language Runtime language such as Visual
Basic and C#. Unlike previous versions of Active Server Pages, this version not use interpreted
scripting language such as VBScript.

An advanced version of .NET 1.1 which has proved to be a milestone in web technology of
today’s time. ASP.NET pages are built out of server – side controls. Web server controls enable
you to represent and program against Hypertext Markup Language (HTML) elements using an
intuitive object model.

ASP.NET includes a new technology called Web Services. You can use Web Services to access
methods and properties and transfer database data across the Internet. ASP.NET is part of
Microsoft’s .NET framework. You can access thousands of .NET classes in your code that
enable you to perform such wondrously diverse tasks as generating images on - the - fly and
saving an array to a file. ASP.Net includes page and data caching mechanisms that enable you to
easily and dramatically improve the performance of your Web Site.
Introduction about ADO.NET

ADO.NET is the next generation ActiveX Data Objects (ADO). It’s a model access that was
built with scalability, the statelessness of the web, and XML as its core. ADO.NET provides an
interface to all OLE DB- compliant data source and lets you connect to, retrieve, manipulate, and
update them. You can use it whether you’re in a remote environment, using a distributed
application, or using disconnected data.

In term s of ASP.NET development, ADO.NET provides the framework for accessing any type
of data for use with ASP.NET pages. This allows users to view or change information stored in
any kind of data warehouse, including, databases, text files, and XML data stores.

Although Microsoft has touted ADO.NET as the next evaluation of ADO, and though it has
some of the same objects, it’s really very different than its predecessor. Whereas ADO was
connection-based, ADO.NET relies on short, XML message interactions with data sources. This
makes ADO.NET much more efficient for Internet based application.

A fundamental change from ADO to ADO.NET was the adoption of XML for data exchanges.
XML is a text based markup language, similar to HTML that presents an efficient way to
represent data. ADO.NET is intimately familiar with XML and uses it in all transactions. This
allows ADO.NET to reach exchange and persist data stores much data is easily converted to and
from any type of data. IT doesn’t require the complex conversions that wasted processor time
with classic ADO.

Another major change is the way ADO.NET interacts with databases. ADO requires “locking” of
database resources and lengthy connections for its applications, but ADO.NET doesn’t; it uses
disconnected data sets, which eliminates lengthy connections and database locks. This makes
ADO.NET much more scalable because users aren’t in contentions for database resource.

This new option enables a DataSet and a DataTable to be serialized in binary format when using
binary transports over remoting. In most cases this will result great performance improvements
and a noticeable reduction in both memory and CPU usage when using DataSet/DataTable
objects in applications that use remoting to connect to different tiers. DataTable as a Stand-Alone
Object .
Many methods that were only available in the DataSet in previous versions are now available in
the DataTable as well (such as ReadXml and WriteXml). Also, a DataTable can be serialized by
itself, so it’s no longer necessary to have a DataSet with a single table just to expose the table
through Web services or any other mechanism that requires serialization.

Create a DataTable from a DataView.

You can now create a DataTable from a DataView. The new DataTable will have the same set
of rows as the current DataView. Optionally the columns of the new DataTable can be a subset
of the DataView columns. The rows can be either all rows or only distinct rows.

Schema Inference Engine Enhancements. The schema inference engine has been enhanced to
infer types when enough information is available; it is also significantly faster.




Namespace-qualified Tables

A DataSet can now support tables that have the same TableName but with a different
Namespace, providing a mechanism to avoid naming conflicts.

New DataTable Loading Capabilities

The new Load method for DataTables and DataSets can stream a DataReader into a DataTable
directly. The Load method also has new options for load behavior that extend the functionality
available through the DataAdapter.

Row State Control.

The new SetAdded and SetModified methods allow applications to explicitly manipulate the row
state for DataSet and DataTable rows.

Enhanced Support for Custom Defined Types

The DataTable provides more support for custom, user-defined types. XML serialization has
been extended to support polymorphism. For example, a Person Column can store an Employee
instance that gets serialized and de-serialized to and from XML without loss of any type fidelity.
Additionally users can now implement the new change tracking interfaces that enable the
DataTable to track changes for such objects.

XML/XSD Enhancements.

Added support for reading and writing simple types in XSD. Added support for reading and
writing of multiple schemas to a stream. Added support for reading and writing of XSD/XML
where a single table or XML Element is nested inside two or more parent tables.

DataRow Enhancements

The new IndexOf can be used to find position of row in DataTable.Rows collection.

Change Position of Column in DataTable. The new SetOrdinal method allows users to change
the position of the column in a DataTable.

DataView Performance Improvements

The DataView in ADO.NET 2.0 uses a new update algorithm resulting in significant
improvement in DataView maintenance.

DataColumn Expressions

An expression in a DataColumn can include columns from the same DataTable. The expression
can be updated, and the column value is maintained.
         WORKING / IMPLEMENTATION OF THE PROJECT WORK
                          /SIMULATION

Chapter : 6 Implementation planning and Details


6.1 Implementation Environment.

As far as our project is concerned, any person who is little bit aware of application and those
who are willing to get information can use this project. As we are planning to carry this
application to GIS based project. The application can be used by many users. If just a single user
uses application then the application will be bound to its personal needs. But if application is
carry forwarded to Internet then database can be expanded to satisfy various users at a time. But
due to shortage of time we had tried to cover all information of single user. This application is
rich with GUI, so it can be understand by naïve users also.


SINGLE USER:

Here, Our Application Geo-graphic Information system (GIS) is a desktop based application and
is purposefully developed for single user. So, as an implementation environment it made for
single user.

GUI:

This is a kind of system, which is user friendly because of its high interactive graphics. It is a
kind of geographic information system based on colored maps and images, which makes its uses
easier and high interactive. So as a part of implementation it is GUI based single user
application.


6.2      Program/Modules Specification
Two main modules are dealing with the system.
      1. Admin
      2. User
The admin module is the main module in our system. Admin can maintain and visualize all the
records of users & files.
The user module is another module of the system which has either partial or full rights. User can
login through his id. & perform work which he/she gets rights.

6.3 Security Features
Security means protecting data and programs against accidental or intentional
destruction or disclosure to unauthorized person. The data and programs must be
protected from theft, fire, disk corruption and other types of physical destruction.


Following steps were taken to protect our system.


1. We needed to take regular backups of our project and database away from the
data processing centre, so that data can be reconstructed whenever necessary.


2. Only authorized users can access or edit the system, so that the security will
not be violated.

6.4 Coding Standards

The coding standards are the well-defined and standard styles of coding. With the
help of the coding standard, any person can go through the code and figure out what’s
going on and new people can get up to speed quickly. A coding standard sets out
standard ways of doing several things such as the way variables are to be named, the
code is to be laid out, the comments are to be described, the work of function are to be
carried out etc.
This section describes the coding standards, which we have used in the program. In
the context of coding standard, the tag consists of one to six lower case characters
followed by an underscore and is used to indicate the type of an object, control or
variable. The prefix applies only to variable names and consists of a single lower case
character used to indicate the variable’s scope. The following coding standards have
been adopted.
Variable Declarations:
   •   We have placed the local variable declarations in the beginning.
   •   The blocks of declarations have been aligned.
Naming Conventions:
   •   The names of the variables that we have used represent the content, purpose or
       the role of the variable.
   •   We have defined each of the variables with a length of seven to eight
       characters.
   •   However the function-names are longer in order to provide a better indication
       of the actions performed by them.


Controls:
       The standard controls that are provided by the Visual studio 2005 are
used. No active controls are used in this application.
                                    RESULT ANALYSIS
Chapter : 7 System Analysis

7.1 Study of Current System
   2. In the current cargo management system the user client was given an account Id and on
        the basis of that the user client can access the account and places the orders. They can
        manage their profile and also manages their clients’ (secondary customer) profiles. They
        able to view the details of their stored products but can’t modify it. They are only allowed
        to place the order and to store the details regarding orders.
   3.
   4. The user employee manages their customers, their products, their customers and depends
        on that they decide the shipment which can places more than one order in a single trip. As
        more orders are placed in minimum no. of trips, the company can gain more profits.


7.2 Problem and weakness of Current System
   •    Now-a-days in the current system the user first need to register them selves at company
        and after getting their account Id they are allowed to register them selves in the system.
   •    In some of the current system the employee have to decide the all shipment details rather
        than a system helps it. He has to decide which orders can be placed in a single trip and
        which route should be followed.
   •    The disadvantage arise from these system is that there is more manual work and that
        doesn’t full fill users’ requirements properly. Hence it doesn’t give the efficient work.


7.3 Requirement of new System
7.3.1   User Requirements:-

As we developed this application for the cargo company, which manages the warehouse and
manages the transportation and gives better services to the client companies , this application
will be helpful for the following categories.
Employees

They can arrange shipment in such a way that the cargo company can get more benefits. It’s
possible by delivering more orders in minimum number of trips and by on time shipments. This
is possible only if a container contains more goods and when the minimum transportation route
is followed. The system will help to them to find optimal route and to arrange goods in proper
way by ultimate loading facilities. Even they can load manually using the system.

ADMIN

The admin will all rights of the system. He can manage whole system by allowing requested
clients and employees to access the system. Even he can arrange or update any details and
shipments as well.

Clients

They will have better services and can place orders in easy way. Even they can manages their
customers’.

7.3.2 System Requirements

7.3.2.1 Functional Requirements: Functional requirements are those that refer to the
functionality of the system. It specifies which output should be produced from the given input. It
describes the relationship between the input and output of the system.

Module 1: Registration/Login

Requirement ID                   1

Requirement Name                 Registration

Requirement Description          To register particular User

Requirement Input                Following details of the customer
                                 Client Id
                                 Client Name
                                 Company Name
                            Address
                            Contact No
                            Email ID
                            User ID
                            Password
                            Security question
                            Answer

Requirement Process         All the information will be stored in the database,
                            client_reg

Requirement Output          Confirmation of registration

Requirement Pre-Condition   Customer has to click on the signUp link



Requirement ID              2

Requirement Name            Login

Requirement Description     To make the user logged into the system to place the
                            order

Requirement Input           UserId, Password

Requirement Process         System will validate the user

Requirement Output          If the user is valid than will logged into the system and
                            redirect to the Home page.
                            If the user is not valid than will redirect to the login
                            page.

Requirement Pre-Condition   A registered user has to click on the signIn link



Requirement ID              3

Requirement Name            Password Recovery

Requirement Description     If any user forgets his/her password than he/she can
                            recover it from this facility
Requirement Input           UserId, Answer of the Security Question

Requirement Process         System will match the answer of the security question of
                            the given UserId in the database entry of the table
                            client_reg

Requirement Output          If the UserId and Answer of the security question
                            matched than user can enter the new password

Requirement Pre-Condition   Registered user has to give correct UserId and Answer
                            of the security question he has submitted at the time of
                            the registration




Requirement ID              4

Requirement Name            Change Password

Requirement Description     User can change his/her password

Requirement Input           Old password
                            New password
                            Confirm password

Requirement Process         If the old password is correct than old password will be
                            updated with the new password

Requirement Output          Password will be changed

Requirement Pre-Condition   User has to log in and enter the correct old password



Requirement ID              5

Requirement Name            Search Client

Requirement Description     To search the client companies

Requirement Input           Company name/ it’s first letter

Requirement Process         System will search the company

Requirement Output          The system will show the details of selected company.

Requirement Pre-Condition   Any employee or admin can search the company.
Module 2: Package management

Requirement ID                 6

Requirement Name               Add Package Details

Requirement Description        Details of the package will be stored in the database,
                               package details

Requirement Input              Following details will be stored,
                               package ID
                               package Name
                               package Type
                               package Weight
                               package Length
                               package Height
                               package Width
                               Section ID (Id of the section of the warehouse where the
                               package is stored)
                               package Quantity
                               Client ID (manufacturer of the package)

Requirement Process            package details will be saved in the database, package
                               details

Requirement Output             New package details are stored safely

Requirement Pre-Condition      package details can be added by only admin or
                               employees



Requirement ID                 7

Requirement Name               View package Details

Requirement Description        Admin/Employee/client can view the package details

Requirement Input              Keyword and/or
                               package ID and/or
                            Client ID and/or
                            package Type and/or
                            Section ID

Requirement Process         package will be searched according to the input

Requirement Output          Searched package will be displayed

Requirement Pre-Condition   Any package detail must be given



Requirement ID              8

Requirement Name            Update package Details

Requirement Description     Admin/Employee can update any package details

Requirement Input           package ID
                            package Name
                            package Type
                            package Weight
                            Section ID (Id of the section of the warehouse where the
                            package is stored)
                            package Quantity
                            Client ID (manufacturer of the package)

Requirement Process         Modified details will be saved in the database

Requirement Output          Updated package will displayed as a confirmation

Requirement Pre-Condition   package details must be pre added in the database



Requirement ID              9

Requirement Name            Delete package Details

Requirement Description     Admin/Employee can delete the package details

Requirement Input           package Name and
                            package ID
Requirement Process          package details will be searched by given input in the
                             database and if it exist then system will delete the record

Requirement Output           package details will be deleted successfully from the
                             database

Requirement Pre-Condition    package details must be pre added in the database



Requirement ID               10

Requirement Name             Search package

Requirement Description      To search the package

Requirement Input            package name/Company name/ it’s first letter

Requirement Process          System will search the package

Requirement Output           The system will show the details of selected company’s
                             package and its details.

Requirement Pre-Condition    Any employee or admin can search the company.



Module 3: Order management

Requirement ID               11

Requirement Name             Order Placement

Requirement Description      Client can place the order

Requirement Input            Order ID
                             package ID
                             package Name
                             Total Quantity
                             Required Quantity
                             Order Date/Time
                             Delivery Date/Time
                             Customer Name (customer of the client)
                             Destination Address
                            Contact Number (customer of the client)
                            Email ID (customer of the client)
                            Fax number (customer of the client)

Requirement Process         Order placement details will be stored in the database,
                            order details

Requirement Output          Order details will be displayed

Requirement Pre-Condition   Client must login and Required quantity should be less
                            or equals to total quantity



Requirement ID              12

Requirement Name            Cost Estimation

Requirement Description     Cost will be estimated by the given order details

Requirement Input           package ID
                            package Name
                            Required Quantity
                            Destination Address
                            Total weight (in case of heavy weight packages) or
                            Total area (in case of low weight packages)

Requirement Process         Cost will be calculated according to the inputs

Requirement Output          Cost will be displayed to the client

Requirement Pre-Condition   Order details must be given



Requirement ID              13

Requirement Name            Update Order

Requirement Description     If client wants to change the order than he/she can
                            update the order before the confirmation

Requirement Input           package ID
                            package Name
                            Total Quantity
                            Required Quantity
                            Order Date/Time
                            Customer Name (customer of the client)
                            Destination Address
                            Contact Number (customer of the client)
                            Email ID (customer of the client)
                            Fax number (customer of the client)

Requirement Process         Modified details will be saved in the database, order
                            details

Requirement Output          Modified details will be displayed to the user

Requirement Pre-Condition   The order must be existed and must not be confirmed



Requirement ID              14

Requirement Name            Cancel Order

Requirement Description     Client can cancel the order

Requirement Input           Cancel button

Requirement Process         Whenever client clicks on the cancel button the order
                            will be cancelled

Requirement Output          Client will redirect to the new order placement page

Requirement Pre-Condition   The order must be existed and must not be confirmed



Requirement ID              15

Requirement Name            Confirmation

Requirement Description     The order will be confirmed and can not be modified or
                            cancelled after then

Requirement Input           Confirm button

Requirement Process         After clicked on the confirmation button the order will
                              be confirmed

Requirement Output            A confirmation message will be displayed to the client

Requirement Pre-Condition     Order should be existed



Module 4: Cargo Arrangement

Requirement ID                16

Requirement Name              Order Filtering

Requirement Description       To filter orders for packing

Requirement Input             Order details from the table order_details

Requirement Process           System will divide orders in the groups according to
                              their destination and delivery time

Requirement Output            Filtered orders

Requirement Pre-Condition     Orders should be existed



Requirement ID                17

Requirement Name              Arrange packages in container

Requirement Description       Filtered goods are manually arranged in the boxes and
                              then system will arrange these boxes in container

Requirement Input             Length
                              Width
                              Height
                              Weight of Manually arranged boxes
                              Length
                              Width
                              Height
                              Capacity (in weight) of container

Requirement Process           Shapes will be created according to the input and it will
                              be Drag and drop in the container
Requirement Output               Successfully Arranged container

Requirement Pre-Condition        Details of the box must be available



Module 5: Cargo Transportation

Requirement ID                   18

Requirement Name                 Deciding Route for Transportation

Requirement Description          Selection of best route for the transportation of the
                                 goods

Requirement Input                Current location
                                 In between delivery location
                                 Destination

Requirement Process              System will calculate the distance between locations and
                                 than according to this distance it will find the best route

Requirement Output               Route information to follow

Requirement Pre-Condition        Location must be given



Module 6: Report Generation

Requirement ID                   19

Requirement Name                 Report Generation

Requirement Description          Reports are generated for the records

Requirement Input                Details of order:
                                 package ID
                                 package Name
                                 Total Quantity
                                 Required Quantity
                                 Order Date/Time
                                 Delivery Date/Time
                                   Customer Name (customer of the client)
                                   Destination Address
                                   Contact Number (customer of the client)
                                   Email ID (customer of the client)
                                   Fax number (customer of the client)


                                   Details of package:
                                   No of packages
                                   Gross weight
                                   Delivery time

Requirement Process                Report will be generated and printed for the record

Requirement Output                 Printed reports

Requirement Pre-Condition          All the details must be filled


   7.3.2.2 Non-Functional Requirements
Reliability & Availability

The information needs to be reliable enough so as to give the user a proper visualization of
the map which is displayed. Any sort of unreliable information will lead to inappropriate
results. Availability deals with the availability of various shape files.

Security

The security concerns are less for this application as compared to other applications as it
is a form based application which does not have any restriction on the user. Also it is
necessary that confidential information from the database is not shown to the user.

Portability

The database is built for a particular system and may not be portable but the results of
queries will be portable between many environments.
Correctness

The output of the operations performed by the user should be precise.

Efficiency

The application needs to be efficient enough to maintain the criticality of the application.

Usability

The inputs and outputs of this application can be easily understood by the user, hence
making it easily usable.

Testability

Each and every feature of the application should be testable in order to ensure smooth working of
the software.



7.4 Requirement Validation

Requirements validation is concerned with showing that the requirements actually define the
system that user wants. If this validation is inadequate, errors in the requirements will be
propagated to the system design and implementation. Requirements are checked to discover if
they are complete, consistent and in accordance with what users want from the projected system.

Validity: - A user may think that a system is needed to perform certain functions.

Consistency: - Any one requirement should not conflict with any other.

Completeness: - The definition should include all functions and constraints intended by the
system user. The software provides all the user requirements.
7.5 Function of System
7.5.1   Use Case Diagram




                           Fig 7.1 Use Case Diagram(Display Module)
7.6     Data Modelling
7.6.1   Class Diagram




                         Fig 7.2 Class Diagram
7.6.2 E-R Diagram




                    Fig 7.3 E-R Diagram
7.6.3 SYSTEM ACTIVITY DIAGRAM




                      Fig 7.4 System Activity Diagram
7.7 FUNCTIONAL AND BEHAVIORAL MODELING
7.7.1 Context Diagram




                        Fig 7.5 Context Diagram
7.7.2 Control Flow Diagram




                             Fig 7.6 Control Flow Diagram
7.8 Main Modules of new System

There are mainly four modules which are briefly described as below:

       Module 1: Registration/Login
              This module manages the details of users which are used to verify them.

          Registration
              It is the process by which the new users will store their details and will manage
       their personal profile.

          Login
          It is the process by which individual access to a computer system is controlled by
       identification of the user using credentials provided by the user.

          Change password
          The user can change his password by verifying his identity by either giving old
       password or by giving correct answer of security question.

          Forgot Password
          In such cases when the user has forgotten his password, he can have his password
       back on his given E-mail Id by giving the correct answer of security question.




        Module 2: Product management
              In this module the product details will be managed by employee of cargo
       management Company.

          Add Product details
          Here the product details will be added into database.

          View Product details
          The product details will be fetched from database and can be viewed to user.

          Delete product details
    The products which are already delivered and not required to store its information for
long time will be deleted from database.

    Update product details
    The product details will be updated by employee.



 Module 3: Order management
    The order will be managed by deciding estimated delivery time and the optimized
cost.

    Order Placement
    Client can place orders online efficiently.

    Cost estimation
    On the basis of order system will display cost of shipment.

    Update order
    Client can update the previously given orders

    Cancel order
    Client can cancel the order.

    Confirmation
    If client will successfully place the order system will give the confirmation of the
    order .




Module 4: Cargo Arrangement


    Order Filtering
    To arrange goods into container first the number of orders will be filtered according
to destination and date/time of delivery.

    Arrange cartons in container
    System will generate the 3 dimension shape of the cartoon from given input. These
shapes will be placed into container size in such a way that it optimizes the available
space.




Module 5: Cargo Transportation


    Deciding Route for Transportation
Form the given input orders details the system will decide the appropriate route of
shipment.




Module 6: Report Generation


    Report Generation
System will generate various reports like delivery report, monthly report, transportation
details etc.
                                          CONCLUSION

Chapter :8 Conclusion
From the project “Cargo Management System” we can conclude the following points as
under:-

          This system is extremely useful for the employees of the center as the work gets
          incredibly decreased.

          Also it saves the time and can get more efficient work in less time.

          The system provides high grade and accurate result of clients to deliver their products on
          time.

          To ensure the highest quality consulting services to meet and exceed customer
          expectations.
          To ensure the customers are given the best information and services delivery, creating
          value added benefits for their business.
          Centralized Data Store available.
          Easy to Handling customer destination data.
          More powerful tools use in the system.
          Export documentation.
                          LIST OF REFERENCES




       www.gati.com
       www.cargomanagementsystem.co.za
       www.paramcargo.com
       www.sourceforge.com
       www.seatech.bc.ca
       www.onboardsystem.com




Marcel Huschebeck, Robert Piers, Dick Mans, Michael Schygulla, Dieter Wild (1994)
Intelligent Cargo Systems study (ICSS) Impact assessment study on the introduction of
intelligent cargo systems in transport logistics industry

				
DOCUMENT INFO
Shared By:
Tags:
Stats:
views:0
posted:6/19/2013
language:
pages:61