Challenge Overview
Competition Task Overview
In previous challenges we've build the SRT phase 4 code and added Estimates related tabs. We've also implemented data syncing between the cloud app and the local app which provided us a fully working app with offline capability.
While that's done and being used, we're ready to move to the next phase: re-build this app as an HTML5 app so that we no longer need to maintain a cloud app and a client app. We'd like to use the offline support of HTML5 and make it transprent to the users.
There will be 10+ assemblies in this series, so now is a good time to get familiar with the project and be prepared for the next ones!!
Requirements
The focus of the challenge is to complete the following:
- Complete SRT 3 and Hybrid paths (see the SRT process flow.pdf document), this is fully implemented in the code we provided, but now we need it to be HTML5
- For all 3 paths, make sure the sidebar menus work exactly like the cloud-app / main-app
- On the Service / Activities tab, only the CORE tab is in scope of this challenge, see below:
- Make sure offline feature is correctly done for the SRT3 and Hybrid paths.
- Note the prototype is for reference only, you should follow the page content (fields, behavior, etc...) from the same pages of the main / cloud app. Reviewers must compare the pages and check them in detail.
Documents Provided
- Code: in the provided code we already have the SRT4 path implemented, and now we need SRT3 and Hybrid paths done. You should check the page contents and behaviors from the main-app and do the same using HTML5.
- Prototype: the provided prototype already has most (if not all) of the pages converted to HTML5 so that should give you a good example on how to start.
- Architecture: the architecture documents are out of date now but they are still valuable since they illustrates why and how we want to do the conversion. Two key requirements are: HTML5, Offline Capability. So make sure you read the documents to understand the requirements
HTML5
As we've stated already, HTML5 is the focus of this challenge. The frontend should be static pages using Angular.js, JSP is no longer allowed.
Code Base / Structure
The current code is well structured and we'd like the new HTML5 app to follow similar structure, example: web / js frontend code should reside in its own folder. Each folder has its own pom.xml file and there's a parent pom.xml at the root folder.
Let's keep the cloud app frontend for now since it serves the purpose of verifying whether the pages are correctly converted to HTML5.
Browser Compatability
Refer to the architecture documents for browser compatability requirements.
Technology Overview
- Java
- Oracle
- Tomcat
- HTML5
- AngularJS
Documentation Provided
Register to download documents from challenge forum.
Final Submission Guidelines
Submission Deliverables
A complete list of deliverables can be viewed in the TopCoder Assembly competition Tutorial at: http://apps.topcoder.com/wiki/display/tc/Assembly+Competition+Tutorials
Below is an overview of the deliverables:
- Code that covers the requirements
- A (NEW) complete and detailed deployment documented explaining how to deploy the application including configuration information. If deployment guide needs no change then a separate verification guide.
- The maven build script to create the war files. Very likely you can reuse the existing one and don't need to modify anything.
Final Submission
For each member, the final submission should be uploaded to the Online Review Tool.