Online Shopping System

09CSA10

Online ShoppingSystem

CONTENTS

Phase 1 Project Analysis and Planning

1.1. Study of the Problem

1.2. Project Scope

1.3. Objectives

Phase 2 Cost Estimation

Phase 3 Modeling the Requirements

3.1. Module Description

3.1.1. Login

3.1.2. Product Details

3.1.3. Add New

Products 3.1.4.

Updating The Quantity 3.2.

UML Diagram

3.2.1. Use case Diagram

3.2.2. Class Diagram

3.2.3. Sequence Diagram

3.2.4. Collaboration Diagram

Phase 4 Configuration Management

4.1. S/W Requirements

4.2. H/W Requirements

4.3. Tools

09CSA10

4.4. Software Development

4.4.1. Form Creation

4.4.2. Script

Phase 5 Software Testing

5.1. Preparing Test Plan

5.2. Perform Validation Testing

5.3. Validation Test Criteria

5.4. Coverage Analysis

5.5. Memory Leaks

Synopsis

This is a small scale project for Online

shopping system.The basic idea is that customer’s

can buy products using online. It consists of

product details, security system, status and

exits. The administrator can enter the name and

password and generate the report and can perform

operations like add , search, delete the products

in the database.

The Online Shopping system enables vendors to

set up online shops, customers to browse through

the shops, and a system administrator to approve

09CSA10

and reject requests for new shops and maintain

lists of shop categories.Also on the agenda is

designing an online shopping site to manage the

items in the shop and also help customers

purchase them online without having to visit the

shop physically.Our online shopping mall will use

the internet as the sole method for selling goods

to its consumers. Shopping will be highly

personalized and the mall will provide lower

prices than most competitors.

09CSA10

Phase 1 Project Analysis and Planning1.1.Study of the Problem

The Current shopping System is critical to set up

online shops, customers to browse through the shops, and

a system administrator to approve and reject requests for

new shops and maintain lists of shop categories. This is

a small scale project for Online shopping System. The

basic idea is that the candidates can buy product from

anywhere during any time by using their card number and

password provided to them. The database will maintain

the product details information. Customer can view their

product details using the card details. This Online

shopping system involves with two types of users.

CUSTOMER

ADMINISTRATOR

CUSTOMER ROLE:The customer’s can login/logout the System. He/She

can view his/her product details and buy their product.

The customer can just view the information whereas he/she

could not make changes in the database.

ADMINISTRATOR ROLE:

The administrator plays a vital role in the Online

shopping system. The administrator controls the entire

database. The report of the product is generated by the

administrator itself. The main role of the administrator

09CSA10

is to safeguard the database and can add/delete the

products from the database.

1.2.Project ScopeThe supplementary specification applies to

online shopping system. This specification defines the

non-functional requirement of the system such as:

Functionality:

Since it stand alone application, one or more user

may use it at a time.

Usability:

Desktop interface

Windows 98/2000/XP/7

Reliability:

The system is available during online time only .

Performance:

The performance depends on hardware specification

1.3.ObjectivesThe purpose of this document is to define the

requirements of Online shopping system. This

supplementary specification lists the requirements that

are not readily captured in the use case model.

Supplementary specification and the use case model

capture a complete set of requirement of the system.

Phase 2 Cost Estimation

09CSA10

An estimate is a prediction based upon probabilistic

assessment. It is the responsibility of the project

manager to make accurate estimations of effort and cost.

This is particularly true for projects subject to

competitive bidding where a bid too high compared with

competitors would result in loosing the contract or a bid

too low could result in a loss to the organization. This

does not mean that internal projects are unimportant.

From a project leaders estimate the management often

decide whether to proceed with the project. Industry has

a need for accurate estimates of effort and size at a

very early stage in a project. However, when software

cost estimates are done early in the software development

process the estimate can be based on wrong or incomplete

requirements. A software cost estimate process is the set

of techniques and procedures that organizations use to

arrive at an estimate. An important aspect of software

projects is to know the cost. The major contributing

factor is effort.

Why SCE is difficult and error prone ?

Software cost estimation requires a significant

amount of effort to perform it correctly.

SCE is often done hurriedly, without an appreciation

for the effort required.

You need experience at developing estimates,

especially for large projects.

09CSA10

Human bias i.e. An Estimator is likely to consider

how long a certain portion of the system would take,

