SHOPPING CART

51
1. INTRODUCTION 1.1 ABOUT THE PROJECT Microsoft .NET is a set of Microsoft software technologies for rapidly building and integrating XML Web services, Microsoft Windows-based applications, and Web solutions. The .NET Framework is a language-neutral platform for writing programs that can easily and securely interoperate. There’s no language barrier with .NET: there are numerous languages available to the developer including Managed C++, C#, Visual Basic and Java Script. The .NET framework provides the foundation for components to interact seamlessly, whether locally or remotely on different platforms. FEATURES OF VISUAL BASIC .NET The .NET Framework is a new computing platform that simplifies application development in the highly distributed environment of the Internet. Objectives of .NET Framework To provide a consistent object-oriented programming environment whether object Codes is stored and executed locally on Internet- distributed, or executed remotely. 1

description

Shopping cart

Transcript of SHOPPING CART

Page 1: SHOPPING CART

1. INTRODUCTION

1.1 ABOUT THE PROJECT

Microsoft .NET is a set of Microsoft software technologies for rapidly

building and integrating XML Web services, Microsoft Windows-based

applications, and Web solutions. The .NET Framework is a language-neutral platform

for writing programs that can easily and securely interoperate.

There’s no language barrier with .NET: there are numerous languages

available to the developer including Managed C++, C#, Visual Basic and Java Script.

The .NET framework provides the foundation for components to interact seamlessly,

whether locally or remotely on different platforms.

FEATURES OF VISUAL BASIC .NET

The .NET Framework is a new computing platform that simplifies

application development in the highly distributed environment of the Internet.

Objectives of .NET Framework

To provide a consistent object-oriented programming environment whether object

Codes is stored and executed locally on Internet-distributed, or executed remotely.

To provide a code-execution environment to minimizes software deployment and

guarantees safe execution of code.

Eliminates the performance problems.

The Common Language Runtime (CLR)

The common language runtime is the foundation of the .NET Framework. It

manages code at execution time, providing important services such as memory

management, thread management, and removing and also ensures more security

and robustness.

The concept of code management is a fundamental principle of the runtime. Code

that targets the runtime is known as managed code, while code that does not target

the runtime is known as unmanaged code.

1

Page 2: SHOPPING CART

The .NET Frame work class library

It is a comprehensive, object-oriented collection of reusable types used to develop

applications ranging from traditional command-line or graphical user interface

(GUI) applications to applications based on the latest innovations provided by

ASP.NET, such as Web Forms and XML Web services.

The .NET Framework can be hosted by unmanaged components that load the

common language runtime into their processes and initiate the execution of

managed code, thereby creating a software environment that can exploit both

managed and unmanaged features. The .NET Framework not only provides

several runtime hosts, but also supports the development of third-party runtime

hosts

Features of the Common Language Runtime

The common language runtime manages memory; thread execution, code

execution, code safety verification, compilation, and other system services these are all

run on CLR.

Security.

Robustness.

Productivity.

Performance.

Security

The runtime enforces code access security. The security features of the runtime

thus enable legitimate Internet-deployed software to be exceptionally featuring rich. With

regards to security, managed components are awarded varying degrees of trust, depending

on a number of factors that include their origin to perform file-access operations, registry-

access operations, or other sensitive functions.

2

Page 3: SHOPPING CART

Robustness

The runtime also enforces code robustness by implementing a strict type- and

code-verification infrastructure called the common type system (CTS). The CTS ensures

that all managed code is self-describing. The managed environment of the runtime

eliminates many common software issues.

Productivity

The runtime also accelerates developer productivity. For example, programmers

can write applications in their development language of choice, yet take full advantage of

the runtime, the class library, and components written in other languages by other

developers

Performance

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A

feature called just-in-time (JIT) compiling enables all managed code to run in the native

machine language of the system on which it is executing. Finally, the runtime can be

hosted by high-performance, server-side applications, such as Microsoft® SQL Server™

and Internet Information Services (IIS).

Managed Code

The code that targets .NET, and which contains certain extra Information -

“metadata” - to describe itself. Both managed and unmanaged code can run in the

runtime, only managed code contains the information that allows the CLR to guarantee,

for instance, safe execution and interoperability

3

Page 4: SHOPPING CART

Common Type System

