Challenge Summary
Welcome to “MNEMOSYNE - Pricing Tool Web Wireframes Design Contest”. The client of this project provides IT consulting services to its customers. When they got an opportunity to sell consulting services, the staffings levels for the services must be estimated and the services priced. The current pricing estimation process was performed using MS Excel and they want to move the process to a web application. In this contest, we need your help to create a new flow for the application using our conceptualization document as references.
At the end of this contest, we are looking an HTML wireframes which showing a new workflow on web browser and provides great user experience for the application and also can be used as suggestion for the next development phase.
Round 1
All use case requirements as stated in contest details for initial client review
Round 2
All use case requirements as stated in contest details with client feedback applied.
The main goal of this project is to build a more maintainable tool to support growing user base for Mnemosyne’s sales opportunities management, and this tool will be used to replace the existing Excel tool. This application will need to support both web and mobile browser, but in this contest, we’re only need to create wireframes for the web parts.
The Pricing Tool is an estimating tool that allows those in the field the ability to estimate the pricing for consulting clients. This tool also is a major driving force within the sales booking process. This process was developed in order to:
1. Provide one consistent tool which will calculate pricing for all practices
2. Provide the same rate cards and calculations that are used in in our system of record as of the last time the sheet was refreshed. This will result in a matching margin across both systems
3. Support and instantiate policy decisions on pricing between operations and sales
4. Reduce the confusion and incorrect deal calculations
5. Provide an audit mechanism to review deals that have been executed
Here are the screens requirements that needs to be built in this contest :
1. Login/Logout Screens (4.4.1 – 4.4.2)
2. Get Help Screens (4.4.3)
3. Print Web Pages - Provides a popup showed the print will be handle by web browser print functionality (4.4.4).
4. View Opportunities (4.4.5)
5. Create Opportunity (4.4.6)
6. Estimate Opportunity (4.4.7)
7. Price Opportunity (4.4.8)
8. Edit Opportunity (4.4.9)
9. Delete Opportunity (4.4.10)
10. Share in Progress Opportunities (4.4.11)
11. Generate BOE Spreadsheet for Booking (4.4.12)
12. Generate Staffing Request Spreadsheet (4.4.13)
13. Review BOE generated Opportunities (4.4.14)
14. Configure Table Data (4.4.15)
Note : Please watch the use case diagrams carefully, There are several functionality that inheret between each user, you must provide all these use case on each user scenario.
Target Audience
There will be 5 kind of audiences that will use this application, which are :
a. Generic User
The registered user refers to any generic user registered to use the application. It is used to represent requirements and functionality available to all user types. The generic functionality includes login, logout, get help and print web-pages.
b. Sales Staff
The sales user can view opportunities, create opportunity, estimate opportunity, price opportunity, edit opportunity, delete opportunity and share in progress opportunities. Additionally, the sales user will be able to generate BOE spreadsheet for booking and staffing request spreadsheet.
This encompasses several types of internal users, including Solution Principals, Practice Pre-Sales, Project Manager, Account Manager, Pre-Sales Support, and Booking Managers.
c. Approval Manager
In this current version of the proposed application, the approval manager will have the same permissions as the sales users.
d. Audit Team Member
The audit team member can review all the BOE generated opportunities.
e. Application Admin
The application admin can configure the static table data.
IMPORTANT :
- Generic user use case should be appear in all user roles.
- sales staff and approval manager have same scenario.
- Create scenario for staff/approval manager, audit team member, and application admin.
Judging Criteria
Your submission will be judged on the following criteria:
- User Experience
- Completeness and accuracy of the wireframe as defined in the requirements.
- 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 (provide any notes or comments for the client)
Submission & Source Files
Preview Image
Create your preview image as one (1) 1024x1024 JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Generated HTML files with all the requested contest requirements stated above.
Source Files
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.
Final Fixes
As part of the Final Fix phase, you may be asked to remove, update, or change some features of the wireframe.
Attachment :
- Mnemosyne_Pricing_Tool_Conceptualization_Document.docx(conceptualization document)
- Pricing_Tool_Conceptualization_Questionnaire.docx (questionnaire document)
- Pricing Model 4.3 Test Data.xlsm (Current Pricing spreadsheet apps – open in excel 2007 - password MACTEST)
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.