eBay Get Help Frontend Integration Challenge

Project Overview

The objective of this project is to develop an App that will be used by 3 types of Users (An Exec, Support Admin, Support Specialist). The GetHelp App will manage the collaboration between these 3 types of Users on requests that need to be fulfilled. Think of a hi-touch support application for Exec users, where it offers instant feedback and communication between these users for speedy resolution of support requests and upto the minute status on the requests, thereby eliminating any delays or disruptions into normal business.

Competition Task Overview

We have previously launched a challenge to build :

- The backend application to support the workflows requried in this application, see details here: http://www.topcoder.com/challenge-details/30039599. You should go through the spec of this challenge since it contains a handful of useful information that will help you better understand how the application works.

- The UI Prototype to represent the intuitive interfaces for the 2 types of users ( Exec User and IT Tech User), the 3rd type of User (Support Admin) is expected to use the standard web interfaces developed in the backend application. You can view the UI Prototype challenge information here: (<< Final UI Prototype Challenge details >>).

The objective of this contest will be to deliver the following key requirements:

• Integrate the 2 Assets {UI prototype pages (angularJS pages)} with our backend app {(which has raw interfaces without any design)}.

• Validate all the Onsite activity flow interactions work through the new design pages and we have no dead spots (i.e. buttons with no events/actions or redirects that lead nowhere.)

• Validate all web-interfaces for the backend continue to work as-is from the last backend challenge. (i.e. Manage Users, Manage Requests & View request history, Manage Configurations, Manage Announcements.)

  • In the Activation process, the Backend App would redirect the user to a User information detail interface, this is no longer required. If successful, it should simply redirect to the “Success” message interface as depicted in the UI Prototypes. When there is an error or cannot activate, we just need to display an error message on the same interface rt below the input box stating “Invalid confirmation number, please re-enter”, and the focus should remain in the input box on this interface.

  • For any differences observed in the backend App flow and the UI Prototype flow, make sure we adapt to the UI prototype flow as the final desired flow/steps.

• We would like the Backend App Code base to be refined to incorporate appropriate naming conventions and follow Code development best practices:

  • The Application needs to be named “GetHelp” - currently called as testkraken, and the labels reflect “GetIT help”.

  • All Backend Services need to be API’s that can be validated and consumed by any external app, agnostic of the current frontend. (*Remember, this is going to be a mobile app, and in the next step, the frontend would be decoupled and wrapped into native device code, so ensuring that they are able to consume these API’s is very important.

  • In the “Request Object”, the values in the Request Type should be either “Onsite, SMS or Call” but never blank, currently they are blank and is allowed. This field should be always either of these 3 values.

  • The ReqId value is currently an Autonumber, it should follow this convention “RQ-0001”, its currently modeled as “1,2,3, etc.”.

  • The EndTime field from RequestHistory should be removed, this is obsolete and not required.

Development Guidelines

We need the same development guidelines from the previous challenge to be followed. We just want to apply the new UI from the prototype pages to the backend we already built.

- Please add appropriate comments around all the API’s that have been built on the backend.

Documentation Provided

Register to download the source code of previous challenge and UI Prototype from challenge forum.

Final Submission Guidelines

Submission Deliverables

• This Solution needs to be a Production quality asset.

• Your Submission should be in the form of a github repository which includes all the Code elements, and a folder that has instructions for Build/deploy/configure.

• An Overview video of the application code blocks (i.e. Code overview) highlighting the discipline of separation of concerns(SoC) applied.

  • Organized Code Walkthrough

  • Demonstrate Test Execution of your Code simulating all the implemented scenarios

• A Demo video that presents all the User Activity flows (end to end) that were provided in the form of design mockups.

  • Feature the Build/Deploy/Install and Config Steps

  • Feature all the Functionality

• A Documentation that covers all aspects of the solution (Requirements / Build / Deploy / Install / Configure)

Final Submission

For each member, the final submission should be uploaded to the Online Review Tool.