Challenge Summary

Welcome to "Green Eel - Cloud Automated Testing Application Design Challenge". In this challenge, we are looking for topcoder community help to create a new look and feel for our application called Green Eel. We're also looking to the community to come up with a beter UI/UX concepts for the apps - we're absolutely open to creative solutions! At the end of this challenge, we are looking to have a new UI/UX solution for the application. Join with us NOW!!

 

Round 1

Initial design for client review

Round 2

All requirements as stated in challenge details with client feedback applied


About Green Eel
Green Eel is an application that help web development teams improve their ability to do full stack automated testing with Selenium. Users can log into the site and ask for virtual machine to be made in a Cloud that will come pre-installed with an automated testing platform. Once the order has been processed, the user will be able to do RDP / VNC into the environment and begin learning or using the automated testing technology. They will have the ability to destroy or pause the environment at any time.

Branding Guidelines :
- We prefer to use single page site interactions (parallax). 
- As much as possible, follow flow interaction and layout from http://www.projectjellyfish.org/, use this site as your UI/UX reference when create your design.

Design Considerations
- Looking for modern, intuitive user interface
- Focus on the design being a great user experience, think simple but effective solutions!
- Give importance to the overall layout and think on how a user would interact with the content on the page.
- Show all the screens and provide a user flow/click-path and navigation, so we can see how the interactions fit together in the application
- Branding colors, fonts are open to the designers. 
- What should the priority features be?
- How quickly could you find information?
- Stock Photos: Feel free to use any images related to this concept.

Screen Sizes
- Desktop: 1280px width and height as required.
- Will be responsive design. Keep this in mind while designing 

Required Screens
01. Login/Logout Screen
- User needs to have ability to login/logout in the apps.
- User needs to login first to be able use features in the apps.
- Provide generic login features in your design

02. Create Order Screen
- Once user successfully login to the apps, they will be able to create an order for a automated testing virtual machine 
- Simple order form contains set of manual form fields or simply choose templates packages for the automated testing virtual machine?
- User should be able to submit their order form into the apps and get confirmation message that their order status is on progress. 
- Once user submitted the order form, they will be able to check their order status in the apps.

03. View Order Status Screen
- Upon successfull login, user will be able to see all his order status from the application.
- There should be several ways to see the view order status, maybe via list, details, or tiles.
- User will be able to dig into details of their order status.

04. Order Confirmation Screen
- Once the order is complete, user should have some kind of notification to receive information about the virtual machine to access it through RDP or VNC
- Feel free to provide the best interaction for user to receive the notification message.

05. Start/Stop/Destroy VM Screen
- User can start navigate and testing the VM once their order is complete.
- They will be able to start the automated testing VM, or Stop it.
- They will be able to delete/destroy the VM if they no longer needs it.
- The apps should account for api calls as follows :
* Post Login/
* (Put /Order/{browser: 'firefox', environment: 'windows', userID: 123} - Response {orderId: 123}
* Get /Order/Status{orderID} - Response {orderStatus: [accepted | provisioning | complete]}
* Post /Logout

Important:
- Keep things consistent. This means all graphic styles should work together.
- All of the graphics should have a similar feel and general aesthetic appearance.

Supporting Documents
- We have a wireframes references in this challenge, you can use any aspect from the wireframes to create the best UI/UX concepts.
- You need to post in forum for your topcoder username in order to get the documentation.
- If You currently participating in the Green Eel wireframe challenge, joining this challenge means you are going to be disqualified from the wireframe challenge automatically.

Target User
- IT professional, Web Development Teams, High tech person that aware of the latest technology.

Judging Criteria
- How well you plan the user experience and capture your ideas for the homepage visually
- Cleanliness of your graphics and design
- Creativity and ease-of-use is key to the success as it must be engaging to users.

Submission & Source Files
Preview Image
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 File
Submit JPG/PNG for your submission files.

Source Files
All original source files of the submitted design. Files should be created in Adobe Photoshop and saved as layered PSD file, or Adobe Illustrator as a layered AI file.

Final Fixes
As part of the final fixes phase you may be asked to modify your graphics (sizes or colors) or modify overall colors. We may ask you to update your design or graphics based on checkpoint feedback.

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.

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:

2015 topcoder 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

  • Layered PSD files created in Adobe Photoshop or similar
  • AI files created in Adobe Illustrator or similar

You must include all source files with your submission.

Submission limit

Unlimited

ID: 30049489