Frenzy TRR ARB Presentation

Size: px

Start display at page:

Download "Frenzy TRR ARB Presentation"

Sophie Richard
5 years ago
Views:

1 Frenzy TRR ARB Presentation CS577A Fall 2016 Team 01 -Arpan Badeka Ankur Palav Jheel Somaiya Sailee Rane Ashwin Hariharan Rishabh Sharma Alan Kwan James Chang

2 Outline Operational Concept Overview TRR Outline Demo of the Project Test Cases and Results Acceptance Test Cases QFP Transition Plan 2

3 Operational Concept Overview 3

4 System Purpose Frenzy website is a one stop shop for Fashion bloggers, stylist, online shoppers and magazine article publishers. It provides: An array of products associated with online articles Conversion of digital media into visual store fronts 4

5 Program Model 5

6 Benefit Chain Diagram Assumptions: People are willing to buy the items posted on fashion blogging site. People like to buy the clothes that celebs and their friends wear. 6

7 System Boundary & Environment 7

8 Core Capabilities Capability Goal OC-1 Sort Items: User can sort products based on prices, new arrival, most popular Priority Level Must Have OC-2 Shop Widget: User can view the product in a slide view fashion and overall better UI OC-3 Shop similar: User can search similar items based on price, color, category and brand OC-4 Clothing Tag: User can get the product details on mouse hover in shop widget. Must Have Must Have Must Have 8

9 Goals & Constraints Organizational goals: OG-1: Automated Ecommerce of fashion blogging website OG-2: Using digital media as store fronts OG-3: Browsing and shopping the latest fashion articles without leaving the website OG-4: Buying similar articles based on color, style and price Constraints: CO-1: Use of Angular JS for front end development CO-2: Use of Code Igniter Framework for backend CO-3: Linux as an Operating System- The backend server is Linux CO-4: Free database system 9

10 TRR Outline 10

11 TRR Outline Transition Objective and Strategy Demo of the Project Transition Plan Transition Preparation. Operational testing, training and evaluation. Stakeholders role and responsibility. Milestone Plan. Required resources and processing strategies. 11

12 Transition Objective and Transition Objective Strategy The web project will be transitioned to the client. Training manual will be provided to client for added support for the future developers. The product will be thoroughly tested to pass all the test cases. The web site will be made public on the will of the client. 12

13 Transition Strategy Transitioned the system to the client by merging the code on GitLab & also providing the project to the client in zip files. Added proper comments to the code against the functionalities implemented for better understandability. The web site has been thoroughly tested & satisfies all the requirements on the win book. Also, passes all the acceptance test cases. We provide two strategies for the transition phase: AWS Local PC 13

14 Demo of the Project 14

15 Hotspot Tags Image 1: Hotspot tags on shop widget 15

16 Hotspot Tags Image 2: Gallery tags popup on mouse hover 16

17 Hotspot Tags Image 3: Hotspot Tags in Article Detail with Gallery Tag 17

18 Shop Widget Image 1: Shop Widget Popup displaying three items at a time 18

19 Shop Widget Image 2: Shop Widget popup displaying save/buy/shop-similar buttons on mouse hover 19

20 Shop Similar Image 1: Shop Similar Popup displaying Back button popup on mouse hover 20

21 Shop Similar Image 2: Shop Similar popup displaying items based on Same Category 21

22 Shop Similar Image 3: Shop Similar popup displaying items based on Lower Price 22

23 23

24 Shop Similar Image 4: Shop Similar popup displaying Sort and Same Brand Items 24

25 Live Demo Demo 25

26 Test Cases and Results 26

27 Overview 27

28 Overview Unit Testing for testing functionalities like Clothing Tag functionality, Sorting functionalities in the Shop Widget and Shop Similar modules Integration Testing for the Shop Popup and Article detail functionalities 28

29 TC-01 Browsing through the shop popup in the shop widget Number Test Item Result TC TC TC TC Check the on sale ribbon on items that are on sale. Check the item details on the pop-up header. Check the shop similar button in shop popup. Check the display of tagged items in the shop popup. Pass Pass Pass Pass 29

30 TC-02 Clothing Tag functionality Number Test Item Result TC TC TC TC TC The concentric tags present in the articles will be checked to provide a valid link to the related item. Null clothing tags will also be detected by the test case in order to remove them from the system. Check the functionality of the Shop similar button in gallery tag Check the functionality of the Buy button in gallery tag Sold out flag set for items in the gallery tag Check the correctness of the location of a clothing tag present in the gallery tag Pass Pass Pass Pass Pass 30

31 TC-03 Sort-Items Functionality in Shop Widget based on Popularity, Price and New Arrival. Number Test Item Result TC TC TC TC TC Checks result(json) correctness of Sort Items Based on Most Popular Checks result(json) correctness of Sort-Items based on Price(Low to High) Checks result(json) correctness of Sort-Items based on Price(High to Low) Checks result(json) correctness of Sort-Items based on New Arrivals Check the Sort Button on-click expands and collapse Pass Pass Pass Pass Pass 31

