Challenge Overview

Challenge Overview

The client has an VBA application in excel format and we’re converting it to a java base application. This application has about 30 tabs and we’ve already converted some of the tabs in the past few challenges.

Challenge Details

For this challenge, we need to update the prototype to have some new pages / tabs, the requirements are described in a google spreadsheet (link in the challenge forum) but here's a summary of the tasks:

  • Risk Calculation: the current "Deal Goverance" page will be put into a sub-tab called "Solution Review" and then another sub-tab called "Risk Calculation" will also be added to the page. The Risk Calculation page/tab should have same content / behavior as the namesake sheet in the "Excel App v7.0" posted in the forum. This corresponds to row#2 in the spreadsheet.

  • Floor levels corrected for F1/F2: Before the Resources section (on the Pricing Tab, Discounting Sub-Tab), there should be a new section called Discount Floors. In that section there will be a table with 3 columns: Material Code, Discount %, Floor Broken. First the overall discount for each material code will be calculated. To do this, find the weighted average of the discount applied to all line items with that material code (sum the total amount discounted for all line items with like material code and divide by the sum of the full price for those same line items). Once the overall discount is calculated for each material code, look up the floor (threshold) which is broken by that discount. Such a threshold will have text value associated with it (and will be shown in the Floor Broken column). Now display all material codes, percentage and floor broken in the table. The text of each row should be colored to match which floor was broken (see the version 7.0 spreadsheet for the colors). If there are no rows to display, the section (and table) should not display either. This corresponds to row#3 in the spreadsheet.

  • IIG – IP/EDU/MSOD: this is under discussion but you can expect details to be provided during challenge phase. You can also see the comment on Column B of row #4 to get a better idea of the ongoing discussion on requirements.

  • Price Per Diem Expenses: this also needs more discussion but details will be provided during challenge phase. Check Column B of row #5 and comment for that cell to find out more details.

  • Shared Template Folder: please check Column B of row #10 in the spreadsheet and comment in that cell to find out the details. Basically we are looking for new pages to manage templates in folder-like structure. We only need to be able to create and manage (delete and move) templates, we do NOT need edit. Creating a template is essentially creating a new service request and then saving it as a template in a folder in the structure. I think we'll also need an extra button in the normal "create service request" pages that allows a super user / admin to save that request as a template.

  • Links back to relevant tabs on Summary page: when on the view page and user clicks Edit, we need it to go directly to the selected sub-tab, not just the Service Activities page with the 1st tab seletected.

Your submission should be based on the provided base prototype. The changes need to be done in all related pages  (create/edit/copy/view/details) and in all paths.

Since we don't have any mockups for these changes please ask questions in the forum to get clarifications.

General Requirements:

The following are general guidelines you must follow in building the prototype:

- Produce a UI Prototype that can be used to demonstrate all tabs mentioned above.

- The prototype will be done based on the provided UI mockups.

- Your submission must be based on the previous prototype (same styles) and replicate all behaviors of the tabs.

You need to include those in your submission:

- Implement hover state for all buttons and links.

- All elements (such as the select boxes, radio buttons and checkboxes) will be browser based but should look consistent with existing ones.

- Follow all coding styles / standards already used in previous prototype.

The following are specific requirements for HTML, CSS and Javascript files:

- Your HTML code must use the same doctype as the provided prototype from a previous challenge (attached to forum)

- Validate your code, reviewers may accept minor validation errors, but please comment your reason for any validation errors. Use the validators listed in the scorecard.

- Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to lay out your page. Only use table tags for tabular data and not for page layout.

- No inline CSS styles, all styles must be placed in an external stylesheet.

- Use semantically correct tags - use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.

- Element and Attribute names should be in lowercase and use a "-" or camel naming to separate multiple-word classes (i.e. "main-content", or "mainContent".

- All JavaScript must not have a copyright by a third party. You are encouraged to use your own scripts, or scripts that are free, publicly available and do not have copyright statements or author recognition requirements anywhere in the code. You are allowed to use the JQuery JavaScript library for this contest.

- Pagination is required to be included where necessary

General Page Requirements:

The following should be working properly and reviewers should check these in review:

- Tab order and field focus
- Existing data Selection -  When tabbing to a field any existing value should be highlighted
- Ensuring that field that are tabbed to can be controlled with the keyboard i.e. check boxes, radio buttons, calendar controls, drop downs, etc.

Timeline

To reviewers and submitters, this challenge has shorter review and appeals phases, make sure you stick to the timeline.

Winner Responsibility

There are a few uncertainties in the requirements so we may need some extra changes during final fixes based on the winning submission, this is part of the challenge scope but we'll make sure the extra fixes are not too many otherwise we'd pay extra for the fixes.

Browsers and Standards:

Your submission must works on browser in the list below:

- IE8+

- FF 3+ Mac & PC

- Safari 4 PC

- Chrome Mac & PC



Final Submission Guidelines

Submission Deliverables

  • A complete prototype with all requirements implemented.

Submission Guidelines

Submit an archive file contains all HTML/CSS/JS/images and another required files into Online Review.

ELIGIBLE EVENTS:

2015 topcoder Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30047614