Mini Project Final Report Unnati 2011

8/6/2019 Mini Project Final Report Unnati 2011

http://slidepdf.com/reader/full/mini-project-final-report-unnati-2011 1/74

TABLE OF CONTENTS

1. INTRODUCTION

1.1 Introduction

1.2 Objective

2. REQUIREMENT AND ANALYSIS

2.1 Feasibility Study

2.2 Hardware and Software Requirements

2.3 Requirements Gathering

2.4 Analysis

2.5 Software Requirement Specification

2.6 Project Planning and Scheduling

3. SYSTEM DESIGN

3.1 Software Design

3.2 Data Dictionary

3.3 Data Flow Diagram

3.4 ER Diagram

3.5 State Machine Diagram

3.6 Database Design

3.7 Class Diagram

3.8 Security

4. CODING



4.1 Introduction to Windows 2003 Server

4.2 Introduction to ASP.NET

4.3 Introduction to SQL Server 2000

4.4 Coding

5. PERT CHART AND GANTT CHART

5.1 Pert Chart

5.2 Gantt Chart

6. IMPLEMENTATION AND TESTING

6.1 Implementation

6.2 Testing

6.3 Screen Shots

6.4 Future Scope of the Project

7. BIBLIOGRAPHY



INTRODUCTION



1.1 INTRODUCTION

E-SHOP is a web-based application intended to provide automated solution and

services to customer. Consider a Business organization which have all of its business through

INTERNET i.e., WEBSITES. The Business Organization has its offices in few states and

normally use courier facility to deliver the product .If possible home delivery is also possible.

This Business Organization mainly has two sectors first one is sale which sale the

product to the customer and second is service which is provided to the customer.

E-SHOP provides sales and service to customer by interaction with customer. The success of

a company is mainly based on its satisfied customers, which in turn gives huge profits.

Retaining existing customers is also an important job of a company. E-SHOP

concentrates on the retention of customers by collecting all data from every interaction, every

customer makes with a company from 'all' access points whether they are phone, mail, web or

field. The company can them use this data for specific business purposes viz., marketing,

service, support or sales

E-SHOP is basically the collection and distribution of "all" data to "all" areas

of business. The data can then help market the company, help up sell to existing customer,

understand customers better so that customers can be given better service and allows them to

interact with the company by whatever means they wish.

BUSINESS ORGANISATION

SALES SERVICE



WEBSITE

BUSINESS HOUSE RECEIVES PRODUCTS

INTERNET EXPLORER

Click

CUSTOMER



1.2 OBJECTIVE

Shopping has long been considered a recreational activity by many. Shopping online is no

exception. The goal of this application is to develop a web based interface for online retailers.

The system would be easy to use and hence make the shopping experience pleasant for the

users. The goal of this application is :

1. To develop an easy to use web based interface where users can search for products,

view a complete description of the products and order the products.

2. A search engine that provides an easy and convenient way to search for products

specific to their needs. The search engine would list a set of products based on the

search term and the user can further filter the list based on various parameters.

3. An AJAX enabled website with the latest AJAX controls giving attractive and

interactive look to the web pages and prevents the annoying post backs.

4. Drag and Drop feature which would allow the users to add a product to or remove a

product from the shopping cart by dragging the product in to the shopping cart or out

of the shopping cart.

5. A user can view the complete specification of the product along with various images

and also view the customer reviews of the product. They can also write their own

reviews.



2. REQUIREMENT AND ANALYSIS

System Analysis is a management technique, which helps in designing a new system

or improving an existing system. System Analysis is the process of gathering and interpreting

facts, diagnosing problems (if any), using information to recommend improvements to the

system. There are four basic elements of system analysis: - Output, Input, Files, processes.

For computerization of any system, the existing system must be thoroughly being understood

to determine ³how the computer can be best used to make its operation most effective´. This

is acquired by analyzing existing system.

2.1 FEASIBILITY STUDY

2.1.1 System Feasibility

The system feasibility can be divided into the following sections:

Economic Feasibility

Economical feasibility determines whether there are sufficient benefits in creating

to make the cost acceptable, or is the cost of the system too high. As this signifies cost-

benefit analysis and savings. On the behalf of the cost-benefit analysis, the proposed system

is feasible and is economical regarding its pre-assumed cost for making a system.

We classified the costs of E-SHOP according to the phase in which they occur.

As we know that the system development costs are usually one-time costs that will not recur after the project has been completed. For calculating the Development costs we evaluated

certain cost categories viz.

1. Personal costs

2. Computer usage

