Mine ProjectReport

8/7/2019 Mine ProjectReport

1/76

A Project Report on

SpeedEx Courier & Cargo

Submitted in partial fulfillment of the requirement for the degree of

B.Techin

Computer Science & Engg.

By:-

Deependra Singh Sengar

Under the supervision of

Ms. Aprna TripathiAssit. Proff.

Department of Computer Applications

Kanpur Institute of Technology, Kanpur

Gautam Buddha Technical University, Lucknow

November 2010


2/76

2 | P a g e

TABLE OF CONTENTS

S. No. Topics Page Number

01 Declaration 3

02 Certificate 403 Acknowledgement 5

04 Introduction

(i) Abstract(ii) Problem Statement/Purpose of the project(iii) Initial Requirements(iv) System Analysis(v) Understanding of existing system(vi) Tools / Environment used

6

7

8

9-10

11

12

13

05 System Development Life Cycle 14-16

06 Requirement analysis phase

(i) Feasibility study(ii) Problem analysis

17

17-18

19

07 System Design

(i) DFD, ERD, Class Diagram(ii) Table Structure

20

20-24

25-27

08 Coding

(i) Front End(ii) Back End

28

28-36

37-50

09 Testing 51-56

10 Screen Snap Shots

Main Screens Forms & Reports

57

57-7411 Further Enhancement 75

12 References 76


3/76

3 | P a g e

DECLARATION

This is to certify that Report entitled SPEEDEX COURIER & CARGO which

is submitted by me in partial fulfillment of the requirement for the award of degree

B.Tech. In Computer Sc. & Engineering to K.I.T, Kanpur, Gautam Buddha

Technical University, Lucknow comprises only my own work and due

acknowledgement has been made in the text to all other material used.

Date: 1/11/2010 Name of Student: Deependra Singh Sengar

Roll No: 0716510024

E-Mail: [email protected]

Approved By:Ms.Aprna Tripathi

Assist. Prof.

Department of Computer Application

KIT, Kanpur


4/76

4 | P a g e

CERTIFICATE

This is to certify that Report entitled SPEEDEX COURIER & CARGO which

is submitted by Deependra Singh Sengar in partial fulfillment of the requirement

for the award of degree B.Tech in Computer Science & Engg to K.I.T, Kanpur,

G.B.T.U. University, Lucknow is a record of the candidate own work carried out

by him under my/our supervision. The matter embodied in this thesis is original

and has not been submitted for the award of any other degree.

Date: 1/11/2010 Supervisor Name & Signature


5/76

5 | P a g e

ACKNOWLEDGEMENT

This is to certify that I, Deependra Singh Sengar student of B.Tech, C.S.E. of

Kanpur Institute of Technology have completed my industrial report. Industrial

report is an effective and interesting method of analyzing project in detail and

learning new things out of it.

I have made the report and presentation with full concentration and I am very

thankful to my instructor Ms. Aprna Tripathifor the help and encouragement given

to me for the success of the same. I hope that my report is up to the expectations of

the examiner.


6/76

6 | P a g e

INTRODUCTION

This project deals with automation of operations of a courier company. Generally it

includes the Data Processing, Employee Management, Reports Generation and

Accounts Management.

Before automating courier company operations we have to understand the concept

of automation. In automation of any operation we make a system which do work

automatically as the respective events occurs, for which it is meant.

There are the some common examples of the automation like that auto pilot system

in the aircraft, automatic home systems (electric system, water system, fire alarm

system, doors system etc). These are best examples of the automation systems.

Here we are try to develop such type system which is provide the automation on

the any type of the courier company. That means a company which has the type

system which provides the facility to the clients to send their packets in bulk and

provide Addressee information in soft form. Also the main objective of this project

is to integrate multiple branches simultaneously so that processing of records

become faster.

For example any client wants to send number packets he/she can provide an Excel

sheet containing addresses and contact details of addressee, and our system will

process that records and generate receipts and print them. Clients can also getdiscounts on such bulk packets sending.


7/76

7 | P a g e

Abstract

The SpeedEx (The Courier Operation Management System) is an interactive,

effective and time saving operation management system for Courier Industry. The

main objective of this application is to help the courier company to maintain its

information system along multiple branches or Franchise and to integrate multiple

branches simultaneously so that processing of records become faster.

This project deals with developing Web based application for Courier and Cargo

Company. It generates all reports required by the customer. The system is

implemented using a 3-tier approach, with a backend database, a middle tier of

ADO.NET, and User interface in ASP.NET as the front end client.

In order to develop this desktop based application, a number of Technologies mustbe studied and understood. These include multi-tiered architecture, implementation

technologies such as ASP.NET, ADO.NET, programming language (such as C#, &

PLSQL etc.) and relational databases (MS SQL SERVER 2005, MS Access and

Oracle).


8/76

8 | P a g e

PROBLEM DEFINITION/ PURPOSE OF PROJECT

Almost every activity in the world today is controlled by computer driven software programs.

This trend was first accommodated by engineering applications in the past. However, as the life

style became more and more complex, every area of human interactions was invaded by varioussoftware systems, such as real time, business, simulation, embedded, web based, personal and

more recently, artificial intelligence software etc.

According to the above facts, managing and maintaining a courier company could also be

controlled by efficient software. This project focuses attention on designing efficient and reliable

software which controls the transactions of a courier company.

In real world, it tends to associate with automated systems as they provide many benefits than

doing the same thing in manually. As above mentioned, here we have introduced a system which

can be used to maintain a courier company.

When we are concerning the manual process of a courier company, the major problem is the

waste of time. A customer has to waste his/her valuable time when he needs to generate receipt

as all the events such as searching, producing MIS reports .In briefly, and the manual process is

very slow. But automation will reduce the time taken in the whole process.

In a courier company we should deal with a large number of packets to be sent. Then person

(Employee of Courier Company) has to maintain it with documents which are recorded by him.

Therefore, there may be defective reports. Also company has to appointed more persons to

complete the maintenance of the stationery. Then the company has to have an additional cost.

As we familiar with this type of system at instance we will be able to have the results that we

want. Communication with clients and other related organizations will be more successful as the

system is so fast.

When the courier company issues a receipt to a customer, all the stages of the transaction

procedure will be facilitated by the system & it will be more accurate.


9/76

9 | P a g e

INITIAL REQUIREMENTS

The main features of this Software solution namely Courier Management System are enlisted

as below-

The utmost features Packet Entry

The Franchise for Delivery

