Onlineshoping

Online Shopping mall system
Table of contents
Contents
CERTIFICATE........................................................................................................... 2
ACKNOWLEDGEMENT............................................................................................ 3
Table of contents................................................................................................... 4
Introduction........................................................................................................... 6
1.1
Assumptions................................................................................................. 7
1.2. System Modelling............................................................................................... 7

1.2.1 System Modelling................................................................................... 8
1.3. Requirement of the system.........................................................................9
1.4. Work Flow of Online Shopping Mall System as per the requirements............9
1.5 Work Flow of System.................................................................................. 11
1.6 Conversion of Requirements into Model.....................................................12
1.6.1 Entities................................................................................................. 12
1.6.2 Events.................................................................................................. 12
1.6.3 Interactions............................................................................................. 12
Chapter 2 - Structure Diagram............................................................................ 14
2.1. Whole System............................................................................................ 14
2.2. Login Module............................................................................................. 14
Chapter 3 - Appropriateness of coding techniques used to implement design....15
Chapter 4 - Appropriateness of the Java concurrent programming facilities used........................18
4.1 Concurrent Programming............................................................................18
4.1.1 Threads................................................................................................ 18
4.1.2. Monitors and Semaphore.....................................................................18
Chapter 5 - Appropriateness of concurrent program design................................21
5.1 Login............................................................................................................. 21
5.2 Buy Product..................................................................................................... 23
5.3 Search product.................................................................................................. 25
5.4 Cancel order.................................................................................................... 27
5.5 Complete system............................................................................................... 28
Chapter 6 Class Diagram.................................................................................. 31
Chapter 7 Evaluation and Testing......................................................................32
7.1 Model Evaluation........................................................................................ 32
Page 1

7.2 Safety Check Results..................................................................................32
7.1 Evaluation of Java Implementation.............................................................33
Chapter 9 Critical Appraisal..............................................................................40
Chapter 10 References...................................................................................... 41
Page 2
Introduction
Online Shopping Mall System is a form of electronic commerce which provides a customer
to check the availability of the products, details of the products, to add/remove the items in
the cart, customer details (sign up), discounts details, placing/cancelling an order, bill
generation, searching the products based on their brand through Internet using a web browser
that is called business-to-consumer (B2C) online shopping.
Online Shopping Mall System are develop to provided customer the facility of buying
products online without wasting time in visiting shops and comparing products. It provides
customer a large variety of products at a chipper rate. Customers get the product delivered at
their doorstep.
The Client side of the Automated Online Shopping Mall System will service one customer at
a time. A customer will be required to login and enter a password for validation. The
customer will then be able to perform one or more actions as mentioned above. A 16 digits
identification number (PIN) will be entered in regards to pay the bill of any purchase made.
An automated Online Shopping Mall System must be able to provide the following services
to the customer:
a. The availability of the products: The Customer can check the availability of a
product.
b. Details of the products: The Customer can check all the details of a product.
c. Add/remove the items in the cart: The Customer can add or remove product in the
cart if he/she want to buy it.
d. Sign up of customer: Customer can sign up by providing his/her details.
e. Discounts details: Customer can see the discount details in a particular transaction.
f. Placing/cancelling an order: Customer can place an order and can cancel a placed
order.
g. Bill generation: Customer can see a final generated Bill.
h. Searching the products based on their brand: Customer can search the products on
the basis of the brands of the product.
Page 3
1.1Assumptions
Developer made certain assumptions on which he lays basis for the development of the
system and made requirement and analysis keeping these assumptions in context:
1. Firstly Customers has Register in online shopping mall through internet web browser,
then they have login online shopping mall website to purchase products.
2. Customers have searched the availability of product and see the price of product.
3. Customers have selected the product and then add products in cart for order the
products.
4. Customers have got online payment for debit/credit card for using 16 digit verification
codes.
5. IF Customers have enter three times wrong 16 digit payment code then they have not
order the product mean there order have been cancel and give the message u can try
again else payment successfully and product order have been done.
1.2.
System Modelling
The Online Shopping mall system needs to be implemented in java by using the principles
and concept of concurrency programming with the help of Threads, Synchronization and
Monitors with adhering to modelling approach. Then it is converted into an executable Java
application. The following diagram will show how the entire system is designed and
developed.
The process includes gathering and analyzing of requirements. These requirements are
modelled into Finite State processes include FSP and LTS representation with proper
implementation of safety and liveness properties. Eventually system is built in Java with
greater use of concurrency features.
Page 4

