CONTENTS

1. INTRODUCTION

1.1. INTRODUCTION TO PROJECT1.2. PURPOSE OF THE PROJECT 1.3. PROBLEM IN EXISTING SYSTEM1.4. SOLUTION OF THESE PROBLEMS

2. SYSTEM ANALYSIS

2.1. SYSTEM WORKFLOW2.2. STUDY OF THE SYSTEM2.3. HARDWARE & SOFTWARE REQUIRMENT 2.4. INPUT & OUTPUT 2.5. PROCESS MODELS USED WITH JUSTIFICATION

3. FEASIBILITY REPORT

3.1. TECHNICAL FEASIBILITY3.2. OPERATIONAL FEASIBILITY3.3. ECONOMIC FEASIBILITY

4. SOFTWARE REQUIREMENT SPECIFICATIONS

4.1. FUNCIONAL REQUIREMENTS4.2. PERFORMANCE REQUIREMENTS

5. SELECTED SOFTWARE

5.1. INTRODUCTION TO .NET FRAMEWORK 5.2. ASP.NET5.3. Java Script5.4. IIS 6.05.5. C#.NET5.6. SQL SERVER

6. SYSTEM DESIGN

6.1. INTRODUCTION6.2. NORMALIZATION6.3. E-R DIAGRAM6.4. DATA FLOW DIAGRAMS6.5. DATA DICTIONARY

7. OUTPUT SCREENS

8. SYSTEM TESTING AND IMPLEMENTATION

8.1. INTRODUCTION8.2. TESTING OBJECTIVES8.3. UNIT TESTING8.4. TEST PLAN8.5. IMPLEMENTATION

9. SYSTEM SECURITY

9.1. INTRODUCTION9.2 SECURITY IN SOFTWARE

10. CONCLUSION

11. FUTURE IMPROVEMENT

12. BIBLIOGRAPHY

CHAPTER- 1

1.1 INTRODUCTION

This project is aimed to manage the export activities of the organization, which exports different kind of goods to their customers across the globe. 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 Performa Invoice and Documents Delivery Details 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. Using the constructs of MS-SQL Server and all the user interfaces has been designed using the ASP.Net technologies.

1.2 EXISTING SYSTEM

Keeping track of goods which we are exporting is done manually now. Because 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. It is less user-friendly and involves lots of manual work. It is unable to generate different kinds of reports.

1.2.1 ISSUES

