Renewals Management Tool Wireframes

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

Register
Submit a solution
The challenge is finished.

Challenge Summary

This contest goal is to help define the user experience of for a new Renewals Management Tool (RMT - Web Application) to support the client’s Software Renewals Subscription and Support (S&S) business.  The application allows sales representative to work with renewal opportunities throughout the process of renewing software and support subscriptions.  Sales Reps will be able to view, update and create renewal opportunities.  The application will also support the creation and management of Support Extension Requests records, Lead Pass records, Reinstatement Win records, and Manager Forecast records.  Users will be able to use search functionality to find these records.

Round 1

Please provide wireframes based on roles.

Each role could view their own pages and Admin could view all pages. (You just need to provide a separate home page for Admin, other pages for admin is same for the normal user)

Context Diagram - Proposed - Users - S&S Forecasting.vsd and Concept Document Section 3.3 could help you to understand the functions of each role and high level workflow.

Use Case 4.4.3: Home Page - Please design separate home pages for each role. You can find the expected functions of each user in Context Diagram - Proposed - Users - S&S Forecasting.vsd (Concept Doc)

Use Case 4.4.4: Help Page - We just need a general popup window to display the help content. e.g. Add '?' button near some web elements (button, input box, etc.). When user click it, it should display a popup window.

Use Case 4.4.5~4.4.8: Search Page and Results Export, Record Mass Update - Round 1 should provide these use cases for Lead Pass (Function) - Entitlement Rep (User Role).

Only Admin and Entitlement Rep could view following pages:

Use Case 4.4.9~4.4.10: View Lead Pass Records and Export

Use Case 4.4.11~4.4.14: View/Add/Edit/Assign Lead Pass

Round 2

All Round 1 pages are required and following pages are required for Round 2:

Use Case 4.4.5~4.4.8: Search Page and Results Export, Record Mass Update - Round 2 should provide these use cases for following View Functions.

Admin could view all pages and please check Context Diagram - Proposed - Users - S&S Forecasting.vsd to get the Functions - Roles mapping.

Use Case 4.4.15~4.4.16: View Support Extension Requests and Export

Use Case 4.4.17~4.4.20: View/Add/Edit/Approve/Reject Support Extension Request

Use Case 4.4.21~4.4.22: View Opportunities and Export

Use Case 4.4.23~4.4.25: View/Add/Edit Opportunity

Use Case 4.4.26~4.4.27: View Reinstatement Win Records and Export

Use Case 4.4.28~4.4.30: View/Add/Edit Reinstatement Win

Use Case 4.4.31~4.4.32: View Manager Forcast Records and Export

Use Case 4.4.33~4.4.35: View/Add/Edit Manager Forecast

Use Case 4.4.36~4.4.38: View Custom/Saved Report and Export

Use Case 4.4.39~4.4.41: Save/Modify/Delete Custom Report Configuration

Use Case 4.4.42~4.4.44: Delete Quote/Extension/Opportunity

Use Case 4.4.45~4.4.47: Add/Modify/Delete Data Field


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:

2012 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: 30027236