1 / 25

Phase I Presentation Outline

Online Music Store MSE Project Presentation I Presented by: Reshma Sawant Major Professor: Dr. Daniel Andresen. Phase I Presentation Outline. Project Overview Use case Diagram System Functionality Project Plan Test Plan Questions. Project Overview.

rhernandes
Download Presentation

Phase I Presentation Outline

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Online Music StoreMSE Project Presentation IPresented by: Reshma Sawant Major Professor: Dr. Daniel Andresen

  2. Phase I Presentation Outline • Project Overview • Use case Diagram • System Functionality • Project Plan • Test Plan • Questions

  3. Project Overview The objective of this project is to design and develop an Online Music CD Store with its user interface. • Target: Public Users • Product : Music CD • Facilities provided for Users: Browsing, searching, managing personal account, buying etc.

  4. Motivation • Motivation is to have experience in design and development of a web-based online transaction application • Gain experience in using technologies: • ASP.NET 2.0 & C# • Microsoft SQL Server 2005 • Microsoft Visual Studio 2005 • UML & Database design

  5. Use Cases

  6. System Functionality • Functionalities for Customer • Functionalities for Administrator

  7. Customer Functionality 1) Browse & Search Product Search Browse Catalog

  8. Customer Functionality • Manage Account: • Register: A new User can signup to create a new account.

  9. Customer Functionality • Login: A valid user account must be used for an existing customer

  10. Customer Functionality • Manage Profile: Customer can edit, update and save his personal information

  11. Customer Functionality • Place Order • Add to Shopping Cart: • Add products to shopping cart while searching or browsing catalog. • Update and Delete product Quantity within Cart. • View Cart Details: To view contents of the shopping cart. • Checkout: To buy the products added to the shopping cart.

  12. Shopping Cart

  13. Customer Functionality • Edit Billing & Shipping Details:To allow customers to edit and update their billing & shipping information.

  14. Administrator Functionalities Manage Catalog • Add New Genre/Category • Delete Genre/Category • Add New Product • Delete Product • Edit Catalog Details: Edit the details of genres, categories, products like description, quantity, price etc.

  15. Project Plan

  16. Task Breakdown • Inception Phase (Phase 1 ) • Vision Document • SQA Plan • Project Plan • Prototype • Architecture Design • Phase 1 Presentation

  17. Task Breakdown • Elaboration Phase (Phase 2) • Revise Vision Document • Revise SQA Plan • Revise Project Plan • Develop Formal Requirement Specification • Revise Architecture Design • Develop Test Plan • Formal Technical Inspection • Develop Prototype • Phase 2 Presentation

  18. Task Breakdown • Production Phase (Phase 3) • Develop Code • Testing • Functional Testing • Evaluate Test Result • Documentation • Test Report • User Manual • Phase 3 Presentation

  19. Test Plan

  20. Unit Testing • To Verify that various parts of the code are working correctly using NUnit testing tool • Test Cases: • User Registration • Login • Search • Edit Shopping Cart • Place Order

  21. Test Cases • User Registration • Incorrect Inputs: • Username already in use with existing users • “Password” and “Confirm Password” fields do not match • An empty required field (Username, password, Confirm password, Email, Security question and answer)

  22. Test Cases • Login • Incorrect Inputs: • Wrong Username and/or wrong Password • An empty required field (Username or Password) • Search • Inputs resulting in no search results: Non-matching Keyword

  23. Test Features • Edit Shopping Cart • Incorrect Inputs: • Negative input number in “Quantity” field • Non-integer input • An empty “Quantity” field • Place Order • Incorrect Input: • An empty required field • Invalid format (FirstName, LastName, Billing Address, Shipping Address, Credit Card details)

  24. Performance Testing • Verifies that the components of the system meet the stated performance requirements. • Possible Performance Metrics: • Response time • For web pages – Login page, Registration page etc • For transactions accessing database • Read - Product Search • Update - Edit Profile information, submitting registration request etc • Example Tool - JMeter

  25. Questions?

More Related