Online Music Platform, Study Guides, Projects, Research of Computer Science

Online Music Platform sdgfsegfsesefsgrgrgresgrgrg

Typology: Study Guides, Projects, Research

2019/2020

Uploaded on 11/30/2020

Nonameeeeeee
Nonameeeeeee 🇺🇸

1 document

1 / 169

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
1
E-COMMERCE ONLINE MUSIC STORE
by
RESHMA D SAWANT
Bachelor of Engineering (B.E), Vidyavardhini’s CoE, University of Mumbai,
Mumbai, INDIA. 2004
A REPORT
submitted in partial fulfillment of the requirements
for the degree of
MASTER OF SOFTWARE ENGINEERING
Department of Computing and Information Sciences
College of Engineering
KANSAS STATE UNIVERSITY
Manhattan, Kansas
2008
Approved by:
Dr. Daniel Andresen
[Major Professor]
pf3
pf4
pf5
pf8
pf9
pfa
pfd
pfe
pff
pf12
pf13
pf14
pf15
pf16
pf17
pf18
pf19
pf1a
pf1b
pf1c
pf1d
pf1e
pf1f
pf20
pf21
pf22
pf23
pf24
pf25
pf26
pf27
pf28
pf29
pf2a
pf2b
pf2c
pf2d
pf2e
pf2f
pf30
pf31
pf32
pf33
pf34
pf35
pf36
pf37
pf38
pf39
pf3a
pf3b
pf3c
pf3d
pf3e
pf3f
pf40
pf41
pf42
pf43
pf44
pf45
pf46
pf47
pf48
pf49
pf4a
pf4b
pf4c
pf4d
pf4e
pf4f
pf50
pf51
pf52
pf53
pf54
pf55
pf56
pf57
pf58
pf59
pf5a
pf5b
pf5c
pf5d
pf5e
pf5f
pf60
pf61
pf62
pf63
pf64

Partial preview of the text

Download Online Music Platform and more Study Guides, Projects, Research Computer Science in PDF only on Docsity!

E-COMMERCE ONLINE MUSIC STORE

by

RESHMA D SAWANT

Bachelor of Engineering (B.E), Vidyavardhini’s CoE, University of Mumbai,

Mumbai, INDIA. 2004

A REPORT

submitted in partial fulfillment of the requirements for the degree of

MASTER OF SOFTWARE ENGINEERING

Department of Computing and Information Sciences College of Engineering

KANSAS STATE UNIVERSITY

Manhattan, Kansas

2008

Approved by:

Dr. Daniel Andresen [Major Professor]

ABSTRACT

The objective of this project is to design a Music store web application with user

interface which will enable them to browse, search, get song recommendations and buy the song-

items of their choice. The motivation of this project comes from my desire to learn the

increasingly growing field of .NET, SQL server database designing, website designing and their

growing popularity by taking up this case study.

The word “design” in the context of a Web Application can mean many things. Its most

popular usage probably refers to the visual and user interface (UI) design of a web site. This

aspect is crucial because, the visitor is often more impressed with how a website looks and how

easy it is to use than about which technologies and techniques are used behind the scenes, or

what operating system the web server is running. If the site is hard to use and easy to forget, it

just doesn’t matter what technologies was used to create it. Unfortunately, this truth makes many

inexperienced programmers underestimate the importance of the way the invisible part of the site

is implemented—the code, the database, and so on. The visual part of a site gets visitors

interested to begin with, but its functionality makes them come back. A web site can sometimes

be implemented very quickly based on certain initial requirements, but if not properly

architected, it can become difficult, if not impossible, to change.

Thus, performance is also a major thrust area in the Web application which is one of the

main reasons why users get attracted to it. Growing user needs should be taken in to concern

with new features to be included. Effective performance can be achieved by making proper

database design strategy. Also, easy navigation also needs to be accomplished while executing

