Challenge Overview
Project Overview
EMP is a migration planning application that's used to streamline the planning process for data migrations onto storage arrays. It's currently implemented as a stand-alone single user desktop installed Windows application, but is in the process of being ported a web application. The goal of this project is to replace the existing EMP UI with a web UI.
This module is responsible for providing the screens in scope of the phase 2.
Competition Task Overview
This assembly provides the controllers and pages for screens of the symmetrix arrays and system bays of the arrays.
Download attachments in contest forum to see details.
Stubs
For this contest you'll need to work with stub services, and if a service that's used by this contest doesn't exist in the stubs folder yet, you need to add the stub to the package (you can find service spec and api in contest forum).
Coding standards
You'll have access to phase 1 code and should following the client's standards for coding (including testing), you should use the phase 1 code as baseline and add phase 2 features to it.
Please follow the standards in gssd-development-standards.pdf and the other files in the gssd-development-standards-v0.4.zip. The gs-code-templates.xml includes the copyright header that should be used.
For version tag please use @version $Id$.
Page/tab/view-specific javascript should be broken out into separate files. Only globally common js should be in script.js. The prototype started to do this, but didn't do it completely.
Also please put external .js in emp-web\src\main\webapp\static\js and .js created for this project in emp-web\src\main\webapp\static\emp-js.
Another thing that should be improved over the prototype is the use of common controls rather than custom ones where ever possible. For example, for tabs or accordion controls we'd prefer that standard jquery tab and accordion controls be used.
You're also required to strictly use the listed versions of libraries in phase 1 code, you're not allowed to delete any dependency from the pom files even fi they are not used by the current code.
Testing
Functional tests are required for the controller methods.
Technology Overview
- Java 1.6
- Tomcat 6
- Spring 3.2.2
- Apache Tiles 2.2.2
- jQuery 1.10.1
- Maven
Documentation Provided
Register to download documents from the contest 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+Tutorial
Below is an overview of the deliverables:
- Fully Implemented code for this contest.
- A complete and detailed deployment documented explaining how to deploy the application including configuration information.
- Functional Tests to verify your application successfully meets the requirements of the application.
- The (updated) Maven build script to create the war files and run tests. This can be highly variable per competition so be sure to specify necessary deliverables clearly.
Final Submission
For each member, the final submission should be uploaded to the Online Review Tool.