3. Supply and equipments costs

4. Cost of any new computer equipments and software.

Technical Feasibility

Technical feasibility determines whether the work for the project can be done with the

existing equipment, software technology and available personnel. Technical feasibility is

concerned with specifying equipment and software that will satisfy the user requirement.



This project is feasible on technical remarks also, as the proposed system is more

beneficiary in terms of having a sound proof system with new technical components installed

on the system. The proposed system can run on any machines supporting Windows and

Internet services and works on the best software and hardware that had been used while

designing the system so it would be feasible in all technical terms of feasibility.

To deploy the application, the only technical aspects needed are mentioned below:

Operating Environment Win 2000/XP

Platform .Net Framework & IIS

Database SQL Server 2000

For Users:

Internet Browser

Internet Connection

2.1.2 Operational Feasibility

Operational feasibility is all about problems that may arise during the operations. There are

other issues related with operational feasibility.

Information

The system needs to provide adequate, timely, accurate and useful information

Response Time

It needs to study the response time of the system in terms of throughput

Accuracy

Accuracy is the degree to which the software performs its required functions and gives

desired output correctly

Security

There should be adequate security to information and data. It should be able to protect itself

from threats.

Services

The system needs to be able to provide desirable an d reliable services to its users.

Efficiency

The system needs to be able to use maximum of the available resources in an efficient

manner so that there are no delays in execution of jobs.



2.1.3 Behavioral Feasibility

The application requires no special technical guidance and all the views available in

the application are self explanatory. The users are well guided with warning and failure

messages for all the actions taken.



2.2 HARDWARE AND SOFTWARE REQUIREMENTS

Networking (Web Designing) contains server side, client side and database approachis used for the desired application.

TOOLS:

WEB SERVER : INTERNET INFORMATION SERVER (IIS)

PLATFORM:

SERVER SIDE : WINDOWS 2003 SERVER

CLIENT SIDE : WINNDOWS XP / WINDOWS 2000 Professional

2.2.1 HARDWARE REQUIREMENTS:

SERVER SIDE:

PROCESSOR : DUAL CORE PROCESSOR

RAM : 1 GB

CLIENT SIDE:

PROCESSOR : INTEL PENTIUM ±IV

RAM : 128 MB

2.2.2 SOFTWARE REQUIREMENTS:

SERVER SIDE:

PLATFORM : ASP.NET WITH LANGUAGE C#

DATABASE : SQL SERVER 2000

CLIENT SIDE:

TOOLS: INTERNET EXPLORER 6.0, FLASH 2.0



2.3 REQUIREMENT GATHERING

As the goal of the application is ease of use and to provide an interactive interface,

extensive research has been done to gain an insight into the needs and behaviors of various

users. The working of the application is made convenient and easy to use for the end user. Dr

Andresen, Associate Professor, CIS provided regular feedback on the project.

Users can be classified into two types based on their knowledge of the products that

suit their needs. They can be classified as users who know about the product that would

satisfy their needs and users who have to figure out the product that would satisfy their needs.

Users who know about the product should be able to find the product easily with the click of

a button. Such users can search for the product by using the product name as the search term.

Users who have to figure out the product that would satisfy their needs could use a search

term to find a list of products and then should be able to filter the results based on various

parameters like product type, manufacturer, price range, platform supported etc.

The users should be able to view the complete specification of the product and various

images at different Zoom levels. The user should be able to read the customer reviews for the

product and the ratings provided. They should be able to write their own reviews. They

should be able to print out the specifications for a product or email the product page to a

friend¶s etc.

To increase the ease of use the user should be able to add a product to the shopping

cart by dragging a product and dropping it in the shopping cart. A user should able to edit thecontents of a shopping cart. They should be able to update the quantities of the products

added to the cart and remove the products from the cart. The user should be able to remove

the product from the shopping cart by dragging the product and dropping it outside the cart.

The application can be made interactive by pop up messages when a product has been

dropped in to the shopping cart or out of the shopping cart. The user can be notified if the

cursor enters a drop area and the object that could be dropped. Also users are impatient

making it important to load pages soon.

Other than this, I did a lot of research on various other methods of building this

application which and was able to incorporate a few stronger features into the application.

The tools and controls used in the application are recommended ASP.NET controls and

AJAX Toolkit controls which improves the navigation and usability and interactivity.



2.4 ANALYSIS

This is the main document which consists of the foundation of the Software to be

developed. It includes the major characteristics of the system which is going to be developed

such as behavioral, environmental and functional characteristics.

NEED

In current competitive scenario every business establishment needs quality processes

