Challenge Summary
This System is new application that will allow customers to purchase money unit gift cards. Recipients of these gift cards will have the ability to redeem the money from the cards and invest it through various investment programs provided by the System.
The Money Unit application is a subset of the System. This goal of this system is to allow users to purchase the money unit gift cards. This sub system will also provide various reporting functionality to be used by internal administration users.
The Money Unit application includes 3 main types of users that will access the system.
Customers - The system will include a customer facing interface for users to purchase money unit cards.
Customer Service Reps (CCPs) - The system will include an internal 'admin' interface which will be used by call center users who will purchase gift cards for customer's who place orders over the phone.
Admin Staff - In addition to CCPs, this application will include admin interfaces that will allow internal users to view various reports.
Entries must be your original work, and must not infringe on the copyright or licenses of others. Stock art, clip art, templates and other design elements from other sources are prohibited unless specifically permitted here in the Contest Details.
You will be working from a Conceptualization Document to create your wireframes. The Conceptualization Document includes context diagrams and work flows that define the business usage of the proposed system. In order to get a holistic view of the application, it will be beneficial to read the entire document. The main areas of the Conceptualization Document you should be most concerned with are: Application Overview 1.1 Overview Of Application Application Workflow 3.3 High Level Workflow Business Requirements 4.4 Customer Task Requirements 4.4.1 Customer Purchases Money Unit Online 4.5 Customer Service Professional (CCP) Tasks 4.5.1 Customer Service Login 4.5.2 Customer Purchases Money Unit Over the Phone 4.5.3 Lookup Order 4.5.4 Refund an order by Credit Card 4.5.5 Refund an order by Check 4.5.6 Resend an order 4.5.7 Record Charge Back on Gift Card Purchase 4.6 Administrative Tasks 4.6.1 Administrative logins 4.6.2 Invalidate Money Unit 4.6.3 Block Customer 4.6.4 Show Blocks 4.6.5 Audit Inquiries 4.6.6 Money Unit Fulfillment Report 4.6.7 Money Unit Inquiry 4.6.8 Financial Activity Report Please review all provided materials and ask the client questions in the forum. Wireframe Requirements - Wireframes should NOT address design - Wireframes are meant to provide content, convey the hierarchy of information and show content groupings. - Provide an intuitive user experience - Analyze navigational possibilities and recommend a solution - Make sure to address all the requirements listed in the Conceptualization Document - The amount of pages/screens is up to you - Usability must be one of your biggest concerns - Wireframes must only be black, gray and white - no color - Wireframes must address the user interface as well as the flow of the application For this contest, your wireframe submission MUST be in HTML. This is so the client can effectively click through these wireframes and the Consumer Site's wireframes during the same review. Wireframe Considerations When designing your wireframes, ask yourself questions that the user is likely to ask when using this system. This will help with usability issues and interaction. Some examples: Consumer Page Considerations - How should the information be displayed on various pages? Customer Service Reps (CCPs) Considerations - How should the information be displayed on various pages? - There are several use cases defined for this user, how should each of these use cases be accessed by the user? Should there be some type of dashboard? Admin Considerations - How will the users be presented with the use cases they can perform? - How will the reports be listed? Wireframe Resources Wireframes on Wikipedia: http://en.wikipedia.org/wiki/Web_site_wireframe Wireframe software option: http://www.axure.com Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php 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 Preview Image You should use a screenshot of the main page of your wireframes. Do no alter, skew, add drop shadows or some other dramatic effect to your preview image.
You will be working from a Conceptualization Document to create your wireframes. The Conceptualization Document includes context diagrams and work flows that define the business usage of the proposed system. In order to get a holistic view of the application, it will be beneficial to read the entire document. The main areas of the Conceptualization Document you should be most concerned with are: Application Overview 1.1 Overview Of Application Application Workflow 3.3 High Level Workflow Business Requirements 4.4 Customer Task Requirements 4.4.1 Customer Purchases Money Unit Online 4.5 Customer Service Professional (CCP) Tasks 4.5.1 Customer Service Login 4.5.2 Customer Purchases Money Unit Over the Phone 4.5.3 Lookup Order 4.5.4 Refund an order by Credit Card 4.5.5 Refund an order by Check 4.5.6 Resend an order 4.5.7 Record Charge Back on Gift Card Purchase 4.6 Administrative Tasks 4.6.1 Administrative logins 4.6.2 Invalidate Money Unit 4.6.3 Block Customer 4.6.4 Show Blocks 4.6.5 Audit Inquiries 4.6.6 Money Unit Fulfillment Report 4.6.7 Money Unit Inquiry 4.6.8 Financial Activity Report Please review all provided materials and ask the client questions in the forum. Wireframe Requirements - Wireframes should NOT address design - Wireframes are meant to provide content, convey the hierarchy of information and show content groupings. - Provide an intuitive user experience - Analyze navigational possibilities and recommend a solution - Make sure to address all the requirements listed in the Conceptualization Document - The amount of pages/screens is up to you - Usability must be one of your biggest concerns - Wireframes must only be black, gray and white - no color - Wireframes must address the user interface as well as the flow of the application For this contest, your wireframe submission MUST be in HTML. This is so the client can effectively click through these wireframes and the Consumer Site's wireframes during the same review. Wireframe Considerations When designing your wireframes, ask yourself questions that the user is likely to ask when using this system. This will help with usability issues and interaction. Some examples: Consumer Page Considerations - How should the information be displayed on various pages? Customer Service Reps (CCPs) Considerations - How should the information be displayed on various pages? - There are several use cases defined for this user, how should each of these use cases be accessed by the user? Should there be some type of dashboard? Admin Considerations - How will the users be presented with the use cases they can perform? - How will the reports be listed? Wireframe Resources Wireframes on Wikipedia: http://en.wikipedia.org/wiki/Web_site_wireframe Wireframe software option: http://www.axure.com Example Wireframe: http://www.gdoss.com/web_info/web-site-wireframe.php 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 Preview Image You should use a screenshot of the main page of your wireframes. Do no alter, skew, add drop shadows or some other dramatic effect to your preview image.
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.