It is limited to a single system. It is less user-friendly. It is having lots of manual work (include working on spread sheets and other simple software's). The present system is very less secure. It is unable to generate different kinds of report. It doesnt have the mail and file upload feature.

1.3 PROPOSED SYSTEM

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.

User friendliness is provided in the application with various controls. The system makes the overall project management much easier and flexible. It can be accessed over the Internet. Various 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. Report generation feature is provided using Crystal Reports to generate different kinds of reports.It provides high level of security using different protocols like https etc.

CHAPTER- 2

2.1 SYSTEM REQUIREMENTS SPECIFICATION2.1.1 SOFTWARE Windows XP/Windows 7/ Windows 8. Visual Studio .Net 2010 Ultimate Edition. Internet Information Server 7.0 (IIS). .Net Framework 4.0(Minimal for Deployment). SQL Server 2012 Enterprise Edition. Crystal Reports.

2.1.2 HARDWARE P IV 2.8 GHz Processor and Above. RAM 2 GB and Above. 40 GB Hard Disk Space and Above.

2.2 FUNCTIONAL AND NON FUNCTIONAL REQUIREMENTS

2.2.1 FUNCTIONAL REQUIREMENTS

The proposed application is developed to cater services to customer across the globe with similar quality and timeliness. This application is also required to show the range of services which are there with the company to get the customer attention to maximum extent. Apart from getting business from customer, the application should also keep track of order information, payments information etc. Most of the mentioned features are there as part of the current application. Some of the features will be added in the future, and hence they are referred as future enhancements

2.2.2 PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.Requirement specification plays an important part in the analysis of a system. Only when the requirement specifications are properly given, it is possible to design a system, which will fit into required environment. It rests largely in the part of the users of the existing system to give the requirement specifications because they are the people who finally use the system. This is because the requirements have to be known during the initial stages so that the system can be designed according to those requirements. It is very difficult to change the system once it has been designed and on the other hand designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below: The system should be able to interface with the existing system The system should be accurate The system should be better than the existing system

CHAPTER- 3

3.1 LITERATURE SURVEY

The GUIS at the top level have been categorized as Administrative user interface. The operational or generic user interface.

The administrative user interface concentrates on the consistent information that is practically, part of the organizational activities and which needs proper authentication for the data collection. The interfaces help the administrations with all the transactional states like Data insertion, Data deletion and Date updation along with the extensive data search capabilities.

The operational or generic user interface helps the users upon the system in transactions through the existing data and required services. The operational user interface also helps the ordinary users in managing their own information in a customized manner as per the assisted flexibilities.

3.2 ASP.NET

ASP.NET is a programming framework built on the common language runtime that can be used on a server to build powerful Web applications. ASP.NET offers several important advantages over previous Web development models:

Enhanced Performance. ASP.NET is compiled common language runtime code running on the server. Unlike its interpreted predecessors, ASP.NET can take advantage of early binding, just-in-time compilation, native optimization, and caching services right out of the box. This amounts to dramatically better performance before you ever write a line of code.

World-Class Tool Support. The ASP.NET framework is complemented by a rich toolbox and designer in the Visual Studio integrated development environment. Drag-and-Drop server controls, and automatic deployment are few of the features. Power and Flexibility. Because ASP.NET is based on the common language runtime, the power and flexibility of that entire platform is available to Web application developers. The .NET Framework class library, Messaging, and Data Access solutions are all seamlessly accessible from the Web. ASP.NET is also language-independent, so you can choose the language that best applies to your application or partition your application across many languages. Further, common language runtime interoperability guarantees that your existing investment in COM-based development is preserved when migrating to ASP.NET.

Simplicity. ASP.NET makes it easy to perform common tasks, from simple form submission and client authentication to deployment and site configuration. For example, the ASP.NET page framework allows you to build user interfaces that cleanly separate application logic from presentation code and to handle events in a simple, Visual Basic - like forms processing model. Additionally, the common language runtime simplifies development, with managed code services such as automatic reference counting and garbage collection.

Manageability. ASP.NET employs a text-based, hierarchical configuration system, which simplifies applying settings to your server environment and Web applications. Because configuration information is stored as plain text, new settings may be applied without the aid of local administration tools. This "zero local administration" philosophy extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework application is deployed to a server simply by copying the necessary files to the server. No server restart is required, even to deploy or replace running compiled code.

Scalability and Availability. ASP.NET has been designed with scalability in mind, with features specifically tailored to improve performance in clustered and multiprocessor environments. Further, processes are closely monitored and managed by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process can be created in its place, which helps keep your application constantly available to handle requests.

Customizability and Extensibility. ASP.NET delivers a well-factored architecture that allows developers to "plug-in" their code at the appropriate level. In fact, it is possible to extend or replace any subcomponent of the ASP.NET runtime with your own custom-written component. Implementing custom authentication or state services has never been easier. Security. With built in Windows authentication and per-application configuration, you can be assured that your applications are secure.

3.2.1 WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language runtime programming model that can be used on the server to dynamically generate Web pages. Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with existing pages), the ASP.NET Web Forms framework has been specifically designed to address a number of key deficiencies in the previous model. In particular, it provides: The ability to create and use reusable UI controls that can encapsulate common functionality and thus reduce the amount of code that a page developer has to write. The ability for developers to cleanly structure their page logic in an orderly fashion. The ability for development tools to provide strong design support for pages.

ASP.NET Web Forms pages are html files with an .aspx file name extension. They can be deployed throughout an IIS virtual root directory tree. When a browser client requests .aspx resources, the ASP.NET runtime parses and compiles the target file into a .NET Framework class. This class can then be used to dynamically process incoming requests. (Note that the .aspx file is compiled only the first time it is accessed; the compiled type instance is then reused across multiple requests).

