1 / 23

Phase II Presentation Outline

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.

anakin
Download Presentation

Phase II 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 MusicCD StoreMSE Project Presentation IIPresented by: Reshma Sawant Major Professor: Dr. Daniel Andresen

  2. Phase II Presentation Outline • Action Items from Phase I • Architecture Design • Formal Requirement Specification • Formal Inspection Checklist • Test Plan • Questions

  3. 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

  4. 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)

  5. 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

  6. Song Recommendation Based on Purchase History

  7. 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

  8. Song Recommendation Based on similar preferences of other users

  9. 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

  10. 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

  11. Domain Model

  12. ASP.NET Forms and Classes Used

  13. Architecture Design Page Flow Diagram for User Login.aspx Recommendation.aspx Search.aspx Default.aspx Catalog.aspx Product.aspx Logout.aspx ShoppingCart.aspx Checkout.aspx OrderPlaced.aspx

  14. Architecture Design Page Flow Diagram for Administrator CatalogAdmin.aspx Login.aspx Index.aspx OrdersAdmin.aspx Logout.aspx ShoppingCartAdmin.aspx

  15. 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.

  16. Inspection Checklist • 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

  17. 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

  18. Test Plan • Unit Testing using NUNIT tool • Performance Testing using JMeter tool

  19. Test Plan – Sample UNIT Test Case Edit shopping Cart

  20. Test Plan – UNIT Test Cases

  21. Performance Testing 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

  22. 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

  23. Questions?

More Related