|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Mayo/Jason||We have run into multiple issues where the performance on the DEV tier has be a problem due to Mayo not being able to replicate the slow points due to the drastic difference in DEV resources. We discuss this with the systems team and they requested us to put in a DRT ticket that provides the specs to match the Mayo DEV server.||08/30/13||7/16/2014||A new development server has been procured and is currently being setup. This AI will be closed.|
|Area of Interest||Details|
During the "Miracle Week" we were able to get a deployment all the way to the Stage tier for each of the EVS tools including the LexEVS API, CTS2, URI Resolver and Term Browser.
There were some issues on the URI Resolver appscan on Stage that need further analysis.
|Report Writer||Put in DRT ticket for DEV tier setup for Report Writer 2.1 environment. |
The 2.5 release is now working on the Stage tier. Testing is currently being performed on the QA tier.
AppScan passed on DEV and QA tiers with no high or medium vulnerabilities.
|Meta Download Validation App|
|Term Suggestion Form|
The containers are still being worked on for the new development environment.
Container was created for DEV tier. Working through deployment issues.
|EVSREPORT-94||Generate reports without the UI.|
Remove CSMAuthorizationManager.java from the utils package.
Create a separate security package to include CSMAuthorizationManager.java.
Identify source code that need to be modified to support the implementation of the feature request.
Modify build script to include a new ant target, ncirw.jar.
Create build script, ncirw-build.xml for building the ncirw.jar.
|Section 508: Readability Custom Report: Value Sets Check Boxes are not available without Style sheet|
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue design activities for new feature requests|
|NCIm Browser 2.5 Release|
Deployment to the DEV tier.
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.5 Release||Deployment to the Stage tier.|
|Term Form 2.4 Release||Deployment to the DEV tier.|
Risks, Issues, Dependencies
|#||Opened Date||Due Date||Description||Likelihood (H, M, L)||Impact||Assigned||Status||Mitigation Strategy|
|04/10/14||Deployments have been taking long periods of time. There is a lot of overhead getting through the iters||H||H||Speaking with members of the QA team to find ways to streamline the testing/deployment process||Finding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.|
|7/17/2014||Deployment of software, even small upgrades, have been a lengthy process.||This especially affects smaller releases in which there are security or bug fixes.||The Agile practices migration have been put on hold for now.|
|09/10/2014||Getting the environment in place for the Mayo trip to NCI.||Need to get each of the environment (DEV,QA,Stage) in place before the Mayo trip on September 22nd. We are currently one week behind. The impact is that the Mayo developer will be onsite to work on the deployments and the tiers will not be in place.||Currently we only have the DEV environment setup for the LexEVS API>|