Challenge Overview
Project Overview
For this challenge, the client wants to design the system architecture for the CMS based architecture (#1 below) for the system.
Competition Task Overview
The system includes 3 major parts, each consisting of multiple modules: a reservation engine (for hotel reservations), a CMS, and a CRM:
- The reservation will probably be custom architected and designed but we are exploring the option of integrating exiting reservation engines if possible. The system will integrate with an existing datasource for reservation information.
- The CMS is not decided yet, but in order of preference the client is currently considering: Drupal, Joomla
- In one of the approaches the CRM will probably be Salesforce, and in the other approach it will definitely be Salesforce.
- There are many additional non-core features (such as integrations with social networking sites, mobile apps, etc.) which are to be implemented in future phases. These features will need to be scoped too, however the scope of these features will not need to be known as accurately.
The Two Approaches:
- The first approach uses the CMS as primary base of the development. All content and other major parts of the system will integrate with the CMS (as Drupal modules or otherwise). Salesforce might be used as the CRM but is not required.
- The second approach uses Salesforce as the primary base of the development. The CMS has a reduced role and a more focused integration with Salesforce.
Detailed Requirements
This challenge must provide system architecture for approach #1 (CMS as primary base). All core and extended (starting from slide#23 in the pptx) requirements are in scope for this architecture.
We still want the standard system architecture deliverables but we'll also add custom sections to the scorecard based on the considerations document (Rec_Gov_Approach_1_Considerations.docx) we attached in contest forum. Make sure you read this carefuly so you can correct address these concerns / requirements in your submission.
Gameplan is important to this architecture, try to provide one that's as accurate as possible, especially in terms of numbers of upcoming contests needed to build the system.
Technology Overview
See provided documents.
Documentation Provided
Register to see documents provided in the contest forum.
Final Submission Guidelines
Submission Deliverables
- System Design Specification
- TCUML containing all necessary diagrams (interface diagrams, sequence diagrams, etc...)
- Data Models
- Game Plan
- Integration Plan
- Module Architecture Speificiations
- Any other documents that you feel better matches the custom scorecard
Submission Guidelines
For each member, the final submission should be uploaded to the Online Review Tool.