Eazy Export

7/18/2019 Eazy Export

http://slidepdf.com/reader/full/eazy-export 1/22

EazyExport

ABSTRACT

This project is aimed to manage the export activities of the organization, which exports

different kind of goods to their customers across the globe. The application should provide

customers a facility to order the goods from any part of the world. Customers are registered

to organizations or firms in their countries. The goods can be sent to the customers by various

means of transportation. Every new customer has to register as a user to the site. The

application will provide different levels of authentication.

The project has been planned to be having the view of distributed architecture, with

centralized storage of the database. The application for the storage of the data has been

planned. sing the constructs of !"#"$% "erver and all the user interfaces has been

designed using the &"'.(et technologies.

The application takes care of different modules and their associated reports which are

produced as per the applicable strategies and standards that are put forwarded by the

administrative staff.

)eeping track of goods which we are exporting is done manually now. *ecause of

this the exporter may not know whether the goods which are exported have reached the

destination properly or not. Customers also will not have any tracking, regarding this.

sing this system we have a comprehensive solution for managing product export

information while managing details of products, supplies and invoice information.



LIST OF TABLES

Table No Title Page No

+.-Chapter no.Table no

tblUserLogin

tblRoadBills

tblSippingBill



tblS!ppliers

tblPay"ent



TblOrder

tblIn#oi$e%etails



tblProd!$ts

tblPersonal%etails



tblC!rren$y

tblAddress%etails

tbl&Stat!s



tblAd"inLogin

tbl&Co!ntry

TblBill%etails



re$eiptdetails

tablelin's



tbl&City%etails

tbl&State

LIST OF FI(URES



Fig!re No Title Page No

.

/.

+.

+./

+.++.0

+.1

+.2

+.3

LIST OF ABBRE)IATIONS

ACRON*+ E,PANSION

%SR 4ynamic "ource 5outing

FSR 6isheye "tate 5outing 'rotocol

I%T 7ndirect TrustI%TRE- 7ndirect Trust 5e8uest

I%TREP 7ndirect Trust 5eply

TTL Time To %ive

INTRO%UCTION

./. OB0ECTI)ES

This project is to manage the export activities of the organization, which exports

different kind of goods to their customers across the globe. The application provide

customers to order for the goods from any part of the world. Customers are registered to

organizations or firms in their countries. Every new customer has to register as a user to the

site. The application should provide the different levels of authentication. The goods can be

sent to the customers by any means e.g. by air, road etc. The 'erforma 7nvoice and



4ocuments 4elivery 4etails should also be maintained by the application. The project has

been planned to be having the view of distributed architecture, with centralized storage of the

database. sing the constructs of !"#"$% "erver and all the user interfaces has been

designed using the &"'.(et technologies. The standards of security and data protective

mechanism have been given a big choice for proper usage. The application takes care of

different modules and their associated reports which are produced as per the applicable

strategies and standards that are put forwarded by the administrative staff.

./1 SCOPE

The proposed application needs to cater services to customer across the globe with

8uality and timeliness. This application is also re8uired to show case the range of serviceswhich are there with the company to get the customer attention to maximum extent. &part

from getting business from customer the application should also keep track of ordered

information, payments information etc. sing this system we have a comprehensive solution

for managing product export information while managing details of products, supplies and

invoice information. The features available are9 managing master data related to customers,

suppliers and products, creation of customer invoices, tracking invoice, administering the

customers and suppliers.

LITERATURE SUR)E*

1 /. E,ISTIN( S*STE+

)eeping track of goods which we are exporting is done manually now. *ecause of

this the exporter may not know whether the goods which are exported have reached the

destination properly or not. Customers also will not have any tracking, regarding this. 7t is

less user#friendly and involves lots of manual work. 7t is unable to generate different kinds of

reports.



1/./. ISSUES

• 7t is limited to a single system.

• 7t is less user#friendly.

• 7t is having lots of manual work -include working on spread sheets and other

simple software:s.

• The present system is very less secure.

• 7t is unable to generate different kinds of report.

• 7t doesn;t have the mail and file upload feature.

1/1 PROPOSE% S*STE+

The development of the new system contains the following activities, which try to

automate the entire process keeping in view of the database integration approach.

• ser friendliness is provided in the application with various controls.

• The system makes the overall project management much easier and flexible.

• 7t can be accessed over the 7nternet.

