Challenge Summary
Welcome to Lycoming - Warranty Claims App Wireframe Contest.
In this contest we are looking for a HTML wireframe which will show a new workflow for the Lycoming Warranty Claims App functionality and can be used as input for the next storyboard contest.
The application must be user friendly, professional, intuitive and easy to use.
Round 1
Your submitted solution for client review.
- For milestone, the following pages must be presented in your design:
1.Login page
-Forgot Password page
2.Update Temporary Password page
3.Landing page
4.User Profile page
5.Create Warranty Claim page
-Claim Confirmation page
-Print-Friendly page
- Any comments about your wireframe, make sure all pages have correct flow!
Round 2
Your submitted solution for client review.
- All pages with milestone feedback implemented.
- Any comments about your wireframe, make sure all pages have correct flow!
Contest Details:
Lycoming Engines is introducing the ability for Distributors or Original Equipment Manufacturers (collectively referred to as the “Customer”) to submit warranty claim forms via a web-based interface. This replaces the legacy processes including the use of paper forms. The data entered into the online forms will be saved to the Oracle EBS and be available for Warranty Administrators via the new Service Request form.
In this contest you are going to use the Warranty Claims Business Requirements document as input to create the HTML wireframe.
General Guidelines:
- Since this wireframe is going to be used as input for the next storyboard contest, your wireframe solutions must be useful. So it can save a web designer so much time and energy!. All pages/elements must linked each others. Show us the correct flow.
- The application must be very easy to use and intuitive.
- The application will be built as website application.
- Your wireframe must represents all pages and flows from Business Requirements Document (We are focus on the section 6.1 Functional Requirements - User Interface) You should use that as a guide, but if there is better way to display any information, feel free to reflected that on your wireframe.
- You MUST use wireframes note pane in every single page you design, to explain what all items are addressed in that page, what things you added/changed/removed, use it to make your idea clearer and help the client to give you constructive feedback.
Wireframe Requirements:
You will find all these pages that need to be designed in the Busines Requirements - section 6.1 Functional Requirements - User Interface section.
The pages that need to be designed are:
1.Login page
-Forgot Password page
2.Update Temporary Password page
3.Landing page
4.User Profile page
5.Create Warranty Claim page
-Claim Confirmation page
-Print-Friendly page
6.Edit Warranty Claim page
7.View Warranty Claim Details page
8.Administration pages
-Administration Landing page
-Add Users page
-Edit User page
-Analytics page
All the functionalities for each page are listed in the document.
Target Audience:
- End Users (pilots)
- Distributors
- Potential Customers (pilots)
- Service Center
- Service Center Users
Judging Criteria:
- User Experience
- Completeness and accuracy of the wireframe as defined in the attached 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
Please create your preview image as one (1) 1024x1024px JPG or PNG file in RGB color mode at 72dpi and place a screenshot of your submission within it.
Submission File
Wireframes should be built in HTML or Axure. The resulting files are not critical in this contest. The most important point is that all the content is listed and the pages are linked together to show page flow. Keep your source files out from this submission folder.
Source Files
All original source files of the submitted ideas. If you would like to submit notes please include notes.txt file.
Final Fixes:
As part of the final fixes phase you may be asked to modify content or user click paths.
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.