1.2.1 System Modelling
Requirements
Basic Requirement of Online Shopping mall system

Login/Signup of the Customer
Search the product on the basis of product name and company name.
Book product
Cancel product
Check order
View Price Details
Special Requirement
To make payment from payment code of 16 digit with only 3 retries
To abort connection in any stage of booking
Maintain log to rollback in case of hardware failure
To cancel tickets
Identify the main action event and interaction
Identify and define the main process
Identify and design properties of interest
Structure the process into an architecture
Model
Create Model outline design

Model the system in FSP
Generate LTS
Implement Safety and Leveness
Evaluate and test the traces
Identify the main activities to implemented as thread

Identify the main shared entities to be implemented as monitors
Identify the display interactive environment
Structure the class as class diagram
Java Implementation
Create class diagram

Plan the concurrency part implementation using threads
Design and implement the UI part as applets
Implement the concurrency part using thread
Integrate the system
Evaluate the implement system
Page 5
1.3. Requirement of the system

Online Shopping Mall would be implemented in java by using the concept of concurrency
programming with the help of Threads, Synchronization and Monitors Then it would be
converted into an executable Java application.
To progress in right direction, developer needs to identify the entities, events and interaction
between them to create a Finite State Machine Model. The following section identifies,
categorizes and lists the entities, events and interactions.
S.No
Functionality
Description
1.
Customer
Up)
2.
Product
order/Cancellation
3.
Schedule
Information
4.
Availability of product in To check the number of products available while making order.
store.
5.
Payment
Calculation of the whole fare is performed with help of a unique

16 digit code given to the customer from here he can make
transaction to order the products.
6.
Check Status
Customer can check their order status from their profile if there is
any cancellation in the order.
7.
Log Sheet
A Log sheet is developed to remove any chance of ambiguity in

