Challenge Overview

1.0 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"). It's a game that incorporates different approaches to keep the users informed and interested.

Note that the front-end will be AngularJS + HTML5, and we want the REST API to be based on ASP.NET WebAPI.
This assembly will implement the data models, exceptions and backend services, DAOs and jobs. 

Please note that there is a previous assembly code that you can reuse but make sure that all updates are properly implemented. This is attached with the contest.

2.0 Challenge Task Details

2.1    Model Classes

This assembly is responsible for implementing all model classes on class diagram "Model Class Diagram".

2.2    Exceptions

This assembly is responsible for implementing all exceptions on class diagram "Exceptions Class Diagram".

2.3    Jobs

This assembly is responsible for implementing all exceptions on class diagram "Schedule Jobs Class Diagram".

2.4    Backend Services and DAOs

This assembly is responsible for implementing all services on class diagram "Services and DAOs Class Diagram".

2.5    Stored procedures

This assembly is responsible for implementing all the needed stored procedures to be used by DAOs.


Note#1: Extensive implementation notes are provided at method documentation on UML Class Diagrams. Please follow them for implementation.

Note#2: Please read the whole Application Design Specification first. All the details not mentioned in this specification are provided in that document.

Note#3: Please refer to the Assmebly Specification for the Stored procedures information

3.0 Technology Stack

 



Final Submission Guidelines

As per the TC Software Assembly guidelines.

 

ELIGIBLE EVENTS:

2015 topcoder Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30049866