Challenge Summary
Welcome to the FEPS User Interface Enhancements Wireframe Contest - we have a tight deadline to complete some much needed fixes and enhancements to FEPS application. For this contest we are looking for you (the community!) to help us solve some of the Functional and Usability issues found after performing some initial UAT (User Acceptance Testing) with the client. We have identified several areas of functionality that is missing or needs improvement.
We are looking for you build Wireframes that illustrate your solution to the Client and eventually to the Prototypers who will be using your Wireframes to update the existing FEPS Prototype. Please pay attention the Round 1 requirements as we are looking for design/functional solutions as opposed to completed wireframes. The Client would like to review/click-thru your solutions and provide you with feedback before finishing the rest of the FEPS application updates.
Round 1 is going to be quick - so please ask us questions as this project is under a tight deadline.
Details In Round One we are looking for help with Search functionality and Search Result User Flows. Two of the Change Requests deal with how you Search for Records and how Records are displayed in the FEPS tree view structure. The FEPS tree view structure is difficult to manage. There are thousands of records in the database - the current left tree view display only shows 10 records at any given time. The 10 record limitation is due to a speed performance constraint. We are looking for your help in providing a REVISED or NEW solution in displaying this information. We are open to changing how the Search results are displayed (remove the tree?, show the results on the right side? - discussion in the forums will be important here). The Search functionality also needs improvement. The current Organization Search only displays the organization's basic information. User's are not able to manage the organization's attributes which are displayed in the left tree view navigation. For example, from the Organization Search (2_1_new_organization.html), users are not able to navigate to the organizations' Contract and Subsidiary information that is displayed in the left tree view. We are looking for a solution that will allow users to access the organization's attributes from the Search Results so they can edit and save attribute details. Please see (FEPS UI Change Requests Wireframe Spec.doc) for additional information/screenshots on these issues #41 and #45. About the CLIENT and FEPS Application CLIENT is a financial services company. One of its services is to provide financial plans for a company's employees. The FEPS application helps to manage these financial plans by providing record management for the Contract's and Subsidy activities, including: Seminars, Plan sales, Billing and Reporting. The CLIENT change requests are split into two groups: User Interface Changes These change include significant issues with the current user interface that need to be addressed (Round 1) New Functionality These changes includes new user interface requirements. For this contest, we are expecting the information and functionality defined in the current HTML to be refined into a new page flow that incorporates the listed changes. The wireframe must be implemented in a CLICKABLE format. The current HTML look and feel should also be considered where possible. When members register for this contest, they will receive several documents: FES Explorer Application Summary.doc -This is a summary of the application. This document will provide users with an overview for what the application is intended to do and how the various screens are used in the application workflow. FEPS UI Change Requests Wireframe Spec.doc -This document lists the UI changes that need to be made Morpheus_FEPS_Explorer_ARS.doc - The requirements document Prototype -The html prototype from the original application. Below is a list of changes required for this competition. these changes are defined in more detail in the FEPS UI Change Requests Wireframe Spec.doc. Please refer to this document once you have registered for the contest. This document provides additional detail that explains the functionality of this application. This is a Studio Wireframe Contest. We are looking for HTML/Clickable formated submissions. User Interface Changes Change Request #41 - Manage FEPS Explorer Views The current feps tree view structure is difficult to manage. There are thousands of records in the database. The current tree view display only shows 10 records at any given time. This is due to a performance constraint to pull back more than that many records and display it on the screen. We would like to see different options for allowing the user to view the same information that is in the navigation. Ideally, we do not want to make significant changes to the User Interface unless necessary. Change Request #45 - Perform Search The current organization search functionality, only displays the organization name and basic information for the organization. Users are not able to manage the attributes that they are form the left navigation. We need a solution that will allow users to access the functionality from the search result that they can from the left navigation. New Functionality Change Request #24 - Process Seminars There needs to be a way to add multiple sessions for different organizations. Users will typically add a set of sessions at one time. The current web tool provides a clone function which provides this ability. We should move the 'clone' button to make it easier to navigate to. Change Request #55 Process Contracts See Use Case 2.24 in Morpheus_FEPS_Explorer_ARS.doc Change Request #27 - View Company Billing See Use Case 2.12 in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #49 - View Company Billing See Use Cases 2.26 Create Billing List and 2.27 Create Billing Statement in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #32 - Generate Activity Report Implement the Report Selection Screen defined in Use Case 2.16 of the Morpheus_FEPS_Explorer_ARS.doc document Change Request #37 - Generate Plan Sale Report Implement the Report Selection Screen defined in Use Case 2.17 in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #38 - Generate Contract Reports Implement the Report Selection Screen defined in Use Case 2.18 in the Morpheus_FEPS_Explorer_ARS.doc document Target User - this is an internal application that is used by the client's business users Judging Criteria Your submission will be judged on how well you updated and improve the current FEPS application experience.
Round 1
This contest is using the Studio Tournament Format. For Round 1, we will be looking specifically at the User Interfaces Changes described below. For Round 1, the solution does not need to be complete with all the search and display types. Enough information should be implemented in Round 1 to provide an overview of how your solution will work and allow the client an opportunity to provide feedback. At the end of Round 1, the client will choose 5 Round 1 winners. Each of the submissions will win $100. The 5 Round 1 winners and any member who had a passing submission in the Round 1 will be eligible to compete in Round 2. The client will also provide feedback on the top 5 submissions after Round 1 is complete.Round 2
Round 2 should include Wireframes for the New Functionality defined in the Change Request Document as well as implementing the current functionality of the HMTL prototype. (We will update this requirement after Round 1)Details In Round One we are looking for help with Search functionality and Search Result User Flows. Two of the Change Requests deal with how you Search for Records and how Records are displayed in the FEPS tree view structure. The FEPS tree view structure is difficult to manage. There are thousands of records in the database - the current left tree view display only shows 10 records at any given time. The 10 record limitation is due to a speed performance constraint. We are looking for your help in providing a REVISED or NEW solution in displaying this information. We are open to changing how the Search results are displayed (remove the tree?, show the results on the right side? - discussion in the forums will be important here). The Search functionality also needs improvement. The current Organization Search only displays the organization's basic information. User's are not able to manage the organization's attributes which are displayed in the left tree view navigation. For example, from the Organization Search (2_1_new_organization.html), users are not able to navigate to the organizations' Contract and Subsidiary information that is displayed in the left tree view. We are looking for a solution that will allow users to access the organization's attributes from the Search Results so they can edit and save attribute details. Please see (FEPS UI Change Requests Wireframe Spec.doc) for additional information/screenshots on these issues #41 and #45. About the CLIENT and FEPS Application CLIENT is a financial services company. One of its services is to provide financial plans for a company's employees. The FEPS application helps to manage these financial plans by providing record management for the Contract's and Subsidy activities, including: Seminars, Plan sales, Billing and Reporting. The CLIENT change requests are split into two groups: User Interface Changes These change include significant issues with the current user interface that need to be addressed (Round 1) New Functionality These changes includes new user interface requirements. For this contest, we are expecting the information and functionality defined in the current HTML to be refined into a new page flow that incorporates the listed changes. The wireframe must be implemented in a CLICKABLE format. The current HTML look and feel should also be considered where possible. When members register for this contest, they will receive several documents: FES Explorer Application Summary.doc -This is a summary of the application. This document will provide users with an overview for what the application is intended to do and how the various screens are used in the application workflow. FEPS UI Change Requests Wireframe Spec.doc -This document lists the UI changes that need to be made Morpheus_FEPS_Explorer_ARS.doc - The requirements document Prototype -The html prototype from the original application. Below is a list of changes required for this competition. these changes are defined in more detail in the FEPS UI Change Requests Wireframe Spec.doc. Please refer to this document once you have registered for the contest. This document provides additional detail that explains the functionality of this application. This is a Studio Wireframe Contest. We are looking for HTML/Clickable formated submissions. User Interface Changes Change Request #41 - Manage FEPS Explorer Views The current feps tree view structure is difficult to manage. There are thousands of records in the database. The current tree view display only shows 10 records at any given time. This is due to a performance constraint to pull back more than that many records and display it on the screen. We would like to see different options for allowing the user to view the same information that is in the navigation. Ideally, we do not want to make significant changes to the User Interface unless necessary. Change Request #45 - Perform Search The current organization search functionality, only displays the organization name and basic information for the organization. Users are not able to manage the attributes that they are form the left navigation. We need a solution that will allow users to access the functionality from the search result that they can from the left navigation. New Functionality Change Request #24 - Process Seminars There needs to be a way to add multiple sessions for different organizations. Users will typically add a set of sessions at one time. The current web tool provides a clone function which provides this ability. We should move the 'clone' button to make it easier to navigate to. Change Request #55 Process Contracts See Use Case 2.24 in Morpheus_FEPS_Explorer_ARS.doc Change Request #27 - View Company Billing See Use Case 2.12 in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #49 - View Company Billing See Use Cases 2.26 Create Billing List and 2.27 Create Billing Statement in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #32 - Generate Activity Report Implement the Report Selection Screen defined in Use Case 2.16 of the Morpheus_FEPS_Explorer_ARS.doc document Change Request #37 - Generate Plan Sale Report Implement the Report Selection Screen defined in Use Case 2.17 in the Morpheus_FEPS_Explorer_ARS.doc document Change Request #38 - Generate Contract Reports Implement the Report Selection Screen defined in Use Case 2.18 in the Morpheus_FEPS_Explorer_ARS.doc document Target User - this is an internal application that is used by the client's business users Judging Criteria Your submission will be judged on how well you updated and improve the current FEPS application experience.
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.