The CLR uses something called the Common Type System to strictly enforce

type-safety. This ensures that all classes are compatible with each other, by describing

types in a common way. CTS define how types work within the runtime, which enables

types in one language to interoperate with types in another language, including cross-

language exception handling.

Common Language Specification

The CLR provides built-in support for language interoperability. To ensure that,

can develop managed code that can be fully used by developers using any programming

language, a set of language features and rules for using them called the Common

Language Specification (CLS) has been defined. Components that follow these rules and

expose only CLS features are considered CLS-compliant.

Data Access with ADO.NET

Develop applications using ADO.NET; it will have different requirements for

working with data. It might never need to directly edit an XML file containing data.

ADO.NET offers several advantages over previous versions of ADO

Interoperability

Maintainability

Programmability

Performance Scalability

4

Page 5: SHOPPING CART

Interoperability

ADO.NET applications can take advantage of the flexibility and broad acceptance

of XML. Because XML is the format for transmitting datasets across the network, any

component that can read the XML format can process data. The receiving component

need not be an ADO.NET component.

The transmitting component can simply transmit the dataset to its destination

without regard to how the receiving component is implemented. The destination

component might be a Visual Studio application or any other application implemented

with any tool whatsoever.

Maintainability

In the life of a deployed system, modest changes are possible, but substantial,

Architectural changes are rarely attempted because they are so difficult.

As the performance load on a deployed application server grows, system resources

can become scarce and response time or throughput can suffer. Faced with this problem,

software architects can choose to divide the server's business-logic process architects can

choose to divide the server's business-logic processing and user-interface processing onto

separate tiers on separate machines.

In effect, the application server tier is replaced with two tiers, alleviating the

shortage of system resources. If the original application is implemented in ADO.NET

using datasets, this transformation is made easier.

ADO.NET data components in Visual Studio encapsulate data access functionality in

various ways that help the program more quickly and with fewer mistake

5

Page 6: SHOPPING CART

Scalability

ADO.NET accommodates scalability by encouraging programmers to conserve

limited resources. Any ADO.NET application employs disconnected access to data; it

does not retain database locks or active database connections for long durations.

Visual Studio 

Visual Studio is a complete set of development tools for building ASP Web

applications, XML Web services, desktop applications, and mobile applications. In

addition to building high-performing desktop applications, Visual Studio's powerful

component-based development tools.

Visual Basic .NET, Visual C++ .NET, and Visual C# .NET all use the same

integrated development environment (IDE), which allows them to share tools and

facilitates in the creation of mixed-language solutions. In addition, these languages

leverage the functionality of the .NET Framework and simplify the development of ASP

Web applications and XML Web services

XML Support

Extensible Markup Language (XML) provides a method for describing

structured data. XML is a subset of SGML that is optimized for delivery over the Web.

The World Wide Web Consortium (W3C) defines XML standards so that structured data

will be uniform and independent of applications.

Visual Basic .NET

Visual Basic .NET, the latest version of visual basic, includes many new features.

The Visual Basic supports interfaces but not implementation inheritance.

6

Page 7: SHOPPING CART

Common Language Specification (CLS)

Visual Basic.NET is also compliant with CLS (Common Language Specification)

and supports structured exception handling. CLS is set of rules and constructs that are

supported by the CLR (Common Language Runtime). CLR is the runtime environment

provided by the

.NET Framework; it manages the execution of the code and also makes the development

process easier by providing services.

Visual Basic.NET is a CLS-compliant language. Any objects, classes, or

components that created in Visual Basic.NET can be used in any other CLS-compliant

language. In addition, they can use objects, classes, and components created in other

CLS-compliant languages in Visual Basic.NET .The use of CLS ensures complete

interoperability among applications, regardless of the languages used to create the

application.

Performance

The runtime is designed to enhance performance. Although the common language

runtime provides many standard runtime services, managed code is never interpreted. A

feature called just-in-time (JIT) compiling enables all managed code to run in the native

machine language of the system on which it is executing.

7

Page 8: SHOPPING CART

1.2 SYSTEM SPECIFICATION

1.2.1 HARDWARE SPECIFICATION

Processor : Intel Pentium 90 MHz or faster

RAM : 42GB

Hard disk drive : 20 GB of available hard-disk space for installation