to increase their efficiency as well as improve their productivity. It is of vital importance

that manual, time consuming & monotonous operations are automated so as to streamline

the working of an organization. Since, the existing system (manual work) takes more time

and manpower for processing. It is keeping in mind this business philosophy (mantra) that

we propose an E-SHOP. Our system will deal with all the aspects SALES of Electronics

Related Products and SERVICES after SALES.

MAJOR OBJECTIVES

The main objectives of developing the E-SHOP are as given below: -

1. To provide information about various Electronics Products in different

category online.

2. Customer can purchase Products Online.

3. Customer can login and get various information about product and can

purchase the suitable product.

4. Customer can pay online, so security is must therefore E-SHOP provides

secure transactions.

5. After sale E-SHOP also provide after sales service in which customer problem

is solved.

6. Data security is maintained to relatively high level by implementing it at

Database level, so as to ensure that only authorized users have access to

confidential client information.



2.5 SOFTWARE REQUIREMENT SPECIFICATION

The primary input to the database design process is the organisation¶s statement of

requirements. Poor definition of these requirements is a major cause of poor database design,

resulting in database of limited scope and utilities which are to adopt to change. The first step

in the software development process is called requirement analysis or system analysis.

During this activity the developer attempts to expand and amplify the statement of

requirements and produce the system specification of the document that is an exact

description of what a planned system is to do.

Requirement analysis delimits the system and specifies the services it offers, identifies

the types of users that will interact with the system, and identifies other systems that interact

with the ours. The system is at first considered box, its services are identified, and typical

interaction scenarios are detailed for each service. Requirement analysis includes both fact-

finding about how is the problem solved in the current practice as well as envisioning how

the planned system might work. In each dialog, the user initiates actions and the system

responds with reactions. The use cases specify what information must pass the boundary of

the system in the course of a dialog.

UML (UNIFIED MODIFY LANGUAGE)

The Unified Modelling Language (UML) is a standard language for specifying,

visualizing, constructing, and documenting the artefacts of software systems, as well as for

business modelling and other non-software systems. The UML represents a collection of best

engineering practices that have proven successful in the modelling of large and complex

systems. The UML is a very important part of developing objects oriented software and the

software development process. The UML uses mostly graphical notations to express the

design of software projects.

Using the UML helps project teams communicate, explore potential designs, and validate the

architectural design of the software.



Goals of UML

The primary goals in the design of the UML were:

1. Provide users with a ready-to-use, expressive visual modelling language so they can

develop and exchange meaningful models.

2. Provide extensibility and specialization mechanisms to extend the core concepts.

3. Be independent of particular programming languages and development processes.

4. Provide a formal basis for understanding the modelling language.

5. Encourage the growth of the OO tools market.

6. Support higher-level development concepts such as collaborations, frameworks,

patterns and components.

7. Integrate best practices.

Why Use UML?

As the strategic value of software increases for many companies, the industry looks

for techniques to automate the production of software and to improve quality and reduce cost

and time-to-market. These techniques include component technology, visual programming,

patterns and frameworks. Businesses also seek techniques to manage the complexity of

systems as they increase in scope and scale. In particular, they recognize the need to solve

recurring architectural problems, such as physical distribution, concurrency, replication,

security, load balancing and fault tolerance. Additionally, the development for the World

Wide Web, while making some things simpler, has exacerbated these architectural problems.

The Unified Modeling Language (UML) was designed to respond to these needs.

UML DIAGRAM TYPES

1. USE CASE

A use case is a set of scenarios that describing an interaction between a user and a

system. A use case diagram displays the relationship among actors and use cases. The two

main components of a use case diagram are use cases and actors.



An act i represents a user or anot er system t at will interact wit t e system you are

modelling. A use case is an external view of t e system t at represents some action t e user

might perform in order to complete a task.

B

¡ ¢

se Catalogue and Searc

£

Ite¤

Access the E-S ¥ ¦ § We ̈ s © te

Get Product Information

CUS ¦ ER



If New User Then User Is Authenticated

Log On to Website

(IF USERD ID IS THERE)

CUSTOMER



Give Shipping Info

Buy the Product

Give Payment Info

CUSTOMER

Get Invoice (i.e., Slip)

Get confirmed i.e. Received Product

User Login

SALES



SERVICE

Enter Product Details

User Login

Small Problem

Medium Problem

CUSTOMER

Replace Product

Customer Satisfied



2.6 Project Planning and Scheduling

Planning

A project plan should be included which provides an estimate of the time that you

