Challenge Overview

The prototype for the Estimation Tool (ET) will be built in to the existing prototype of the Service Request Tool (SRT).  The SRT provides functions for managing a profile, manage customers and manage and submit service requests (SRs).  With the inclusion of ET functionality, we will also have the ability to manage and submit estimates (ETs).

Challenge Details

Header/TopNav:

-The header should include a new option, between Service Requests and Customers, called Estimates.
-When selecting "Estimates" from the header, there will be two options
-Manage estimates - takes you to the Estimates page
-Create new estimate - takes you to the CreateEstimate page

Estimates page:

- Use ServiceRequests.html as the base for this page
- This page should look and behave very much like the ServiceRequests page, only that it is for Estimates instead
- There should be two tabs on this page: Draft (#d) and Submitted (#s)
- Functionality in the right nav (Common Tasks) should be retained. So there will be the ability to Create Estimate, Copy Estimate, Edit Estimate, Submit Estimate, Delete Estimate, Export to PDF and Print Estimate
- Filter functionality on the page should be retained.
- Anywhere on the ServiceRequests page where it says Service Request(s) or just Request(s) it should say Estimate(s) instead

Create/Edit/Copy Estimate page:

- Use CreateServiceRequest.html and EditServiceRequest.html as the base for this page
- This process should follow similar logic as creating a Service Request, with echelon navigation near the top, Save as Draft, Next, Previous and Cancel buttons near the bottom, and Common Tasks on the right all retained
- Anywhere on the page where it says Service Request(s) or just Request(s) it should say Estimate(s) instead
- The echelon navigation for Estimates is different than it is for Service Requests, the steps should be:
1. Set Up Deal
2. Solutions Review
3. Set Up Opportunity
4. Estimate Opportunity
5. Price Opportunity
6. Perform Staffing Reqest
7. Setup Delivery
8. Perform Delivery Action

Each of the above steps should correspond with a seperate prototype page.  Please refer to the ARS and ET excel document for content. Note you'll need Excel on Windows to try the excel document to understand how this works.

General Requirements:

The following are general guidelines you must follow in building the prototype:

- Produce a UI Prototype that can be used to demonstrate all tabs mentioned above.
- Your submission must be based on the previous prototype (same styles) and replicate all behaviors of the tabs.
- If you need to use grids in this prototype, same styles and behavior from existing prototype should be used

You need to include those in your submission:

- Implement hover state for all buttons and links.
- All elements (such as the select boxes, radio buttons and checkboxes) will be browser based but should look consistent with existing ones.
- Follow all coding styles / standards already used in previous prototype.

The following are specific requirements for HTML, CSS and Javascript files:

- Your HTML code must use the same doctype as the provided prototype from a previous challenge (attached to forum)
- Validate your code, reviewers may accept minor validation errors, but please comment your reason for any validation errors. Use the validators listed in the scorecard.
- Use CSS to space out objects, not clear/transparent images (GIFs or PNGs) and use proper structural CSS to lay out your page. Only use table tags for tabular data and not for page layout.
- No inline CSS styles, all styles must be placed in an external stylesheet.
- Use semantically correct tags - use H tags for headers, etc. Use strong and em tags instead of bold and italic tags.
- Element and Attribute names should be in lowercase and use a "-" or camel naming to separate multiple-word classes (i.e. "main-content", or "mainContent".
- All JavaScript must not have a copyright by a third party. You are encouraged to use your own scripts, or scripts that are free, publicly available and do not have copyright statements or author recognition requirements anywhere in the code. You are allowed to use the JQuery JavaScript library for this contest.
- Pagination is required to be included where necessary

Extra Requirements:

The following should be working properly and reviewers should check these in review:

- Tab order and field focus
- Existing data Selection -  When tabbing to a field any existing value should be highlighted
- Ensuring that field that are tabbed to can be controlled with the keyboard i.e. check boxes, radio buttons, calendar controls, drop downs, etc.

Browsers and Standards:

Your submission must works on browser in the list below:

- IE8+
- FF 3+ Mac & PC
- Safari 4 PC
- Chrome Mac & PC

Final Submission Guidelines

Submission Deliverables

• A complete prototype with all required pages implemented.

Submission Guidelines

Submit an archive file contains all HTML/CSS/JS/images and another required files into Online Review.