Challenge Summary

Welcome to the Corningstone Application Wireframe Contest Part I.
The objective of this contest is to create the HTML wireframes as starting base of Corningstone application based on provided conceptualization document.

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 and bring new User Experience when customer use the application.

Round 1

Your submitted solution for client review:
4.4.1 Login
4.4.2 Logout
4.4.3 Access application dashboard
4.4.4 Get Help
4.4.5 Manage Application Account
4.4.6 Print Application Data
4.4.7 Change application currency
4.4.8 Undo application change
4.4.9 Redo application change
4.4.10 Import QuoteExpress job
Any comments about your wireframe, make sure all pages have correct flow!

Round 2

Round Two (2)
Final pages of wireframe contains these flow:
4.4.1 Login
4.4.2 Logout
4.4.3 Access application dashboard
4.4.4 Get Help
4.4.5 Manage Application Account
4.4.6 Print Application Data
4.4.7 Change application currency
4.4.8 Undo application change
4.4.9 Redo application change
4.4.10 Import QuoteExpress job
4.4.11 Manage job plans
4.4.12 Manage items
4.4.13 Manage bids
4.4.14 Manage submittal documents
4.4.15 Manage item packages
4.4.16 Manage customers information
4.4.17 Manage vendors information
4.4.18 View bid calendar portlet
4.4.19 View validation errors
4.4.20 Produce material list
4.4.21 Sort data
4.4.22 Filter data
Any comments about your wireframe, make sure all pages have correct flow!


Contest Details
The purpose of this project is to improve current Corningstone application. Current application has been developed for some time now and its limitations are starting to hold back the business. This project will implement from scratch a new application and will build based on a more scalable and reliable platform and leveraging a proven application architecture that comes with good support and wide developer base able to sustain future growth of the application and possible scalability requirements.

Wireframe Requirements:
- Your wirefame solutions must useful for all users.
- Your wireframe must represents all pages and flows from Corningstone-Application-Conceptualization.doc.
- Use conceptualization document as a guide, if there is better way to display information, feel free to reflected on your wireframe design.
- This application will be developed in a web-server use HTML5 and running on Desktop and Tablet platform.
- Make sure your wireframe is possible to build in future development.
- Feel free to suggest any great ideas to leverage User Experience of this application. Give notes for us.

These following functionality required on your submission.
All information below just starting point. Read more details information at Conceptualization Document!

I. User
4.4.1 Login

- User can login by entering username and password.
- How validation error looks?
- Show login flow for 3 different level : "User", "Application Administrator User " and "System Administrator".
- Create empty page for "Application Administrator User " and "System Administrator". It will take care in another contest.

4.4.2 Logout
- Click this logout will be able take user out of system and then landed on Login page.
- There will be an automatic logout on expiration of the session timer. What message can displayed?
- If the user is inactive for a configurable amount of time, then s/he will be automatically logged out.

4.4.3 Access application dashboard
- That dashboard will collect data and features that are most important and relevant to the user role.
- The dashboard can be customized by users by having the abilities to move portlets by the user to create a custom layout.

4.4.4 Get Help
- The help information will be accessible via a GUI element like – like by pressing “Help” hyperlink or button.
- This tooltip information will be displayed to users when hovering over a given user interface control.
- Some visually attractive help (like getting started) is needed, so the user will be quickly and easily get involved in the usage of the application.
- There will be a downloadable full Getting Started document on this web-application usage.

4.4.5 Manage Application Account
- Users can configure their application account information and change their settings.
- Check required fields at concept doc.
- The users can also reset their current password which will be generated and sent by the application to their configured email address.

4.4.6 Print Application Data
- Any of the application data will support printing functionality directly.

4.4.7 Change application currency
- Users can change the currency type that the application uses for the display of item prices.
- The application will support multiple currencies and currency symbols.

4.4.8 Undo application change
- The application will support the ability to undo a large number of application changes.

4.4.9 Redo application change
- The application will support the ability to redo a large number of application changes.

4.4.10 Import QuoteExpress job
- The user can initiate an export to PowerScope which will connect to the PowerScope web application.
- From the QuoteExpress, an import wizard will retrieve item information, which can be introduced in the PowerScope application to start a bid.
- The application will automatically detect duplicates with the current session data and flag (select) them so that the user will have a quick option to remove all duplicates.

4.4.11 Manage job plans
- The user can view and manage the job plans
- note that the initial template can be imported from QuoteExpress job plan.

4.4.12 Manage items
- The user can manage the items required to complete the given job.
- For the items page there will be two tabs in detail screen which will display the for each item the following information:
-- All the bids that contain the given item
-- All the pages that contain the given item
- Check required fields at concept doc.

4.4.13 Manage bids
- The user can manage the items required to complete the given job.
- Additionally, bids will be have a special lock and unlock property.
- Check required fields at concept doc.

4.4.14 Manage submittal documents
- The user can manage the submittals documents.
- The user can manually change the settings of these submittal documents.

4.4.15 Manage item packages
- The user can manage the list of item packages.
- Packages are grouping of items that are used to perform common tasks.
- Check required fields at concept doc.

4.4.16 Manage customers information
- The user can manage all the customers configured in the application.
- Check required fields at concept doc.

4.4.17 Manage vendors information
- The user can manage all the vendors configured in the application.
- Check required fields at concept doc.

4.4.18 View bid calendar portlet
- Bids can also be displayed in a special bid calendar portlet that will display the most important timelines of filtered bids in an intuitive graphical manner.
- The "Bid Calendar" dashboard portlet will display the current month in a calendar view with buttons to scroll to prior and future months.

4.4.19 View validation errors
- The application will automatically perform data validation on all fields and dependency documents.
- The warning can simply be cancelled and the user can override the setting and proceed with the other data entry steps.

4.4.20 Produce material list
- The user can manage the material list required to complete the given job.

4.4.21 Sort data
- Sorting will have three possible values which are cycled by repeated pressing: o
-- default (default order as the data is retrieved from the database)
-- ascending
-- descending

4.4.22 Filter data
- The user can filter the information displayed in any tabular control from the application.
- This data information is normally viewed in a table format so the sorting functionality can be implemented by clicking on the table header.

Target Audience
- Internal User

Judging Criteria
- User Experience
- Completeness and accuracy of the wireframe as defined in the attached requirements.
- How well your wireframes provide a consistent user flow

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 or 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. Keep your source files out from this submission folder.

Source Files
All original source files of the submitted ideas. If you would like to submit notes please include 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.

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.

ELIGIBLE EVENTS:

2014 TopCoder(R) 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

  • HTML
  • RP file created with Axure

You must include all source files with your submission.

Submission limit

5 submissions

ID: 30034684