We Go Look - Drupal Environment Enhancement Architecture Challenge

Project Overview

WeGoLook is a third-party verification company featuring 10,000+ Lookers (Agents) in the United States to capture dynamic data and complete a variety of custom tasking.  Data capture includes photos, video, observations, measurements and completing personalized report templates.  Custom tasking includes picking up items then delivering to a shipper, retrieving courthouse records, notarizing documents and more. WeGoLook is looking to  extract certain information from the existing system and present it within the existing Drupal framework.  

Currently, this data is being captured but not being exposed.  Creating reports that query the existing system and expose the desired data will be the first challenges that we need to perform.  For this challenge, we need you to need to design the related data models and backend services to accompish this goal.

We look forward to seeing your architecture designs!

 

Project Description:

The client for this project is WeGoLook, a third-party verification company featuring 10,000+ Lookers (Agents) in the United States to capture dynamic data and complete a variety of custom tasking.  Data capture includes photos, video, observations, measurements and completing personalized report templates.  Custom tasking includes picking up items then delivering to a shipper, retrieving courthouse records, notarizing documents and more. WeGoLook is looking to extract certain information from the existing system and present it within the existing Drupal framework.  This data is being captured but not being exposed.  Creating reports that query the existing system and expose the desired data will be the first challenges that we need to perform.

Competition Task Overview

For this challenge, based on the provided materials, competitors need to design the related data models and backend services to expose the necessary data and present it within the existing Drupal framework. With the design, competitors can integrate frontend with the backend easily to build the final application. Basically, we need to understand how the necessary data can be exposed.

For this architectural challenge we would like to have further detailed documentation on how these enhancements should be implemented.  

You may need to create fake orders as the VM system will have limited orders in the running system.

Clear instructions will be required on any enhancements to integrate them into the production environment.

Questions (examples of what we're trying to understand):
- Orders:
    - How many orders did a corporate customer place
- Day of the week, Time of the day
- Payment Method of order
- How long does it take for an order to be claimed
- How long does it take for an order to completed after being claimed
- Orders per day (overall average) and orders by day (Monday, Tuesday, etc)
- Location of the order.
- Location of the looker
- Cost of the item
- When do users register for the site
- Where are they registering
- When do they claim their first look

Other examples of information that the client would like to have exposed will be provided in the supporting documents.

Documentation Provided

For this challenge, the following materials are provided:
1. Access to a VM that currently reflects the client’s existing Drupal System.
2. WeGoLookDeveloperDocumentation.docx:  Documentation explaining existing system and usernames and passwords to navigate the existing system.
3. Desired Data - EventTracking.docx:  Further documentation detailing possible desired information to be exposed within the Drupal framework. 

Technology Overview

Key Technologies:
- Debian
- Apache
- MySQL
- Drupal

Final Submission Guidelines

Using the provided documentation, competitors will complete the architecture deliverables (https://apps.topcoder.com/wiki/display/tc/Module+Architecture+Tutorial+-+Deliverables).

Detailed Requirements

1. Application Design Specification
2. ERD (if any)
3. Sequence Diagrams
4. Interface Diagrams
5. Assembly Specifications