Challenge Summary
This is a $1500 Studio competition to build the Online Closing Systems (OCS) prototype Real Estate Brokers and Attorneys will use. Currently, this data is handled by hand and the client's goal is to provide these busy Brokers and Attorneys with an easy way to organize their important data in a user-friendly way.
You will be using the provided storyboards, the Business Requirements Document (BRD) as well as the client-provided wireframes to create a full working prototype of this application.
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.
The client would like to develop an application to support, streamline and facilitate contract preparation from the buyer and sellers agreement, between Real Estate Brokers and Attorneys, to the final contract preparation and delivery. The goal is to eliminate redundancy of entering identical information by all parties, support the routine operations with databases, and easily retrieve the database information. The output of the overall application is the "Deal Sheet" between Brokers that is delivered to seller's Attorney with basic deal terms. Much of this information flows into the contract, which is then transmitted to the buyer's Attorney and their respective clients for signature. Given the following inputs, create a full prototype. The prototype must contain all screens described in the BRD and wireframed in the UI specification the client has provided. The look and feel of this prototype must match the provided Storyboards. Storyboard Changes The main content of the page needs to fit within 1024px. The rest of the page needs to have a fluid layout. If the main content needs to be expanded to accommodate input areas, please make sure that area itself fits within 1024px. Wireframes/BRD The wireframe document provided by the client (Interface-wireframes.doc) uses screens that are somewhat branded in the old look. Do not use these screens for look and feel - only for content and content references. All look and feel references need to match the storyboards provided for this contest. A full Business Requirements Document (BRD) is also being provided for reference to help with page flow and requirements. Please ask the client questions in the forum! This prototype must be complete and contain all required pages as outlined in the provided documents. If anything is unclear, the client is happy to clarify all points in the forums. HTML / CSS - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reason for any validation errors. Your validation results must be documented in a text file. - Your code must render properly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Use CSS to space out objects, not clear/transparent images (GIFs or PNGs). - Proper use of structural CSS to lay out your page is strongly encouraged. - 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 - Only use table tags for tables of data/information and not for page layout. - Build upon the existing stylesheet - Class and ID names should not visually describe the content (e.g .bigRedTextLeft) JavaScript 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. For this contest you are allowed and encouraged to use the jQuery library. Judging Criteria Your submission will be judged on the following, in order of importance: - Completeness/accuracy of the prototype - How closely the prototype matches the provided storyboards - How well items are styled that are not provided in the storyboards - Cleanliness and organization of source code Preview Image Your preview image should be a screenshot of one page of your choice with no added effects or skewing.
The client would like to develop an application to support, streamline and facilitate contract preparation from the buyer and sellers agreement, between Real Estate Brokers and Attorneys, to the final contract preparation and delivery. The goal is to eliminate redundancy of entering identical information by all parties, support the routine operations with databases, and easily retrieve the database information. The output of the overall application is the "Deal Sheet" between Brokers that is delivered to seller's Attorney with basic deal terms. Much of this information flows into the contract, which is then transmitted to the buyer's Attorney and their respective clients for signature. Given the following inputs, create a full prototype. The prototype must contain all screens described in the BRD and wireframed in the UI specification the client has provided. The look and feel of this prototype must match the provided Storyboards. Storyboard Changes The main content of the page needs to fit within 1024px. The rest of the page needs to have a fluid layout. If the main content needs to be expanded to accommodate input areas, please make sure that area itself fits within 1024px. Wireframes/BRD The wireframe document provided by the client (Interface-wireframes.doc) uses screens that are somewhat branded in the old look. Do not use these screens for look and feel - only for content and content references. All look and feel references need to match the storyboards provided for this contest. A full Business Requirements Document (BRD) is also being provided for reference to help with page flow and requirements. Please ask the client questions in the forum! This prototype must be complete and contain all required pages as outlined in the provided documents. If anything is unclear, the client is happy to clarify all points in the forums. HTML / CSS - Your HTML code must be XHTML 1.0 Strict compliant - Validate your code - we will accept minor validation errors, but please comment your reason for any validation errors. Your validation results must be documented in a text file. - Your code must render properly in Internet Explorer 6, Internet Explorer 7, Firefox 2 and 3, Google Chrome and Safari in both Mac and PC environments. - Use CSS to space out objects, not clear/transparent images (GIFs or PNGs). - Proper use of structural CSS to lay out your page is strongly encouraged. - 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 - Only use table tags for tables of data/information and not for page layout. - Build upon the existing stylesheet - Class and ID names should not visually describe the content (e.g .bigRedTextLeft) JavaScript 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. For this contest you are allowed and encouraged to use the jQuery library. Judging Criteria Your submission will be judged on the following, in order of importance: - Completeness/accuracy of the prototype - How closely the prototype matches the provided storyboards - How well items are styled that are not provided in the storyboards - Cleanliness and organization of source code Preview Image Your preview image should be a screenshot of one page of your choice with no added effects or skewing.
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.