this project.

  • Chapter 1 – Vision Document
      1. Introduction
      1. Project Overview
      • 2.1 Introduction
      • 2.2 Goal
      • 2.3 Purpose
      1. Requirements Specification......................................................................................
      • 3.1 Main Requirements
      • 3.2 External Interfaces Requirements
      • 3.3 Critical Use Case Requirements
      • 3.4 Performance Requirements
      • 3.5 Assumptions
      • 3.6 Constraints.....................................................................................................
      • 3.7 Environment
  • Chapter 2 – Project Plan
      1. Task Breakdown
      • 1.1 Inception Phase
      • 1.2 Elaboration Phase
      • 1.3 Production Phase
      1. Architecture Elaboration Plan
      • 2.1 Revision of Vision Document
      • 2.2 Revision of Project Plan
      • 2.3 Formal Requirements Specification
      • 2.4 Architecture Design.......................................................................................
      • 2.5 Test Plan
      • 2.6 Formal Technical Inspections
      • 2.7 Architecture Prototype
      1. Cost Estimate............................................................................................................
      1. Implementation Plan
      • 4.1 Deliverables
      • 4.2 Work Breakdown Structure...........................................................................
  • Chapter 3 – Architecture Design
      1. Introduction
      1. Architecture of the System
      • 2.1 Presentation Tier
      • 2.2 Business-Tier.................................................................................................
      • 2.3 Data Tier (Database)
      1. Formal Specification
  • Chapter 4 – Inspection List
      1. Purpose
      1. Items to be Inspected
      1. Formal Technical Inspectors
      1. Formal Technical Inspection Checklist
  • Chapter 5 – Component Design
      1. Introduction
      1. Class Description and Diagrams
  • Chapter 6 – Software Quality Assurance Plan
      1. Purpose
      1. Reference Documents
      1. Management
        • 3.1 Organization
        • 3.2 Responsibilities
        • 3.3 Tasks..............................................................................................................
      1. Documentation
      1. Standards, Practices, Conventions, and Metrics
      1. Reviews and Audits
      1. Test and Problem Reporting.....................................................................................
      1. Tools, Techniques, and Methodologies....................................................................
      1. Records collection, Maintenance, and Retention
      1. Deliverables
  • Chapter 7 – Test Plan
      1. Introduction
      1. Test Features
      1. Test cases for User Requirements
      1. Test Cases for Administrator Requirements……………………………………......
        1. Approach
        • 4.1 Manual Testing
        • 4.2 Performance Testing
      1. Item Pass/Fail Criteria
      1. Suspension Criteria and Resumption Requirements
        • 7.1 Suspension Criteria
        • 7.2 Resumption Requirement
      1. Test Deliverables
      1. Environmental Needs
        • 9.1 Hardware
        • 9.2 Software
        • 9.3 Operating System
  • Chapter 8 – Assessment Evaluation
      1. Introduction
      1. Test Case Result Summary
      1. Detailed Test Results
        • 3.1 Manual Testing
        • 3.2 Performance Testing
      1. Scalability
  • Chapter 9 – User Manual
      1. Introduction
      1. Installation and Set-up
        • 2.1 Required Hardware
        • 2.2 Required Software
        • 2.3 Required Network Configuration
      • 2.4 Software Set-up
      1. OnlineMusic Store Usage.......................................................................................
      • 3.1 User
      • 3.2 Administrator
  • Chapter 10 – Project Evaluation...................................................................................
      1. Introduction
      1. Problems Encountered............................................................................................
      • 2.1 Solution domain research and learning
      • 2.2 Learning ASP.NET and C # Language
      • 2.3 Security Issues
      1. Source Lines of Code
      1. Project Duration
      1. Lessons Learnt........................................................................................................
  • References
  • Appendix A. Srunokshi Neelakantan’s Formal Inspection Checklist
  • Appendix B. Inspection Letter
      1. Srunokshi Neelakantan’s Inspection Letter............................................................
  • Figure 1 Page Flow Diagram…………………………………………………………….. LIST OF FIGURES
  • Figure 2 Overview of System............................................................................................
  • Figure 3 System in Three-Tier Architecture
  • Figure 4 Use Case Diagram
  • Figure 5 The Project Gantt Chart
  • Figure 6 Three-Tier Architecture Diagram
  • Figure 7 Domain Model Diagram
  • Figure 8 Page Flow Diagram of User
  • Figure 9 Page Flow Diagram of Administrator.................................................................
  • Figure 10 User Class Diagram
  • Figure 11 Customer Class Diagram
  • Figure 12 Administrator Class Diagram
  • Figure 13 SessionManager Class Diagram
  • Figure 14 Genre Class Diagram
  • Figure 15 Product Class Diagram
  • Figure 16 ShoppingCart Class Diagram………………………………………………….
  • Figure 17 CartItem Class Diagram……………………………………………………….
  • Figure 18 Order Class Diagram
  • Figure 19 OrderDetail Class Diagram
  • Figure 20 ShippingInfo Class Diagram
  • Figure 21 keyword Class Diagram………………………………………………….........
  • Figure 22 searchFacade Class Diagram
  • Figure 23 RecommendationSet Class Diagram
  • Figure 24 productSet Class Diagram……………………………......................................
  • Figure 25 System Login Sequence Diagram
  • Figure 26 System Buying Sequence Diagram...................................................................
  • Figure 27 System Search Sequence Diagram
  • Figure 28 Physical Database Schema................................................................................
  • Figure 29 Middle Tier Class Diagram...............................................................................
  • Figure 30 User Class Component Diagram.......................................................................
  • Figure 31 Customer Class Component Diagram...............................................................
  • Figure 32 Administrator Class Component Diagram
  • Figure 33 SessionManager Class Component Diagram
  • Figure 34 Genre Class Component Diagram
  • Figure 35 Product Class Component Diagram
  • Figure 36 ShoppingCart Class Component Diagram……………………………….........
  • Figure 37 CartIten Component Diagram
  • Figure 38 Order Class Component Diagram
  • Figure 39 OrderDetail Class Component Diagram
  • Figure 40 ShippingInfo Class Component Diagram
  • Figure 41 keyword Class Component Diagram
  • Figure 42 searchFacade Class Component Diagram……………………………………..
  • Figure 43 RecommendationSet Class Component Diagram……………………..………
  • Figure 44 productSet Class Component Diagram…………..............................................
  • Figure 69 Breakdown for Each Phase
  • Figure 70 Phase I Breakdown
  • Figure 71 Phase II Breakdown
  • Figure 72 Phase II Breakdown
  • Table 1 The Work Breakdown Structure Table LIST OF TABLES
  • Table 2 Client Site ASP.NET Web Forms
  • Table 3 Administrator Site ASP.NET Web Forms
  • Table 4 Database Table
  • Table 5 Formal Technical Inspection List.........................................................................
  • Table 6 Features to be Tested
  • Table 7 Test Case Result Summary
  • Table 8 Register Test Case Result Summary
  • Table 9 User Login Test Case Result Summary
  • Table 10 Search Test Case Result Summary
  • Table 11 Edit Shopping Cart Test Case Result Summary
  • Table 12 Place Order Test Case Result summary
  • Table 13 Administrator Login Test Case Result Summary
  • Table 14 Create & Delete Product Test Case Result Summary………………………….
  • Table 15 Create & Delete Category Test Case Result Summary………………………...
  • Table 16 Create & Delete Genre Test Case Result Summary…………………………..
  • Table 17 Manage Orders Test Case Result Summary…………………………………..
  • Table 18 Manage Shopping Carts Test Case Result Summary……;;;;..………………..
  • Table 19 Project Duration
  • Table 16 Activities Breakdown in Each Phase

