Challenge Summary
In this contest, you will be developing wireframes for an appliation that will help configure and manage a lead distribution system. the lead distribution system matches consumers looking for loans with venoders who are selling loans. One of the key features of this system is to send and recieve data between the CLIENT system and the vendors system. This user interface will provide functionality for CLIENT users to configure vendors as well as manage message. It will also allow vendors to test communication with teh CLIENT systems.
The user interface of this system should be straightforward, intuitive and "cool" for a non-technical user. The overal scope of the Lead Distrubtion system is defined in the conceptualization document which is attached. There are several sections in the document that focus on the user interfaces. The section below documents which sections define the user interfaces this wireframe should include. The user interface will include two main sub applications 1) an internal Admin tool this admin tool will be used by internal resources to configure new vendors. it will also be used to manage orders that have communication issues between the vendor and the CLIENT system. 2) A vendor testing applicaiton. we will provide vendors with a testing application that will allow them to send test messages to the CLIENT's QA environment to verify the communication before turing systems on in produciton. Internal Admin Tool Workflows 3.3.1.3 Internal Admin Tool (Vendor Setup) 3.3.1.4 Admin Tool / Error Handling External Vendor Tool Screens 3.3.1.5 Vendor Self Test - Vendor Configuration 3.3.1.6 Vendor Self Test - Vendor Offer Response validation Internal Admin Tool Use Cases (Vendor Setup) 4.4.1 Login 4.4.2 Logout 4.4.3 Configuration Vendor Communication Data 4.4.4 Configuration Data Translation Format 4.4.5 Configure Data Attributes 4.4.10 Import / Export Data Internal Admin Tool Use Cases (Error Queue / Error Handling) 4.4.6 Review Non-Delivered Orders 4.4.7 Retry Orders Delivering 4.4.8 Convert NOn-Converted Orders 4.4.9 Retry Orders Conversion External Vendor Tool Use Cases 3.3.1.5 Vendor Self Test - Vendor Configuration 4.4.11 Log into QA Environment 4.4.12 Logout of QA Environment 4.4.13 View Configuration Details 4.4.14 Perform Basic Search for Vendors 4.4.15 Perform Advanced Search for Vendors 4.4.16 Apply Testing QF to Vendor 4.4.17 Validate Response Message Vendor Self Test - Vendor Offer Response validation (No Use Cases but uses should include functionality defined in workflow The conceptualization document is also attached for your reference. This document outlines functionality for two web based applications as well as backend / system functionality. There are still some notes you need pay attention: 1) this will be a part of an existing admin tool. A visio draft screenshot for the vendor setup screen has been defined and will be provided . The wireframes / Tool should assume that users who have access to the vendor setup do not have access to the Error Handing / Manual Configuration Functionality. 2) The vendor tool will be an application that will be accessed by Vendors in both QA environments (for testing) and production environments. this wireframe should account for this requirement by displaying the 'environment' clearly on the pages so users will know which environment they are in. 3) There are four separate web-based part for new CLIENT application: system service, manual error resolving tool , internal admin tool and vendor self-test tool. In this competition, only the Internal Admin Tool and Vendor Configuration / Testing tool need to be implemented in the wireframe. TARGET AUDIENCE: Admin The internal administration staff of the CLIENT company. Vendor A Vendor is a partner who offers products to consumers. The vendor can login to the QA self-testing tool and test the communication path to his/her lead system. The special self-testing tool was created by our concept for vendors. Consumer A consumer is a person that comes to the CLIENT web-sites looking for a product or service. JUDGING CRITERIA: Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required data and any suggestions, interactions and user flow you recommend
The user interface of this system should be straightforward, intuitive and "cool" for a non-technical user. The overal scope of the Lead Distrubtion system is defined in the conceptualization document which is attached. There are several sections in the document that focus on the user interfaces. The section below documents which sections define the user interfaces this wireframe should include. The user interface will include two main sub applications 1) an internal Admin tool this admin tool will be used by internal resources to configure new vendors. it will also be used to manage orders that have communication issues between the vendor and the CLIENT system. 2) A vendor testing applicaiton. we will provide vendors with a testing application that will allow them to send test messages to the CLIENT's QA environment to verify the communication before turing systems on in produciton. Internal Admin Tool Workflows 3.3.1.3 Internal Admin Tool (Vendor Setup) 3.3.1.4 Admin Tool / Error Handling External Vendor Tool Screens 3.3.1.5 Vendor Self Test - Vendor Configuration 3.3.1.6 Vendor Self Test - Vendor Offer Response validation Internal Admin Tool Use Cases (Vendor Setup) 4.4.1 Login 4.4.2 Logout 4.4.3 Configuration Vendor Communication Data 4.4.4 Configuration Data Translation Format 4.4.5 Configure Data Attributes 4.4.10 Import / Export Data Internal Admin Tool Use Cases (Error Queue / Error Handling) 4.4.6 Review Non-Delivered Orders 4.4.7 Retry Orders Delivering 4.4.8 Convert NOn-Converted Orders 4.4.9 Retry Orders Conversion External Vendor Tool Use Cases 3.3.1.5 Vendor Self Test - Vendor Configuration 4.4.11 Log into QA Environment 4.4.12 Logout of QA Environment 4.4.13 View Configuration Details 4.4.14 Perform Basic Search for Vendors 4.4.15 Perform Advanced Search for Vendors 4.4.16 Apply Testing QF to Vendor 4.4.17 Validate Response Message Vendor Self Test - Vendor Offer Response validation (No Use Cases but uses should include functionality defined in workflow The conceptualization document is also attached for your reference. This document outlines functionality for two web based applications as well as backend / system functionality. There are still some notes you need pay attention: 1) this will be a part of an existing admin tool. A visio draft screenshot for the vendor setup screen has been defined and will be provided . The wireframes / Tool should assume that users who have access to the vendor setup do not have access to the Error Handing / Manual Configuration Functionality. 2) The vendor tool will be an application that will be accessed by Vendors in both QA environments (for testing) and production environments. this wireframe should account for this requirement by displaying the 'environment' clearly on the pages so users will know which environment they are in. 3) There are four separate web-based part for new CLIENT application: system service, manual error resolving tool , internal admin tool and vendor self-test tool. In this competition, only the Internal Admin Tool and Vendor Configuration / Testing tool need to be implemented in the wireframe. TARGET AUDIENCE: Admin The internal administration staff of the CLIENT company. Vendor A Vendor is a partner who offers products to consumers. The vendor can login to the QA self-testing tool and test the communication path to his/her lead system. The special self-testing tool was created by our concept for vendors. Consumer A consumer is a person that comes to the CLIENT web-sites looking for a product or service. JUDGING CRITERIA: Your submission will be judged on the following criteria: - How well your wireframes provide a consistent user flow - How well you implement the required data and any suggestions, interactions and user flow you recommend
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.