Challenge Summary

Welcome to the VUC Wireframe Design Contest!
The VUC (Value Unit Converter) is a mobile application for sales person to quickly determine a proposal price.
We’re looking for you to design a clean and easy to use mobile wireframe to capture the workflow and functionality from provided document.

Round 1

Submit for milestone review/feedback, at least include following screens
The 3 functions under 320x480 and 1024x768
 Value Unit conversion (based on an exhibit)
 - D
isplay and pricing of a specific product using its associated Value Unit Exhibit
 - Creation of an inventory configuration for pricing of multiple products

Round 2

Submit for final review
- All required screens
- Any update from milestone feedback 


Overview
The Value Unit Converter application is intended to provide the sales person the ability to quickly determine a proposal price using a mobile smart device.  Determining a proposal price, particularly for software offerings priced with Value Units (VU) requires a complex calculation.  If a client requests a quick price, the sales person either has to use a laptop application or access the IBM network to determine the price.   Often access to the IBM network is not available or not practical, which delays getting the price to the client, potentially impacting the sale.

The GUI works with three areas of value unit pricing:
- VU Exhibit – This is the conversion of a system characteristic (such as MSUs) to the number of Value Units used for pricing. 
- Products – This is working with a specific product to determine the price based on the number of value units calculated using the associated exhibit and the desired system parameters.  Each product will have one VU Exhibit associated with it.
- Inventory – This is a collection of products that represent a configuration that is being priced. 

Due to the wide variety of mobile devices, the design point should be such that both HTML5 and native Android implementation could be supported.

Primary Goals
The goal is to develop a wireframe of a GUI suitable for mobile devices of various sizes.  The initial development is targeted at a minimum device level of Android 2.2, but should allow for support of tablet sized devices.  This wireframe may also be used in implementation of an HTML5 web based GUI to support non Android devices.

How to create wireframe?
- You can build wireframe by Axure, and export to HTML files.
- Make sure all pages have a good click-path/user flow.
- Provide comments in your wireframe screen - help guide the client through your solution/idea

Requirements
- Following Mobile User Experience best practice (such as Android User Interface Guidelines), note your layout, UI element size and text size should work well under mobile and like a mobile application.
- Size: 320x480, 480x320, 1024x768, 768x1024. Although we only required 4 size here, but your UI layout should be simple and flexible to fit any size screen.
- Functions: (totally follow functions.doc)
  -
Value Unit conversion (based on an exhibit)
  - D
isplay and pricing of a specific product using its associated Value Unit Exhibit
  - Creation of an inventory configuration for pricing of multiple products

Target Audience
The target audience for this application is the sales organization.  It is intended to provide a quick, easy method for generating a proposal.

 Judging Criteria
- The completeness of the design with regard to data display and flow between screens will be the primary criteria.  Screens should be well organized, with a logical data presentation. 
- How well your design follow Mobile User Experience best practice, and work well under different size. 

What to Submit
Preview JPG/PNG Image File
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 ZIP File
All requested contest requirements as clickable HTML files or in the format stated in the requirements above.

Source ZIP File
All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the side bar.

Final Fixes
As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. See more information about Final Fixes.

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: 30028837