Register
Submit a solution
The challenge is finished.

Challenge Summary

 

This project needs to develop a tool called ‘Application Health Dashboard’ , that provides information about Server utilization and usage of various DB2 and WebSphere resources. This dashboard is also expected to provide links to various documents related to the application, its hosting infrastructure and other hosting related policies and standards. This tool will show real time information about server and application resource utilization. The target audience are system administrators, application owners, Application support teams and end users.

This competition is to develop HTML pages that best suggest screen look and feel and navigation from one page to other.


Primary Goals:

The primary goal of this contest is to build a wireframe that will show the layout and page flow for the feature on the site, along with the descriptive information, graphs, and links to documents or other sites. Here are the main areas you will be wire framing:

 

-          Welcome page ‘Application Dashboard’ page, with description about application

-          A landing page that gives a snapshot about all features that the application provides, with any necessary icons.

-          Page to different documentation available related to the application.

-          Page that shows all servers used by the application

-          Page that shows software components used by the application

-          Page that provides selection of what graphs to use, by server or by software component

-          Page(s) with graphs on server utilization like CPU, Memory utilization every 30minsfor a given day.

-          Page(s) with graphs on Software component resource utilization like Java memory, deadlocks, number of connections etc…

-     Every page or graph should have a refresh button to refresh the data in the graph.

      

In addition to these main areas, you will need to wireframe any error and confirmation pages the user may encounter

 

Sample screen shots are shown in appendix

 

Target Audience:

System administrators, System Architects, System Capacity planners, project Managers and Application support teams are the target audience who are familiar with the application, software components.

 

Judging Criteria:

- How well your wireframes provide a consistent navigation and screen transition.

- How well you implement the required data, graphs, user interface and any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)

- Wire frame screens that meet the in number of screen transitions,

- way the inputs are taken and the way next screen appears based on the inputs

- The way user makes selections

-  The positioning of text, buttons, font size,

 

Submission Files:

Wireframes should be built in HTML, Axure, MS Visio or OmniGraffle. The resulting files are not critical in this contest. The most important point is that all the content is 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.

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

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30022299