3.2.2 CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the method, where the page code is physically declared within the originating .aspx file. An alternative approach--known as the code-behind method--enables the page code to be more cleanly separated from the HTML content into an entirely separate file.

3.2.3 INTRODUCTION TO ASP.NET SERVER CONTROLS

In addition to (or instead of) using code blocks to program dynamic content, ASP.NET page developers can use ASP.NET server controls to program Web pages. Server controls are declared within an .aspx file using custom tags or intrinsic HTML tags that contain a runat="server" attributes value. Intrinsic HTML tags are handled by one of the controls in the System.Web.UI.HtmlControls namespace. Any tag that doesn't explicitly map to one of the controls is assigned the type of System.Web.UI.HtmlControls.HtmlGenericControl. Server controls automatically maintain any client-entered values between round trips to the server. This control state is not stored on the server (it is instead stored within an form field that is round-tripped between requests). Note also that no client-side script is required. In addition to supporting standard HTML input controls, ASP.NET enables developers to utilize richer custom controls on their pages. For example, the following sample demonstrates how the control can be used to dynamically display rotating ads on a page. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI. ASP.NET Web Forms pages can target any browser client (there are no script library or cookie requirements). ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages. ASP.NET server controls provide an easy way to encapsulate common functionality. ASP.NET ships with 45 built-in server controls. Developers can also use controls built by third parties. ASP.NET server controls can automatically project both uplevel and downlevel HTML. ASP.NET templates provide an easy way to customize the look and feel of list server controls. ASP.NET validation controls provide an easy way to do declarative client or server data validation.

3.3 JAVA SCRIPTJavaScript is a script-based programming language that was developed by Netscape Communication Corporation. JavaScript was originally called Live Script and renamed as JavaScript to indicate its relationship with Java. JavaScript supports the development of both client and server components of Web-based applications. On the client side, it can be used to write programs that are executed by a Web browser within the context of a Web page. On the server side, it can be used to write Web server programs that can process information submitted by a Web browser and then update the browsers display accordinglyEven though JavaScript supports both client and server Web programming, we prefer JavaScript at Client side programming since most of the browsers supports it. JavaScript is almost as easy to learn as HTML, and JavaScript statements can be included in HTML documents by enclosing the statements between a pair of scripting tags ... .

JavaScript statements

Here are a few things we can do with JavaScript: Validate the contents of a form and make calculations. Add scrolling or changing messages to the Browsers status line. Animate images or rotate images that change when we move the mouse over them. Detect the browser in use and display different content for different browsers. Detect installed plug-ins and notify the user if a plug-in is required.We can do much more with JavaScript, including creating entire application.JavaScript Vs JavaJavaScript and Java are entirely different languages. A few of the most glaring differences are: Java applets are generally displayed in a box within the web document; JavaScript can affect any part of the Web document itself. While JavaScript is best suited to simple applications and adding interactive features to Web pages; Java can be used for incredibly complex applications.There are many other differences but the important thing to remember is that JavaScript and Java are separate languages. They are both useful for different things; in fact they can be used together to combine their advantages.Advantages: JavaScript can be used for Sever-side and Client-side scripting. It is more flexible than VBScript.JavaScript is the default scripting languages at Client-side since all the browsers supports it.

5.4. IIS 6.0 The IIS 6 process model is the default model on machines running Windows 2003 Server operating system. It introduces several changes and improvements over the IIS 5 process model. One of the biggest changes is the concept of application pools. On IIS 5.X all web applications, that is, all AppDomains, were hosted by the ASP.NET worker process. To achieve a finer granularity over security boundaries and personalization, the IIS 6 process model allows applications to run inside different copies of a new worker process, w3wp.exe. Each application pool can contain multiple AppDomains and is hosted in a single copy of the worker process. In other words, the shift is from a single process hosting all applications to multiple processes hosting each an application pool. This model is also called the worker process isolation mode.Another big change from the previous model is the way IIS listens for incoming requests. With the IIS 5 model, it was the IIS process, inetinfo.exe, who was listening on a specific TCP port for HTTP requests. In the IIS 6 architecture, incoming requests are handled and queued at kernel level instead of user mode via a kernel driver called http.sys; this approach has several advantages over the old model and is called kernel-level request queuing.The IIS 6.0 process model

