09CSA10

Online Shopping System

CONTENTS
Phase 1 Project Analysis and Planning 1.1. 1.2. 1.3. Phase 2 Phase 3 Study of the Problem Project Scope Objectives

Cost Estimation 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. 4.2. 4.3. 4.4. S/W Requirements H/W Requirements Tools Software Development 4.4.1. Form Creation 4.4.2. Script

Phase 5

Software Testing 5.1. 5.2. 5.3. 5.4. 5.5. Preparing Test Plan Perform Validation Testing Validation Test Criteria Coverage Analysis Memory Leaks

09CSA10

Synopsis
This is a small scale project for Online shopping system.The basic idea is that customers 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 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 Planning

1.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 customers 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 is to safeguard the database and can add/delete the products from the database.

1.2.

Project Scope
The 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

09CSA10 Reliability:
The system is available during online time only .

Performance:
The performance depends on hardware specification

1.3.

Objectives
The 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

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

09CSA10

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 Pricing

Our 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 Description
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.1.1. Login

09CSA10

3.2.

UML Diagram
Use Case diagrams show the various activities the users can perform on the

3.2.1. Use case Diagram system. The System is something that performs a function. They model the dynamic aspects of the system. It provides a users perspective of the system.

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.

customer

items di splayed

purchase

admin

login

add item

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
ite m s to d is p la y n a m e : va ria n t n e w itm no : va ria n t m a n u f d a te : va ria n t e xp d a te : va ria n t p u rch a s e ()

cu s to m n a m e : va ria n t n e w a g e : va ria n t a d d re s s : va ria n t n e w city : va ria n t n e w vie w ()

p u rch a s e ite m n a m e : va ria n t ne w itm no : va ria n t q u a n tity : va ria n t co s t p e r ite m : va rian t to ta l co s t : va ria n t vie w ()

a d m inis n a m e : va ria nt n e w a g e : va ria n t city : va ria n t n e w a d d ite m s ()

lo g in u s e r na m e : va ria n t n e w p a s s w o rd : va rian t n e w a d d ite m s ()

a d d ite m ite m n a m e : va ria n t ne w ite m n o : va ria n t q u a n tity : va ria n t vie w ()

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 inis trato r cus tom er add item view item purch as e

add ing the ite m view ing the ite m to purch as e

p urcha s ing

up dating th e item s to cus tom er

p urcha s ing again

3.2.4. Collaboration Diagram

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

09CSA10
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.

a d m in is tra t or

1 : a d d th e ite m

a d d ite m

c u s to m e r

5 : p u rc h a s in g a g a in 2 : vie w in g th e ite m to p u rch a s e 3 : p u rc h a s in g vie w ite m p u rch a s e 4 : u p d a tin g th e ite m s to cu s to m e r

Phase 4 Configuration Management

Configuration management is also used in software development, where it is called Unified Configuration 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 Requirements
OS: Windows Language: Visual Basic

4.2.

H/W Requirements
Intel PII Processor with 300 MHz speed. 64 MB RAM 10MB Hard disk space

09CSA10 4.3. 4.4. Tools

Design Tool: Rational Rose suite

Software Development

4.4.1. Form Creation Form1:

Form2:

09CSA10

Form3:

Form4:

09CSA10
Form5:

Form6:

09CSA10
4.4.2. Script Coding for form1 (MENU): Private Sub Command1_Click() Form2.Show End Sub Private Sub Command2_Click() Form3.Show End Sub Coding for form2 (CUSTOMER PURCHASE): Dim db As Database Dim rs As Recordset Private Sub Command1_Click() Text7.Text = Text5.Text End Sub Private Sub Command2_Click() If (Text6.Text = "") Then MsgBox "ENTER THE QUANTITY" Else Text5.Text = (Val(Text5.Text) - Val(Text6.Text)) Data1.Recordset.Edit Data1.Recordset.Update Text7.Text = (Val(Text4.Text) * Val(Text6.Text)) MsgBox "TRANSACTION SUCEESSFUL.. PAY TO DEALER" End If End Sub Private Sub Command3_Click() rs.MoveFirst Text1.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() rs.MovePrevious Text1.Text = rs(0) Text2.Text = rs(1) Text3.Text = rs(2) Text4.Text = rs(3) Text5.Text = rs(4) End Sub

09CSA10
Private Sub Command5_Click() rs.MoveNext Text1.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.MoveLast Text1.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 Sub Private Sub LO_Click() Form1.Show End Sub Coding for form3 (ADMINISTRATOR LOGIN): Private Sub Command1_Click() If Text1.Text = "bhuva" And Text2.Text = "123" Then Me.Hide Text1.Text = "" Text2.Text = "" Form4.Visible = True Else MsgBox "invalid username and password" Text1.Text = "" Text2.Text = "" Text1.SetFocus End If End Sub Private Sub Command2_Click() End End Sub

09CSA10

Coding for form4 (ADMIN CHECK): Private Sub Command1_Click() Form5.Show End Sub Private Sub Command2_Click() Form1.Show End Sub Private Sub Command4_Click() Form6.Show End Sub Coding for form5 (ADD PRODUCTS): Dim db As Database Dim rs As Recordset Private Sub Command1_Click() Data1.Recordset.AddNew End Sub Private Sub Command2_Click() Text1.Text = "" Text2.Text = "" Text3.Text = "" Text4.Text = "" Text5.Text = "" End Sub Private Sub Command3_Click() Form2.Show End Sub Private Sub Form_Load() Set db = OpenDatabase("Z:\BIG SHOP.MDB") Set rs = db.OpenRecordset("SHOP") End Sub Private Sub Label1_Click() End End Sub Coding for form6 (UPDATION OF PRODUCTS): Dim db As Database Dim rs As Recordset

09CSA10
Private Sub Combo1_Change() End Sub Private Sub Command1_Click() If Combo1.List(0) = "NN" Then Text2.Text = rs(4) Text1.Text = (Val(Text2.Text) + Val(Text1.Text)) Data1.Recordset.Edit Data1.Recordset.Update Else If Combo1.List(0) = "HAMAM" Then Text2.Text = rs(4) Text1.Text = (Val(Text2.Text) + Val(Text1.Text)) Data1.Recordset.Edit Data1.Recordset.Update Else If Combo1.List(0) = "MYSORESANDLE" Then Text2.Text = rs(4) Text1.Text = (Val(Text2.Text) + Val(Text1.Text)) Data1.Recordset.Edit Data1.Recordset.Update End If End 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() End End Sub

Phase 5 Software Testing

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

09CSA10

5.3.

Validation Test Criteria Software validation is achieved through a series of black box test that

demonstrates conformity with requirements. 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.