EMP Panels Phase 3C MetaVolume and Device and FLM Device and Private Device Controllers And Pages Assembly

Register
Submit a solution
The challenge is finished.

Challenge Overview

 

1. 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 3C.

2. Competition Task Overview

This assembly provides the controllers and pages to build the screens for the MetaVolume And Device.

2.1 Code Base

Code Base: https://coder.topcoder.com/tcs/clients/mnemosyne/emp_panels/Src/branches/3C - MetaVolume and Device and FLM Device and Private Device Controllers And Pages

Hint: You can get the code of commom part from here (https://coder.topcoder.com/tcs/clients/mnemosyne/emp_panels/Src/branches/2 - Storage Bay and Disk Controllers and Pages and Common Parts Merge).

Notes:

  1. Remove the empty constructor if it's the only constructor.
  2. Use spring-form tag to generate the form in JSP file.
  3. Remove thread safety warning in javadocs. Singleton pattern is well understood and is not a comment specific to these classes functions.
  4. Don't chain the URL's. Follow standard to specifying the whole URL string for clarity.
  5. Controller design - by default, all the assemblies return a ModelAndView for non-AJAX requests, client wants to pass in a model and just return the view name (String).

2.2 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).

2.3 Coding standards

You'll have access to phase 1 code and should following the client's standards for coding (including testing).

You're also required to strictly use the listed versions of libraries in existing code, you're not allowed to delete any dependency from the pom files even fi they are not used by the current code.

2.4 Testing

Functional tests are required for the controller methods.

3. Technology Overview

  • Java 1.6
  • Tomcat 6
  • Spring 3.2.2
  • Apache Tiles 2.2.2
  • jQuery 1.7.2
  • Maven

4. Documentation Provided

Documents are only available to registrants.



Final Submission Guidelines

5. 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

Review style

Final Review

Community Review Board

Approval

User Sign-Off

Challenge links

ID: 30034638