Challenge Overview

Project Overview

Platane is a web-based resource-planning-tool (a resource is an employee with its work-capacity).

In Platane an employee can be reserved for a particular project (example: John works for project PLATANE 40% (2 days/week) from 1.1.2015 – 30.6.2015).Platane displays the work levels of the teams and employees, and projects the workload.. Platane collects from Exchange Server the absences of the employees and collects from Jira the assigned tasks for the employees. With an optimizing-algorithm, Platane calculates the optimal work-order of the tasks and the workload of the employees.

Competition Task Overview

In the previous challenge we've implemented some of the pages and integration.

For this challenge, we need to integrate the rest of the UI with the backend services. This challenge must cover all the pages from the prototype.

The following use cases (see Platane-business-requirements_V01.01.pdf for details) should be covered but scope is not limited to these but should cover all pages from the prototype.

  • 3.1.5 Add Resource (note that add/edit/delete is in scope)
  • 3.1.7 Maintain Public Holidays (note that add/edit/delete is in scope)
  • 3.1.8 View Outlook Absence
  • 3.1.9 View Jira Task
  • 3.1.10 Generate RSS Feed

Detailed Requirements

  • The backend needed to support the UI was already implemented in ch.post.it.plat.process.manager ch.post.it.plat.web.controller. Please see section 4 and section 5.4 in Platane-software-specification_V01.02.pdf to better understand how the layers are separated. This challenge should wire the pages with the REST API.
  • The code must be delivered in \plat-web\src\main\webapp\app (and subdirectories) for this challenge
  • The base for the GUI is the provided GUI-Prototype (dialogs, styling, etc). This prototype overrules the screenshots provided in the business-spec-documentation.
  • Please do NOT include security-control in this challenge, because it will be handled in upcoming challenges.

Client Standards

Please make sure you go through all client documents, they contain important information about how you should write your code:

  • Developers-guide.pdf
  • Platane-business-requirements-v01.01.pdf
  • Platane-software-specification-v01.02.pdf

Testing

Unit tests are not required for this challenge.

Existing unit tests must still work after this challenge.

Technology Overview

  • Java 8
  • Maven 3
  • Jira REST API
  • Exchange Server EWS Web Services
  • Spring MVC
  • Oracle 11 / Express Edition
  • Angular.js
  • HTML5
  • Javascript
  • CSS

Documentation Provided

Register to download all 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 all requirements
  • A complete and detailed deployment document explaining how to deploy the application including configuration information.
  • The maven build script to build and run the code / tests.

Final Submission

For each member, the final submission should be uploaded via the challenge detail page on topcoder.com.

ELIGIBLE EVENTS:

2016 TopCoder(R) Open

REVIEW STYLE:

Final Review:

Community Review Board

Approval:

User Sign-Off

SHARE:

ID: 30051683