Chapter 1 – Vision Document

  1. Introduction

1.1. Purpose and Motivation

The objective of this project is to implement a Music CD store web application with user interface. The motivation of this project comes from my desire to learn the increasingly growing field of .NET, SQL server database designing, website designing and their growing popularity by taking up this case study. The word “design” in the context of a Web Application can mean many things. Its most popular usage probably refers to the visual and user interface (UI) design of a web site. This aspect is crucial because, the visitor is often more impressed with how a website looks and how easy it is to use than about which technologies and techniques are used behind the scenes, or what operating system the web server is running. If the site is hard to use and easy to forget, it just doesn’t matter what technologies was used to create it. Unfortunately, this truth makes many inexperienced programmers underestimate the importance of the way the invisible part of the site is implemented—the code, the database, and so on. The visual part of a site gets visitors interested to begin with, but its functionality makes them come back. A web site can sometimes be implemented very quickly based on certain initial requirements, but if not properly architected, it can become difficult, if not impossible, to change. Thus, performance is also a major thrust area in the Web application which is one of the main reasons why users get attracted to it. Growing user needs should be taken in to concern with new features to be included. Effective performance can be achieved by making proper Database design strategy. Also, easy navigation also needs to be accomplished while executing this project. These are the main motivations for the project.

  1. Project Overview

2.1. Introduction

This application, called the Music Store is implemented using C# and ASP.NET 2.0.

This project covers the following implementations:

  1. An online product catalog that can be browsed: The work starts with adding many

new product catalog features which includes displaying categories, products, and product details.

  1. Searching the Catalog: For the visual part, a text box is used in which the visitor can