32 TC-04 Article Detail Functionality Number Test Item Result TC Check appropriate Article Details Pass TC Check Item Tag correctness Pass TC Check Image Tag buttons Pass TC Check articles saved by buyer Pass TC Check Images in Item Slider based on the Article and Author Detail Pass 32

33 TC-05 Similar Items Functionality Number Test Item Result TC TC TC Similar Item Query Relevance Testing Similar Item Visualization Check Same Brand Query Relevance Check Pass Pass Pass TC Empty Query Result check Pass TC Image URL does not exist Pass 33

34 TC-06 Similar products of lower prices Number Test Item Result TC TC TC TC TC Backend API calls generating correct response Generation of results for the appropriate selection of a div element Display similar products relevant to a chosen product 10 elements in the product slider Checking on another checkbox should deselect lower prices functionality Pass Pass Pass Pass Pass 34

35 Acceptance Test Cases 35

36 Acceptance Test Cases Part 1: Shop Widget Lower the brightness of the Shop Popup on Shop button click: PASS Display item details in popup-header: PASS Differentiate on-sale items from other items with sale ribbon over on-sale items: PASS Shop Similar button with CSS animation and CSS highlighting on mouse-over: PASS 36

37 Acceptance Testing Part 2: Shop Similar Sort by button to sort the items based on New Arrivals, Most Popular, Price: Low to High and Price: High to Low : PASS Display similar items based on Same Brand, Same Category, and Lower Prices : PASS Display of item on which Shop Similar functionality is performed, on hover of back button: PASS 37

38 Acceptance Testing Part 3: Hotspot Tags Hotspot tags should display the appropriate item on which it is tagged: PASS Display of item price on top of the gallery tag: PASS Save/Saved/Buy/Shop-Similar buttons on top of the gallery tag on mouse hover: PASS Close button with CSS highlighting on mouse hover: PASS 38

39 Quality Focal Point 39

40 Traceability Matrix OCD WC UC OC-1 WC_4126 UC-8 OCD WC UC OC-2 WC_4128 UC-5 OCD WC UC OC-3 WC_4140 UC-4 WC_4234 UC-8 WC_4141 UC-4 WC_4241 UC-3 WC_4236 UC-8 WC_4145 UC-5 OC-4 WC_4144 UC-4 WC_4237 UC-4 WC_4229 UC-4 WC_4230 UC-4 WC_4231 UC-2 WC_4233 UC-4 WC_4238 UC-3 WC_4239 UC-2 WC_4242 UC-4 (c) USC-CSSE 40

41 Unresolved Technical Debt # Description Category1 Category2 How did you fix it/mitgation plan Lack of external documentation & code commenting creates problems in understanding the current codebase such as how the various models, controllers and views interact with each other. Deference of code integration, and inconsistencies in individual code leads to errors/unfinished implementations in final code Not all stakeholders (Users) were present for win/win condition negotiations; Client and team proceeded with negotiations with risk. Life Cycle Management Shortfalls Prudent_Deliberate Team members now have a reasonable understanding of the codebase. The developers have understood the basic flow of the MVC application and are able to work on the modules and add additional features. The developers are still working on improving the code by commenting the code and making it cleaner Life Cycle Management Shortfalls Reckless _Deliberate The communication workflow between the team members is becoming clearer as we are gaining a good insight into the code and there is a clear establishment of division of development between the team members. The team has started committing the code to Github as features are completed Life Cycle Management Shortfalls Reckless _Deliberate Risk mitigation: Attain User win conditions from Client, then present working prototype to (actual) Users then get their input to revise requirements if necessary. 41