think you will require working and meeting each of your objectives. The process of planning

can help you sort out your ideas, make vague ideas precise and sequential. A plan is another

toll to be used to get work completed according to a satisfactory standard

Scheduling

Scheduling of a software project can be correlated to prioritizing various tasks with

respect to their cost, time and duration. Scheduling can be done with resources constraint in

mind. Depending upon the project, scheduling methods can be static or dynamic in

implementation.

Work Breakdown structure

The project is scheduled in various phases following a bottom-up or top-down

approach. A tree like structure is followed without loops. At each phase or step, milestone

and deliverables are mentioned with respect to requirements. The work breakdown structure

shows the overall breakup flow of the project and does not indicate any parallel flow. The

project is split into requirement and analysis, design, coding, testing and maintenance phase.

Software Project

Analysis Design Coding Testing

Implementation



3. SYSTEM DESIGN

In order to design a web site, the relational database must be designed first. Conceptual

design can be divided into two parts: The data model and the process model. The data

model focuses on what data should be stored in the database while the process model deals

with how the data is processed. To put this in the context of the relational database, the data

model is used to design the relational tables. The process model is used to design the queries

that will access and perform operations on those tables.

3.1 Software Design

There are fundamentally two different approaches to the software design-

1. Function Oriented Design

In these techniques, to start with view a system a system as a blackbox that performs aset of high level functions. During the design process, these high level functions are

successively decomposed into more detailed functions and finally the different

identified functions are mapped to modules. The term top-down approach is often use

to denote such successive decompositions of a set of high level functions into more

detailed functions.

2. Object Oriented Design

In the object oriented approach, a system is designed as a set of interacting objects.

Normally, each object represents a tangible real world entity.

When a system is analyzed, developed and implemented in terms of the natural

objects occurring in it, it becomes easier to understand the design and implementation

of the system. Each object essentially consists of some data that are private to the

object and a set of functions that operates on those data. The functions of an object

have the sole authority to operate on the private data of the object. Therefore an object

cannot directly access the data internal to another object. However an object can

indirectly access the internal data items of other objects by invoking the operations

supported by those objects. The mechanism is popularly known as the data abstraction

principle.



3.2 Data dictionary

A dictionary lists all the data items appearing in a DFD, i.e. a data dictionary list all

data flows and the content of all the data stores appearing on the DFD.

A data dictionary plays a very important role in any software development process

because of the following reasons:

A data dictionary provides a standard terminology for all relevant data for use by all

engineers working in the same project. A consistent vocabulary for data items is very

important, since in large projects different engineers have a tendency to use different terms to

refer to the same data, which unnecessarily causes confusion.

The data dictionary provides the analyst with a means to determine the definition of

different data structures in terms of their component elements.

The dictionary contains two types of description for the data flowing through the

system: data elements and data structures. Data elements are grouped together to make up a

data structures.

Data elements are recorded in data dictionary at the fundamental data level. Each item

is defined by a data name, description, alias and length has specific values that are

permissible for it in the system.

Analysts use the detail for the following reasons:

1. To manage the detail in the large systems.

2. To communicate a common meaning for all the system elements.

3. To document the features of the system.

4. To facilitate analysis the details in order to evaluate characteristics and determine

changes that should be made to the system.

5. To locate the errors and omissions in the system.



3.3 Data Flow Diagram

A Context Level Diagram

A First Level Diagram



A SECOND LEVEL DIAGRAM



A SECOND LEVEL DIAGRAM



3.4 E-R DIAGRAM

Customer Entity





3.5 State Machine Diagram or Activity Diagram Activity diagrams describe the workflow behaviour of a system. Activity diagrams

are similar to state diagrams because activities are the state of doing something. The

diagrams describe the state of activities by showing the sequence of activities performed.Activity diagrams can show activities that are conditional or parallel.

A state machine diagram is normally used to model how the state of an object changes

in its lifetime. State machine diagrams are good at describing hoe the behaviour of an object

changes across several use case executions.

GET INFO.

REGISTER

CONTINUELOGIN

HANDLE

PURCHASE

NEXT

IDENTIFY

PLACE

PROBLEM

IDENTIFY

SOLUTION

NEXT

BUY

SERVICE

NEW

EXIST



State machine diagrams are based on finite state machine formalism. An FSM consists of a

finite number of states corresponding to those of the object being modelled.

The basic elements of the state machine diagram are as follows:

1. Initial state

2. Final state

3. State

4. Transition

3.6 Database Design

TABLE NAME: User Table

FIELD NAME TYPE DATAID int