Updating the delivery status for the packets

Printing of the bills invoice

Client Management

Employee Management

Initial Settings

Queries

Reporting

The utmost feature being the automation of the packet entry at the time of receiving the

packet from the clients so as to ease the primary activity of the company. This includes :

Generating a unique tracking no. (AWB NO.) for each packet received

Specifying the client/customer who has given this packet for delivering (i.e. whether onetime customer/regular client).

Entering the information about the address where the packet is to be delivered.

Calculating the charge of the packet delivery at the time of packet entry. Packet charge is

calculated based on the following criteria :

Packet WeightPacket Delivery Area

Local (Within Lucknow)

Satellite (Noida, Gurgaon, Ghaziabad and Faridabad)

Metro (Mumbai, Kolkata, Banglore, and chennai)

North India

Rest Of India

International

The rates as decided with that client for the above criteria.

Allowing for modifications to the details of the packet so entered for rectifying anytypographical errors.

Assigning the packets to the Franchise for delivery. This part of the objectives includes aassigning the packets to a delivery on the basis of :

The area in which they deliver packets.


10/76

10 | P a g e

The face value of the packets (Packet category).

Updating the delivery status of the packets (e.g. whether packet is delivered, pending or

returned back to the client etc.) after received the proof of delivery (POD) from the deliveryboys. The POD includes the following details about receiving the packet

Details of the person who received with the address [self in case packet is packet is receivedby the addressee], contact information etc).

In case of non-delivery of the packet, the reasons for the same

Date and time of packet delivery (or an attempt for the same).

And delivery conformation SMS on mobile of sender.

Printing of the bills invoice for the clients against the packet received for the delivery. This

includes three parts :

Preparing the bills invoice. Depending on the rates, respective packet weights and theirdestination areas. The bills invoice is prepared for that client for all the packets receivedduring that month.

Printing of the bills invoice to be handed over to that client for payment.

Corrections to the bills invoice this part allows the management to correct the erroneous

one.

One of the important objectives being Client Management.

It has two major parts-

Proposed Client Management- This part allows the managing the details of clients proposed

by managing executives.

Regular Client management- this includes entering, modifying, and managing clients

contact details and respective rates.

Allowing the client and management to query about the delivery status and generatingreports about the packets.

Allowing Client to send details of address for bulk processing.


11/76

11 | P a g e

SYSTEM ANALYSIS

BUSINESS NEEDS

Currently the courier companies are using a CUI based operation management system developedin FOXPRO or they are maintaining records manually. It very difficult to work on manual

system or on a CUI based system i.e. why processing of records are slow and system is not

efficient.

Now the courier company needs user friendly Web/GUI based interface and which provide faster

data processing and proper management reports and information can be generated whenever they

need such reports.

OBJECTIVES

To enhance automation in courier operations providing speed and cost benefits. To increase operational efficiency. To integrate with optical bar code readers. Maintains report of daily processed records and proof of delivery report. Proper accounting. Proper employee and delivery boy information management. Packet tracking facility. Enquiry facility, so that the user can ask directly any querry to the system.


12/76

12 | P a g e

UNDERSTANDING OF EXISTING SYSTEM

EXISTING SYSTEM DESCRIPTION

The existing system has following drawbacks:

1. Ether Courier Company does not have computerized system or they have a CUI based.2. Manual system and CUI based systems are slow and not providing a feel good user interface.3. User needs more training to work with a CUI based system.4. Records handling is again an issues in manual system.5. Errors and mistakes are there in manual systems.

PROPOSED SYSTEM

We (Softpro) proposed complete website solution for the application to create an Courier

Operation Management System website. The iterative, time bound approach adopted by Softpro

to address the client requirements that are as follows:

y Define To- Be processesi. Come up with the solution of the existing problem

ii. Go through the regressive reviews by different business processiii. Prepared user interface requirements

y Develop High Level Design and Low Level Design before Executioni. Built and design all the processes required by Client

ii. Conducted survey of all Courier services Dealing Websites and documented realitiesiii. Developed the architecture of the Software Solutioniv. Developed the project design in detail for the software developer in company


13/76

13 | P a g e

TOOLS/ENVIRONMENT USED

Tools & technology used:

y ASP.NET 3.5 as Application architecture.y Visual Studio 2008 as development IDE.y Microsoft SQL Server 2005 for back end database.y Application will be tested on Windows XP platform.y Microsoft Office.

Languages for Programming:

1. C# for ASP.NET.2. SQL for PLSQL.Software Requirement:

y Microsoft Office.y Operating System Windows Server 2003 and highery Framework - .NET Framework 3.5.y Data Base Server: MS SQL SERVER 2005.y Development End: Visual Studio 2005, MS SQL SERVER 2005, OS (Windows Server2003 and higher).

Hardware Requirement:

Client - Side:Printer Processor RAM Disk Space Optical Reader

Any Dot MatrixPrinter

Pentium 4 512 MB 1 GB Any bar code reader

Server - Side:Web server Database Processor RAM Disk SpaceIIS 6 or Higher SQL SERVER

2005Pentium 4 2GB 120 GB


14/76

14 | P a g e

SYSTEM DEVELOPMENT LIFE CYCLE

To solve actual problems in an industry setting, a software engineer or a team of engineers must

incorporate a development strategy that encompasses the process, methods, and tools layers etc.

The strategy is often referred to as a process model or a Software Engineering Paradigm. A

process model for software engineering is chosen based on the nature of the project and

application, the methods and tools to be used, and the controls and deliverables that are required.

All software development can be characterized as problem solving loop in which four distinct

stages are encountered status quo, problem definition, technical development, and solution

integration. Status quo represents the current state of affairs. Problem definition identifies the

specific problem to be solved. Technical Development solves the problem through the

application of some technology, and Solution Integration delivers the results.

The problem-solving loop applies to software engineering work at many different levels of

resolution. It can be used at the macro level when the entire application is considered, at a mid-

level when program components are being engineered, and even at the line of code level.

There are varieties of process models for software engineering. Each represents an attempt to

bring order to an inherently chaotic activity

SPIRAL MODEL

The spiral model is an evolutionary software process model that couples the iterative nature of

prototyping with the controlled and systematic aspects of the linear sequential model. It provides

the potential for rapid development of incremental versions of software. Using the spiral model,

software is developed in a series of incremental releases.

A spiral model is divided into a number of framework activities, also called task regions.

Typically, there are between three and six task regions.

