BONUS: 5‌ CHECKPOINTS AWARDED WORTH ‌$100‌ EACH

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Variable Interest Entities Consolidation Wireframe Contest.

Client is going to build a web-based application that can manage the various insurance entities. The application is called as Variable Interest Entities Consolidation (VIE Consolidation). The application will be used to automate processes performed by client's Surveillance department. The client can identify transactions that they may have the power to direct activities of the Variable Interest Entity (VIE).

We already have the Conceptualization Document that defined the solution. We need your help in this contest to create wireframe based on provided document. At the end of this contest we are looking for a process flow and layout design of the functionality mentioned in document. Your solution should have all requirement functionality, user friendly, intuitive and easy to use.

Round 1

You need to submit wireframe that cover functionality of Generic User, Surveillance Analysts, Sector Lead and Chief Surveillance Officer.

Round 2

You need to submit wireframe that cover all required functionality plus any feedback and Checkpoint phase.


Project Overview

The client Assured Guaranty is the leading provider of financial guaranty insurance. They guarantee scheduled principal and interest payments when due on municipal, public infrastructure and structured financings. They manage thousands of insurance policies. The insurance policies have to be analyzed for various attributes each quarter. The analyses could involve change in status of the policies. Global Surveillance is a group within client's organization that monitors the underlying financial product insured by a policy. Their business is to insure primarily fixed income securities like Municipal Bonds. Surveillance keeps an eye on those bonds through the life of the policy. The client need a web-based application that can manage the various insurance entities. The application will be called Variable Interest Entities Consolidation. It will be one of the many line of business applications.

 

General Requirement

Following are general notes you should keep in mind while you are creating the wireframe:

Your solution must be useful so it can save web designer time and energy. All pages/elements must linked each others and must show correct flow.

The application is a web-based application.

The application must be easy to use and intuitive.

- Your solution must implements all functionalities that are explained in attached Conceptualization Document. You should use it as a guide, but if there is a better way to display any information, feel free to reflected it in your solution.

- You must use wireframe note pane in every single page you design, to explain what all items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help us to give you constructive feedback.

- We suggest you to follow high level requirements details with use case diagram, it is provided in contest document.

 

Wireframe Requirement

Following are general information and functioality that must be implemented in your solution. For more details please refer to Section 4 in Conceptualization Document, you must implement all functionalities from Section 4.4.1 to Section 4.4.27

- Generic User, they will have functionality to login, logout, search, filter and view policies, export report and view help. See Section 4.4.1 to 4.4.8 for its details.

- Surveillance Analysts, they will have functionality to modify policies, get and acknowledge notifications. See Section 4.4.9 to 4.4.11 for its details.

- Sector Lead, they will have functionality to approve changes that made by Surveillance Analysts. See Section 4.4.12 for its details.

- Chief Surveillance Officer, they will have functionality to review and approve changes made by Sector Lead. See Section 4.4.13 and 4.4.14 for its details.

- Consolidator, they will have functionality to mark policies for consolidation. See Section 4.4.15 for its details.

- Team Lead, they will have functionality to approve changes made by consolidator. See Section 4.4.16 for its details.

- Surveillance Administrator, they will have functionality to manage triggers and sector categories. See Section 4.4.18 for its details.

- Administrator, they will have functionality to import data, export data, manage alerts, manage authorization conditions, manage user roles, manage groups and manage activities. See Section 4.4.19 to 4.4.26 for its details.

- Auditor, they will have functionality to view change history made by users. See Section 4.4.27 for its details.

 

Target Audience

Surveillance Analysts, Sector Lead, Chief Surveillance Officer, Consolidator, Team Lead, Surveillance Administrator, Auditor and Administrator.

 

Judging Criteria

- User Experience

- Completeness and accuracy of the wireframe as defined in Conceptualization Document.

 

Submission Deliverable

Preview Image

Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.

Submission Files

Wireframes should be built in HTML or Axure. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.

Source Files

All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.

 

Final Fix

As part of the final fixes phase you may be asked to modify content or user click paths.

Please read the challenge specification carefully and watch the forums for any questions or feedback concerning this challenge. It is important that you monitor any updates provided by the client or Studio Admins in the forums. Please post any questions you might have for the client in the forums.

Stock Photography

Stock photography is not allowed in this challenge. All submitted elements must be designed solely by you. See this page for more details.

How To Submit

  • New to Studio? ‌Learn how to compete here
  • Upload your submission in three parts (Learn more here). Your design should be finalized and should contain only a single design concept (do not include multiple designs in a single submission).
  • If your submission wins, your source files must be correct and “Final Fixes” (if applicable) must be completed before payment can be released.
  • You may submit as many times as you'd like during the submission phase, but only the number of files listed above in the Submission Limit that you rank the highest will be considered. You can change the order of your submissions at any time during the submission phase. If you make revisions to your design, please delete submissions you are replacing.

Winner Selection

Submissions are viewable to the client as they are entered into the challenge. Winners are selected by the client and are chosen solely at the client's discretion.

ELIGIBLE EVENTS:

2013 TopCoder(R) Open

Challenge links

Screening Scorecard

Submission format

Your Design Files:

  1. Look for instructions in this challenge regarding what files to provide.
  2. Place your submission files into a "Submission.zip" file.
  3. Place all of your source files into a "Source.zip" file.
  4. Declare your fonts, stock photos, and icons in a "Declaration.txt" file.
  5. Create a JPG preview file.
  6. Place the 4 files you just created into a single zip file. This will be what you upload.

Trouble formatting your submission or want to learn more? ‌Read the FAQ.

Fonts, Stock Photos, and Icons:

All fonts, stock photos, and icons within your design must be declared when you submit. DO NOT include any 3rd party files in your submission or source files. Read about the policy.

Screening:

All submissions are screened for eligibility before the challenge holder picks winners. Don't let your hard work go to waste. Learn more about how to  pass screening.

Challenge links

Questions? ‌Ask in the Challenge Discussion Forums.

Source files

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30033423