Key Information

Register
Submit
The challenge is finished.

Challenge Overview

Project Overview

The client of this application is Sharous, a company that is in progress of starting a mobile-based, location-centric social networking application, also called Sharous. The objective of this project is to build a proof-of-concept and to enrich the idea that they have for Sharous.

Sharous will initially be offered as a mobile application for iOS devices, where users will be able to share their location from their phone in close to real-time, view a world map showing the location of their friends, people around them, and other users, and interact with other users in the map or on their contact list.
The application will also provide standard social networking features such as requesting to add friends, accepting or rejecting friend requests, removing friends, viewing contact (friends) list, posting status message, changing profile and avatar and chat messages.
This module provides the backend server-side functionality for the application. It includes the backend service implementations and the REST layer wrapper of them.
This assembly provides the models, common service resources, abstract service implementation, and the miscellaneous services

Competition Task Overview

The classes in TCUML “Misc Services - Class Diagram” are in scope. The corresponding interfaces are also in scope.

The model classes in TCUML “Model Class Diagram” are in scope. Note that these cases are mapped with the provided Hibernate mapping file to the tables in database. All Hibernate managed entity classes must have equals() and hashCode() methods that base on the ID.

The service DTO classes in TCUML “Service Resource - Class Diagram” are in scope.

The exception classes in TCUML “Exceptions Class Diagram” are in scope.

Please check the attached Model_and_Misc_Services_Assembly_Specification.doc and architecture documentations for detail reference.

Technology Overview

Documentation Provided

Documentation and Applications that will be provided to registered members:

Document Name Document Description                                
Architecture docs see attachments
Requirements Documentation see attachments

 

Payment

TopCoder will compensate members with first and second place submissions. Initial payment for the winning member will be distributed in two installments. The first payment will be made at the close of the approval phase. The second payment will be made at the completion of the support period.

Winning Submission and Second Place payments are shown at the top of the contest details page.



Final Submission Guidelines

Submission Deliverables

Below is an overview of the deliverables:

  • Source code with builld.xml for build and deployment.
  • A complete and detailed deployment documented explaining how to deploy the application including configuration information.

Support

  • Standard 30-days support is required.

Final Submission

For each member, the final submission should be uploaded to the Online Review Tool.

ELIGIBLE EVENTS:

2013 TopCoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30032950