1.2.2 SOFTWARE SPECIFICATION

Technology : Microsoft Visual Studio

Front end : Visual Basic.Net

Back end : SQL Server

8

Page 9: SHOPPING CART

2. SYSTEM STUDY

2.1EXISTING SYSTEM

In existing system all the data of products and the prices are entered

manually, so is takes more time to retrieve details like product details, customer

details and the total amount paid. Furthermore, it is time consuming to retrieve

one specific customer information and the complaints or suggestions provided by

them.

2.1.1 DRAWBACKS

Retrieval of information takes more time

Redundancy will be more

While entering the data manually, some data might miss out

2.2PROPOSED SYSTEM

Proposed system is an automated Shopping cart. Through our software

user can add product details, customer details and update information and edit

information within short time. All the manual difficulties in managing a shopping

cart have been removed by implementing computerization.

2.2.1 FEATURES

User friendly interface

Less error

More Storage Capacity

Search facility

Quick Updating

9

Page 10: SHOPPING CART

3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

Information must be collected, accumulated edited and should directly be

retrieved. So, directly or indirectly we need the file. The files should be properly

designed and planned. File design refers to the design of the data organization, in the

backup storage systems. This play an important and crucial role for the successful

performance of the system. In the system we have three master files and number of

transaction files. The design phase was started viewing the study phase activities and

making decisions about which functions are to be performed by the hardware.

3.2 INPUT DESIGN

The various screens are used in this project to serve as data entry screens in order

to input data into the system and to retrieve data from the system. The login screen is

loaded and verifies the user authentication. If user Id and password are valid then the

users enter into the project.

The input forms involved in this project are:

1) Buyer Registration form

This form is used to enter the customer details such as customer id,

customer name, address and phone number.

2) Product form

This form is used to enter the product details such as product id, product

name, quantity and price.

3) Stock form

This form is used to enter the new stock updated date.

4) Selection form

This form is used to enter the products selected by the customer. The

number of quantity is also entered.

5) Acknowledgement form

This form is used to enter the suggestions/ complaints provided

by the customer about the products.

10

Page 11: SHOPPING CART

3.3 OUTPUT DESIGN

The output generally refers to the results and information that is generated from

the system. The output design is used to give reports. They are used to communicate the

result of processing hard copy of the result.

The output forms involved in this project are,

1) Buyer Registration details

This form is used to view the customer details such as customer id,

customer name, address and phone number.

2) Product details

This form is used to view the product details such as product id, product

name, quantity and price.

3) Stock details

This form is used to view the new stock updated after the customer

purchase.

4) Selection details

This form is used to view the products selected by the customer. The bill is

generated after the purchase.

5) Acknowledgement details

This form is used to view the suggestions/ complaints provided by the

customer about the products.

3.4 DATABASE DESIGN

The over all objective in the developments of a data base treated and

organizational resource and as an integrated whole. The primary objectives are fast

response time to inquire more information at low cost, control redundancy, clarity and

ease or use accuracy and fast recovery.

11

Page 12: SHOPPING CART

3.5 SYSTEM DEVELOPMENT

3.5.1 DESCRIPTION OF MODULES

1) Buyer Registration

This module is used to register the new user. The personal information of

user such as name, address and the phone number is stored. The unique

identification number for each customer is maintained.

2) Product Details

The product available in the cart is stored in this module. The product id is

available for all products and the price for each product is also maintained

simultaneously.

3) Stock Details

The products available after purchase are maintained in this module. When

the customer purchase a product the quantity of product automatically decreases

in the stock.

4) Selection Details

The products selected by the customer are added in the cart. Then the total

amount is calculated and the bill is generated.

5) Acknowledgement

The complaints and any suggestions about the product or service is

maintained separately in this module. According to the suggestions provided by

the customer the necessary steps are taken.

12

Page 13: SHOPPING CART

4. TESTING AND IMPLEMENTATION

4.1 SYSTEM TESTING

The method of designing the program to produce the desired result is

accomplished to the section. Programs are written and tested by using sample data: if the

output produces good result was that the actual required output. All the facilities required

for developing the new system acquired and program preparation is started. Quality

assurance is an important step in software engineering. This overlaps with all the phases

of development right from the requirement analysis. This quality requirement phase of the

