$1600 Marketing QF Tool Wireframe Contest

The client is a leader in consumer home loan products, real estate services, and non-home loan products and is always looking to add new and exciting products for consumers. In offering these products, the client uses various web based Qualification Form (referred as QF). A QF gathers information about a consumer in an effort to match them with the best offer for a particular product. The qualification forms are published on the client's website. The consumers (or prospective consumers) visiting the website fill up the form. The process of filling up involves answering the questions shown on the form and submitting it. The client has to handle a lot of such qualification forms and publish them on the website. The client is looking to build a web based tool that will help QF administrators to create and management new forms more easily. The purpose of this contest is to create a set of wireframes to 1. Create a sample QF form that illustrates what a customer would fill out on the web site. 2. Create a wireframe of the administrative tool that will be used to manage this application. 3. Create a wireframe for the administration tool that will be used to manage defining the question
This contest will include implementing three main subsystems of the marketing QF application. This includes: 1. Consumer QF Application Module -- A sample consumer facing QF form. 2. QF Template Display Management Module - The web-based administrative tool that will allow QF administrators to create new forums and administer existing forms. 3. QF Data Management Module -- This module is responsible for maintaining the QF repository. This preserves all the data elements associated with a QF questionnaire like the questions, answers, the data types and other meta-information. The details of this functionality are defined in the "Final_Marketing_Web_Form_Management_Conceptualization.doc" document which is provided as a part of this contest. Below is an overview of the deliverables and references to the sections of the conceptualization document that should be reviewed by resources. Consumer QF Application Module This functionality represents the consumer's user experience to complete a QF form. The conceptualization document includes functionality regarding auditing, failover and data persistence which is not in scope for the wireframe. For this wireframe contest we want to illustrate a sample QF. This sample user form will be used to illustrate how content is management in the "QF Template Display Management Module". For this functionality, we will provide a list of questions and the pages they should be displayed. Sample Workflows (See Section 3.3 of Conceptualization Document)

• See "User QF Form Submission Process Map"

QF Template Display Management Module This module lets the administrator organize the QF questions, pages, cross-sells and the question text. Functionality Overview (See 3.1 of Conceptualization Document)

• Open QF -- The administrator can open a QF that is created using the data management module.
• Manage Cross Sells -- The administrator can add or remove existing cross sells from the QF.
• Manage Ordering -- The administrator can change the ordering of questions and cross sells from this UI.
• Link Questions/Cross Sells to Pages -- The administrator can specify which questions and which cross sells must appear on a page.
• Change Text -- The admin can change the text to be displayed on a question.
• Validate Dependencies -- The application validates the dependencies defined in the data management module and shows the errors to the administrator so that he/she can correct them.
• Manage Pages -- The administrator can add new or remove existing pages from the QF.
• Manage Cross Sell Pages -- The admin can add or remove existing pages that are specifically used for cross sells.
• Mark Questions as Mandatory -- The admin can mark certain questions as Required questions and leave the rest as optional.
• Manage A/B Scenarios and assign scores -- The admin can create A/B scenarios of a QF and assign scores to them. The A/B Scenarios define multiple versions of the same QF with some minor changes in each version.
• Preview QF -- This shows how the QF looks. This deals with logical organization of content.
• Consumer QF Reports -- This shows the consumer reports to user, which shows the user behavior on how the QFs are being answered.
• Save QF -- This saves the changes made in this layer to the data store.

Sample Workflows (See Section 3.3 of Conceptualization Document)

• See workflow: Overall Flow Process Map
• See Workflow: QF Template Management Process Map

Use Cases: Use Cases 4.4.24 -- 4.4.40 are applicable to this functionality QF Data Management Module This module is responsible for maintaining the QF repository. This preserves all the data elements associated with a QF questionnaire like the questions, answers, the data types and other meta-information. Functionality Overview (See 3.1 of Conceptualization Document)

• QF Data Management
• Manage Question in Repository -- The administrator can manage questions in the repository. The operations include-- create, edit and delete the existing questions, answers and some meta-information associated with these items.
• Manage QF Types -- The administrator can create/update/delete QF Types
• Manage QFs -- The administrator can create/update/delete QFs
• Manage Questions Group -- The administrator can identify logical grouping of questions and mark them as a group.
• Define Dependencies -- The administrator can define the dependencies among questions. (i.e. Sequencing of questions)

Sample Workflows (See Section 3.3 of Conceptualization Document) * See Workflow: QF Data Management Process Map Use Cases: Use Cases 4.4.56 -- 4.4.66 are applicable to this functionality Competition Details Judging Criteria This is a wireframe contest. This contest is not focused on the look and feel and color scheme of the system. It is focused on defining the page flow and the content that will be defined on the pages. 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 Wireframe Resources Wireframes on Wikipedia: http://en.wikipedia.org/wiki/Web_site_wireframe Wireframe software option: www.axure.com Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php Wireframe Requirements Wireframes must be built in HTML. The tool can be written using wireframe tools such ash Axure (listed above).