Online MusicCD Store

MSE Project Presentation II

Presented by: Reshma Sawant

Major Professor: Dr. Daniel Andresen

Phase II Presentation Outline

Action Items from Phase I

Architecture Design

Formal Requirement Specification

Formal Inspection Checklist

Test Plan

Questions

Action Items from Phase I

1) Additions to Vision Document

Description of “Pagination” feature on

Product.aspx Web Page

Specify Browser requirements – IE or Mozilla

Firefox

More flexibility when searching a Music CD

Search by AlbumName, Artist, Style, Price

range

Action Items from Phase I

2) Goals for Performance Testing (Test Plan)

Tests to be performed

Different environments for testing

Expected load (number of concurrent users

and requests)

Additional Functionality

1) “Song Recommendation” feature for

User Actor

Based on Purchase History of past Users

Order details of each product will be saved in

order table

Song Recommendation

Based on Purchase History

Additional Functionality

1) “Song Recommendation” feature for Customer

Actor

Based on data gathered from other users with

similar preferences

Data Mining Technique called Case-Based Reasoning

Process

Retrieve

Reuse

Revise

Retain

Song RecommendationBased on similar preferences of other users

Additional Functionality

2) “Manage Orders” functionality for

Administrator

View User Order History

Update Order status to completed, uncompleted,

verified, unverified

Delete Orders having status uncompleted and

unverified

Architecture Design

The architecture design of the system is based on a three-tier architecture which consists of three logical tiers: Presentation Business (Middle) Data

Domain Model

ASP.NET Forms and Classes Used

ASP.NET Web Forms Classes Used

Default.aspx N.A.

Register.aspx User, SessionManager

Login.aspx User, SessionManager

CustomerDetails.aspx Customer, User

Catalog.aspx SessionManager, Genre

Product.aspx Product, Genre

Recommendation.aspx Product. productSet, RecommendationSet

Search.aspx Product, searchFacade, keyword, productSet

ShoppingCart.aspx ShoppingCart, CartItem, Product

Checkout.aspx ShoppingCart, Product

OrderPlaced.aspx Customer, Order

Index.aspx N.A.

CatalogAdmin.aspx Administrator, Genre, Product

OrdersAdmin.aspx Administrator, Order

Architecture DesignPage Flow Diagram for User

Login.aspx

Default.aspx

Search.aspx

Catalog.aspx

Product.aspx

ShoppingCart.aspx

Checkout.aspx

OrderPlaced.aspx

Logout.aspx

Recommendation.aspx

Architecture DesignPage Flow Diagram for Administrator

Login.aspx

Index.aspx

CatalogAdmin.aspx

OrdersAdmin.aspx

ShoppingCartAdmin.aspx

Logout.aspx

Formal Requirement Specification

Constraints The UserId for each user must be unique Products are not shared across Genres Price of the product should be positive Each Shopping Cart belongs to exactly one

user Shopping Cart exists only when it contains a

cart item Each Order belongs to exactly one user Each Order must have a status as completed,

uncompleted, verified, unverified.

The symbols used in Class diagrams conform to UML

standards.

The classes in the Class diagram have a corresponding

description provided in Architecture Design Document

Classes in the Architecture Design correspond to the

classes in USE Model

Inspection Checklist

Inspection Checklist The multiplicities in the USE Model are reflected

in Class diagram

The attributes in the USE Model are compatible

with attributes of the corresponding class

diagram

All the requirements on Software Requirement

Specification have been covered in Architecture

Design document

Sequence Diagram matches Class diagram

Test Plan

Unit Testing using NUNIT tool

Performance Testing using JMeter tool

Test Plan – Sample UNIT Test Case

Purpose: Test that clicking Update Quantities will update the cart

summary accordingly.

Incorrect Input: Negative input number or input other than integer number,

input number greater than ‘max’ count specified in

“Quantity” field

Pass criteria: An appropriate message should be displayed and information

should not be updated in Shopping Cart.

Correct Input: Positive integer number. within the max count specified.

Pass criteria: The product quantity should be updated or deleted according

to the specified input number.

Steps:1. Visit ShoppingCart.aspx Web page2. Check after entering incorrect input, an appropriate

message should be displayed.3. If entered a valid number, check if the total quantity and

relative price is updated after clicking update or delete button.

Edit shopping Cart

Test Plan – UNIT Test Cases

Test Cases

USER System Register

System Login

Add to Cart

Edit Shopping Cart

Place Order

ADMINISTRATOR System Login

Delete Product from a Genre

Delete Genre from the Catalog

Manage Orders

Manage Shopping Carts

1) Tool to be used - JMETER

2) System components to test:

Buying: Includes browsing, add to cart,

enter personal details and checkout

Searching

Getting song recommendations

Performance Testing

Performance Testing

3) What to measure:

Response time for each component

Eg. approx. 100 concurrent users and

minimum 50 requests/user

Local Connection of 54Mbps

LAN Connection of 100Mbps

Wired connection

Questions?