software system must be clearly extracted during the requirement analysis and all the

subsequent should be made biased to that, so that the final testing will become trivial and

less expensive. The testing is carried in the following steps,

Unit Testing

Unit Testing refers testing of the all individual program. This is sometimes called

as program testing. This test should be carried out during programming stage in order to

find the errors in coding and logic for each program in each module. Unit test focuses

verification effort on the smallest unit of software design module. In this project, the user

must fill each field otherwise the user to enter values.

Integration Testing

In integration testing all modules are combined. This testing starts from main form

to entire module. Input is given to check whether all modules are connected properly or

not. The main objective in this testing is to unit test the modules and built a program

structure that has been dictated by the design.

Validation Testing

Valid and invalid data should be created and the program should be made to

process this data to catch errors. If the user gives the wrong password or userid then the

13

Page 14: SHOPPING CART

information is provided to the user like “you must enter use rid and password”. Here the

inputs given by the user are validated.

Acceptance Testing

Accepting test is performed on a collection of business functions in a production

environment and after the completion of functional testing. This is the final stage in the

testing process before the system is accepted for operational use. This testing is should be

done with original data and with the presence of the users. This test confirms the system

ready for production.

Code Testing

It describes the degree to which source code of the program has been tested. The

target software is built with special options or libraries and run under a special

environment such that every function is exercised in the program are mapped back to the

function points in the source code.

14

Page 15: SHOPPING CART

4.2 SYSTEM IMPLEMENTATION

Implementation means the process of converting a new raised system design into

an operational one. Depending on the nature of the system, extensive user may be

required. Implementation simply means converting a new system design into operation.

An important aspect of system analyst’s job is to make sure that the new system is

implemented to establish standards.

After the system is implemented successfully, training of the user is one of the

most important subtasks of the developer. For this purpose user manuals are prepared and

handled over to the user to operate the development system. Thus the users are trained to

operate the developed system. Both the hardware and software securities are made to run

the developed systems successfully in future.

15

Page 16: SHOPPING CART

5. CONCLUSION

We understand the importance of planning and designing as a part of shopping

cart. The concept of peer-reviews helped to rectify the problems as and when they

occurred and also helped us to get some valuable suggestions that were incorporated by

us. Developing the project has helped us to gain some experienced on real time

development procedures.

All the objectives that had been charted out in the initial phases were achieved

successfully. System satisfies all the requirements for which the company developed the

system. System has strong security.

System is fully GUI based. It is easy operate and user friendly. Platform includes

the inbuilt backup and recovery facility. Working on the project was a good experience.

Working together in teams helped us to communicate better.

16

Page 17: SHOPPING CART

BIBLIOGRAPHY

BOOK REFERENCES

1. Roger S. Pressman, ‘Software Engineering: A Practioner’s Approach’, McGraw-Hill

International Edition, Fifth edition, 2001.

2. Designing Microsoft VB.NET Applications TataMcGrawHill Edtion, 2001.

3. Chris Goodge, John Kauffman,’Microsoft Visual Basic.NET Programmer’s Cookbook’

TataMcGrawHill Edtions, 2002.

4.http://www.nytimes.com/2010/04/11/books/review/Schuessler-t.html?pagewanted=all

WEB REFERENCES

1. https://elsevise/default.asp

2. http://www.aptaracorp.com/publishing-services

3. http://www.infinitypublishing.com/

4. http://www.lulu.com/

5. http://www.authorsonline.co.uk/

6. http://www.samhainpublishing.com/

17

Page 18: SHOPPING CART

APPENDIX

A.DATA FLOW DIAGRAM

Billing

18

ProvidesAcknowledgement Customer

Register

ViewAdmin Customer details

Product

Purchase

Update

Stock

Page 19: SHOPPING CART

B.TABLE STRUCTURE

1)Table Name: Buyer Registration

Primary Key: CID

Field Name Data Type Size Description

CID Nvarchar 10 Customer Identification Number

Cname Nvarchar 20 Name of the Customer

Addr Nvarchar 30 Address

Phno Bigint 10 Phone number

Rdate Date __ Date of Registration

2)Table Name: Product Details

19

Page 20: SHOPPING CART

Primary Key: PID

Field Name Data Type Size Description

PID Nvarchar 10 Product Identification Number