and then to merely extrapolate this estimate to the

rest of the system, ignoring the non-linear aspects of

software development.

The causes of poor and inaccurate estimation

New software projects are nearly always different

form the last.

Software practitioners don't collect enough

information about past projects.

Estimates are forced to match the resources

available.

2.1. Cost and PricingOur project is of high range and is highly efficient

which can satisfy the shopping calculation for almost all

software companies. The chances of error occurrence is

very limited and so our costs around Rs 10, 00,000(app).

A team of 11 members is required for completing the

task.

It takes a time span of 3 weeks to shape the

project.

There are no specific environmental constraints.

Phase 3 Modeling the Requirements

3.1.Module Description3.1.1. Login

09CSA10

It is the login session for the Administrator,

customer and Exit.

3.1.2. Product Details

It is used to view the product details from the

database.

3.1.3. Add New Products

It is used to add a product into the database and it

includes searching a product details and removing a

product from database.

3.1.4. Updating The Quantity

It is used to update the product details from the

database.

3.2.UML Diagram

3.2.1. Use case Diagram

Use Case diagrams show the various activities the

users can perform on the system. The System is something

that performs a function. They model the dynamic aspects

of the system. It provides a user’s perspective of the

system.

09CSA10

Actor:

An actor is a user of the system playing a particular

role.

Use case:

Use case is a particular activity a user can do on

the system.

Relationship:

Relationships are simply illustrated with a line

connecting actors to use cases.

adm in login

custom er

add item

item s displayed purchase

3.2.2.Class Diagram

A class diagram describes the types of objects in

the system and the various kinds of static relationships

that exist among them.i.e.,A graphical representation of

a static view on declarative static elements. A class is

the description of a set of objects having similar

attributes, operations, relationships and behavior.

09CSA10

adm inisnam e : variant newage : variantcity : variant new

add item s()

customnam e : variant newage : variantaddress : variant newcity : variant new

view()

purchaseitem nam e : variant newitm no : variantquantity : variantcost per item : varianttotal cost : variant

view()

loginuser nam e : variant newpassword : variant new

add item s()

item s to displaynam e : variant newitm no : variantm anuf date : variantexp date : variant

purchase()

add itemitem nam e : variant newitem no : variantquantity : variant

view()

3.2.3. Sequence Diagram

A sequence diagram in Unified Modeling Language

(UML) is a kind of interaction diagram that shows how

processes operate with one another and in what order. It

is a construct of a Message Sequence Chart. Sequence

diagrams are sometimes called event diagrams, event

scenarios, and timing diagrams.

adm inistrator custom er add item view item purchase

adding the item

viewing the item to purchase

purchasing

updating the item s to custom er

purchasing again

3.2.4.Collaboration Diagram

09CSA10

A Collaboration diagram is very similar to a

Sequence diagram in the purpose it achieves; in other

words, it shows the dynamic interaction of the objects in

a system. A distinguishing feature of a Collaboration

diagram is that it shows the objects and their

association with other objects in the system apart from

how they interact with each other. The association

between objects is not represented in a Sequence diagram.

A Collaboration diagram is easily represented by modeling

objects in a system and representing the associations

between the objects as links. The interaction between the

objects is denoted by arrows. To identify the sequence of

invocation of these objects, a number is placed next to

each of these arrows.

adm inistrator

custom er

add item

view item purchase

5: purchasing again

1: add the item

2: viewing the item to purchase

3: purchasing

4: updating the item s to custom er

Phase 4 Configuration ManagementConfiguration management is also used in software

development, where it is called Unified Configuration

09CSA10

Management (UCM). Using UCM, developers can keep track of

the source code, documentation, problems, changes

requested, and changes made. An advantage of a

configuration management application is that the entire

collection of systems can be reviewed to make sure any

changes made to one system do not adversely affect any of

the other systems

4.1.S/W RequirementsOS: Windows

Language: Visual Basic

4.2.H/W RequirementsIntel PII Processor with 300 MHz speed.

64 MB RAM

10MB Hard disk space

4.3.ToolsDesign Tool: Rational Rose suite

4.4.Software Development4.4.1. Form Creation

Form1:

09CSA10

Form2:

Form3:

09CSA10

Form4:

Form5:

09CSA10

Form6:

09CSA10

4.4.2. Script

Coding for form1 (MENU):

