|#||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||The server resources have been expanded with an addition vCPU and an additional 2GB memory. Initial tests have shown better performance but the testing is ongoing.|
|Area of Interest||Details|
|LexEVS 6.2||Still waiting for development environment approval. |
|Report Writer||Starting preparations for a possible release of the report writer with tech stack upgrades after the tech stack upgrade release of the Browsers.|
Continuing with updating BDA Lite for the upgrade to Tomcat and Java 1.7 tasks. Looks like the development environment DRT ticket is getting activity now.
|Meta Download Validation App|
Deployment to stage was successful. Production environment has been setup and waiting for deployment.
|Term Suggestion Form|
Preparing for upgrade to the new tech stack.
|NCIm Browser||Putting together the documentation for the 2.5 release. Mostly just tech stack upgrades.|
Provided technical support to the caDSR team to resolve an unable to retrieve all coding schemes issue.
|NCITERM-600||Java 1.7 Upgrade.|
Update the template of the local.properties file.
Modified build.xml to replace JBoss Ant tasks by Tomcat 7 Ant tasks.
Prepared a draft Test Plan for JIRA items 600, 606, and 611.
|NCITERM-601||OWL2 Annotation Features.|
Checked GO owl:Axiom Property load and observed that all such Axiom properties have not been loaded. The Operations team will look into the OWL2 loader issues.
|NCITERM-611||Disable hyperlink of some source codes on the Synonym Tab.|
Assessed the code change required to implement the feature request.
|Area of Interest||Details|
|Term Browser 2.5 Release||Continue design activities for new feature requests|
|NCIm Browser 2.4 Release|
Provide required support for deployment to Prod 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/2013||The Term Browser deployments using AntHillPro require JAVA 1.6.||This would affect the deployments and production environment for the EVS tools. It sounds like this is going to be a future issue but we should have time to upgrade before it is part of the CBIIT tech stack.||Currently working on the JAVA 1.7 upgrade for Term Browser|
|7/31/2013||We currently have an issue where the browsers are ready to move to the QA tier for testing but due to the dependency of LexEVS 6.1 cannot start the QA testing process. LexEVS 6.1 does not currently have all the pre-QA qualification to proceed with the deployment to the QA tier.||With a hard deadline of Sept. 30 for both the browsers and LexEVS API 6.1 there is concern that there will be time to finish all the testing and deployments on time.||This is closed. The hard deadline was expanded due to factors we cannot control.|