Customer Communication: - Tasks required establishing effective communication between

developer and customer.


15/76

15 | P a g e

Planning: - Tasks required defining resources, timelines and other project-related information.

Risk Analysis: - Tasks required to assess both technical and management risks.

Engineering: - Tasks required building one or more representations of the application.

Construction and release: - Tasks required to construct, test, install and provide user support.

Customer Evaluation: - Tasks required obtaining customer feedback based on evaluation of the

software representations created during the engineering stage and implemented during the

installation stage.

Each of the regions is populated by a set of work tasks, called a task set, that are adapted to the

characteristics of the project to be undertaken. For small projects, the number of work tasks and

their formality is low. For larger, more critical projects, each task region contains more work

tasks that are defined to achieve a higher level of formality.

PLANNING RISK ANALYSIS

ENGINEERING

CUSTOMER

EVOLUTION

Planning

based on

customerevaluation

Risk Analysis

Based oninitialrequirement

Customer

Evaluation

Initial

software

prototype


16/76

16 | P a g e

As this evolution process begins, the software engineering team moves around the spiral in a

clockwise direction, beginning at the center. The first circuit around the spiral might result in the

development of a product specification; subsequent passes around the spiral might be used to

develop a prototype and then progressively more sophisticated versions of software. Each pass

through the planning region results in adjustments to the project plan. Cost and schedule are

adjusted based on feedback derived from customer evaluation. In addition, the project manager

adjusts the planned number of iterations required to complete the software.

Unlike classical process models that end when software is delivered, the spiral model can be

adapted to apply throughout the life of the computer software.

The spiral model is a realistic approach to the development of large-scale systems and software.

Because software evolves as the process progresses, the developer and customer better

understand and react to risks at each evolutionary level. The spiral model uses prototyping as a

risk education mechanism but, more important, enables the developer to apply the prototyping

approach at any stage in the evolution of the product. It maintains the systematic stepwise

approach suggested by the classical life cycle but incorporates it into an iterative framework that

more realistically reflects the real world. The spiral model demands a direct consideration of

technical risks at all stages of the project and, if properly applied, should reduce risks before they

become problematic.


17/76


18/76

18 | P a g e

Operational feasibility:By automating the Courier Company operation both the customers and employees of Courier

Company will feel better than when it was manual. Users will get a very quick service by

reducing the manual recordings. Also employees will feel comfortable by reduction of their

work. Recording errors will be reduced. Easy to handle a large database. Losing of records will

be avoided.

Considering all these factors we can conclude that all the users and end users will be satisfied by

the system.

Technical feasibility:For the design and development of the system, several software products have been

accommodated.

Database design MS SQL SERVER 2005.

Interface design ASP.NET Framework.

Coding C# or any other supported Language.

This softwares have the enough efficiency in producing the system. Therefore the project is

technically feasible.

Schedule feasibility:

The duration of time required for the project has been planned appropriately and it is the same as

the duration of time expected by the customer. Therefore the product can be delivered to the

customer within the expected time duration, satisfying the customer. Hence the project is feasible

in scheduling.

Economic feasibility:According to the resources available and the project scheduling process it is estimated that theexpenses allocated for the software to be developed, by the customer is sufficient enough. Hencethe economical factor has been considered feasible.


19/76

19 | P a g e

Problem Analysis

Almost every activity in the world today is controlled by computer driven software programs.His trend was first accommodated by engineering applications in the past. However, as the life

style became more and more complex, every area of human interactions was invaded by various

software systems, such as real time, business, simulation, embedded, web based, personal andmore recently, artificial intelligence software etc.

According to the above facts, managing and maintaining a courier company could also becontrolled by efficient software. This project focuses attention on designing efficient and reliable

software which controls the transactions of a courier company.

In real world, it tends to associate with automated systems as they provide many benefits thandoing the same thing in manually. As above mentioned, here we have introduced a system which

can be used to maintain a courier company.

When we are concerning the manual process of a courier company, the major problem is thewaste of time. A customer has to waste his/her valuable time when he needs to generate receipt

as all the events such as searching, producing MIS reports .In briefly, and the manual process isvery slow. But automation will reduce the time taken in the whole process.

In a courier company we should deal with a large number of packets to be sent. Then person

(Employee of Courier Company) has to maintain it with documents which are recorded by him.Therefore, there may be defective reports. Also company has to appointed more persons to

complete the maintenance of the stationery. Then the company has to have an additional cost.

As we familiar with this type of system at instance we will be able to have the results that wewant. Communication with clients and other related organizations will be more successful as the

system is so fast.

When the courier company issues a receipt to a customer, all the stages of the transactionprocedure will be facilitated by the system & it will be more accurate.


20/76

20 | P a g e

System Design

Zero level DFD:

Figure Context Level DFD for Courier Operation Management System


21/76

21 | P a g e

First level DFD:

Figure First Level DFD for Courier Operation Management System


22/76

22 | P a g e

Second level DFD:

Figure Second Level DFD Describing Data Processing Module


23/76

23 | P a g e

Figure Second Level DFD Describing Query Process Module


24/76


25/76

25 | P a g e

Table Structure

Table1: BillDetailsS No Fields Size Null/Not Null Datatype Description

1 Bill_No 10 Primary Key Varchar Holds unique bill no for client2 Client_Id 50 Not Null Varchar Holds the id of client3 AWBNO 10 Not Null Varchar Unique AWBNO for a packet4 Destination Not Null Int Destination Branch code

5 Weight 10 Null Varchar Weight of packets in gram6 Amount 10 Not Null Varchar Total amont of bill7 Bill_DT Not Null Datetime Date of bill generation

Table2: BranchesS No Fields Size Null/Not Null Datatype Description

1 Branch_CD Primary Key Int Holds unique code for a branch2 Branch_NM 50 Not Null Varchar Name of branch3 countryId Not Null Int Country code of branch

4 stateId Not Null Int State code of branch

5 cityId Not Null Int City of branch

6 Address 100 Not Null Varchar Address of branch

Table3: ChargeDetailsS No Fields Size Null/Not Null Datatype Description

1 PlanCode 10 Primary Key Varchar Holds unique plan code

2 Distance 10 Not Null Varchar Distance described in plan3 Weight 10 Not Null Varchar Maximum weight limit of packet4 Amount 10 Not Null Varchar Total amount for packet in this plan

for particular distance

Table4: ClientS No Fields Size Null/Not Null Datatype Description