enter one or more words to search through the product catalog. In Music CD Shop, the words entered by the visitor are searched for in the products’ names and descriptions. Also, the user can search for a particular song by entering the title, artist, style, format and the price range.

  1. A Custom Shopping Cart and checkout in ASP.NET: A custom shopping basket is

implemented, which stores its data into the local database. Also a “shopping cart summary control” is created that shows up in every catalog page except the shopping cart page.

  1. Handling Customer Accounts: In customer account system, details such as credit

card numbers are stored in a database so that customers don’t have to retype this information each time they place an order. Customers can log in via a login page or dialog box to get access to secured areas of the web site. Once logged in, the Web Application remembers the customer until the customer logs out (either manually via a Log Out button or automatically, if the session times out or a server error occurs). All secure pages in a Web Application need to check whether a customer is logged in before allowing access.

  1. Making Song Recommendations: One of the most important advantages of an online

store is the capability to customize the web site for each visitor based on his or her preferences, or based on data gathered from other visitors with similar preferences. In product recommendations system, additional products are suggested to an individual visitor in a clever way to increase sales. Here, song (product) will have recommendations based on the users’ past purchases and based on data gathered from other users with similar preferences.

Fig1. Page Flow Diagram

Figure below shows the high-level layout diagram of the system.

Fig2. Overview of System

The said system will interact as follows: a. The client sends request and .NET form inputs over the network. b. The Internet Information Server (IIS) receives .Net form inputs. c. IIS Web server i. Processes inputs ii. If required, queries to the database and retrieves data d. The IIS Web server sends back processed output over the network as a Web page. e. The client receives the output as a Web page.

2.2. Goal

The goal of this project is to provide an automated .NET Web application that allows a user to browse and buy a music CD over the Internet at any time.

2.3. Purpose The purpose of this project is to explore the capabilities of the Microsoft .NET Framework and to provide a convenient service of buying a music CDs to online customers.

  1. Requirement Specifications

3.1. Main Requirements

  1. Construct a system with three-tier architecture. Figure 3 shows the system on three- tier architecture.
  2. Microsoft Visual Studio 2005, ASP.NET, C# language, Microsoft SQL Server 2005 and XML will be used to develop the system.
  3. The final product will be run on Internet Information Server (IIS).
  4. Mozilla Firefox will be used as a main browser.

3.3. Critical Use Case Requirements

Fig4. Use Case Diagram

There are two actors for Online Music CD Store - a Customer and an Administrator. A customer can use the system in four scenarios

  • Browse Catalog
  • Search Catalog
  • Get Song Recommendation
  • Manage Account
  • Place Order
  1. Use Case 1 : Browse Catalog Requirements:

 Purpose: A customer can browse through the different genres, categories and can also view the details of the products such as the description, price and songs listing etc. Depending upon the genre/category selected, the contents of the table are accessed using a select query.  Input: The User will select one of the genre and its category.  Output: The system will display product list and information of the selected genre and/or category. The product list will be displayed on product.aspx page and 6 products will be displayed on each page and the rest (if any) will be on the next page. This will be executed using the “pagination” property i.e. there will a link named “Previous” and “Next” on the bottom of every product.aspx page to enable the customers to go to the next and previous pages to view products. The current page of the customer will also be displayed on every page.

  1. Use Case 3: Get Song Recommendations:

 Purpose: The purpose of this part of the application is to enable the customer to find recommendations for the songs of his choice.  Input: The customer will hit the “Get Recommendations” button on the top of every page. This will redirect the user to Recommendations.aspx Web page where he/she will have the options to enter title of the song, artist and style of his/her choice and click the “Get Similar Songs” button.  Output: Initially, a list of most similar songs (to the input song) will be displayed to the user, from which the user can choose some songs and get their most recommended songs.

To implement this functionality, a method called Case-based Reasoning is used. A description of the method is included at the end of this chapter.

  1. Use Case 4 : Manage Account Requirements:

 System Login:  Purpose: This is implemented to enable user authentication. A valid user account must be used for an existing customer.  Input: The customer can login to the e-Commerce shopping system by entering his user name and password.  Output: The system will verify that the login name matches the login password. If the user name or password is invalid, the appropriate error

message will be indicated and the user will be requested to re-enter user name and password. If the user inputs are valid, the main page will be displayed.

 System Register:

 Purpose: This is implemented to enable a new user authentication. A valid user account must be used for an existing customer or a new customer can register.  Input: If the customer is a new user, he can request to register with the system.  Output: The system displays a registration page and asks the customer to choose a user name, password and enter a valid email id, security question and answer.