42 Resolved Technical Debt # Description Category1 Category2 How did you fix it/mitgation plan The clothing tags move into other div elements after adding or deleting an article which is undesirable for the user Problems faced while updating the existing SVG files which does not allow current developers to add new icons. Also the indiviual elements are referenced in different files which prevents from updating the vector file. Images take a lot of time to download when the article is first published. Unstable Jira prevents coordinating Scrum tasks to tracking defects and progress; if new Scrum tasks arise then Jira tickets cannot be created Inconsistent/incomplete documentation for FC Package (draft) Methods, Processes and Tools (MPT) Shortfalls Personnel Shortfalls Reckless_Inadvertent Rectify the current CSS positioning to incorporate the positioning features of Boilerplate and test the incorporated features Methods, Processes and Tools (MPT) Shortfalls Prudent_Deliberate Client provided the developers with a broken down SVG file which allows accessing, updating and removing the indiviual icons without introducing any error code in the files. Personnel Shortfalls Prudent_Deliberate Providing thumbnails to the user and downloading the images in the background Methods, Processes and Tools (MPT) Shortfalls Prudent_Inadvertent Jira issue resolved therefore allowing defect tracking and progress Reckless_Inadvertent Conduct Peer Review meetings to update documents for next revision. Deferred to a new technical debt as Revision 1.1 has been released and graded. Resolved below. Resolve findings and update from graded FC Package Methods, Processes and Tools (MPT) Shortfalls Reckless_Inadvertent Updated documentation with corrections to package for next revision submission Implementation defects in product content search Personnel Shortfalls Reckless_Inadvertent Web Crawling to get more Clothing tag keywords, NER to get keywords from product description, find all occurences of categories and description keywords in tables Dearth of rigorous testing under different use cases and Life Cycle Management Shortfalls Prudent_Deliberate Team members have started testing certain corner cases where failure of application might occur features developed by testing them for performance and also by integrating it with other modules Unable to use the existing controllers for newly added Life Cycle Management Shortfalls Reckless_Inadvertent Creating new controllers for the developed functionalities due to predefined methods. modules. Code redundancy in the existing files makes it difficult to add Life Cycle Management Shortfalls Prudent_Inadvertent Refining the existing code by creating a single new functionalities without introducing bugs reference file to reduce the redundancy. Client is very detail oriented about minute UI elements, making Life Cycle Management Shortfalls Prudent_Inadvertent Working on the different elements of the CSS in the CSS time consuming shop widget to fix the UI isssues SCRUM board is not updated therefore there are inconsistencies in progress tracking; tasks that are done are not marked as done/complated, making metrics skewed, and SCRUM board is not organized in a way to distinguish tasks for each sprint. Personnel Shortfalls Reckless _Deliberate Proactivately update SCRUM board as tasks are assigned with responsible engineers listed; interferes with accurate metrics representation 42

JIRA TICKET Completion Date Hours Logged FRENZY-66 13-Nov 112 FRENZY-67 7-Nov 10 FRENZY-68 13-Nov 112 FRENZY-70 30-Oct 8 FRENZY-71 25-Oct 3 FRENZY-72 7-Nov 5 FRENZY-76 7-Nov 4 FRENZY-80 21-Nov 35

43 JIRA TICKET Completion Date Hours Logged FRENZY Nov 112 FRENZY-67 7-Nov 10 FRENZY Nov 112 FRENZY Oct 8 FRENZY Oct 3 FRENZY-72 7-Nov 5 FRENZY-76 7-Nov 4 FRENZY Nov 35 FRENZY Nov 3 FRENZY Nov 45 FRENZY Nov 6 FRENZY Nov 3 FRENZY Nov 16 FRENZY Nov 16 FRENZY Nov 88 FRENZY Nov 3 FRENZY Nov 24 FRENZY Nov 24 FRENZY Nov 16 FRENZY Nov 64 FRENZY Nov 24 FRENZY-95 2-Dec 3 FRENZY Nov 32 Assumes that Day logged is 8 hours 43

44 Number of Defects Sprint 1 (10/5) 45 Sprint 2 (10/19) 41 Sprint 3 (11/2) 38 Sprint 4 (11/19) 30 Sprint 5 (12/2) 0 44

45 Transition Plan 45

46 Transition Preparation Two Transition Strategies are used: 1) AWS 2) Local PC Hardware Software Local PC One PC with Ubuntu MySQL AngularJS CodeIgniter AWS + Other Software One PC Gitlab AWS Beanstalk Staging Site On Campus N/A Staff Developers, Trainer; Tester; Client; Developers, Trainer; Tester; Client; 46

47 Operational testing, training, and evaluation Category Category perations Operations Training Documentation including Training Plan; Training Session; Technical support; Testing Documentation including Testing Plan and Cases; Acceptance Test Case; Evaluation Client Feedback & Testing

48 Stakeholder Roles & Responsibilities Role Responsibility Location Developers Trainer Tester GitLab: Source Code GitLab: Wiki Documentation Deployment on AWS Staging Environment Technical Manual Training Plan Training Session Technical Support Testing Plan and Cases Acceptance Testing Client AWS Authorization N/A On-Campus On-Campus On-Campus 48

49 Milestone Plan 49

50 Milestone Plan 50

51 Required Resources & Processing Strategies Products Source Code Technical Manual AWS Staging Server SQL Database Transition Processing and Status Have private Gitlab repository Have technical manual for developers with code comments, functions and important components explained Staging environment integrated with latest features. Technical support and documentation SQL ready with new changes 51

52 Q & A 52

Test Plan and Cases (TPC)

Test Plan and Cases (TPC) Frenzy Team 01 Name First Role Second Role Third Role Ashwin Hariharan Software Architect Prototyper Implementer Ankur Palav Software Architect Prototyper Implementer Arpan Badeka