• <arious classes have been used to provide file upload and mail features.

• There is no risk of data mismanagement at any level while the project

development is under process.

• 5eport generation feature is provided using Crystal 5eports to generate different

kinds of reports.

7t provides high level of security using different protocols like https etc.

+od!les

The following modules are identified in the system.

&dmin, Customer, "upplier, ser, 7nvoice, 5eports, and &uthentication.

Ad"in

This module contains all the information about the &dmin. =e can add all the

products and all the employees and all the suppliers and he can generate invoice for the

customer when they order for any product and he can also give the billing information to the



user when they buy the products. >hen any suppliers add any product admin will get that

information and when he is updating that product then only all the customer and supplier can

see the product else they can;t see the product.

C!sto"ers

This module contains all the information about the customer. Customer are the

registered person who will select the product which they want to order. when they click on

order then that product will go to admin view and admin will create the invoice for that and

after that invoice is once again seen by the customer and when the customer click on ok then

based on that invoice billing will be created by the admin and that billing can be seen by the

customers.

Suppliers:

This module contains all the information about the Suppliers. He can add new

products; can view the list of the customers who bought products from his organization.

Users:

This module contains information for the Users. Users are the general public

who can view the product information available.

Invoice:

This module contains all the information about the Invoice. Invoice is

generated by the admin based on the particular customer, particular products. He

can also send the invoice to the user for confirmation.

Reports:

This module contains all the information about the reports generated by the

admin based on the particular user, particular uotation, all customers or users, all

uotations generated by the users.

Authentication:

Using this module authentication is provided so that only authenticated user

can use all the features of the system. Unauthorized users have restricted access.



