Arpan Badeka -Prototyper, UML Modeler

Prototype Report

Frenzy

Team 01

Arpan Badeka -Prototyper, UML Modeler

Ankur Palav-Software Architect, Prototyper

Ashwin Hariharan-Software Architect, Prototyper

Jheel Somaiya-Project Manager, Lifecycle Planner

Sailee Rane- Requirements Engineer, Feasibility Analyst

Rishabh Sharma-Software Architect, Operational Concept Engineer

Alan Kwan- Quality Focal Point

10/10/2016

1

Version History

• Original template for use with Frenzy v1.0

• To mitigate risk based on “Risk Reduction” strategy

Table of Contents

Prototype Report

Version History

Table of Contents

Table of Tables

Table of Figures

1.Introduction

1.1Purpose of the prototype report

1.2Status of the prototype

2.Navigation Flow...... 3

3.Prototype...... 4

3.1 Prototype1: Shop Similar………………………………………………………………………………………. 4

3.2 Prototype2:Shop Widget……………………………………………………………………………………… 5

1

Table of Tables

Table 1: Shop Similar Implementation Description

Table 2: Shop Widget Description #Page1

Table 3: Shop Widget Description #Page2

Table of Figures

Figure 1: Navigation Flow of Frenzy Website...... 3

Figure 2: Server Daigram of Shop Similar...... 5

Figure 3: Shop Widget_1...... 6

Figure 4: Shop Widget_2...... 7

1

1.Introduction

1.1Purpose of the prototype

The key purpose of the prototype report is to provide details of the prototype which are used to mitigate the risk of the project. The mitigation strategy used is “Risk Reduction”. These prototypes can be used to analyze the flow of the system and user interface of the system to the client. Also, some prototypes will help to show the implementation of modified logics of the concepts of the system for better understanding of modified system to the client.

In this report, we have described two risks and their prototypes and they are described as follows:

1.Risk: Shop Similar:

The shop similar feature is an essential part of the application which caters to the demands of all types of customer base.

Prototype:

By interfacing with the back end through a search model in Code Igniter framework.

2.Risk: Shop Widget

The UI experience for the user is required to be improved the customer base and interaction with website.

Prototype:

The User Interface Prototype to enhance the user experience to maintain a consistent flow throughout the website.

1.2Status of the prototype

Since the prototype presentation, some improvements are made, including:

1. Shop-Widget prototype is to improve the UI experience for the user and clarify website look and flow with the client.
2. Shop Similar prototype is revision of Server-Side Management Concept.

2.Navigation Flow

Figure 1: Navigation Flow of Frenzy Website

3.Prototype

3.1 Prototype 1Shop Similar

3.1.1 Purpose of this prototype

One of the major requirement for this feature is to allow the user to browse through similar items and shop similar items based on price, brand, category and color. The team has experience working on the Web Application but limited with the retrieving data from the server and projecting on the front-end. Teammadethe prototype of the algorithm for better understanding.

3.1.2Result

After building the prototype, team is able to better understand and visualize the flow and implementation of the algorithm. This also helped team to better deploy the back-end server. Thus mitigates the risk of less experience of the server implementation and deployment.

Table 1: Shop Similar Implementation Description

Figure 2: Server Diagram of Shop Similar

3.2Prototype 1 Shop Widget

3.2.1 Purpose of this prototype

The purpose of this prototype is to improve the user interface, the risk involved was because of inconsistent flow on the website and even the visualization was inconsistent causing lost of interest of the user. Also, this can be used to clarify the requirements and user-interface to the client.

3.1.2Result

The prototype shows the designed user interface showing the UI experience. The following screenshots describe the features.

Table 2: Shop Widget Description #Page1

• Can be redirected to the shop similar article.
• Can be redirected to page showing three images when user clicks on next.

Figure 3: Shop Widget_1

Table 3: Shop Widget Description #Page2

• Can be redirected to the shop similar article.
• Can be redirected to page showing three images when user clicks on next.

Figure 4: Shop Widget_2

1