1 Client_Id 50 Primary Key Varchar Holds unique id for client2 Client_Name 20 Not Null Varchar Name of client3 Client_Address 100 Not Null Varchar Address of client4 Client_contact_N0 15 Allow Null Varchar Contact of client

5 Client_Email_Id 30 Allow Null Varchar EmailId of client

Table5: Login_InfoS No Fields Size Null/Not Null Datatype Description

1 User_Id 50 Not Null Varchar Holds Id for user2 User_Password 20 Not Null Varchar Holds the password of user3 User_Type 1 Not Null Char Hold type of user


26/76

26 | P a g e

Table6: Data_RecordsS No Fields Size Null/Not Null Datatype Description

1 AWBNO 10 Primary Key Varchar Holds unique code for aeach packet

2 Sender_Name 100 Allow Null Varchar Name of sender

3 Sender_Address 100 Allow Null Varchar Address of sender4 Sender_Contact_No 15 Allow Null Varchar Contact number of sender5 Sender_city 30 Allow Null Varchar Name of senders city6 Reciever_Name 100 Not Null Varchar Name of receiver7 Reciever_Address 100 Not Null Varchar Address of receiver8 Reciever_Contact_No 15 Allow Null Varchar Contact No of receiver9 Reciever_city 30 Allow Null Varchar Name of receiverscity

10 Book_date Not Null Datetime Date of booking

11 Weight 10 Allow Null Varchar Weight of packet12 Price 10 Allow Null Varchar Total charge of packet13 POD_Flag 2 Allow Null Char Status of delievery14 Print_Flag 2 Allow Null Char Staus of print form

15 Sender_MobileNo 12 Allow Null Varchar Mobile number of sender16 Pin_Number 10 Allow Null Varchar Pin number of senders city17 State 30 Allow Null Varchar State Name of senders18 Country 30 Allow Null Varchar Country Name of senders19 Sender_Branch_CD Int Int Branch ID of senders

20 Receiver_Branch_CD Int Int Branch ID of Recivers

21 Type 50 Allow Null Varchar Type of sender packets22 Client_Id 50 Allow Null Varchar Client ID23 Alert_Flag 2 Allow Null Char Report of delivery packets

Table7: delivery_Boy_IDS No Fields Size Null/Not Null Datatype Description

1 Current ID 4 Primary Key Varchar Current ID of delivery boy

Table8: delivery_BoyS No Fields Size Null/Not Null Datatype Description

1 Delivery_Boy_Id 10 Primary Key Varchar Holds unique id forDelivery boy

2 Delivery_Boy _Name 20 Not Null Varchar Name of Delivery boy3 Delivery_Boy _Address 100 Not Null Varchar Address of Delivery boy4 Delivery_Boy

_contact_No15 Allow Null Varchar Contact of Delivery boy

5 Delivery_Boy _Area 30 Allow Null Varchar Area of Delivery boy6 Branch_CD Not Null int Branch Id of Delivery boy


27/76

27 | P a g e

Table9: FeedbackS No Fields Size Null/Not Null Datatype Description

1 Feedback_Id Primary Key Int Holds unique id for everyfeedback

2 F name 50 Not Null Varchar First Name of user3 Lname 50 Not Null Varchar Last name of user

4 ContactNo 50 Allow Null Varchar Contact No of user5 FeedbackMsg Max Not Null Varchar Massage of feedback6 Date Allow Null Datetime Date of sending feedback

7 Email 50 Allow Null Varchar Email address of user8 Reply_flag 1 Not Null Char Satatus of reply

Table10: Import_FilesS No Fields Size Null/Not Null Datatype Description

1 File_CD Primary Key Int Holds unique id for every file

2 File_NM 50 Not Null Varchar Name of file3 Import_DT Not Null Datetime Date of imported file

4 User_ID 50 Not Null Varchar Unique id of user5 Branch_CD Not Null Int Branch code where file is

imported

Table11: POD_RecordsS No Fields Size Null/Not Null Datatype Description

1 AWBNO 10 Primary Key Varchar Holds unique awbno ofevery packet

2 Del_Status 20 Not Null Varchar Hold the satus of delievery3 Reciever_Name 20 Not Null Varchar Hold the name of reveiver

4 Rec eiver_Contact_No 15 Allow Null Varchar Hold the contect no ofreceiver

5 RTO_Reason 30 Allow Null Varchar Hold the reason forundelivered packet

6 Relation 50 Allow Null Varchar Hold the relation with theclient

7 Attempt_Date Allow Null Datetime Hold the date of attemptingpackets

Table12: User_InfoS No Fields Size Null/Not Null Datatype Description

1 User_Id 50 Primary Key Varchar Holds unique id for User2 User_Name 20 Not Null Varchar Name of User3 User_Address 100 Not Null Varchar Address of User4 User_contact_N0 15 Allow Null Varchar Contact of User5 User_Email_Id 30 Allow Null Varchar EmailId of User6 Branch_CD Int Code of branch


28/76

28 | P a g e

Coding

(i) Front End:UserControlPanel:

User Control Panel

function ChangeSrc(strsrc){

var frm=document.getElementById("ifrm");

frm.setAttribute("src",strsrc);}

window.history.forward();

Log Out

Home


29/76

29 | P a g e

Contact Us

ServicesLogisticsFragile PackagesLegal OfficesCourt Documents

School/College CampusHospitals/Labs

Enquiries

Delivery StatusPacket Tracking

Rate DetailsBranch DetailsBranch AreasBill Inquiries

Feedback

Jobs

Career Options

Openings

Sitemap


31/76

31 | P a g e

UserProfile:

Client Profile

Profile


32/76

32 | P a g e


33/76

33 | P a g e

DeliveryBoy:

Delivery Boy

Delivery Boy Details

Name

Contact No

Address

Branch

Area


34/76

34 | P a g e

Select Branch

Search Delivery Boy

Search By

By NameBy Branch

By Area


35/76

35 | P a g e

Select Branch


36/76

36 | P a g e


37/76

37 | P a g e

(ii) Back End:LoginManager:

using System;using System.Data;

using System.Data.SqlClient;using System.Configuration;

using System.Web;using System.Web.Security;

using System.Web.UI;using System.Web.UI.HtmlControls;

using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;

///

/// Summary description for LoginManager///

