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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Currently our clients Morpheus want to improve the technical environment availability reporting within the Program. The Program oversees several projects and is currently challenged with assessing system availability and its affect on project test teams within the program.  This purpose of the application is to provide senior management with improved real-time access to the following information related to Program testing activities:

  • The availability of systems that affect project test teams
  • The impact of system downtime on project test teams

Round 1

You need to show the UCs 4.4.1 ~ 4.4.12

Round 2

- All required screens mentioned in the requirements section
- Any notes for the client about your submission


The customer needs to monitor a testing effort organized into several releases, which are in turn made up of multiple projects, known as the Program. Each project has its test team, which depends on multiple systems for conducting the testing effort. These systems are used by the applications under test. When a system fails, any application under test that depends on the system cannot be tested correctly. This affects the productivity of the project testing teams. Currently, the Program is using around 40 different systems.A new application is needed to monitor the systems on which the testing teams depend. Basically, the application will be a dashboard to monitor the system availability, the current and historical outages and the incident records created to address the outages. The customer desires to improve the system availability reporting mechanisms within the Program.

As part of the specification and architecture phases for this application, a static HTML prototype should be created to demonstrate the user interface functionality. This HTML Prototype will be used as the foundation for future implementation of this system.

If you have any question, please raise in the forum, we will answer you as soon as possible.

In this wireframe contest, the goal is to design the workflow of this application.

Detail requirements:

There are 2 roles of this application. You need to design the wireframes for the Senior Managers and the admins. The UCs are 4.4.1 ~ 4.4.25


Primary Goals:

The goal is to develop an easy to use application

Target Audience:
All common users, mainly office employees

Judging Criteria:
The wireframes need to:

Define how the user would work within the application.
Completeness and accuracy of the wireframe as defined in the attached requirements.
How well your wireframes provide a consistent user flow
How well you implement the required data and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

Preview Image

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

Submission File

All Requested Contest Requirements stated above.

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.

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
  • JPG - Image
  • description

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30024918