the system. F there is any database error the data can be
synchronized through the Log file.
Detail(Sign Customer who will use the System, they can be user of system.
A console where customer can see the details of the product and
order the products and also provide the feature of cancelling the
product order.
products It provides the facility of checking the particular product and

offers a choice to the user to choose the product and proceed
forward for the order of product on a particular date.
1.4. Work Flow of Online Shopping Mall System as per the
requirements
The software to be designed is a simulated system for the automated booking of products.
The system Main screen consists with option of Login and Registration.
Page 6

On clicking on registration user need to give their personal information to get a unique id and
password. Then move forward for the signing up as a user from Login Page. On login a
session will be created for the user and user will get a Menu from where he get the option to
select from different menu like
Search products.
Order product.
View product order Status
Cancel order
Log Out
On selecting Search products user can view the availability of the product by the date
from the list of product and proceed toward order of products. In Order of product
user will get the full information of the product and can give the names of the product
and then proceed on the Confirm for order the product to confirm order and make
payment by entering 16 digit code to order the product and finally a display page to
show the order of customer which can be printout from the printer.
On selecting Check order Status from Menu user will get a page which shows the
status of the order.
Cancel order option in menu can be selected to cancel the product order and all the
status of the product of the customer will be changed to be cancelled.
And finally Log Out to destroy the session and return back to the Login Page.
Page 7

1.5 Work Flow of System
Register
customer
Login
(admin/custome
Search product
Cancel product order
View product Available

Book product order Enter order ID
Enter product id and quantityCancel

order
Enter 16 digit code
Make payment
Show order
Page 8
Admin page
Log Out
Add products
Login Page
Update products
1.6 Conversion of Requirements into Model

1.6.1 Entities
Entity
Description
Customer
Customer who will use AOSMS.
Payment
For getting money/amount from the customer after booking of product
product
Product can be enquired, order and cancelled.
Order bill
It will be a proof to customer containing the product and booking order

details
Log
To generate user log maintenance.
1.6.2 Events
Entity
Description
Card Number
AOSMS will ask customer to enter the 16 digit card number
Customer Number
Number of unsuccessful attempts recorded by AOSMS.
Request to enter ID and The machine will request customer to credentials

Password
Putting AOSMS
holding pattern
in Customer can anytime press cancel to hold any type of transaction
Book
To book product order
Enquiry
Enquiry for the product availability as well as status of booked

product order.
Transaction
To represent various kinds of transaction an AOSMS can perform
cancelation
The customer can cancel the booked product order.
1.6.3 Interactions
Number
Customer approaching to AOSMS
1.
AOSMS will be deployed online for accessing from various terminals.
2.
User credentials have been checked for valid users.
3.
For a new user registration facility will be available.
4.
Enquiry for available of product in store.

Page 9
5.
Available product is listed along with details of prices.
6.
Customer is filling the product order details.
7.
Customer is making payment for the booking product orders.
8.
Transaction can be cancelled at anytime.
9.
Account and payment database is updated.
10.
When customer request is put on holding pattern it will be managed by AOSMS

waiting in arrival queue.
11.
AOSMS will communicate each transaction to main database.
12.
Incase customer is requesting for order cancelation, system will prompt an ask for
order ID number.
13.
Finally the product order will be cancelled and database is updated.
14.
And at last the customer will logged out from AOSMS.
15.
A log file of each transaction will be maintained for the Administrative use.
Page 10
Chapter 2 - Structure Diagram

2.1. Whole System
2.2. Login Module
Page 11
Chapter 3 - Appropriateness of
coding
techniques
used
to
implement design
The System is developed using JAVA which is an object oriented language. So Developer has
used appropriate technique required to developed a object oriented system and some common
guidelines to code a system which are discussed as follow i.
Use of Object Principles: System is using OOPs design principle. It is modelled using
appropriate Classes which encapsulate required data and method for their operation and it
is also using interface and inheritance wherever required.
1) Use of Encapsulation (Class and Methods) Proper class and method are used to
encapsulate program. For each task a class is created which contains data members
and methods.
2) Use of Inheritance & Interface Appropriate Inheritance and interface is used to
implement the design. Inheritance by extending JFrame class in action package and
interface is used by Runnable interface.
3) Use of Polymorphism System developed uses adequate amount of polymorphism
concept such as method overloading, overriding etc.
ii.
Use of Design Pattern: Design Pattern provides a common solution to a common

recurring problem for a given context, drawn from proven, prior experience. In this
design Developer has used Singleton pattern.
Page 12

iii.
Memory Utilization: For utilizing less memory the developer has used List and Maps as
it utilizes the memory as required(Dynamically) instead of array that uses fix amount of
memory whether that is usable or not.
iv.
Loosely coupled design: Coupling is the factor of dependency of one class on another
class. The factor of coupling varies between low and high. Systems having high coupling
are unstable and require more effort to modify. High efforts require more cost. High
coupling also decreases the reusability of a class because the dependant class must be
included. Systems having low/loose coupling are stable and when a change is made in
one class, it will not require change in the implementation of other classes.
v.
Use of Comments: Usage of comment is a sign of good programming. It is utmost

important for the maintenance of the system. Commenting the codes in the program
enables the third party to understand the program logic and behaviour.
vi.
Use of Proper Indentation: It is very important to make the code with proper indentation
so that there will not be any problem to read the code properly. It makes the code more
attractive and readable. Implementation uses proper indentation.
Page 13
vii.
Use of Proper Naming Convention: In object any system it is very important to follow
the proper naming conventions to define the classes, objects and methods. It helps to
dangerous chaotic situation which can lead to logical error. Implementation uses proper
naming convention.
Page 14
Chapter 4 - Appropriateness of the Java concurrent programming facilities

