Professional Documents
Culture Documents
1.2.
Project Scope
1.3.
Objectives
Phase 2
Cost Estimation
Phase 3
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
4.4.
Software Development
4.4.1. Form Creation
4.4.2. Script
Phase 5
Software Testing
5.1.
5.2.
5.3.
5.4.
Coverage Analysis
5.5.
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
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.
SCE is often done hurriedly, without an appreciation for the effort required.
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
New software projects are nearly always different form the last.
Module Description
3.1.1. Login
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.
09CSA10
3.2.
UML Diagram
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
admin
items di splayed
login
purchase
add item
09CSA10
custom
items to display
view()
purchase()
purchase
item name : variant new
itm no : variant
quantity : variant
cost per item : variant
total cost : variant
view()
adminis
add item
login
add items()
add items()
customer
add item
view item
purchase
purchasing
purchasing again
09CSA10
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.
administrat
or
add item
customer
5: purchasing again
2: viewing the item to purchase
3: purchasing
view item
purchase
4: updating the items to customer
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.
Tools
Design Tool: Rational Rose suite
4.4.
Software Development
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
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
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.
uncovered and a final series of software test validation testing may begin. Validation
successive when the customer is satisfied.
09CSA10
5.3.
Coverage Analysis
Coverage analysis is used to identify untested code. Using rational pure
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.