Challenge Summary
Welcome to “Cloud Management Portal Wireframes Updates Design Contest”. Our client have an application called Cloud Management Portal (CMP) that being designed to help client developer quickly and easily deploy applications to their cloud hosting platform. The current CMP application have a major problem because the CMP functionality improvements (backends) outpaced user interface improvements.
In our previous wireframes contest, we’ve been successfully tackle major issues in the applications by proposed deployable group solution (see the "Deployable Groups" page in winning wireframes) that allows users to manually create collections of deployables. This time, we need you to expand the solutions and tackle another issues in the applications.
At the end of this contest, we are looking an HTML wireframes which showing an improvements of the workflow solutions for our problems, provides great user experience for the application and can be used as suggestion for the next development phase.
Round 1
initial submissions for client review
Round 2
all contest requirements as stated in contest details with client feedback applied.
The CMP application was created so client developers can “serve themselves”. Right now, the application (CMP) backend has evolved to include more functions than those applying in the the front end. The main goal of this contest is to re-design the CMP application flow to be able perform simultaneous actions on multiple components across the cloud.
In the last contest, we asked participants to create a way for users of the Portal to perform actions on multiple deployables at once. This led to a Deployable Group solution (see the "Deployable Groups" page in winning wireframes) that allows users to manually create collections of deployables. Thinking more about this solution, we realize that, in a sense, these groups already exist in the cloud. However, rather than calling them "groups", they're called "dependencies", which may be a familiar term. Certain deployables call other deployables, and are in turn called by other deployables. And these dependencies often span multiple pods.
We'd like to build upon the Group solution from last contest's winning submission, extending it to incorporate the dependencies that exist in the cloud.
Three Issues Needs to be tackled :
1. As mentioned above, the Deployable Group concept and the existing dependencies in the cloud resemble one another. Because of this, the Portal could suggest Groups to users based on these dependencies. These existing dependencies typically extend across pods, and don't have assigned names. So, the solution should suggest discrete sets of dependencies and show their contents. We're interested in seeing all of the functionality required to suggest a group to a user, and to enable him to create and modify it. The functionality shouldn't be limited to a page devoted to groups – we'd like there to be some flexibility in how groups are created and managed.
2. Deployables in a group can exist across environments as well as across different pods. So, along with showing associated pods, views of groups to indicate the environment and sub-environments in which each deployable of the dependency exists, as well as its state (e.g. "active") in those locations.
3. Deployables can belong to various groups. We'd also like to create a way to show all of the groups that a deployable belongs to, and to show deployables that overlap between groups. So, for example, if Deployable A exists in Group 1 and Group 2, we'd like a user to be able to see, from Deployable A's page, that it exists in each of these groups. We'd also like the user to be able to see, from a more complex view, that Deployable A is part of the overlap between Group 1 and Group 2.
Notes : Please read our documents attached to get more understanding about the current application behaviour and interaction.
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 :
- document references
- questionnaire.zip
- Previous Winning wireframes.
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.