OR(ANI2ATION PROFILE

CONTENTS

./ INTRO%UCTION

.. 7(T5?4CT7?( T? '5?@ECT

./. '5'?"E ?6 T=E '5?@ECT

.+. '5?*%E! 7( EA7"T7(B ""TE!

.0. "?%T7?( ?6 T=E"E '5?*%E!"

1/ S*STE+ ANAL*SIS

/.. ""TE! >?5)6%?>

1/1/ "T4 ?6 T=E ""TE!

1/3/ =&54>&5E D "?6T>&5E 5E$75!E(T

1/4/ 7('T D ?T'T

1/5/ '5?CE"" !?4E%" "E4 >7T= @"T767C&T7?(

3/ FEASIBILIT* REPORT

+.. TEC=(7C&% 6E&"7*7%7T

+./. ?'E5&T7?(&% 6E&"7*7%7T+.+. EC?(?!7C 6E&"7*7%7T

4/ SOFT6ARE RE-UIRE+ENT SPECIFICATIONS

0.. 6(C7?(&% 5E$75E!E(T"

0./. 'E56?5!&(CE 5E$75E!E(T"

5/ SELECTE% SOFT6ARE

1.. 7(T5?4CT7?( T? .(ET 65&!E>?5)

1./. &"'.(ET1.+. @ava "cript

1.0. 77" 2.

1.1. CF.(ET

1.2. "$% "E5<E5

7/ S*STE+ %ESI(N

2.. 7(T5?4CT7?(

2./. (?5!&%7G&T7?(

2.+. E#5 47&B5&!

2.0. 4&T& 6%?> 47&B5&!"

7/5/ 4&T& 47CT7?(&5



8/ OUTPUT SCREENS

9/ S*STE+ TESTIN( AN% I+PLE+ENTATION

H.. 7(T5?4CT7?(9/1/ TE"T7(B ?*@ECT7<E"

9/3/ (7T TE"T7(B

9/4/ TE"T '%&(

9/5/ 7!'%E!E(T&T7?(

:/ S*STE+ SECURIT*

I.. 7(T5?4CT7?(

I./ "EC57T 7( "?6T>&5E

.;/ CONCLUSION

../ FUTURE I+PRO)E+ENT

.1/ BIBLIO(RAP<*

%ETAILE% ARC<ITECTURE %ESI(N OF T<E

PRO0ECT

3 Tier Ar$ite$t!re

There are three layers in + Tier &rchitecture as given below9#

. 'resentation %ayer -7 %ayer

/. *usiness &ccess %ayer -*&%

+. 4ata &ccess %ayer -4&%

./= Presentation Layer >UI=9#



'resentation %ayer is nothing but it is a user interface which every user see on your

computer, mobile and window screen. ou can say, designing part of any application is

known as 'resentation %ayer. The ser can post input and get output on your presentation

%ayer only. 7n asp.net .axpx file is known as a presentation layer.

1/= B!siness A$$ess Layer >BAL=9#

*usiness &ccess %ayer is act as mediator %ayer between 'resentation layer and 4ata

&ccess layer. This layer is used to transfer the data between 'resentation %ayer and 4ata

&ccess %ayer. This layer is mainly used for <alidations and calculations purpose.

Every validations and calculations of data are held on that layer only. 7 have also

implemented Property layer or Entity Layer concepts in *usiness &ccess %ayer. 7t is

optional layer if you are working on a small projects. *ut if you are working on large projects

then you have to include this layer in your + Tier &rchitecture &pplications. 7t is used to

enhance the security and prevent to brokering the application.

3/= %ata A$$ess Layer >%AL=9#

This %ayer only communicate with *usiness &ccess %ayer. 4ata &ccess %ayer

contains the methods that helps *usiness &ccess %ayer. *usiness layer class:s methods call

the 4ata &ccess %ayer Class methods to perform some re8uired action with database such as

insertion, deletion, updation etc. &ll database related connection codes are written in this

layer only such as s8l 8uery, stored procedure etc.

ou can easily understand the exact concepts of + Tier &pplications as show below9#



6at are te ?or'ing pro$ess o@ 3 Layers9#

>hen any user post data from your presentation layer -user 7nterface layer

Thenthis data first goes to *usiness &ccess %ayer &fter that validation and calculation are held

on this layer &fter that this data pass data to 4ata &ccess %ayer &fter that data &ccess

%ayer fetch re8uired data or insert the data in database &fter that 4ata &ccess %ayer pass

the re8uired data to the business &ccess %ayer &fter that *usiness &ccess %ayer send the

re8uired data to the 'resentation %ayer &fter that 'resentation %ayer is responsible to

display the re8uired data to the user:s computers or mobiles or >indows.

6y does ?e !se 3 Tier Ar$ite$t!re#

There are following reasons to use + Tier &rchitecture in our asp.net application as given

below9#

• To increase the security in &pplication.

• To easily maintain the application.

• To easily modify or change in application.

• To reduce the server over load.

• To reduce the loading time of application.



Ad#antages o@ 3 Tier Ar$ite$t!re9#

• Each layer always use your separate codes, so it is easy to modify the codes.

• 7t is helpful to easily maintain and understand the large projects.

• ou can easily change your graphical Environment.

• 7t is more secure because any users can:t access the database directly.

• ou can easily change any layer codes without affecting other two layers.

• 7t is a more consistence application.

%ATA FLO6 %IA(RA+S

& data flow diagram is graphical tool used to describe and analyze movement of data

through a system. These are the central tool and the basis from which the other componentsare developed. The transformation of data from input to output, through processed, may be

described logically and independently of physical components associated with the system.

These are known as the logical data flow diagrams. The physical data flow diagrams show

the actual implements and movement of data between people, departments and workstations.

%F% S*+BOLS

7n the 464, there are four symbols,

• & s8uare defines a source -originator or destination of system data.

• &n arrow identifies data flow. 7t is the pipeline through which the information flows.

• & circle or a bubble represents a process that transforms incoming data flow into

outgoing data flows.

• &n open rectangle is a data store, data at rest or a temporary repository of data.



'rocess that transforms data flow.

"ource or 4estination of data.

4ata flow

4ata "tore

CONSTRUCTIN( A %F%

"everal rules of thumb are used in drawing 464;"9

• 'rocess should be named and numbered for an easy reference. Each name should be

representative of the process.

• The direction of flow is from top to bottom and from left to right. 4ata traditionally

flow from source to the destination although they may flow back to the source. ?ne

way to indicate this is to draw long flow line back to a source. &n alternative way is

to repeat the source symbol as a destination. "ince it is used more than once in the

464 it is marked with a short diagonal.

• >hen a process is exploded into lower level details, they are numbered.

• The names of data stores and destinations are written in capital letters. 'rocess and

dataflow names have the first letter of each work capitalized



Context Le#el %iagra"

First Le#el %F%



Se$ond Le#el %F%

Tird Le#el %F%

Eazy Export

Documents

Transcript of Eazy Export