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

Register
Submit a solution
The challenge is finished.

Challenge Summary

Welcome to Morpheus - PC Health Monitor Wireframes Contest. The client of this application would like to build a windows form application that is efficient, easy to use and low resource consuming solution for manual and automatic monitoring, analysis and processing of the hardware/software characteristic and state (health) of all the client company’s user computers.

Round 1

4.4.1    Get Help
4.4.2     Run Monitoring (Manually)
4.4.4    View Textual Report on PC Monitoring
4.4.5    Get Notified on Monitoring Alerts
4.4.6    Schedule Automatic Execution of Tool
- Any notes for the client about your submission
- Because the conceptualization document is too generic, the following reuirements also are in scope:
1. users can see the hardwares and softwares lists.
2. For each hardware/software, user also can see the detail attributes.
3. users can check the health for each hardware/software or selected hardwares and softwares, then generate reports for them manually or automatically.
4. if the report generation is manually, there should be a button when users click it, user can select to generate Textual Report or Visual Graphic Report.
5. it should have a label where users can see the last time of checking PC health.
6. users can see the Microsoft patches that have not been installed in the current PC, and users can make decision to install them or not.
7. users can configure the application, eg: internet connection, log folder, report directory, automatically run interval, ....

Round 2

4.4.3    View Visual Graphic Report on PC Monitoring
4.4.7    Get Information on Installed Microsoft Updates
4.4.9    Reinstall Tool
4.4.10    Uninstall Tool
- All Required uses cases from Round 1
- Any notes for the client about your submission


The client of this application has a company supporting thousands (17,000) of user computers. Those computers are MS Windows-based machines based on different hardware with various installed software.

Users can encounter some problems, errors, performance issues, etc. during using their computers, running regular and custom applications, access the client’s company network and related servers. Sometimes, it is quite clear what’s the root cause of the problem (say not enough memory or hard disk is full), but there are many cases when it’s not obvious if the problem in computer’s hardware, or in the installed software, or in the network connection, or event on the server side of the client’s company. Support teams can provide reliable suggestions on problem settlement only if the characteristics and current state (i.e. health) of user computers is known. The client company is especially interested in keeping the user’s computers in very good state and up-to-date for the technologies/applications used within the company.

The main goal of this project is to deliver an efficient, easy to use and low resource consuming solution for manual and automatic monitoring, analysis and processing of the hardware/software characteristic and state (health) of all the client company’s user computers. Parts of this goal will be logging of acquired results, comparing them with predefined benchmark metrics, alerting users on encountered bad results, providing a visual graphic report on computer health, an automatic installation of software updates to user computers.

Requirements

It is not a web application, so please design wireframes that like windows form application style.

Target Audience

-          User

This is a regular user (an Advisor), having a PC to be monitored by this application.

-          Support

This is a help support staff user, which can re-install or uninstall the Tool for the User.

-          Administrator

This is a management staff user that can configure PC Health Tool and prepare its distribution.

Judging Criteria

Your submission will be judged on the following criteria:

- User Experience

- 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)

Submission & Source Files

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 as clickable HTML files.

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.

Final Fix

As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.

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