Challenge Summary
Welcome to “Cloud Management Portal Wireframe Design Contest”. Our client has an application called Cloud Management Portal (CMP) that is being designed to help developers quickly and easily deploy applications to their cloud hosting platform. The current application has a major problems because the functionality improvements (backend development) outpaced their user interface improvements. The goal of this contest is to is re-design the CMP application click-path/user flows to accommodate new features and fix the existing workflow problems.
We are looking for HTML wireframes to quickly improve the user experience can capture new workflow solutions.
Round 1
Initial submission for client review
Round 2
All contest requirements with client feedback applied.
Contest Description
The CMP application was originally created so developers could “serve themselves”. Recently the application development (backend functionality) has evolved to include more functions then what users are seeing on the front-end. The main goal of this contest is to re-design the CMP application user flow to be able to perform simultaneous actions on multiple components across the cloud.
Contest Requirements :
Issue 1 : Re-create and Understand the current portal general functionality
- This issue should be easy, all you need to do is to re-create the general flow of this application so user can easily see the apps interaction.
- The current flow can be found under Portal_contest_overview_1.rtf (portal functionality) and apps_screenshot.zip :
- By default, user will open CMP_Cloud_Landing_Overview.png when the first time open "ICP/TP" in CMP application.
- in "CMP_Cloud_Landing_Overview.png", you will be able to see Pods available in the cloud, click any Pods available and it will open "CMP_Pod_Page_Overview.png" showing details of each POD.
- in page "CMP_Pod_Page_Overview.png", you will see details selected POD information and several action that can be done in this page.
- If you click "deployable" link in left side area, it will open "CMP_Pod_Deployable_List_view", click any of the deployable listed in this page and it will open "CMP_Deployable_Page_Overview".
- Else if you click any of deployable in Pod compartments, a small drop down appears under the deployable with and options of "more info" link, and if you click that link, it will open "CMP_Deployable_Page_Overview".
- From the "CMP_Pod_Deployable_List_View" and the "CMP_Deployable_Page_Overview", the "Stage" button will trigger the "CMP_Stage_Pop-up".
- The CMP_Stage_Pop-up can also be triggered from CMP_Pod_Page_Overview by clicking a deployable in "Ready" column in a compartment and selecting "Stage" from the drop-down that will be displayed.
- Likewise, the CMP_Pod_Deployable_List_View and CMP_Deployable_Page_Overview "Activate" and "Deprovision" buttons will trigger the CMP_Activation_Pop-up and CMP_Deprovision_Server_Pop-up respectively.
- The CMP_Activation_Pop-up can also be triggered from CMP_Pod_Page_Overview by clicking a deployable in the "Checkout" column in a compartment and selecting "Activate" from the drop-down that will be displayed.
- The CMP_Deprovision_Server_Pop-up can also be triggered from CMP_Pod_Page_Overview by clicking a deployable in the "Checkout", "Active" (admins only), or "Backout" columns in a compartment and selecting "Deprovision" from the drop-down that will be displayed.
Issue 2 : Tackles the current issue for handle Multiple Actions in the CMP application
- In the current application, a user can perform one action on a deployable at a time. This works well for the most part, however, there are often situations when an action needs to be performed on a group of deployables. For example, a group of applications and services that are dependent on each other to run successfully would need to be activated at the same time. This is what we'd like to solve. How might a user perform actions on multiple components in multiple environments and multiple pods?
- Bundle actions can be performed relatively simply on items in a list. A group of selected deployables within a pod, for example, could be deprovisioned at the same time (see CMP_Pod_Deployable_List_View and CMP_Deprovision_Server_Pop-up) because the deprovision action is a one-click action. The same applies to activating, deprecating, and rolling back deployables (see also CMP_Activation_Pop-up). However, when figuring out how to perform other types of bundle actions:
- For actions such as promote, repackage, add credentials, and stage, multiple settings must be selected (see CMP_Stage_Pop-up). Unlike activating, for example, which only requires a user to press "Activate," when staging a deployable a user has to select the type of virtual machine template, profile, data fabric, and number of virtual machines per data center for each deployable.
- The deployables that need to be acted upon may exist across different environments and different pods. Because the navigation of the Portal reflects the structure of the cloud, we currently don't have a way to view multiple pods or environments at once. So, while a user could go to Pod A to stage a deployable and then go to Pod B to stage a dependent deployable, this becomes more complicated and time-consuming when a user needs to stage a dozen deployables. This applies, too, to deployables within a pod. How might a user choose stage settings for and stage ten deployables at once?
- Because deployables are often moved in groups, five deployables that were staged a few weeks ago may now be ready to be activated. How might a user access and activate that same group?
Target Audience
- Information Technology professionals
- Code developers
- Test specialists
- Deployment specialists
Judging Criteria
Your submission will be judged on the following criteria:
- User Experience
- Completeness and accuracy of the solution to solve client problems.
- How well your wireframes provide a consistent user flow
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
Generated HTML files with all the 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.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Attachment :
- cloud_framework.zip
- client_requirements_document.zip
- apps_screenshot.zip
- client_questionnaire.zip
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.