UserName )50(nvarchar

Password )50(nvarchar

Email )50(nvarchar

Address )50(nvarchar

NumberID )50(nvarchar

epytUser )50(nvarchar

TABLE NAME: ShoppingCart

TABLE NAME: Reviews

DATA TYPEFIELD NAME

intReviewID

nvarchar(50)Username

nvarchar(4000)Review

nvarchar(50)ProductID

DATA TYPEFIELD NAMEintShoppingID

nvarchar(50)ProductIDNo

nvarchar(50)UserID

nvarchar(50)SalesStatus

intqty



TABLE NAME: PRODUCT TABLE

DATA TYPEFIELD NAME

intProductID

nvarchar(50)ProductName

nvarchar(2000)ProductDescription

nvarchar(500)ProductShortDescription

intPricenvarchar(50)Category

nvarchar(500)ProductImage

nvarchar(50)ProductImageThumb

TABLE NAME: PRODUCT CATEGORY

DATA TYPEFIELD NAME

Nvarchar(50)CatogeryID

intCatogery

TABLE NAME: ORDER TABLE

DATA TYPEFIELD NAME

intSerialNumber

nvarcharUserName

floatAmount



3.7 Class Diagram



3.8 Security

For a secure use of application used in this system, a user id and password will be allotted to

every user who will use the system. An authorised user will be capable of opening the form.

When a user will attempt to use the software, a login form will come in front of the user,

displaying appropriate message. After entering the correct user id and password he / she will

be able to use the application.



4. CODING

4.1 Introduction to Windows 2003 Server

4.2 Introduction to ASP.NET

4.3 Introduction to SQL Server 2000

4.4 Coding AdminNewItem.aspx.cs

using System;

using System.Collections;

using System.Configuration;

using System.Data;

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;

public partial class AdminPage : System.Web.UI.Page

{

protected void Page_Load(object sender, EventArgs e)

{

btnInsert.Visible = false;

}

protected void RadioButtonList1_SelectedIndexChanged(object sender, EventArgs e)

{

}

protected void btnsaveProduct_Click(object sender, EventArgs e)



{

if (FileUpload1.HasFile)

{

FileUpload1.SaveAs("F:/Documents and

Settings/shift/Desktop/EWAPP/Uploadedpix/" + FileUpload1.FileName);

lblFullSizeImage.Text = FileUpload1.FileName;

}

if (FileUpload2.HasFile)

{

FileUpload2.SaveAs("F:/Documents andSettings/shift/Desktop/EWAPP/Thumbnails/" + FileUpload2.FileName);

}

lblThumbSizeImage.Text = FileUpload2.FileName;

btnsaveProduct.Visible = true;

SqlDataSource1.Insert();

this.lblAddingNewItem.Text = "Item Has Been Added into the Database";

btnsaveProduct.Visible = false;

btnInsert.Visible = true;

txtPrice.Enabled = false;

txtShortDescription.Enabled = false;

txtProductDescription.Enabled = false;

txtProductName.Enabled = false;

dropCatInsert.Enabled = false;

}

protected void btnInsert_Click(object sender, EventArgs e)

{

txtPrice.Text = "";

txtProductDescription.Text = "";

txtProductName.Text = "";

txtPrice.Enabled = true;



txtProductDescription.Enabled = true;

txtProductName.Enabled = true;

btnsaveProduct.Visible = true;

dropCatInsert.Enabled = true;

}

protected void LinkButton1_Click(object sender, EventArgs e)

{

}


{

}

protected void DropSearchItems_SelectedIndexChanged(object sender, EventArgs e)

{

}

}

AdminMainItems.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;









public partial class AdminMaintainItems : System.Web.UI.Page

{


{

}

protected void DropSearchCat_SelectedIndexChanged(object sender, EventArgs e)

{

}

protected void FormView2_ItemUpdated(object sender, FormViewUpdatedEventArgs e)

{

this.GridView1.DataBind();

}

}

AdminSalesMaintenance.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;







public partial class AdminSalesMaintenance : System.Web.UI.Page



{


{

}


{

MultiView1.ActiveViewIndex = RadioButtonList1.SelectedIndex;

}


{


}


{


}

}

AdminUserMaintenance.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;









public partial class AdminUserMaintenance : System.Web.UI.Page

{


{

}


{


}

protected void Button1_Click(object sender, EventArgs e)

{

SqlDataSource sds = new SqlDataSource();

sds.ConnectionString =

ConfigurationManager .ConnectionStrings["ConnectionString" ].ToString();

sds.SelectParameters.Add("Username", TypeCode.String, this.txtUserName.Text);

sds.SelectParameters.Add("Email", TypeCode.String, this.txtEmail1.Text);

sds.SelectCommand = "SELECT * FROM [UserTable] WHERE [Username] =

@Username OR [Email] = @Email";

DataView dv = (DataView)sds.Select(DataSourceSelectArguments.Empty);

if (dv.Count != 0)

{

this.Label1.ForeColor = System.Drawing.Color .Red;

this.Label1.Text = "The user already Exist!";

return;

}



else

{

this.SqlDataSource2.Insert();

this.Label1.Text = "New User Profile has been created you can login now";

Button1.Enabled = false;

txtAddress.Enabled = false;

txtEmail1.Enabled = false;


txtName.Enabled = false;

txtpassportNumber.Enabled = false;

txtPassword1.Enabled = false;

txtpassword2.Enabled = false;

txtUserName.Enabled = false;

}

}


{


}


{


}

}

DescriptionPurchase.aspx.cs

using System;



using System.Data;



using System.Linq;

using System.Web;







public partial class test2 : System.Web.UI.Page

{


{

this.lblusernam.Text = this.Session["Username"].ToString();

ListView1.Visible = false;

lblItem.Visible = false;

Linklogin.Visible = false;

txtReview.Visible = false;

Button1.Visible = false;

Label2.Visible = false;

if (Session["UserType"] == null)

{

Linklogin.Visible = true;

btnAddToCart.Visible = false;


}

if (Request.QueryString["ProductID"] != null)

{

string ProductID;

ProductID = Request.QueryString["ProductID"].ToString();



string connectionString =ConfigurationManager .ConnectionStrings["ConnectionString" ].ToString();

System.Data.SqlClient.SqlConnection conn = new

System.Data.SqlClient.SqlConnection(connectionString);

System.Data.SqlClient.SqlCommand cmd = conn.CreateCommand();

cmd.CommandText = "SELECT * FROM [ProductTable] where ProductID='"

+ ProductID + "'";

conn.Open();

System.Data.SqlClient.SqlDataReader dr = cmd.ExecuteReader();

this.lblProductID.Text = "";

while (dr.Read())

{

this.lblProductID.Text = dr["ProductID"].ToString();

this.lblDescription.Text = dr["productDescription"].ToString();

this.lblPrice.Text = dr["Price"].ToString();

this.lblProductName.Text = dr["ProductName"].ToString();

this.Image2.ImageUrl = dr["ProductImage"].ToString();

Image2.ImageUrl = "uploadedpix/" + dr["ProductImage"].ToString();

}

dr.Close();

conn.Close();

}

else

Response.Redirect("UserMainPage.aspx");

}


{

btnAddToCart.Visible = true;

}

protected void btnAddToCart_Click(object sender, EventArgs e)

{





lblItem.Visible = true;

}


{

Response.Redirect("login.aspx");

}

protected void Button1_Click1(object sender, EventArgs e)

{


Button1.Visible = false;

Label2.Visible = true;

}

protected void LinkButton2_Click1(object sender, EventArgs e)

{

txtReview.Visible = true;

Button1.Visible = true;

}


{

ListView1.Visible = true;

}

}

DescriptionPurchaseAnonymus.aspx.cs

using System;





using System.Data;

using System.Linq;

using System.Web;







public partial class test2 : System.Web.UI.Page

{


{

ListView1.Visible = false;


Linklogin.Visible = false;

if (Session["UserType"] == null)

{

Linklogin.Visible = true;




}

if (Request.QueryString["ProductID"] != null)

{

string ProductID;

ProductID = Request.QueryString["ProductID"].ToString();



string connectionString = "Data Source=.\\SQLEXPRESS;"

+ "AttachDbFilename=\"F:\\DOCUMENTS AND

SETTINGS\\SHIFT\\DESKTOP\\EWAPP\\APP_DATA\\EWAPP.MDF\";"

+ "Integrated Security=True;"

+ "Connect Timeout=30;"

+ "User Instance=True";

System.Data.SqlClient.SqlConnection conn = new

System.Data.SqlClient.SqlConnection(connectionString);

System.Data.SqlClient.SqlCommand cmd = conn.CreateCommand();

cmd.CommandText = "SELECT * FROM [ProductTable] where ProductID='" +

ProductID + "'";

conn.Open();

System.Data.SqlClient.SqlDataReader dr = cmd.ExecuteReader();

this.lblProductID.Text = "";

while (dr.Read())

{

this.lblProductID.Text = dr["ProductID"].ToString();

this.lblDescription.Text = dr["productDescription"].ToString();

this.lblPrice.Text = dr["Price"].ToString();

this.lblProductName.Text = dr["ProductName"].ToString();

this.Image2.ImageUrl = dr["ProductImage"].ToString();

Image2.ImageUrl = "uploadedpix/" + dr["ProductImage"].ToString();

}

dr.Close();

conn.Close();

}

else

Response.Redirect("UserMainPage.aspx");

}


{



btnAddToCart.Visible = true;

Label1.Visible = true;

}

protected void btnAddToCart_Click(object sender, EventArgs e)

{


lblItem.Visible = true;


}


{

Response.Redirect("login.aspx");

}

protected void LinkButton2_Click1(object sender, EventArgs e)

{

ListView1.Visible = true;

}

}

Login.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;









public partial class Login : System.Web.UI.Page

{


{

}


{


sds.ConnectionString =

ConfigurationManager .ConnectionStrings["ConnectionString" ].ToString();

sds.SelectParameters.Add("Username", TypeCode.String, this.TextBox1.Text);

sds.SelectParameters.Add("Password", TypeCode.String, this.TextBox2.Text);

sds.SelectCommand = "SELECT * FROM [UserTable] WHERE [Username] =

@Username AND [Password] = @Password";


if (dv.Count == 0)

{


this.Label1.Text = "Login Failed!";

return;

}

this.Session["Username"] = dv[0].Row["Username"].ToString();

this.Session["UserType"] = dv[0].Row["UserType"].ToString();

if (this.Session["UserType"].ToString().Equals("user"))

Response.Redirect("MainPageUsers.aspx");

else if (this.Session["UserType"].ToString().Equals("admin"))



Response.Redirect("MainPageAdmin.aspx");

}

}

Registernewuser.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;







public partial class registernewuser : System.Web.UI.Page

{


{


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

sds.SelectParameters.Add("Username", TypeCode.String, this.txtUserName.Text);

sds.SelectParameters.Add("Email", TypeCode.String, this.txtEmail1.Text);

sds.SelectCommand = "SELECT * FROM [UserTable] WHERE [Username] =@Username OR [Email] = @Email";




if (dv.Count != 0)

{


this.Label1.Text = "The user already Exist!";

return;

}

else

{

this.SqlDataSource1.Insert();

this.Label1.Text = "New User Profile has been created you can login now";

Button1.Enabled = false;

txtAddress.Enabled = false;



txtName.Enabled = false;

txtpassportNumber.Enabled = false;

txtPassword1.Enabled = false;

txtpassword2.Enabled = false;

txtUserName.Enabled = false;

}

}


{

}

protected void ImageButton1_Click(object sender, ImageClickEventArgs e)

{

}



}

SearchItems.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;







public partial class test : System.Web.UI.Page

{


{

}

protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)

{

}

protected void GridView3_SelectedIndexChanged(object sender, EventArgs e)

{

}


{



}

protected void txtItemSearch_TextChanged(object sender, EventArgs e)

{

}


{


}

}

SearchItemsAnonymus.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;








{


{

}

protected void DropDownList1_SelectedIndexChanged(object sender, EventArgs e)



{

}


{

}


{

}

protected void txtItemSearch_TextChanged(object sender, EventArgs e)

{

}


{


}

}

ShoppingCart.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;









public partial class ShoppingCart : System.Web.UI.Page

{


{

}


{


}

protected void GridView1_RowUpdated(object sender, GridViewUpdatedEventArgs e)

{

}

}

Test.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;










{


{

}

protected void DetailsView1_ItemUpdated(object sender, DetailsViewUpdatedEventArgs

e)

{


}

}

ViewMyReviews.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;







public partial class viewMyReviews : System.Web.UI.Page

{


{



}


{


}

}

ViewReviews.aspx.cs

using System;



using System.Data;

using System.Linq;

using System.Web;







public partial class ViewReviews : System.Web.UI.Page

{


{

}


{

}




{


}

}



5. PERT CHART AND GANTT CHART

5.1 Pert Chart

5.2 Gantt Chart

Pert Chart & Gantt Chart

PERT (Project Evaluation and Review Technique) charts consist of a network of boxes and arrows.

The boxes represent activities and the arrow represents the task dependencies. Pert chart for our

project is given under:-

Draw the pert chart««.

Gantt chart

Gantt chart are useful for scheduling, budgeting and resource planning. Gantt charts are a special type

bar charts where each bar represents an activity. The bars are drawn alone a time line. The gantt chart

for our project is given under:-

Draw the gantt chart here««.



6. IMPLEMENTATION AND TESTING

6.1 Implementation

During Implementation we can turn system specification into working system that is

tested and put into use. It includes coding testing and installation during coding

programmers write program that make up the system. During testing, and analysis test

the individual programs and the entire system in order to find and correct errors. During

installation, the new system becomes the part of the daily activity of the organization.

Implementation activities also include initial user support such as the finalization of

documentation, training program¶s and ongoing user assistance.

6.2 Testing

Black-box (Functional) Testing

Testing against specification of system or component. Study it by examining

its inputs and related outputs. Key is to devise inputs that have a higher likelihood of

causing outputs that reveal the presence of defects. Use experience and knowledge of

domain to identify such test cases. Failing this a systematic approach may be necessary.

Equivalence partitioning is where the input to a program falls into a number of classes.

E.g. positive numbers vs. negative numbers. Programs normally behave the same way

for each member of a class. Partitions exist for both input and output. Partitions may be

discrete or overlap. Invalid data (i.e. outside the normal partitions) is one or more

partitions that should be tested. Test cases are chosen to exercise each portion. Also test

boundary cases (atypical, extreme, zero) since these frequently show up defects. For

completeness, test all combinations of partitions. Black box testing is rarely exhaustive

(because one doesn't test every value in an equivalence partition) and sometimes fails to

reveal corruption defects caused by "weird" combination of inputs. Black box testing

should not be used to try and reveal corruption defects caused, for example, by assigning

a pointer to point to an object of the wrong type. Static inspection (or using a better

programming language!) is preferable for this.



White-box (structural) Testing

Testing based on knowledge of structure of component (e.g. by looking at source

code). Advantage is that structure of code can be used to find out how many test case need to

be performed. Knowledge of the algorithm (examination of the code) can be used to identifythe equivalence partitions. Path testing is where the tester aims to exercise every independent

execution path through the component. All conditional statements tested for both true and

false cases. If a unit has n control statements, there will be up to 2n possible paths through it.

This demonstrates that it is much easier to test small program units than large ones. Flow

graphs are a pictorial representation of the paths of control through a program (ignoring

assignments, procedure calls and I/O statements). Use flow graph to design test cases that

execute each path. Static tools may be used to make this easier in programs that have a

complex branching structure. Tools support. Dynamic program analyzers instrument a

program with additional code.

Typically this will count how many times each statement is executed. At end, print out report

showing which statements have and have not been executed. Problems with flow graph

derived testing:

1. Data complexity not taken into account.

2.

Does not test all paths in combination.

3. Really only possible at unit and module testing stages because beyond that complexity

is too high.

Interface testing

Usually done at integration stage when modules or sub-systems are combined.

Objective is to detect errors or invalid assumptions about interfaces between modules.

Reason these are not shown up in unit testing is that test case may perpetuate same incorrectassumption made by module designer. Particularly important when OO development has

been used. Four types of interface:

1. Parameter: data (or occasionally function references) passed from one unit to another.



2. Shared memory: block of memory shared between units (e.g. global variable) .One places

data there and the other retrieves it.

3. Procedural: object-oriented or abstract data type form of interface, encapsulating several

procedures.

4. Message passing: one sub-system requests a service by passing a message. Client-server

interface also used by some OO architectures.



6.3 SCREEN SHOTS

AdminAddNewItem.aspx



AdminMaintainItems.aspx



VIewReviews.aspx



AdminSalesMaintenance.aspx



AdminUserMaintenance.aspx









MainPageAdmin.aspx



MainPageUser.aspx



ViewUserProfile.aspx



SearchItems.aspx



DescriptionPurchase.aspx/ProductID=3



ShoppingCart.aspx



ContactUs.aspx



6.4 Future Scope of the Project

1. The E-SHOP at present not provides service through telephony, but in E-SHOP we

can provide it in future.2. Automatic mail sending facility is provided to the customer ,that purchases the

product

3. Live help will be provided in the future.

4. Websites will be mounted using secure http connection.



7. BIBLIOGRAPHY

1) Asp .NET 2.0 with Visual C# .NET 2005 by Wrox publications.

2) Web application development with c# by Microsoft press no.-70-315

3) www.startvbdotnet.com: - tutorial for asp.net with c#

4) www.quickstart.com: - tutorial for asp.net

5) www.asp.net.com :-tutorial for asp.net

Date post:	08-Apr-2018
Category:	Documents
Upload:	saurabh-jha
View:	215 times
Download:	0 times