Pname Nvarchar 20 Name of Product

Qty Float 20 Quantity of the Product

Price Float 20 Price of the Product

3)Table Name: Stock Details

Foreign Key: PID

20

Page 21: SHOPPING CART

Field Name Data Type Size Description

PID Nvarchar 10 Product Identification Number

Pname Nvarchar 20 Name of Product

Uqty Float 20 Updated Quantity of the Product

Price Float 20 Price of the Product

Udate Date ____ Updated date

4)Table Name: Selection Details

Foreign Key: CID, PID

Field Name Data Type Size Description

21

Page 22: SHOPPING CART

CID nvarchar 10 Customer Identification Number

PID nvarchar 10 Product Identification Number

Pname nvarchar 10 Name of Product

qty float 20 Quantity of the Product

Price float 20 Price of the Product

Tot float 20 Total

Bdate date ____ Billing date

5)Table Name: Acknowledgement details

Foreign Key: CID, PID

Field Name Data Type Size Description

CID Nvarchar 10 Customer Identification Number

22

Page 23: SHOPPING CART

Cname Nvarchar 20 Name of the Customer

PID Nvarchar 10 Product Identification Number

Pname Nvarchar 10 Name of Product

Comp Nvarchar 100 Suggestions/ Complaints

C.SAMPLE CODING

Imports System

Imports System.Data

23

Page 24: SHOPPING CART

Imports System.Data.SqlClient

Imports System.IO

Imports CrystalDecisions.CrystalReports.Engine

Imports CrystalDecisions.Shared

Public Class frmBilling

Dim available As Boolean

Public selRow As New DataGridViewRow

Dim a As Integer = 0

Dim con As New SqlConnection("Data Source=.\SQLEXPRESS;Initial

Catalog=Geeva;Integrated Security=True")

'Dim cmd As New SqlCommand

Dim qry, qry1 As String

Dim da As New SqlDataAdapter

Dim ds As DataSet

Dim dbind As New BindingSource

Dim i As Integer

Dim reader As SqlDataReader

Dim com As SqlCommand

Dim adp As SqlDataAdapter

Public Sub ComboBox1_SelectedIndexChanged(ByVal sender As

System.Object, ByVal e As System.EventArgs) Handles

ComboBox1.SelectedIndexChanged

24

Page 25: SHOPPING CART

qry1 = "select Unit,Price from tblInventoryDetails1 where Productname='" +

ComboBox1.SelectedItem.ToString + "'"

com = New SqlCommand(qry1, con)

adp = New SqlDataAdapter(com)

ds = New DataSet

adp.Fills(ds, "tblInventoryDetails1")

TextBox5.Text = ds.Tables("tblInventoryDetails1").Rows(0)(0)

TextBox3.Text = ds.Tables("tblInventoryDetails1").Rows(0)(1)

End Sub

Private Sub frmBilling_Load(ByVal sender As System.Object, ByVal e As

System.EventArgs) Handles MyBase.Load

'If

ComboBox1.Items.Clear()

qry = "select Productname from tblInventoryDetails1"

com = New SqlCommand(qry, con)

adp = New SqlDataAdapter(com)

ds = New DataSet

adp.Fill(ds, "tblInventoryDetails1")

i = ds.Tables("tblInventoryDetails1").Rows.Count

Dim j As Integer

For j = 0 To i - 1

ComboBox1.Items.Add(ds.Tables("tblInventoryDetails1").Rows(j)(0))

Next

25

Page 26: SHOPPING CART

'DropDownList1.Text = ""

'TextBox2.Text = "0"

TextBox5.Text = ""

TextBox3.Text = ""

'TextBox4.Text = "0"

'End If

LoadGridViewHeaders()

available = True

End Subs

D.SAMPLE INPUT

26

Page 27: SHOPPING CART

27

Page 28: SHOPPING CART

28

Page 29: SHOPPING CART

29

Page 30: SHOPPING CART

30

Page 31: SHOPPING CART

31

Page 32: SHOPPING CART

E. SAMPLE OUTPUT

32

Page 33: SHOPPING CART

33

Page 34: SHOPPING CART

34

Page 35: SHOPPING CART

35

Page 36: SHOPPING CART

36

Page 37: SHOPPING CART

37

Page 38: SHOPPING CART

38