Private Sub Command1_Click()Form2.ShowEnd Sub


Coding for form2 (CUSTOMER PURCHASE):

Dim db As DatabaseDim rs As Recordset

Private Sub Command1_Click()Text7.Text = Text5.TextEnd Sub

Private Sub Command2_Click()If (Text6.Text = "") ThenMsgBox "ENTER THE QUANTITY"ElseText5.Text = (Val(Text5.Text) - Val(Text6.Text))Data1.Recordset.EditData1.Recordset.UpdateText7.Text = (Val(Text4.Text) * Val(Text6.Text))MsgBox "TRANSACTION SUCEESSFUL.. PAY TO DEALER"End IfEnd Sub

Private Sub Command3_Click()rs.MoveFirstText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End Sub

Private Sub Command4_Click()

09CSA10

rs.MovePreviousText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End Sub

Private Sub Command5_Click()rs.MoveNextText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End Sub

Private Sub Command6_Click()rs.MoveLastText1.Text = rs(0)Text2.Text = rs(1)Text3.Text = rs(2)Text4.Text = rs(3)Text5.Text = rs(4)End Sub

Private Sub Form_Load()Set db = OpenDatabase("Z:\BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")Text1.Text = " "Text2.Text = " "Text3.Text = " "Text4.Text = " "Text5.Text = " "Text6.Text = " "End SubPrivate Sub LO_Click()Form1.ShowEnd Sub

Coding for form3 (ADMINISTRATOR LOGIN):

09CSA10

Private Sub Command1_Click()If Text1.Text = "bhuva" And Text2.Text = "123" ThenMe.HideText1.Text = ""Text2.Text = ""Form4.Visible = TrueElseMsgBox "invalid username and password"Text1.Text = ""Text2.Text = ""Text1.SetFocusEnd IfEnd SubPrivate Sub Command2_Click()EndEnd Sub

Coding for form4 (ADMIN CHECK):




Coding for form5 (ADD PRODUCTS):Dim db As DatabaseDim rs As RecordsetPrivate Sub Command1_Click()Data1.Recordset.AddNew

End Sub

Private Sub Command2_Click()

09CSA10

Text1.Text = ""Text2.Text = ""Text3.Text = ""Text4.Text = ""Text5.Text = ""End Sub


Private Sub Form_Load()Set db = OpenDatabase("Z:\BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")End SubPrivate Sub Label1_Click()EndEnd Sub

Coding for form6 (UPDATION OF PRODUCTS):

Dim db As DatabaseDim rs As Recordset

Private Sub Combo1_Change()End SubPrivate Sub Command1_Click()If Combo1.List(0) = "NN" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))Data1.Recordset.EditData1.Recordset.UpdateElseIf Combo1.List(0) = "HAMAM" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))Data1.Recordset.EditData1.Recordset.UpdateElseIf Combo1.List(0) = "MYSORESANDLE" ThenText2.Text = rs(4)Text1.Text = (Val(Text2.Text) + Val(Text1.Text))

09CSA10

Data1.Recordset.EditData1.Recordset.UpdateEnd IfEnd Sub

Private Sub Form_Load()Combo1.AddItem "NN"Combo1.AddItem "HAMAM"Combo1.AddItem "MYSORESANDLE"Set db = OpenDatabase("Z:\BIG SHOP.MDB")Set rs = db.OpenRecordset("SHOP")End Sub

Private Sub Label1_Click()EndEnd Sub

Phase 5 Software Testing5.1. Preparing Test Plan

Preparing test plan is the first step in the last

phase of software development cycle .The test plan

consists of all the activities that had to be done in the

software testing phase. This test plan has been

documented using the rational test manager software.

5.2. Perform Validation Testing

Software is completely assembled as a package

interfacing errors have been uncovered and a final series

of software test validation testing may begin. Validation

successive when the customer is satisfied.

5.3. Validation Test Criteria

Software validation is achieved through a series of

black box test that demonstrates conformity with

requirements.

09CSA10

5.4. Coverage Analysis

Coverage analysis is used to identify untested code.

Using rational pure coverage, untested code can easily be

identified.

5.5. Memory Leaks

Memory leak testing has been done using rational

purity software.

Result: Based on the system requirements specification

ONLINE SHOPPING INFORMATION SYSTEM has been designed and

implemented

09CSA10

Online Shopping System

Documents

Transcript of Online Shopping System