public class LoginManager{

public LoginManager(){

//

// TODO: Add constructor logic here//

objConnection = new ConnectionManager();}

//Fields

private ConnectionManager objConnection;private string ExceptionInfo;

//Properties

public string GetException

{get{

return this.ExceptionInfo;}

}

//Methodspublic bool AddLoginInfo(string userid, string password, char usertype){

string Query="insert into Login_Info(User_Id,User_Password,User_Type) values(@uid,@pwd,@utype)";SqlParameter[] parameters = { new SqlParameter("@uid", userid), new SqlParameter("@pwd", password), new

SqlParameter("utype", usertype) };try

{return objConnection.NonQuery(Query, parameters);

}catch (Exception ex){

this.ExceptionInfo = ex.Message;return false;

}

}


38/76

38 | P a g e

public bool ValidateUser(string userid, string password){

string Query = "select * from Login_Info where User_Id=@uid and User_Password=@pwd";try{

SqlParameter[] paramaters = { new SqlParameter("@uid", userid), new SqlParameter("@pwd", password) };DataSet ds = objConnection.GetDataSet(Query, "Login", paramaters);

if (ds.Tables["Login"].Rows.Count == 1)return true;

else return false;}catch (Exception ex){


}}

public bool ChangePassword(string userid, string oldpassword, string newpassword)

{string Query = "update Login_Info set User_Password=@newpassword where User_Id=@userid and

User_Password=@oldpassword";SqlParameter[] parameters = { new SqlParameter("@userid", userid), new SqlParameter("@newpassword",

newpassword), new SqlParameter("@oldpassword", oldpassword) };try


}catch (Exception ex)

{this.ExceptionInfo = ex.Message;return false;

}}

public bool ResetPassword(string userid){

string defaultpwd = "welcome";

string Query = "update Login_Info set User_Password=@defaultpwd where User_Id=@userid";SqlParameter[] parameters = { new SqlParameter("@userid", userid), new SqlParameter("defaultpwd", defaultpwd)

};try




}}public char GetUserType(string userid){

string Query = "select User_Type from Login_Info where User_Id=@userid";try{

SqlParameter[] parameters ={ new SqlParameter("@userid", userid) };DataSet ds = objConnection.GetDataSet(Query, "UserType", parameters);char user_type =Convert.ToChar( ds.Tables["UserType"].Rows[0][0].ToString());


39/76

39 | P a g e

return user_type;}catch (Exception ex){

this.ExceptionInfo = ex.Message;return 'F';

}

}

public bool CheckAvailability(string userid){

string Query = "select * from Login_Info where User_Id=@userid";try{

SqlParameter[] parameters = { new SqlParameter("@userid", userid) };DataSet ds = objConnection.GetDataSet(Query, "Availability", parameters);if (ds.Tables["Availability"].Rows.Count == 0)

return true;else return false;


{this.ExceptionInfo = ex.Message;

return false;}

}

public bool RemoveLogin(string userid){

string Query = "delete from Client where userid=@userid";try{

SqlParameter[] parameters = { new SqlParameter("@userid", userid) };return objConnection.NonQuery(Query, parameters);

}

catch{

this.ExceptionInfo = objConnection.GetException;

return false;}

}public bool RemoveUserLogin(string User_Id)

{string Query = "delete from Login_Info where User_Id=@User_Id";

try{

SqlParameter[] parameters = { new SqlParameter("@User_Id", User_Id) };return objConnection.NonQuery(Query, parameters);

}

catch (Exception ex){


}}

}


40/76

40 | P a g e

ConnectionManager:

using System;using System.Data;using System.Data.SqlClient;using System.Configuration;using System.Web;

using System.Web.Security;using System.Web.UI;using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;

/// /// Summary description for ConnectionManager/// public class ConnectionManager{

public ConnectionManager(){

connectionDB.ConnectionString = ConfigurationManager.ConnectionStrings["ConnectionStr"].ToString();

command.Connection = connectionDB;dataadapter.SelectCommand = command;

}

//Fieldsprivate SqlConnection connectionDB=new SqlConnection();private SqlCommand command=new SqlCommand();private SqlDataAdapter dataadapter=new SqlDataAdapter();private DataSet data_set=new DataSet();private string ConnectionStr;private string ExceptionInfo;SqlTransaction objTransaction;

//Propertiespublic string ConnectionString{

set{

this.ConnectionStr = value;}

}

public string GetException{

get{

return this.ExceptionInfo;

}}

//Methods

public DataSet GetDataSet(string Query, string AliasName, SqlParameter[] Param_Array){

try{

command.CommandText = Query;if (Param_Array != null)


41/76

41 | P a g e

command.Parameters.AddRange(Param_Array);dataadapter.Fill(data_set, AliasName);return data_set;


this.ExceptionInfo = ex.Message;return null;

}finally{

if (connectionDB.State == ConnectionState.Open)connectionDB.Close();

}}

public bool NonQuery(string Query,SqlParameter[] Param_Array){


command.Parameters.AddRange(Param_Array);try

{if (connectionDB.State == ConnectionState.Closed)

connectionDB.Open();objTransaction = connectionDB.BeginTransaction();

command.Transaction = objTransaction;int result = command.ExecuteNonQuery();

if (result >= 1){

objTransaction.Commit();return true;

}else{

objTransaction.Rollback();

return false;}

}


objTransaction.Rollback();this.ExceptionInfo = ex.Message;

return false;}

finally{

if(connectionDB.State==ConnectionState.Open)connectionDB.Close();

}

}

public object GetScalar(string Query,SqlParameter[] Param_Array){


command.Parameters.AddRange(Param_Array);try{

if (connectionDB.State == ConnectionState.Closed)


42/76

42 | P a g e

connectionDB.Open();objTransaction = connectionDB.BeginTransaction();command.Transaction = objTransaction;object obj = command.ExecuteScalar();objTransaction.Commit();return obj;


{objTransaction.Rollback();this.ExceptionInfo = ex.Message;return null;

}finally{

if (connectionDB.State == ConnectionState.Open)connectionDB.Close();

}}

}


43/76

43 | P a g e

UserManager:

using System;

using System.Data;using System.Data.SqlClient;

using System.Configuration;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;

/// /// Summary description for UserManager///

public class UserManager{

public UserManager(){

//// TODO: Add constructor logic here//

objConnection = new ConnectionManager();

}//Fields


//Propertiespublic string GetException{

get{

return this.ExceptionInfo;

}}

//Methods