The above figure illustrates the principal components taking part in the request processing when using the II 6 model. Once a request arrives the kernel level device driver http.sys routes it to the right application pool queue. Each queue belongs to a specific application pool, and thus to a specific copy of the worker process, which next receives the request from the queue. This approach highly reduces the overhead introduced by named pipes used in IIS 5 model since no inter process communication is taking place, but the requests are headed to the worker process directly from the kernel level driver. This has many advantages concerning reliability, too. Since running in kernel mode, the request dispatching isnt influenced by crashes and malfunctions happing at user level, that is, in the worker processes. Thereby, even if a worker process crashes, the system is still capable of accepting incoming requests and eventually restarts the crashed process.Its the worker process who is in charge of loading the ASP.NET ISAPI extension, which, in turn, loads the CRL and delegates all the work to the HTTP Runtime.The w3wp.exe worker process, differently from the aspnet_wp.exe process used in IIS 5 model, isnt ASP.NET specific, and is used to handle any kind of requests. The specific worker process then decides which ISAPI modules to load according to the type of resources it needs to serve.

LIST OF TABLES

Table NoTitlePage No

3.1(Chapter no.Table no)

tblUserLogin

tblRoadBills

tblShippingBill

tblSuppliers

tblPayment

TblOrder

tblInvoiceDetails

tblProducts

tblPersonalDetails

tblCurrency

tblAddressDetails

tbl_Status

tblAdminLogin

tbl_Country

TblBillDetails

receiptdetails

tablelinks

tbl_CityDetails

tbl_State

List of Figures

Figure NoTitlePage No

1.1

2.1

3.1

3.2

3.3

3.4

3.5

3.6

3.7

LIST OF Abbreviations

ACRONYMEXPANSION

DSRDynamic Source Routing

FSRFisheye State Routing Protocol

IDTIndirect Trust

IDTREQIndirect Trust Request

IDTREPIndirect Trust Reply

TTLTime To Live

1.1 OBJECTIVES

1.2 SCOPEThe proposed application needs to cater services to customer across the globe with quality and timeliness. This application is also required to show case the range of services which are there with the company to get the customer attention to maximum extent. Apart from getting business from customer the application should also keep track of ordered information, payments information etc. Using this system we have a comprehensive solution for managing product export information while managing details of products, supplies and invoice information. The features available are: managing master data related to customers, suppliers and products, creation of customer invoices, tracking invoice, administering the customers and suppliers.

Literature Survey

2 .1 EXISTING SYSTEM

Keeping track of goods which we are exporting is done manually now. Because 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. It is less user-friendly and involves lots of manual work. It is unable to generate different kinds of reports.

2.1.1 ISSUES

It is limited to a single system. It is less user-friendly. It is having lots of manual work (include working on spread sheets and other simple software's). The present system is very less secure. It is unable to generate different kinds of report. It doesnt have the mail and file upload feature.

2.2 PROPOSED SYSTEM

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.

User friendliness is provided in the application with various controls. The system makes the overall project management much easier and flexible. It can be accessed over the Internet. Various 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. Report generation feature is provided using Crystal Reports to generate different kinds of reports.It provides high level of security using different protocols like https etc.ModulesThe following modules are identified in the system. Admin, Customer, Supplier, User, Invoice, Reports, and Authentication.

AdminThis module contains all the information about the Admin. He 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. When 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 cant see the product.CustomersThis 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.

SuppliersThis module contains all the information about the Suppliers. He can add all the products which his organization has and he can see the list of the customer who has purchased the product from his organization. When he is adding any product in the organization that product only admin can see but customer and even suppliers cant see the products. When the admin is updating the product then only all customers and suppliers can see the products.UsersThis module contains all the information about the Users. Users are the General person who will only see the product which they want and see all the information about the product.

InvoiceThis 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.

ReportsThis module contains all the information about the reports generated by the admin based on the particular user, particular quotation, all quotations generated by the users.

AuthenticationUsing this module authentication is provided so that only authenticated user can use all the features of the system. Unauthorized users have restricted access.

ORGANIZATION PROFILE

DETAILED ARCHITECTURE DESIGN OF THE PROJECT

3 Tier Architecture

There are three layers in 3 Tier Architecture as given below:-1. Presentation Layer (UI Layer)2. Business Access Layer (BAL)3. Data Access Layer (DAL)

1.) Presentation Layer (UI):-

