|#||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|
Setting up the 6.3 development environment
We were able to successfully deploy Report Writer to the DEV environment. Running into some DAO issues that we are currently working through. Anticipating another tag.
The 2.5 release of the Term Browser is now live on the production environment.
|Meta Download Validation App|
|Term Suggestion Form|
Term Suggestion Form 24 release is now live on production.
The 2.5 release of the Metathesaurus Browser is now live on the production environment.
Insure Interfaces align with public implementation methods where appropriate.
Developed a test program for testing a remote API method in the Mapping extension. The mappingExtension.resolveMapping method previously found to fail under remote calls appears to be able to sort mapping columns properly in LexEVSAPI 6.2.
|NCITERM-595||Handle coding schemes with multiple namespaces.|
Tested the tree extension lexevs-tree-2.1.0.jar. Reported an SQL too many results exceptions to Mayo for further investigation.
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue review fixes and deployment.|
|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>|