Key Information

Register
Submit
The challenge is finished.

Challenge Summary

Welcome to OPM Wireframes Contest. We need you to create HTML wireframes to represent an existing desktop application as web-based.


The primary goal of this contest is to create HTML wireframes based on an existing desktop application. This contest is not typical, in that we want you to COPY the desktop application, and make NO improvements. Just get it as close as possible so that your wireframes match the application exactly. No new features or improvements are required, and at this time, we do not want them. If your submission includes new features or improvements, it will be disqualified.

It would be good for you to know our development strategy for this project. We’re first going to copy the desktop application into wireframes (this current contest). After we get these initial wireframes we’ll round up the features and requirements with the client and launch another wireframes contest afterwards to make improvements, and turn the wireframes into web application wireframes (versus desktop application wireframes). This means you should speak out your thoughts in the forums in order to clear any doubt to understand this initial phase.

Notice there is not a conceptualization document attached in this contest. Instead we provide access to a VM (Virtual Machine - remote server connection) with a working demo from the existing application and recorded videos that explain how the current application works. You need to capture the application features and data (as best as you can).

About OPM
The Office of Personnel Management (OPM) has an existing legacy application called the Service Credit Redeposit/Deposit System (SCRD) that is in charge of the management of the retirement plan monetary benefits system.

Accounts are established for federal employees for periods of federal employment that are either not covered by retirement deductions (deposits), or were covered and later refunded (re-deposits).

The SCRD application computes deposits and re-deposits, create an initial bill, post payments, and send out receipts to federal employees for periods of federal employment service that were either not covered by retirement deductions (deposits), or were covered and later refunded by the federal government (re-deposits).

SCRD Application on VM

We have a copy of the application running on a virtual machine (VM). You will need to use a remote desktop connection tool in order to enter the VM and use the existing SCRD application. In order to gain access, please email the PM at rsial@topcoder.com. If you need assistance on the connection don’t hesitate to ask in forums.
- See how to connect to a VM using Windows OS instructions.
- See how to connect to a VM using MAC OS instructions. You could use MS Office's RDC too.

General Requirements
- Produce HTML click-through wireframes that are as close as possible to the actual working SCRD application. The wireframes will be based on the demo recording walk-through (download and watch all 6 videos), and the SCRD application running on the VM. As optional resource, there are application screenshots attached (SCRD_Screenshots.zip).
- Read SCRD_Application_Walkthrough_Test.doc (section 2, desktop application functionality) to get an idea in details of the application data.
- The design should be simple, user-friendly and easy to understand. Avoid over populating spaces with too many form elements.
- Develop as many pages/elements you need to complete all the requirements.

Wireframes Requirements
There are several user roles in this application. For now, we’re focusing on the RIO User role which has access to all the application features. Check the basic features brief you should cover in this contest (scope):

Login
- User needs to enter username and password to enter the application.

Logout
- User should be able to leave the application.

Employee
- A user should be able to create and edit accounts and to perform search/filter.
- Full account data can be seen in screenshot #05.

Service History
- Samples can be seen from screenshots #08 - #12.

Payment History
- Samples can be seen from screenshots #13 - #14.

Account Summary
- It shows an area with information about a selected employee the user is working on.
- Account summary can be seen (filled in) in screenshot #05.

Account Notes
- It shows a placeholder with notes added by the system users.
- A single note contains date, author and string.
- Samples can be seen in screenshots #06, #07.


Target Audience
The main users of this web application will be financial planners and government employees.

Judging Criteria
- Capability to capture and represent the application features.
- User experience..

Submission File
All requested contest requirements/screens as clickable HTML files unless otherwise stated in the contest details.

Source Files
Wireframes should be built in Axure. The resulting files should have generated HTML files. Also, all the content must be listed and the pages are linked together to show page flow.

Preview Image
Create a 1024x1024 JPG or PNG file in RGB color mode and place a screenshot from your submission within it.

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

SHARE:

ID: 30032322