Register
Submit a solution
The challenge is finished.

Challenge Overview

Welcome to Claims Management - Multiple Screens Part 2 Contest. This is the second in a series of contests aimed at creating the UI Prototype for a Claims Management application.

 

Contest Details

The requirement is straightforward - create the UI Prototype for the provided designs. Only the following screens are in scope:

  • Training screen (Admin user)

  • Analyst user screens

  • QC user screens

 

In the contest forum, we will share with you the designs that you can use to create the UI prototype. Additionally, we will also be sharing the existing code based with you that you need to work with. Finally, we will share a document with you that will describe all the pages in scope

 

Kindly note that the screens require you to make an API call, the details of which we will share in the contest forum. Also, we will share an existing code base with you that you need to use. This code base already contains most of the screens for the Admin user. You will need to update it and follow the same conventions used.

 

Points To Note

  • Build the screens component wise and then add the necessary components in your container (page).

  • The initial code is using Angular (latest version) and is built using Angular CLI. You need to create the prototype using the same. Additionally, we also have ng-bootstrap which you need to make use of. We are also using Twitter Bootstrap that we have customized for our app. You are expected to make use of the same. This time, we have provided a style guide as well that you can refer to and update the custom theme to match the style guide, if necessary.

  • The screens need to work on IE11, latest Edge, Google Chrome and Firefox browsers for desktop. Only Desktop is in scope. No mobile or tab versions exist.

  • The width of the pages is fluid. It will expand and contract based on the screen size and occupy full width. You need to support a width of 1366px and above.

  • You are expected to follow best practices in Angular development

  • Use texts wherever possible. Images are only for icons and logos.

  • Ensure your submission has no lint errors



Final Submission Guidelines

Zip your code base and upload it to topcoder.

 

ELIGIBLE EVENTS:

2018 Topcoder(R) Open

Review style

Final Review

Community Review Board

Approval

User Sign-Off

ID: 30064825