Business Requirements

Project Name: ADK Web

1 EXECUTIVE SUMMARY

This is Phase II of the ADK Web Project, aimed at enhancing the existing functionality of Adirondack-Rent-A-Cabin website (www.adirondackrentacabin.com)

2 OVERVIEW

2.1 Timeline

The website went live on 24 June 2013. Changes and additions as per the scope of Phase II shall be developed and applied to live website as we go. The disturbance to the site shall be avoided to the extent possible and all deployments conducted between 1 AM - 5 AM EST.

2.2 Assumptions and Restrictions The project is implemented in 3 phases:- Phase I – deployment of core functionality (completed);- Phase II – deployment of owner stats/analytics and optional features/add-ins (in scope).- Phase III – deployment of optional online bookings for selected properties and owner calendar

synchronization via API. Phase III is expected to commence after 3-6 months of stable production run. Continuous support during initial UAT and Production Run periods is expected to be provided based on

1 day response SLA. Production Run is defined for the use of the system between: (i) the date of initial release of functionality in scope for Phase II, and (ii) three months thereafter. The same level of support may be subsequently required for the most intensive use of the system during pre- and mid-seasonal usage peaks.

Each of the deliverables in this document includes both front-end and back-end components, unless stated otherwise and as necessary per technical design.

Tasks marked with (!) are the most urgent ones, and shall be commenced immediately upon contract award.

3 DESCRIPTION OF REQUIREMENTS

3.1 Business Scope

3.1.1 Transaction Types

- Subscription & payment;- Subscription upgrade;

3.1.2 Primary Business Users

- Renter/Traveller;- Property Owner;

- Application/Website Admin

3.2 Specific Business Requirements

Key Business Requirement #1: Property search 1 Renters must have the ability to search and select rentals directly from the home page of the

application through specifying desired criteria in designated ‘search’ portlet.Detailed Description

1.1 Featured properties shall always appear on top of unsorted search results. (!)

1.2 User’s search requests are to be logged for further analysis.

Key Business Requirement #2: Featured listings module

2 The solution to support the ‘featured listings’ functionality for rental owners to list their property.

Detailed Description

2.1 The front-end functionality to allow selecting the property directly from the list by clicking on either “more info” button/link, or any area on the property photo.

Key Business Requirement #3: “Last minute” listings module3 Ability for the owner to list property as ‘last minute’ offer at a discounted price.

Detailed Description

3.1 The front-end functionality to allow selecting the property directly from the list by clicking on either “more info” button, or any area on the property photo.

3.2 Positions of the properties within the “last minute list” are randomly rotated/shuffled, to ensure that each listing gets equal exposure. The list to be changed each time following home page refresher.

Key Business Requirement #4: Google Maps Integration

4 Google-map component to be integrated into property card

Detailed Description

4.1 When clicking on the map, the user shall be able to see both selected property and all other regional rental properties, and can go explore those by clicking on the property pin on the map.

4.2 Properties with “featured” subscription shall be displayed prominently on the map by means of different and/or bigger icon. (!)

Key Business Requirement #5: Owner’s account module

5 Property owners to have the ability to maintain the information displayed for their properties within the system.

Detailed Description

Page 2 of 5

5.1 Create Stats/Analytics menu inside owner account (i.e. to monitor views/inquiries statistics broken down by daily, weekly, monthly intervals; view bookings – after Phase III deployment). (!)

5.2 The summary stats shall be also displayed as a dashboard in owner account in My Account landing page and Tips & Resources page. (!)

5.3 Change default entry in the “State” field in Step 1 of property creation process from New York to NY (!)

Key Business Requirement #6: Travellers Profiles

6 Ability for users to register on the website by creating a traveller profile

Detailed Description

6.1 Within their respective accounts, travellers shall be able to send a copy of inquiry to themselves (to external e-mail). (!)

Key Business Requirement #7: Notifications functionality

7 The system should support sending notifications to users, both property owners and travellers

Detailed Description

7.1 System to support the ability to send ad-hoc bulk notification to pre-selected group of registered users (either travellers or owners).

7.2 System to generate notification to the owners, whose active subscription is due to expire soon. For seasonal subscriptions:

- 7 days prior to expiration date (initial)- 3 days prior to expiration date (follow up)- 24 hours prior to expiration date (final)

For annual subscriptions:- 30 days prior to expiration date (initial)- 7 days prior to expiration date (follow up)- 3 days prior to expiration date (final)

Notifications shall stop immediately once extension of the subscription term has been processed.

Key Business Requirement #8: Admin Functionality

8 Site stats and analytics and content management

Detailed Description

8.1 Site performance stats:- number of properties/owner accounts;- number of traveller accounts- listings due to expire in 30 days;- listings with completed free trial;- inactive listings (cancelled, expired, created but not yet paid);- incomplete property profiles (paid);- number of inquiries sent (bookings – after Phase III deployment);- zip code stats

8.2 Site visits stats:- visitors stats: IP address

Key Business Requirement #9: Optimization for mobile phones and tablets

Page 3 of 5

Optimization for mobile phones and tablets

Detailed Description

9.1 Site shall be optimized for viewing on mobile phones (iOS, Android) with load time of 4 seconds or less.

9.2 Site shall be optimized for viewing on tablets (iOS, Android) with load time of 4 seconds or less.

3.3 Performance and Non Functional Requirements

3.3.1 Performance- The system is expected to respond to a standard expanded search request in less than 4 seconds,

provided broadband internet connection bandwidth. (!)- ‘Search’ or ‘system busy’ indicator is to be displayed while the system is busy processing the request.

3.3.2 Exceptions Handling (!)All financial transactions exceptions and/or fails are to be logged and provided in a designated report with details by:

- Property owner; - Property ID/Name;- Amount;- Payment method;- IP Address;- Reason for failure.

3.3.3 Usability

The solution is to be developed in line with current usability standards as well as WEB 2.0 considerations facilitating user feedback.

3.3.4 DesignThe design of the web-pages and the site overall must conform to the following baselines:- Pages layout are to be optimized for IE7 and higher, but should also support, Safari, Mozilla and Google

Chrome browsers.- Use resizable fonts and table sizes.- Looks and feel must be consistent across all pages (some minor fixes to the existing design may be

required to ensure consistent fonts, colors throughout the site, clean up of unnecessary caps in pop up messages etc.).

- Similar alternative fonts are to be used for different browsers and operating systems.- User standardized scroll bars. - Images must be optimized for download speed in order not to slow down the review process.

3.3.5 System AvailabilitySystem must be available 24/7. Website is hosted in a cloud (iPage).

Maintenance time is to be discussed separately.

Page 4 of 5

3.3.6 Audit Logging and Alerts (!)The following events to be logged:

User profile creation, changes, deletion User subscription to newsletter, un-subscription New property addition, changes, hold, deletion New subscription activation, upgrade, cancellation or expiration ‘last minute’ module changes: addition, expiration

3.3.7 Data Retention RequirementsHistorical data to be maintained in the system for the period of last five (5) years

4 DELIVERY AND TRANSITION STRATEGIES

4.1 Implementation Considerations

- Whenever applicable, the content displayed on the front end as well as notifications and all other data is to be dynamic and based on the information contained in the database, as opposed to being hard-coded.

4.2 Project Timing Considerations

The selected Contractor is expected to start work no later than 20 August 2013.

Page 5 of 5