used
4.1 Concurrent Programming
A concurrent program has multiple threads to perform multiple computations in parallel at the
same time. It is used increase the performance, throughput, and application responsiveness.
4.1.1 Threads
Concurrencies in Java are achieved by the use of light weight processes called Threads. In
java it can be created in two ways.
To directly control thread creation and management, simply instantiate Thread each
time the application needs to initiate an asynchronous task.
To abstract thread management from the rest of your application, pass the
application's tasks to an executor
In the System, the developer has created threads using the first method. The following is the
code extract of threadThread
public class CCSDassignment
Runnable{
void StartThread(){
new Thread().start();}
public void run(){
Login.setVisible(true);
}
Explanation
implements This is the main class from where the project
starts and this class instantiate the login, so
to maintain multiple logins, the login is
instantiated with the help of Threads.
The idea behind using threads in
login is to allow multiple users to
login into the system at the same
time.
4.1.2. Monitors and Semaphore
For using threads in a concurrent program, resources should be shared for efficient
management and use of resources. But sharing the resources among threads which are
running concurrently may create a deadlock situation if we do not provide proper lock and
release mechanism.
To develop concurrent programmers with all considerations of shared resources, java
provides many other features for safety and for avoiding deadlock. This is mainly
Page 15

accomplished by using monitors in Java. Monitors are passive objects which provide a
controlled access to data in a concurrent environment.
The following is the code extract from the projectCode
Explanation
Method Update Quantity is called only when
the users are booking the product.
Synchronized is used so that only one writer
can enter into the system at a time.
public Boolean Update Product() {

}
If two or more users are booking the product

comes they are allowed to book Product at
the same time with the help of Booking
Product.
Now the developer had to satisfy three criterias which are as follows1. Requires that multiple clients access the server concurrently (i.e. solution should
use concurrent programming)
This condition has achieved by following methodso By allowing multiple users to login, booking & cancel the products at the
same time with the help of threads described in Section 4.1.2. For examplepublic class CCSDassignment implements Runnable{
void callThread(){
new Thread().start();
}
public void run(){
Login.setVisible(true);
}
The above code allows multiple login into the system at a time
2. Has the possibility of more than one client modifying a given resource at one
time (i.e. your solution will need to be able to handle the issue of data
corruption)
This condition has achieved by following methods-
Page 16

synchronized public void UpdateQuantity() This method is called when
two or more users wants to purchase product so the developer is assuming that
they are modifying a given resource at one time so to avoid data corruption the
developer has provided synchronized so that only one user purchase a product.
3. Has the possibility of more than one client requiring locks on more than one
resource at a given time (i.e. your solution will need to be able to handle the issue
of deadlock)
If more than one client wants to purchase the product then they require locks on the
resource means acquiring the lock on product and then booking the product so to
avoid deadlock situation the developer has allowed one by one access by using
synchronized method & as soon as one user purchase the product then notifyAll gets
called to allow other user to purchase the product.
Page 17
Chapter 5 - Appropriateness of concurrent program

design
5.1 Login
5.1.1
Descripti
on
Login is mandatory to enter into the system means performing

different functions like booking, cancelling & view status etc.
5.1.2
Assumpt
ion
The developer is assuming the following assumptions for making this

FSP
5.1.3
FSP
5.1.4
Java
Code
The value of username & password is coming from the database

and previously registered by the user.
loginerror shows the error message to the user.
Only way to reach the homepage is login process
LOGIN = (loginDetails->checklogin->LOGINCHECK|register->LOGIN),
LOGINCHECK
=
(invalid_user->LOGIN|customer_user>CUSTOMERHOME
|admin_user->ADMINHOME),
CUSTOMERHOME = (logout->LOGIN),
ADMINHOME = (logout -> LOGIN).
Input From User
String username = txt_loginID.getText(); //input username from user
String password = txt_password.getText(); //input password from user
Checking if user exists
SQL = SELECT
status='Active';
username,password
FROM
customer
WHERE
//check in the database if given username & password exists

If username & password matches
while(result.next())
{
String tempUserName = result.getString(1);
String tempPassword = result.getString(2);
if(userName.equals(tempUserName)
&&
password.equals(tempPassword))
{
message = tempUserName; /// if login is successfull then username is
returned to maintain the session
Page 18

}
}
If username & password doesnt matches
if(message.equals("invalid"))
{
//wrong login
}
User is being forwarded to home page
else if(message.equals("admin")) //User is being forwarded to home
page
{
// admin home
}
else //User is being forwarded to home page
{
//CustomerHome
}
5.1.5
LTSA
5.1.6
TracesSafety
5.1.7
TracesProgress
Page 19

5.1.8
Traces
5.2 Buy Product

5.2.1
Descripti
on
This module is to buy product from the system. The input required for
this system is product id and quantity
5.2.2
Assumpt
ion

FSP
5.2.3
FSP
5.2.4
Java
Code
User should login into the system. Enter prodict id and quantity.
purchageerror shows the error message to the user.
LOCK = (acquire->release->LOCK).
BUYPRODUCT
=
(search_product->SEARCHPRODUCT|cancel>BUYPRODUCT),
SEARCHPRODUCT
=
(enter_quantity->validate->(acquire>MAKEPAYMENT|cancel->BUYPRODUCT)),
MAKEPAYMENT = (enter_detals->validate->(success->order_place>release->BUYPRODUCT|{failure1,failure2,failure3}->MAKEPAYMENT|
failure4->release->BUYPRODUCT)).
||SHARED_BUY = (BUYPRODUCT||LOCK).
Input From User
String productid = txt_proditId.getText(); //input product Id from user
int quantity = Integer.parseInt(txt_quntity.getText());
from user
//input quantity
Checking if products exists

SQL = SELECT * FROM item WHERE itemid='+ productid +' and
Page 20

quantity>+ quantity +;
5.2.5
LTSA
5.2.6
TracesSafety
5.2.7
TracesProgress
5.2.8
Traces
Page 21

5.3 Search product
5.3.1
Descripti
on
This module is to search product from the system. The input required
for this system is product id.
5.3.2
Assumpt
ion

FSP
5.3.3
FSP
5.3.4
Java
Code
User should login into the system. Enter prodict id.

producterror shows the error message to the user.
SEARCHPRODUCT
=
(bybrand->BRANDFORM|byproduct>PRODUCTFORM),
BRANDFORM
=
(enter_detail->search->SEARCHRESULT|close>SEARCHPRODUCT),
PRODUCTFORM
=
(enter_detail->search->SEARCHRESULT|close>SEARCHPRODUCT),
SEARCHRESULT = (close->SEARCHPRODUCT).
Input From User
String productid = txt_proditId.getText(); //input product Id from user
Checking if product exists

SQL = SELECT * FROM item WHERE itemid='+ productid +';
If username & password matches
If(record)
//purchage Code
If username & password doesnt matches
JOptionPane.showMessageDialog(null, "Sorry No Products Found...!!!",
"ERROR", JOptionPane.ERROR_MESSAGE);
5.3.5
LTSA
Page 22

5.3.6
TracesSafety
5.3.7
TracesProgress
5.3.8
Traces
5.4 Cancel order

5.4.1
Descripti
on
This module is to cancel already ordered product.
5.4.2
Assumpt
ion

FSP
5.4.3
User should login into the system. Enter order id.

cancelerror shows the error message to the user.
User can only cancel those products which he has ordered.
CANCELORDER = (choose_order->validate->Validate),
Page 23

FSP
5.4.4
Java
Code
Validate=(success->acquire->quantity_update->order_canceled>release-> CANCELORDER|failure->CANCELORDER).
||SHARED_Cancel = (CANCELORDER||LOCK).
Input From User
String orderId = txt_orderId.getText(); //input product Id from user
String userid = session.getuserId();// getuserid from session
Checking if order exists
SQL = SELECT * FROM purchase WHERE order='+ orderId +' and
userid=+ userid + and status=placed;
If record matches found
If(record)
//Cancel Order Code
If Order ID doesnt matches
JOptionPane.showMessageDialog(null, "Sorry No such order found
Found...!!!", "ERROR", JOptionPane.ERROR_MESSAGE);
5.4.5
LTSA
5.4.6
TracesSafety
Page 24

5.4.7
TracesProgress
5.4.8
Traces
5.5 Complete system

5.5.1
Descripti
on
This is the working of complete system
5.4.2
Assumpt
ion

FSP
5.4.3
FSP
User should login into the system.

OSM = (login->LOGIN|new_user->REGISTRATION),
LOGIN = (checklogin->LOGINCHECK),
LOGINCHECK
=
(invalid_user->LOGIN|customer_user>CUSTOMERHOME|admin_user->ADMINHOME),
CUSTOMERHOME
=
(search_product->SEACRHPRODUCT|
previous_orders->MYORDERS|logout->OSM),
ADMINHOME
=
(add_product->ADMINHOME|updateQuantity>ADMINHOME|logout->OSM),
Page 25

REGISTRATION = (enter_details->validate->(success->LOGIN|failure>REGISTRATION)),
SEACRHPRODUCT
=
(bybrand->BRANDFORM|byproduct>PRODUCTFORM),
BRANDFORM
=
(enter_detail->search->SEARCHRESULT|close>SEACRHPRODUCT),
PRODUCTFORM
=
(enter_detail->search->SEARCHRESULT|close>SEACRHPRODUCT),
SEARCHRESULT
=
(close->SEACRHPRODUCT|buy_product>BUYPRODUCT),
MYORDERS
=
(choose_order->validate->(success->acquire>quantity_update->order_canceled->release->CUSTOMERHOME|
failure->CUSTOMERHOME)),
BUYPRODUCT
=
(enter_quantity->validate->(success->acquire>MAKEPAYMENT|failure->BUYPRODUCT)|cancel->BUYPRODUCT),
MAKEPAYMENT = (enter_detals->validate->(success->order_place>release->BUYPRODUCT|{failure1,failure2,failure3}->MAKEPAYMENT|
failure4->release->BUYPRODUCT)).
||SHARED_OSM = (OSM||LOCK).
5.5.5
TracesSafety
5.5.6
Traces
Page 26
Chapter 6 Class Diagram
Page 27
Chapter
Testing
Evaluation
and
Testing allows the development team to make sure that they have built the right product by
following a right process. This fact is true for any software model we build. The purpose of
the Model Based Design in concurrent programming is to test and find our errors for all
possible traces. The java application again was tested for the same functionalities as of FSP
model. Although the testing method is different, the goal of the testing is same.
7.1 Model Evaluation

The FSP model was compiled, composed, and checked for any syntax error, functional error
and safety and aliveness property. The compilation of the FSP was successful without any
error and the result is shown in the following table.
7.2 Safety Check Results

No deadlock occurs
Page 28
7.1 Evaluation of Java Implementation

Test Cases-1
Project Name
Online Shopping Mall System
Test ID
AOSMS -01
Testing module Verifying working of AOSMS physical module.
Name of tester
Developer
Description of The module basically deals with physical foundation of AOSMS. It is
Module
dealing with customer console, Login and Registration.
Pre Condition
The AOSMS must be running
No.
Actual Input Expected
Actual
Status
Error
Correction
Result
Result
(Pass/fail)
Measure
1.
In the User The AOMSS Blank User Pass
No Error N.A
Console
should
be ID
and
Index Frame
running and Password
asking for the filed
is
User Id and available to
Password
the user.
from the end
user.
2.
Customer has The
Identical to Pass
No Error N.A
given
the credentials
the expected
login
has
been result
credentials
checked and
matched from
the database if
exist
then
redirected to
the Customer
home page for
online order
products,
enquiry etc.,
else
the
system
will
again ask for
the same by
showing the
message
Invalid User.
1.
Customers
selected the
option for the
first
time
registration
using
the
Register
button
available on
the
Index
page
Registration
Identical to P
page will be the expected
available to result.
the user along
with
the
required field
to fill up the
user details.
No Error
N.A
Test Cases-2
Project Name
Test ID
Testing module
Name of tester
Description of
Module
Pre Condition
No.

AOSMS -02
Customer Availability Check
Developer
The module basically deals with the New user registration.
The AOSMS must be ON
Actual Input
1.
2.
Customer will
enter his/her
desired login
name in the
User
name
field.
Expected
Result
After inserting
the
desired
user name and
upon clicking
on the check
availability
button
the
user
name
availability
should
be
checked and
the message
should
available
to
the user
User
will The entered
enter his/her text should be
contact
in
numeric
number
format
and
will be exactly
composed of
10 digit, if not
then
the
message
should
be
popped to the
user.
Actual Result Status

(Pass/fail)
Error
Correction
Measure
Identical
to Pass
the expected
result
No Error
N.A
Identical
to Pass
the expected
result
No Error
N.A
3.
4.
User
will Entered text
enter his/her should be a
email id
valid email id
in the email id
format after
changing the
text
system
should pop a
message
whether valid
or not
Finally user On clicking
registration
Register
button all the
validation
check should
be done if the
information
provided by
the user will
be valid then
the
registration
should
be
done and the
feedback
should
be
available
to
the user.
Identical
to Pass
the expected
result.
No Error
N.A
Identical
to Pass
the expected
result
No error
N.A
Test Cases-3
Project Name
Test ID
AOSMS -03
Testing module Product online order
Name of tester Developer
Description of The module basically deals with the products availability.
Module
Pre Condition
The AOSMS must be Running
No.
Actual
Status
Error
Correction
Result
Result
(Pass/fail)
Measure
1.
The customer The selecting The
Pass
No Error N.A
selecting the item through available
item.
user is done. product
is
2.
Customer has
submitted the
selected item
to
order
successfully.
selected.
If product is Identical to Pass
available to the expected
the customer result
Then order
products.
No Error N.A
Test Cases-4
Project Name
Test ID
AOSMS -04
Testing module Online product order.
Name of tester
Developer
Description of This module basically deals with product order of the customer.
Module
Pre Condition
No.
Actual
Status
Error
Correction
Result
Result
(Pass/fail)
Measure
1.
The customer A customer Identical to Pass
No Error N.A
has selected has enter her expected
the option of name
for result.
book product order
the
order for the product.
specific item.
2.
The customer The payment Identical to Pass
No Error N.A
has selected form should the expected
the option of be accessible result
payment
to the user
with proper
validation and
critical check
3.
4.
The
card
number for
payment
is
given by the
customer
A
highly
validation
check should
be done and
the
card
number
should be of
exactly
16
digit, numeric
and valid.
Complete
The product
details
has should
be
been given by booked and a
the customer
product
ID
and
order
number
should
be
generated for
the
future
reference .
Identical to Pass
the expected
result.
No Error
N.A
Identical to Pass
the expected
result.
No Error
N.A
Test Cases-5
Project Name
Test ID
AOSMS -05
Testing module Cancel order
Name of tester
Developer
Description of This module basically deals with order cancelation of the customer.
Module
Pre Condition
No.
Actual
Status
Error
Correction
Result
Result
(Pass/fail)
Measure
1.
The customer A form for the Identical to Pass
No Error N.A
has selected cancelation of expected
the option of product along result.
order
with a field
cancelation
asking
for
order
have
been cancel or
not if yes then
order
have
been
canceled.
Chapter 9 Critical Appraisal

The project is implemented successfully and all the functionalities of the system have been
fulfilled. Its interface is developed to facilitate user to order online products and have
something experience while using the simulator. System is free from deadlock and terminal
progress.
This subject Computing and Concurrent System Design is proved to be critical in the real
world application. It can be applied into many information systems. For example, the Stock
Trading System which require appropriate mechanism to update and carry out different
market related transaction and updating s at the same time to solve the deadlock because
database application system can be used in multi user environment where users can read and
update the value at the same time. Without the mechanism from concurrency design, the
application will lead to update anomalies and inconsistency throughout the whole Trading
System.
Concurrent programming encompasses the programming languages and algorithms used to
implement concurrent systems. Concurrent programming is usually considered to be more
general than parallel programming because it can involve arbitrary and dynamic patterns of
communication and interaction, whereas parallel systems generally have a predefined and
well-structured communications pattern. The base goals of concurrent programming include
correctness, performance and robustness.
The developer has learnt various aspect of concurrent programming. The key aspect of this
module is Model Based Design Concept. As part of modelling developer has learnt to prepare
FSP, generate LTS diagram using tool LTSA. Apart from testing the LTSA through traces is
very useful to find the error and deadlocks. Developer also acquired the skills to implement
concurrent systems in Java in a systematic way, requirement -> Model -> Implementation.
Extensive use of threads, monitors and other features helped the developer to learn
concurrent programming in practice.
To be more specific, developer has obtained knowledge in the areas of concurrency,
deadlock, deadlock avoidance, parallel composition of asynchronous processes, interleaving,
structure diagrams, monitors and Conditional Synchronization, Safety & Aliveness
properties.
Chapter 10
References
BOOKS
Fowler, M. and Scott, K., UML Distilled Applying the Standard Object Modelling
Language, 1997, Addison-Wesley.
- Magee, J. And Kramer, J., 2008, Concurrency: State Models & Java Programs, 2nd Edition,
Wiley, J. and Sons.
- D.J.Hatley, I.A. Pirbhai, Strategies for Real-Time System Specification, 1988, Dorset House
N.Y.
-Balagurusamy E, (ed) 2007, Programming with Java A premier, 3rd Edition, TATA McGrawHill, New Delhi.
Bashman B, Sierra K, Bates B, (ed) 2009, Head First Java, 2nd Edition, SPD OReilly, USA.
Herbert Schildt (2002), The Complete Reference Java 2, 5 th Edition, TATA McGraw-Hill,
New Delhi.
WEBSITES
1. http://www.math-cs.gordon.edu/courses/cs211/ATMExample/ClassDiagram.html
Accessed on: 5th May 2013.
2. Lars Vogel. (2011). Java Concurrency / Multithreading - Tutorial. Available:
http://www.vogella.de/articles/JavaConcurrency/article.html. Last accessed 22 April
2013.
3. Corky
Cartwright.
(2007).
What
is
Concurrent
Programming?.
Available:http://www.cs.rice.edu/~cork/book/node96.html. Last accessed 1st May
2013.
4. Bill
Venners.
(2009).
Thread
Synchronization.
Available:
http://www.artima.com/insidejvm/ed2/threadsynch.html. Last accessed 3rd may
2013.
5. Asim Smailagic, Dan Siewiorek. (2000). User-Centered Interdisciplinary Concurrent
System Design., pg-1

Onlineshoping

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Onlineshoping

Uploaded by

Copyright:

Available Formats

Online Shopping mall system

1.2. System Modelling............................................................................................... 7

Online Shopping mall system

Online Shopping mall system

Online Shopping mall system

Online Shopping mall system

Basic Requirement of Online Shopping mall system

Create Model outline design

Identify the main activities to implemented as thread

Create class diagram

Online Shopping mall system

1.3. Requirement of the system

Calculation of the whole fare is performed with help of a unique

A Log sheet is developed to remove any chance of ambiguity in

products It provides the facility of checking the particular product and

1.4. Work Flow of Online Shopping Mall System as per the

Online Shopping mall system

View product order Status

Online Shopping mall system

Cancel product order

View product Available

Enter product id and quantityCancel

Enter 16 digit code

Online Shopping mall system

1.6 Conversion of Requirements into Model

Customer who will use AOSMS.

For getting money/amount from the customer after booking of product

Product can be enquired, order and cancelled.

It will be a proof to customer containing the product and booking order

To generate user log maintenance.

AOSMS will ask customer to enter the 16 digit card number

Number of unsuccessful attempts recorded by AOSMS.

Request to enter ID and The machine will request customer to credentials

in Customer can anytime press cancel to hold any type of transaction

To book product order

Enquiry for the product availability as well as status of booked

To represent various kinds of transaction an AOSMS can perform

The customer can cancel the booked product order.

Customer approaching to AOSMS

AOSMS will be deployed online for accessing from various terminals.

User credentials have been checked for valid users.

For a new user registration facility will be available.

Enquiry for available of product in store.

Online Shopping mall system

Available product is listed along with details of prices.

Customer is filling the product order details.

Customer is making payment for the booking product orders.

Transaction can be cancelled at anytime.

Account and payment database is updated.

When customer request is put on holding pattern it will be managed by AOSMS

AOSMS will communicate each transaction to main database.

Finally the product order will be cancelled and database is updated.

And at last the customer will logged out from AOSMS.

Online Shopping mall system

Chapter 2 - Structure Diagram

2.2. Login Module

Online Shopping mall system

Use of Design Pattern: Design Pattern provides a common solution to a common

Online Shopping mall system

Use of Comments: Usage of comment is a sign of good programming. It is utmost

Online Shopping mall system

Online Shopping mall system

Chapter 4 - Appropriateness of the Java concurrent programming facilities