public bool CreateUserProfile(string User_Id, string User_Name, string User_Address, string User_Contact_No, string

User_Email_Id, int Branch_CD){

string Query = "insert intoUser_Info(User_Id,User_Name,User_Address,User_Contact_No,User_Email_Id,Branch_CD)values(@User_Id,@User_Name,@User_Address,@User_Contact_No,@User_Email_Id,@Branch_CD)";

try{

SqlParameter[] parameters = { new SqlParameter("@User_Id", User_Id), new SqlParameter("@User_Name",User_Name), new SqlParameter("@User_Address", User_Address), new SqlParameter("@User_Contact_No",User_Contact_No), new SqlParameter("@User_Email_Id", User_Email_Id), new SqlParameter("@Branch_CD",Branch_CD) };

return objConnection.NonQuery(Query, parameters);}catch{

this.ExceptionInfo = objConnection.GetException;return false;

}


44/76

44 | P a g e

}

public int GetUserBranch(string User_Id){

string Query = "select Branch_CD from User_Info where User_Id=@User_Id";try{

SqlParameter[] parameter = { new SqlParameter("@User_Id", User_Id) };

return (int)objConnection.GetScalar(Query, parameter);}catch (Exception ex){

this.ExceptionInfo = ex.Message;return -1;

}}public DataSet GetUserProfile(string userid){

try{

string Query = "SELECT dbo.Branches.Branch_NM, dbo.User_Info.User_Id, dbo.User_Info.User_Name,dbo.User_Info.User_Address, dbo.User_Info.User_Contact_No, dbo.User_Info.User_Email_Id,

dbo.User_Info.Branch_CD FROM dbo.Branches INNER JOIN dbo.User_Info ON dbo.Branches.Branch_CD =dbo.User_Info.Branch_CD WHERE User_Id=@userid";

SqlParameter[] parameters = { new SqlParameter("@userid", userid) };return objConnection.GetDataSet(Query, "UserProfile", parameters);



return null;}

}public DataSet GetAllUserProfile(){

string Query = "Select * from User_Info";

try{

return objConnection.GetDataSet(Query, "AllUser", null);



return null;}

}public DataSet GetAllUserProfile(int Branch_CD){

string Query = "Select * from User_Info where Branch_CD=@Branch_CD";try

{SqlParameter[] parameter = { new SqlParameter("@Branch_CD", Branch_CD) };return objConnection.GetDataSet(Query, "AllUser", parameter);



}}


45/76

45 | P a g e

public bool DeleteUserProfile(string User_Id){

string Query = "delete from User_Info where User_Id=@User_Id";try{

SqlParameter[] parameter = { new SqlParameter("@User_Id", User_Id) };return objConnection.NonQuery(Query, parameter);



}}

public bool UpdateUserProfile(string User_Id, string User_Name, string User_Address, string User_Contact_No, stringUser_Email_Id, int Branch_CD,string old_User_Id)

{

string Query = "update User_Info set User_Id=@User_Id, User_Name=@User_Name,User_Address=@User_Address, User_Contact_No=@User_Contact_No,User_Email_Id=@User_Email_Id,

Branch_CD=@Branch_CD where User_Id=@old_User_Id";try

{SqlParameter[] parameters = { new SqlParameter("@User_Id", User_Id), new SqlParameter("@User_Name",

User_Name), new SqlParameter("@User_Address", User_Address), new SqlParameter("@User_Contact_No",User_Contact_No), new SqlParameter("@User_Email_Id", User_Email_Id), new SqlParameter("@Branch_CD",

Branch_CD), new SqlParameter("@old_User_Id", old_User_Id) };return objConnection.NonQuery(Query, parameters);

}catch{


}

}

public bool UpdateUserProfile(string User_Id, string User_Name, string User_Address, string User_Contact_No, string

User_Email_Id){

string Query = "update User_Info set User_Name=@User_Name, User_Address=@User_Address,User_Contact_No=@User_Contact_No,User_Email_Id=@User_Email_Id where User_Id=@User_Id";

try{

SqlParameter[] parameters = { new SqlParameter("@User_Id", User_Id), new SqlParameter("@User_Name",User_Name), new SqlParameter("@User_Address", User_Address), new SqlParameter("@User_Contact_No",User_Contact_No), new SqlParameter("@User_Email_Id", User_Email_Id) };

return objConnection.NonQuery(Query, parameters);}

catch{


}}

}


46/76

46 | P a g e

AdministratorManager:

using System;

using System.IO;using System.Data;

using System.Data.SqlClient;using System.Configuration;using System.Web;using System.Web.Security;using System.Web.UI;using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;

/// /// Summary description for Administrator

/// public class Administrator

{public Administrator()

{//// TODO: Add constructor logic here//


//Fields



get

{return this.ExceptionInfo;

}}

//Methods

public DataSet GetUserRights(char User_Type){

string Query = "SELECT dbo.Rights_Set.User_Type, dbo.Rights_Set.Right_Id, dbo.Rights.Caption,dbo.Rights.Right_URL FROM dbo.Rights_Set INNER JOIN dbo.Rights ON dbo.Rights_Set.Right_Id =dbo.Rights.Right_Id WHERE (dbo.Rights_Set.User_Type =@utype)";

try{

SqlParameter[] parameters = { new SqlParameter("@utype", User_Type) };return objConnection.GetDataSet(Query, "UserRights", parameters);



}}


47/76

47 | P a g e

public DataSet GetPermission(){

string Query = "select Right_id,Caption from Rights";try{

return objConnection.GetDataSet(Query, "Permissions", null);}catch (Exception ex)

{this.ExceptionInfo = ex.Message;return null;

}}

public DataSet GetPermission(char User_Type){

string Query = "SELECT dbo.Rights_Set.User_Type, dbo.Rights_Set.Right_Id, dbo.Rights.Caption FROMdbo.Rights_Set INNER JOIN dbo.Rights ON dbo.Rights_Set.Right_Id = dbo.Rights.Right_Id WHERE(dbo.Rights_Set.User_Type = @utype)";

try

{SqlParameter[] parameters = { new SqlParameter("@utype", User_Type) };

return objConnection.GetDataSet(Query, "UserPermissions", parameters);}



}}

public bool GrantPermission(string Right_Id, char User_Type){

string Query = "insert into Rights_Set(User_Type,Right_Id) values(@User_Type,@Right_Id)";try

{

SqlParameter[] parameters = { new SqlParameter("@User_Type", User_Type), new SqlParameter("@Right_Id",Right_Id) };

return objConnection.NonQuery(Query, parameters);

}catch

{this.ExceptionInfo = objConnection.GetException;

return false;}

}

