Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Heritage qJack qHMO Card Game is a game that launches from within the qHMO web application. The idea is that a user of the qHMO app can spend time learning about their profession or organization when they have idle time in their work day and they are on the qHMO app.  This is meant to be engaging, fun, simple and easy to get into or exit out of to return to the user's original task in the qHMO web application.  The key areas of this application are the "Question and Answer" section, where the user can win cards or loose turns which can be used in the second section (i.e. "the qJack Card Game").  Have fun with this one!  It's a game that incorporates different approaches to keep the users informed and interested.

In this contest, we want you to implement the following tasks:

  • Come up with the data model Architecture (i.e. Object definitions and relationships) to represent the q-Jack application DB
  • REST API interface specs, no actual implementation is needed, but you need to describe your approach in details about how the REST API interfaces will interact with the UI.
  • API to represent the Admin functionality of this app, there are no storyboards for this, as the UI for this was not designed, however, we will need this to be a simple 1 page UI, to manage Adding/Editing Questions, Global Settings for the q.Jack app, etc.
  • The HotSpots that you will see in the Storyboard designs to launch the qJack game are supposed to be random on any of the qHMO app interfaces. We will need the Architecture to suggest some random logic that suggests where this hotspots shows up for the end user interface.
  • We will need the Architecture to think about logging all session data in a db, such that it know which questions to not repeat for the same user, and when needed, an Admin can pull entire user activity on qJack to audit (i.e. Day/Date Points earned, questions answered, etc.)

Note that the front-end will be AngularJS + HTML5, and we want the REST API to be based on ASP.NET WebAPI. 

 



Final Submission Guidelines

Submission Deliverable

  • Source Code
  • Word Document explaining your idea and describe how it address all the requirements. 

ELIGIBLE EVENTS:

2015 topcoder Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30048351