Challenge Summary
Welcome to the TopCoder Cockpit Asset View Wireframe Repost Contest. The objective of this contest is to create wireframe for TopCoder Cockpit application specified for Asset View based on provided concept document and In the end of this contest we are looking for a process flow and layout design of the pages mentioned below that are part of the whole application. This application must be user friendly, intuitive, and easy to use.
This is REPOST contest, we not satiesfied on previous submission results. This time we need you not focus by simply uses table style of present each fields. Impress us, suggest any better User Experience. Make sure you understand what we want achieved on contest spec details. If you got any questions, LET'S DISCUSS on forum. We want make everythings as clear as crystal.
Round 1
Your submitted solution for client review.
1. View project documents
2. Upload project document
3. Remove document
Any comments about your wireframe, make sure all pages have correct flow!
Round 2
Final pages of wireframe contains these functionality
1. View project documents
2. Upload project document
3. Remove document
4. Download document
5. Manage document permissions
Any comments about your wireframe, make sure all pages have correct flow!
Contest Details
TopCoder is going to add a new "Asset View"into new TopCoder Cockpit. Currently, everything in Cockpit is very focused on displaying and aggregating contest information within projects. However, it's very difficult for a user to access their latest deliverables and assets for the project.
The main goal is to have a central place for the cockpit project users to upload and manage assets / deliverables within a project. The assets / deliverables of a project can be any latest deliverables and assets produced by the contests of the project. They can also be any documents related to project that the customer wants to upload and share.
The benefits can be achieved by this project:
- Users has a central place to get the latest documents of a project so people always know where to get the latest version of the asset / deliverable. Now customers often say they have no idea how to find the latest version.
- The assets / deliverables can be included by the upcoming contests so there is no need to upload them to contest requirements specification again.
- The document versioning can help user to track the history of the documents.
This contest is an integration project to Cockpit Project Dashboard. These following requirements need created in your submission. Check attached (Project Dashboard.zip) to help you get better visualization how current Cockpit Project Dashboard looks.
1. View Project Documents
- The Project Dashboard will show all the documents uploaded for the cockpit to the project stakeholders.
- Some documents may have restrictions set on them and not all users will be allowed to access/download them.
- The uploading documents will be sorted by uploading time and grouped day by day.
The user can sort the uploaded documents by:
- Date and time uploaded
- Document name A-Z
- File Size
- Uploader
The user can filter the uploaded document by:
- Document Category
- Document Uploader
- For each file, the following will be shown:
- File Type Icon
- Filename
- Description
- Category
- Filesize
- Date and time uploaded
- Current version number
- Uploader
- Upload time
- If the document file is a picture, it will be possible to see a picture preview in a modal window.
2. Upload Project Document
- The Cockpit application will allow project stakeholders to upload different documents to a Cockpit project.
- This function will allow the ability to upload important files for the whole cockpit project such as client's questionnaire, Project's game plan, requirement documents, important documents from client etc.
The document uploaded will need the following information defined:
- Name - the name of the file. Automatically collected from the uploaded file. The name will contains the file name and file extension.
- Category - defined by the user. There will be a standard set of category for user to choose. User can choose add a new document category to the project.
- Upload time - automatically populated from the timestamp of the upload operation
- Description - the user inserted description of the uploaded file. This is optional.
- Possible version number - automatically done by Cockpit if another file with the same name exists
- Access restrictions:
-- Public - no restrictions
-- Private, the following types of stakeholders can be selected and access rights can be given (multi-selectable):
---- Clients
---- Project managers
---- Copilots
- The user could also choose to upload a new version of an uploaded file. It should be similar to upload a new file except the uploaded new version will replace the old file. The old file will be moved to the history list but still downloadable.
- The user should be able to add multiple files to upload at one batch.
- Drag and drop of files to upload will be supported (HTML5)
- When uploading an upload progress bar should be displayed to show the progress of the uploading.
- It's recommended to use AJAX to improve the user experience.
To support project assets management, the standard set of project file categories will be :
- Conceptualization
- Specification
- Architecture deliverable
- UI prototype
- Storyboards
- QA plan
- Copilot Project Game Plan
- Copilot Development Strategy
- Client Questionnaire
3. Remove Document
- Any of the uploaded documents can be removed.
- The user can only remove the documents on which he/she has write access to.
- The user can also remove a old version of the existing uploaded document.
- Confirmation should be prompted to user when delete a file.
4. Download Document
- The project uploaded documents can be downloaded.
- Only users with read access permission on the document can download them.
- All documents that can be viewed (same access settings) can also be downloaded.
5. Manage Document Permissions
- Contest mangers will have the ability to manage permissions to the uploaded documents.
- The updated Cockpit application will contain a special button which will launch the modal dialog with the restriction assigned for the project can be updated.
- The document permissions dialog will be of the same type as the one for managing permissions with read, write and read/write permission scheme for each uploaded project document.
- The default document permission scheme is extrapolated from the document type (public private) from the metadata associated with the uploaded file.
This means that the depending on the settings on upload, restrictions can be configured from that point on with not additional effort.
Target Audience
- New Customers
- Non expert Customers
- Administrator and Copilots
Judging Criteria
- How well you update the navigation and it makes sense/helps the user
- Cleanliness of your layout
- User Experience
- Introduce some up-to-dates features on wireframe pages
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
Wireframes should be built in HTML and Axure. 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.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include ia notes.txt file.
Final Fixes
As part of the final fixes phase you may be asked to modify content or user click paths.
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.