public bool RemovePermission(string Right_Id, char User_Type){

string Query = "delete from Rights_Set where User_Type=@User_Type and Right_Id=@Right_Id";try{

SqlParameter[] parameters = { new SqlParameter("@User_Type", User_Type), new SqlParameter("@Right_Id",Right_Id) };

return objConnection.NonQuery(Query, parameters);}catch{

this.ExceptionInfo = objConnection.GetException;


48/76


49/76

49 | P a g e

PacketTracking:

using System;using System.Data;using System.Data.SqlClient;using System.Configuration;using System.Linq;using System.Web;

using System.Web.Security;using System.Web.UI;using System.Web.UI.HtmlControls;using System.Web.UI.WebControls;using System.Web.UI.WebControls.WebParts;using System.Xml.Linq;

/// /// Summary description for PacketTracking/// public class PacketTracking{

public PacketTracking(){

//// TODO: Add constructor logic here//


//Fieldsprivate ConnectionManager objConnection;private string ExceptionInfo;


get{

return this.ExceptionInfo;}

}

//Methods

public bool AssignPacket(string AWBNO, string Delivery_Boy_Id, DateTime Assign_DT){

try{

string Query = "insert into PacketAssignmentDetails(AWBNO,Delivery_Boy_Id,Assign_DT)values(@AWBNO,@Delivery_Boy_Id,@Assign_DT)";

SqlParameter[] parameters = { new SqlParameter("@AWBNO", AWBNO), newSqlParameter("@Delivery_Boy_Id", Delivery_Boy_Id), new SqlParameter("Assign_DT", Assign_DT) };

return objConnection.NonQuery(Query, parameters);


this.ExceptionInfo = ex.Message;

return false;}

}

public DataSet GetPacket(string AWBNO){


50/76

50 | P a g e

try{

string Query = "SELECT dbo.Delivery_Boy.Delivery_Boy_Id, dbo.Delivery_Boy.Delivery_Boy_Name,dbo.Delivery_Boy.Delivery_Boy_Address, dbo.Delivery_Boy.Delivery_Boy_Contact_No,dbo.PacketAssignmentDetails.AWBNO, dbo.PacketAssignmentDetails.Assign_DT FROM dbo.Delivery_Boy INNERJOIN dbo.PacketAssignmentDetails ON dbo.Delivery_Boy.Delivery_Boy_Id =dbo.PacketAssignmentDetails.Delivery_Boy_Id where AWBNO=@AWBNO";

SqlParameter[] parameter = { new SqlParameter("@AWBNO", AWBNO) };

return objConnection.GetDataSet(Query, "PacketDetails", parameter);}catch (Exception ex){


}}public DataSet GetShipment(string AWBNO){

try{

string Query = "SELECT dbo.Data_Records.AWBNO, dbo.POD_Records.Del_Status,dbo.POD_Records.Receiver_name, dbo.POD_Records.Receiver_Contact_No, dbo.POD_Records.RTO_Reason,

dbo.POD_Records.Relation, dbo.POD_Records.Attempt_Date, dbo.Data_Records.Book_date, dbo.Data_Records.Weight,dbo.Data_Records.Type FROM dbo.Data_Records INNER JOIN dbo.POD_Records ON dbo.Data_Records.AWBNO =

dbo.POD_Records.AWBNO where dbo.Data_Records.AWBNO=@AWBNO";SqlParameter[] parameter = { new SqlParameter("@AWBNO", AWBNO) };

return objConnection.GetDataSet(Query, "Shipment", parameter);}



}}

}


51/76

51 | P a g e

Testing

This module is tested by the following testing methods

yUnit Testing

y Integration Testing1 Unit Testing:

Unit testing is a procedure used to validate that individual units of source code are working

properly. A unit is the smallest testable part of an application. In procedural programming a unit

may be an individual program, function, procedure, etc., while in object-oriented programming,

the smallest unit is a method, which may belong to a base/super class, abstract class or

derived/child class.

Ideally, each test case is independent from the others; mock or fake objects as well as test

harnesses can be used to assist testing a module in isolation. Unit testing is typically done by

software developers to ensure that the code they have written meets software requirements and

behaves as the developer intended.

Unit testing provides a sort of living documentation of the system. Developers looking to learn

what functionality is provided by a unit and how to use it can look at the unit tests to gain a basic

understanding of the unit API.

Unit test cases embody characteristics that are critical to the success of the unit. These

characteristics can indicate appropriate/inappropriate use of a unit as well as negative behaviors

that are to be trapped by the unit. A unit test case, in and of itself, documents these critical

characteristics, although many software development environments do not rely solely upon codeto document the product in development.

On the other hand, ordinary narrative documentation is more susceptible to drifting from the

implementation of the program and will thus become outdated (e.g. design changes, feature

creep, relaxed practices to keep documents up to date).


52/76

52 | P a g e

2 Integration Testing:

It is sometimes called I&T i.e. Integration and testing, it is the phase of software testing in which

individual software modules are combined and tested as a group. It follows unit testing and

precedes system testing.

Integration testing takes as its input modules that have been unit tested, groups them in larger

aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its

output the integrated system ready for system testing.

The purpose of integration testing is to verify functional, performance and reliability

requirements placed on major design items. These "design items", i.e. assemblages (or groups of

units), are exercised through their interfaces using black box testing, success and error cases

being simulated via appropriate parameter and data inputs. Simulated usage of shared data areas

and inter-process communication is tested and individual subsystems are exercised through their

input interface. Test cases are constructed to test that all components within assemblages interact

correctly, for example across procedure calls or process activations, and this is done after testing

individual modules, i.e. unit testing


53/76

53 | P a g e

Test Cases & Bug Report

Test Id: 1001

Purpose: Testing of unit LoginManager responsible for Login of Administrator, Operator and

Client.

Identifier Function/Procedure Parameter Values Expected

Result

Actual

Result

Remark

C001 ValidateUser Userid=adminPasswd=123

True True Correct

C002 ValidateUser Userid=ADMIN

Passwd=123

True True Correct

C003 ValidateUser Userid=AdminPasswd=123

True True Correct

C004

AddLoginInfo Userid=Operator

Passwd=456 UserType=O

True True Correct

C005 AddLoginInfo Userid="Client"Passwd="789"

UserType=C

True True Correct

C006 ValidateUser Userid="jon"

Passwd=""

False False Correct

C007 ValidateUser Userid="Jon"

