EMP Panels Phase 3A Integration Assembly

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 3A.

Competition Task Overview

This assembly will integrate following 3A assemblies with the latest trunk code, and make sure the integrated code works with the actual services instead of the stubs.

https://coder.topcoder.com/tcs/clients/mnemosyne/emp_panels/Src/branches/3A - Directors Initiators and Port Flags Controllers Pages and Common Parts (Based on Revision 231128 of the trunk code)

https://coder.topcoder.com/tcs/clients/mnemosyne/emp_panels/Src/branches/3A - DX Directors Fibre Director Ports and RDF Directors Controllers Pages (Based on Revision 231128 of the trunk code) 

Latest Trunk (Based on 232224): https://coder.topcoder.com/tcs/clients/mnemosyne/emp_panels/Src/branches/3A - Integration

Please send your request to subversion@topcoder.com if you don't have access.

Tips: You can download the winning submission of Phase 2 Integration Assembly from this page but it's just for reference and please don't make any assumpation based on it because it's not reviewed by client yet.

Integration / Merge

The trunk code has been updated and we need to merge the the submissions with the latest trunk code. You need to make sure duplicates in the submissions are removed and all functionalities and tests still work properly.

In order to merge the changes correctly, the branches should be updated with code from the trunk and any conflicts/issues resolved. The winner will also be responsible for applying any additional updates before the final submission is merged back to the trunk.

The winner will be asked to commit the merged code back to our trunk in SVN.

Additional Changes

1. Show an "enter icon" when user start typing in a filter text box
2. Apply the "modal over modal" fix (previously if you have a modal pop up shown and then click some element on this modal to show another modal popup over it, it doesn't display/behave correctly) in the prototype to the assembliles (if applicable)
3. Make sure the SQ button style is correct in the assemblies (if applicable). Also the SQ correctly defaults to GB, but the table headers default to MB. In the assembly this is correct (both default to GB), we need to make sure that the assembly stays correct when the SQ/Filter fix is applied.
4. We found that many of the Size Qualifiers are missing KB and some that have Cyl, shouldn't. For this assembly, this needs to be fixed: Hosts -> Storage Devices, This one has GB, MB, Blocks, CYL, Should add KB, Should remove CYL (the devices here could be Symm, CLARiiON, HDS, 3rd party, etc.)
5. Previously we had a requirement to implement CTRL-A and CTRL-C for the tables, we're dropping this requirement and instead replacing this with exporting the rows to CSV.
6. Multiple States (See forum)

Test Data

See contest forum.

VM

For this contest, we'll need to make sure that the code works with actual services instead of stubs. And in order to do that you'll need a VM. You'll see more info about VM in contest forum, and you can request a VM by posting in the contest forum.

Technology Overview

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

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:

• The merged code that contains the latest phase 1 code and the code from the 3 phase 4 assemblies.
• A complete and detailed deployment documented explaining how to deploy the application including configuration information. The deployment document must also contain detailed verification steps about how to verify your submission on the VM.
• All tests should still work.