Challenge Summary
The Benchmark Metrics and Report Centre (BMARC) is a report request workflow application. This web-based internal application will enable Requestors to submit requests for various report types. Admins and Analysts will review those requests and approve or deny the request. Approved requests are assigned to Anyalyst who will proceed to process them. They will access external systems and gather the necessary data to meet the request. They will attach the data as well as reference documents to the Request as it is processed. They will enter comments as needed. Once the data is gathered and attached, the request is marked as Completed and the Requestor may access the information.
This is an $1800 tournament to design a total of 4 pages for the web based application. There will be 2 pages designed for Round 1 and 2 additional pages designed in Round 2. All four pages are due when submitting for Round 2. The interface will be clear and intuitive for users. The wireframes for the four pages have been provided.
This contest will be run in the Studio Tournament format. Please read the contest specification carefully and watch the forums for any questions or feedback concerning this contest. 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.
Tournament Format This Studio competition will be run as a two-round tournament with a total prize purse of $2000. Round 1 At the end of Round 1 on May 18, 2009, the client will choose three (3) Round 1 winners, each will win $100 and a Design Review. These winners and any member who had a passing submission in round one will be eligible to compete in Round 2 for the additional $1500 in prizes. Round 2 Round 2 will start with the announcement of the three (3) $100 Round 1 winners and their design review from the client.
We are now in Round 2 - if you did not submit to Round 1 you are not eligible to compete in this contest. Congratulations Round 1 Winners on your $100 Prizes: 20080 - abedavera 20106 - thinkcreeper 20079 - abedavera Round 2 pages to design are: 4.4.12.2.4 - View Output Reports Files- this page allows the user (analyst/admin) to attach output report files to the request. they will also be able to view all files already attached and to enter overall comments about the files. Wireframes to reference: 4.4.12.2.4_Output_Reports.html 4.4.14 and 4.4.14..3 - Search Requests - Analysts may search all requests by entering certain criteria. they will receive a list of matching requests from which they can click and go to the detail of the request. The search criteria entry and search results should be designed here. Wire Frames to reference:4.4.14_Search.html, 4.4.14.3_Admin_Result1.html. Round 2 Project Comments/Updates Notes on Tables - Column headings should have a different background color (light gray) compared to the rest of the rows. The font should be bold. - Grid lines should be avoided. - Rows should have a faint blue background color alternating with white. - All text should be black with non-serif fonts such as Arial or Trebuchet MS - The column of default sorting should be indicated with a small arrow, pointing in the direction of the sort. Use up or down arrows to show whether the sort is in ascending or descending order. The presence of the arrow shows which column was last sorted on. Other: - Hyperlinks should have the standard blue color "#0000FF" - Stick to a background color of white as much as possible - If a box is used to delineate a widget or grouping of fields, use a faint gray or blue color. Using dark colors for this purpose is distracting. - Keep the buttons gray - use a faint color upon hover over - something easily noticed but not overpowering - This is an internal workflow application -It is not necessary to entice or dazzle users with "Loud" or eye-catching color schemes or in order to capture attention (something that you might do with an e-commerce application) Keep it clean and simple. - The color red should only be used for a warning or error message. (Or a stop sign icon for example) - Stick to one color and lighter shades of that same color along with gray and white Primary Goals The wireframes provided show the fields and navigation for the four pages to be designed. The client's stated goals for this competition are: - Solid web-application that will enable requestors to efficiently request benchmark reports and estimates and will enable analysts to process and return these requests. It will also enable quick and thorough reporting of the data - Develop an intuitive user interface that allows quick searches and easier input of information It is imperative that the design convey a clear and intuitive user interface. This is an internal web application with a great deal of information on certain pages. The client is looking to convey this information in as clear and easy to use/read format as possible. An important requirement of the web site is that it requires little if any training. The users currently use a Lotus Notes application to perform this functionality. It is critical that they be able to switch to this new web application seamlessly. Round 1 pages to design are: 4.4.12 - View Requests - this is the heart of the system. Every user will be able to view a list of their requests that are in a variety of states. This will be the screen displayed upon successful login. Users must be able to quickly view the list(s) and select the request that they would like to see in detail. Wireframes to reference: 4.4.12_View_Requests.html 4.4.24 - Reference List - Analysts are aloowed to upload reference documents. this page enables them to do that as well as search and manage the list of documents. Wire Frames to reference:4.4.24_Reference_List.html, 4.4.24.1_Hide_Attachment.html, 4.4.24.2_Search_Result.html Branding Guidelines Color choices are up to the designer, however the client prefers white background and clear simple graphics. Judging Criteria All designs will be judged as follows: - Showing an intuitive interface that is easy-to-use. - Creating a clean, simple and professional design that does not feel "cramped" or "stuffy" - All design choices should be focused on usability
Tournament Format This Studio competition will be run as a two-round tournament with a total prize purse of $2000. Round 1 At the end of Round 1 on May 18, 2009, the client will choose three (3) Round 1 winners, each will win $100 and a Design Review. These winners and any member who had a passing submission in round one will be eligible to compete in Round 2 for the additional $1500 in prizes. Round 2 Round 2 will start with the announcement of the three (3) $100 Round 1 winners and their design review from the client.
We are now in Round 2 - if you did not submit to Round 1 you are not eligible to compete in this contest. Congratulations Round 1 Winners on your $100 Prizes: 20080 - abedavera 20106 - thinkcreeper 20079 - abedavera Round 2 pages to design are: 4.4.12.2.4 - View Output Reports Files- this page allows the user (analyst/admin) to attach output report files to the request. they will also be able to view all files already attached and to enter overall comments about the files. Wireframes to reference: 4.4.12.2.4_Output_Reports.html 4.4.14 and 4.4.14..3 - Search Requests - Analysts may search all requests by entering certain criteria. they will receive a list of matching requests from which they can click and go to the detail of the request. The search criteria entry and search results should be designed here. Wire Frames to reference:4.4.14_Search.html, 4.4.14.3_Admin_Result1.html. Round 2 Project Comments/Updates Notes on Tables - Column headings should have a different background color (light gray) compared to the rest of the rows. The font should be bold. - Grid lines should be avoided. - Rows should have a faint blue background color alternating with white. - All text should be black with non-serif fonts such as Arial or Trebuchet MS - The column of default sorting should be indicated with a small arrow, pointing in the direction of the sort. Use up or down arrows to show whether the sort is in ascending or descending order. The presence of the arrow shows which column was last sorted on. Other: - Hyperlinks should have the standard blue color "#0000FF" - Stick to a background color of white as much as possible - If a box is used to delineate a widget or grouping of fields, use a faint gray or blue color. Using dark colors for this purpose is distracting. - Keep the buttons gray - use a faint color upon hover over - something easily noticed but not overpowering - This is an internal workflow application -It is not necessary to entice or dazzle users with "Loud" or eye-catching color schemes or in order to capture attention (something that you might do with an e-commerce application) Keep it clean and simple. - The color red should only be used for a warning or error message. (Or a stop sign icon for example) - Stick to one color and lighter shades of that same color along with gray and white Primary Goals The wireframes provided show the fields and navigation for the four pages to be designed. The client's stated goals for this competition are: - Solid web-application that will enable requestors to efficiently request benchmark reports and estimates and will enable analysts to process and return these requests. It will also enable quick and thorough reporting of the data - Develop an intuitive user interface that allows quick searches and easier input of information It is imperative that the design convey a clear and intuitive user interface. This is an internal web application with a great deal of information on certain pages. The client is looking to convey this information in as clear and easy to use/read format as possible. An important requirement of the web site is that it requires little if any training. The users currently use a Lotus Notes application to perform this functionality. It is critical that they be able to switch to this new web application seamlessly. Round 1 pages to design are: 4.4.12 - View Requests - this is the heart of the system. Every user will be able to view a list of their requests that are in a variety of states. This will be the screen displayed upon successful login. Users must be able to quickly view the list(s) and select the request that they would like to see in detail. Wireframes to reference: 4.4.12_View_Requests.html 4.4.24 - Reference List - Analysts are aloowed to upload reference documents. this page enables them to do that as well as search and manage the list of documents. Wire Frames to reference:4.4.24_Reference_List.html, 4.4.24.1_Hide_Attachment.html, 4.4.24.2_Search_Result.html Branding Guidelines Color choices are up to the designer, however the client prefers white background and clear simple graphics. Judging Criteria All designs will be judged as follows: - Showing an intuitive interface that is easy-to-use. - Creating a clean, simple and professional design that does not feel "cramped" or "stuffy" - All design choices should be focused on usability
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.