Passwd="JON"

False False Correct

C008 ValidateUser Userid=""Passwd="" False False Correct

C009 ValidateUser Userid=" jon"Passwd="jon"

True True Correct

C010 ChangePassward Userid=adminoldPasswd=123

newpassward=111

True True Correct

C011 ChangePassward Userid=admin

oldPasswd= newpassward=111

False False Correct

C012 ChangePassward Userid=admin

oldPasswd=123newpassward=

False False Correct

C013 ChangePassward Userid= oldPasswd=123

newpassward=111

False False Correct

C014 ChangePassward Userid=Genral

oldPasswd=123newpassward=111

False False Correct


54/76

54 | P a g e

Test Id: 1002Purpose: Testing of unit POD responsible for adding the delivery report of packets


Result

Actual

Result

Remark

C001 AddPOD AWBNO=1

Del_Status=deliverdReceiver_name=vivek

Receiver_Contact_No=9969571602

RTO_Reason=Relation=client

Attempt_Date=12/3/2010

True True correct

C002 AddPOD

AWBNO=hah


Receiver_Contact_No=9969571602

RTO_Reason=Relation=client

Attempt_Date=

False False correct

C003 AddPOD AWBNO=3


Receiver_Contact_No=

RTO_Reason=Relation=

Attempt_Date=12/3/2010

True True correct

C004 GetData Void POD_Record POD_Record Correct

C005 UpdatePODFlag AWBNO=2 True True Correct

C006 UpdatePODFlag AWBNO=gjhg False False Correct


55/76

55 | P a g e

Test Id: 1003Purpose: Testing of unit Client responsible for managing all types of operations related toclient.


Result

Actual

Result

Remar

C001 AddNewClient Client_Id=client01Client_Name=ram singh

Client_Address=13, gokulpur

Client_Contact_No=9935648876

Client_Email_Id=jgfjy@hg

True True Correc

C002 AddNewClient Client_Id=hgklf

Client_Name=ram singhClient_Address=13, Gokul

purClient_Contact_No=993564

8876Client_Email_Id=jgfjy@hg

False False Correc

C003 UpdateClient Client_Id=Client01Client_Name=ram singh

Client_Address=13, Gokulpur

Client_Contact_No=9935648876

Client_Email_Id=jgfjy@hg

True True Correc

C004 UpdateClient Client_Id=hgklfClient_Name=ram singhClient_Address=13, Gokul



False False Correc

C005 UpdateClient Client_Id=hgklf

Client_Name=Client_Address=13, Gokul



False False Correc

C006 DeleteClient Client_Id=Client01 True True Correc


56/76

56 | P a g e

Test Id: 1004Purpose: Testing of unit DeliveryBoy responsible for performing all types of functionalityrelated to delivery boy


Result

Actual

Result

Remark

C001 GetId Void New

Delivery_boy_id

New

Delivery_boy _id

Correct

C002 AddDeliveryBoy Delivery_Boy_Id=12Delivery_Boy_Name=

ramDelivery_Boy_Address

=12 indra nagar lkoDelivery_Boy_Contact

_No=99897645Branch_CD=9

Delivery_Boy_Area=aligang

True True Correct

C003 DeleteDeliveryBoy Delivery_Boy_Id=12 True True Correct

C004 DeleteDeliveryBoy Delivery_Boy_Id=s False False Correct

C005 UpdateDeliveryBoy Delivery_Boy_Id=12Delivery_Boy_Name=

ramDelivery_Boy_Address

=12 indra nagar lkoDelivery_Boy_Contact



True True Correct

C006 UpdateDeliveryBoy Delivery_Boy_Id=fDelivery_Boy_Name=

ram

Delivery_Boy_Address=12 indra nagar lkoDelivery_Boy_Contact



False False Correct


57/76

57 | P a g e

Screen Snap Shots

Home page:-


58/76

58 | P a g e

About us Page:-


59/76

59 | P a g e

Job pages:-

Job opening:


60/76

60 | P a g e

Post your resume:


61/76

61 | P a g e

Feedback page:-


62/76

62 | P a g e

Create user/client:-


63/76

63 | P a g e

Bulk data entry:-


64/76

64 | P a g e

Singe data entry:-


65/76

65 | P a g e

View Client Report:-


66/76

66 | P a g e

Delievery Message:-


67/76

67 | P a g e

User Feedback:-


68/76

68 | P a g e

Delivery Boy Management:-


69/76

69 | P a g e

Grant Permission to Client/User:-


70/76

70 | P a g e

Profile:-


71/76

71 | P a g e

Client Payment Details:-


72/76

72 | P a g e

Client Profile:-


73/76

73 | P a g e

Login Fail Page:-


74/76

74 | P a g e

Windows pages:-

Server Ip address page:

Login To Speedex:


75/76

75 | P a g e

Implementation of Security Mechanism:The security will be achieved in system in following way:

1. User level authentication through User Id and Password for each User.2. Administrator level authentication through administrative Id and Password.3. Hashed password is stored in database using MD5 algorithm so that evendatabase

4. Administration is not able to get password.

Future Scope:Following modification or upgrades can be done in system.

1. More than one company can be integrated through this software.2. Web services can be used to know exact delivery status of packets.3. Client can check there packets delivery status online.


76/76

References:

[1] ASP.NET and Web Development Overview,

http://msdn.microsoft.com/en-us/library/4w3ex9c2.aspx

[2] Microsoft Visual Studio Overview,http://en.wikipedia.org/wiki/Microsoft_Visual_Studio#Visual_Studio_2005

[3] Microsoft SQL Server 2005,

http://en.wikipedia.org/wiki/Microsoft_SQL_Server

[4] 3-Tier System Architecture,http://en.wikipedia.org/wiki/Multitier_architecture

[5] Introduction to ADO.NET,

http://en.wikipedia.org/wiki/ADO.NET

[6] Load Testing using Apache JMeter Testing Tool,http://jakarta.apache.org/jmeter/

[7] Introduction to .NET Architecture,

http://www.devtopics.com/what-is-net/

[8] Common Language Infrastructure Definition,http://en.wikipedia.org/wiki/Common_Language_Infrastructure

[9] AJAX Bridging the Thin-Client Performance Gap,

http://www.ironspeed.com/articles/ajax-bridging%20the%20thinclient%20performance%20gap/article.aspx

[10] 3-Tier Architecture

http://www.c-sharpcorner.com/

[11] SAMS Asp.Net Unleashed 3.5