Presentation Layer is nothing but it is a user interface which every user see on your computer, mobile and window screen. You can say, designing part of any application is known as Presentation Layer. The User can post input and get output on your presentation Layer only. In asp.net .axpx file is known as a presentation layer.

2.) Business AccessLayer (BAL):-

Business Access Layer is act asmediatorLayer between Presentation layer and Data Access layer. This layer is used to transfer the data between Presentation Layer and Data Access Layer. This layer is mainly used for Validations andcalculations purpose. Everyvalidationsandcalculations of data are held on that layer only. I have also implementedProperty layerorEntity Layerconcepts in Business Access Layer. It is optional layer if you are working on a small projects. But if you are working on large projects then you have to include this layer in your 3 Tier Architecture Applications. It is used to enhance the security and prevent tobrokeringthe application.

3.) Data AccessLayer(DAL):-

This Layer only communicate with Business Access Layer. Data Access Layer contains the methods that helps Business Access Layer. Business layer class's methods call the Data Access Layer Class methods to perform some required action with database such as insertion, deletion, updation etc. All database related connection codes are written in this layer only such as sql query, stored procedure etc.

You can easily understand the exact concepts of 3 Tier Applications as show below:-

What are the working process of 3 Layers:-

When any user post data from your presentation layer (user Interface layer) Then this data first goes to Business Access Layer After that validation and calculation are held on this layer After that this data pass data to Data Access Layer After that data Access Layer fetch required data or insert the data in database After that Data Access Layer pass the required data to the business Access Layer After that Business Access Layer send the required data to the Presentation Layer After thatPresentation Layeris responsibletodisplaytherequireddata to the user's computers or mobiles or Windows.

Why does we use 3 Tier Architecture:-

There are following reasons to use 3 Tier Architecture in our asp.net application as given below:-

To increase the security in Application. 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.

Advantages of 3 Tier Architecture:-

Each layer always use your separate codes, so it is easy to modify the codes. It is helpful to easily maintain and understand the large projects. You can easily change your graphical Environment. It is more secure because any users can't access the database directly. You can easily change any layer codes without affecting other two layers. It is a more consistence application.

DATA FLOW DIAGRAMS

A 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 components are 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.

DFD SYMBOLS

In the DFD, there are four symbols,

A square defines a source (originator) or destination of system data. An arrow identifies data flow. It is the pipeline through which the information flows. A circle or a bubble represents a process that transforms incoming data flow into outgoing data flows. An open rectangle is a data store, data at rest or a temporary repository of data.

Process that transforms data flow.

Source or Destination of data.Data flow

Data Store

CONSTRUCTING A DFD

Several rules of thumb are used in drawing DFDS:

Process 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. Data traditionally flow from source to the destination although they may flow back to the source. One way to indicate this is to draw long flow line back to a source. An alternative way is to repeat the source symbol as a destination. Since it is used more than once in the DFD it is marked with a short diagonal. When a process is exploded into lower level details, they are numbered. The names of data stores and destinations are written in capital letters. Process and dataflow names have the first letter of each work capitalized

Context Level Diagram

First Level DFD

Second Level DFD

Third Level DFD

Requirements Specification