Challenge Summary
The client for this project has an existing Quality Incident Reporting (QIR) system. This existing application was created using SharePoint and is used for creating and managing quality incident records. The goal for this project is to build a new Quality Incident Reporting application using .NET (based on the existing QIR application).
For this contest, we need you to create Wireframes for the new Quality Incident Reporting application. We have provided screenshots and a demo of the existing application for you to understand what the existing system does. The screenshots also include markup to show a few areas of the existing application that should be changed / modified in the new application.
We look forward to seeing your creative wireframe designs!
Round 1
Round 1 will focus on the following user functionality for the new QIR application:
1) Quality Incident Report
2) Manage Cause Categorizations
3) Manage Codes
4) Manage Dept Regions
NOTE: See the video demo and existing QIR screenshots to understand what functionality is needed for the new application. Please make sure to include the changes described in the screenshot notes / comments and the changes listed in this challenge spec If anything is unclear, please ask for clarification on the forum and we will be happy to help!
Round 2
In Round 2, you will need to include all Round 1 screens (updated based on milestone feedback). For Round 2, you must also include all the remaining functionality descibed in the project documentation, including the following screens:
5) Manage Dept Notification Lists
6) Email Templates
7) Event Log
Primary Goals:
The goal of this project is to design and develop a new Quality Incident Reporting application in .NET based on the existing QIR application with a few modifications and changes.
For this challenge, we are asking you to put together wireframes for the new Quality Incident Reporting application. The new QIR application needs to include all the functionality of the existing system, along with some small enhancements and improvements.
The QIR demo provided will walk you through what the existing application does. The existing QIR screenshots also show what the existing application does and looks like. Please pay close attention to the notes and mark up included on the screenshots! These notes / comments explain a few areas the client would like changed from the existing application in the new QIR application. Some additional details about changes are explained below.
Changes from Existing QIR Application:
There are a few key changes from the existing system that the client has requested. Below are some of of the major changes that should be captured in your wireframe design:
2) The "QIR Form Changes" worksheet (in the attached file "Quality Incident Report Enhancements - July 2014.xlsx") has a list of fields to be removed, added, and changed.
3) The "Manage Cause Categorizations" page should be redesigned for performance and usability (no longer by dept).
4) "Form Buttons" worksheet (in the attached file "Quality Incident Report Enhancements - July 2014.xlsx") are buttons that should be included for the form.
5) "Classification" worksheet (in the attached file "Quality Incident Report Enhancements - July 2014.xlsx") defines a controlling picklist. For example, if you first choose Plant, then a 2nd picklist is filtered to include "Plant make line isolation, Plant shutdown, etc". If you then pick "Plant make isolation", then only show fields 1, 2, 3.
6) "Root Cause" worksheet (in the attached file "Quality Incident Report Enhancements - July 2014.xlsx") is similar to Classification: There are 3 dependent picklists. If you choose "Equipment defects", then "Mechanical failure", you then have options 1-6. Sometimes users know the lowest level Classification or Root Cause, but don't remember the parent picklist values. Is there a way to quickly enter the final value (e.g. search, or tree, or type ahead, etc)? We are open to your creative ideas to solve this!
General Requirements:
- Produce HTML click through wireframes that can be used to demonstrate all mentioned functionalities as required in each round.
- The new application must be very easy to use and intuitive. Keep that in mind when designing your solution.
- You MUST cover all functionality shown and described in the project documentation (demo and screenshots, including changes described in the screenshot notes / comments and changes listed above on the challenge spec).
- The new application needs to match the look-and-feel of the client's existing system, although we would love to see your ideas on ways we can improve the new application without moving too far away from the existing application look-and-feel.
- Your wireframe must represents all pages and flows from project documentation. You should use that as a guide, but if there is better way to display any information, feel free to reflect that on your wireframe.
- You must use wireframes notes on every single page you design to explain what items are addressed on that page, what things you added/changed/removed, and to make your idea easier to understand so the client can provide constructive feedback.
Project Description:
The client for this project has an existing Quality Incident Reporting (QIR) system. This existing application is used for creating and managing quality incident records. The goal for this project is to build a new Quality Incident Reporting application using .NET (based on the existing QIR application). A video demo of the existing QIR application has been provided for you to understand and capture the functionality that can be performed in the existing application.
Project Documentation:
The following documents are attached to this challenge specification to explain what is required for the wireframes:
1. QIR Video Demo: Demo of the existing QIR application (note: due to file size the zip file is split into 3 parts - download all 3 parts and extract the video like a normal zip file).
2. Existing App Screen Shots: Screenshots from the existing application. IMPORTANT: These screenshots also include comments and markup to show a few areas of the existing application that should be changed / modified in the new application.
3. 'Quality Incident Reporting - .Net Version SOW v2': Document that includes the statement of work and a list of requirements for the new QIR .NET application.
4. 'Quality Incident Report Enhancements - July 2014.xlsx' - Contains several worksheets that describe changes / elements that should be captured in the new QIR .NET application.
Wireframe Requirements:
Please see the video demo current system screenshots for detailed requirements of the existing QIR application. All changes are described in the screenshot notes / comments and the changes listed in this spec. Also, the file "Quality Incident Reporting - .Net Version SOW v2.1-edited.doc" includes a supplementary list of requirements for the new QIR .NET application.
Look and Feel:
The new Quality Incident Reporting application needs to roughly match the look-and-feel of the existing system. Users are familiar with this existing system and we don't want to make any major changes. However, the client would like to see your ideas on ways we can improve the new application without moving too far away from the existing application look-and-feel. Please feel free to get creative and show us your best ideas for the new QIR application!
IMPORTANT: The attached video demo shows video and screenshots of the existing system.
Target Audience
Existing users of the current QIR application.
Judging Criteria
- User Experience
- Simplicity and Consistency
- Completeness and accuracy of the wireframe.
- How well your wireframes provide a consistent user flow.
- How well you implement the idea
- Any suggestions, interactions and user flow you recommend (provide any notes or comments for the client)
What to Submit:
Preview JPG/PNG Image File
- 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 ZIP File
- All requested contest requirements as clickable HTML files generated by Axure. All the content must be listed and the pages are linked together to show page flow.
Source ZIP File
- 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.
- All fully editable original source files of the submitted wireframe as required by the contest under "Source Files" in the side bar should be included in your Source zip file.
Final Fixes
- As part of the final fixes phase you may be asked to complete one round of minor changes to ensure your submission meets the stated requirements of this contest. See more information about Final Fixes.
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.