|#||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|
Continued to support LexEVS OWL2 API requirement validation.
|Report Writer||Looking at what is needed to complete the deployment on DEV. It appears to be completed and just waiting for the database from the old deployment moved to the Shady Grove deployment.|
Requested additional memory on the Stage tier to match what is currently on DEV and QA. The additional memory has helped with completing AppScans.
Identified methods for instantiating IE, Chrome, and Firefox web drivers in a selenium test run.
Reviewed appscan report generated by the JIRA item [SECURITYTEAM-480]. There is one high vulnerability item left related to cross-site scripting. The term browser was able to detect the scripting and responded by displaying a message indicating an invalid request parameter was identified. Apparently, the appscan team feels that echoing invalid parameter value is not necessary.
Made further modification to the backend code to address the above cross-site scripting vulnerability. A new scan request is submitted subsequently (refer to SECURITYTEAM-495]).
Created a new tag for QA (2015-03-18.1-v2.6).
Responded to the QA team inquiries regarding value set search, hierarchies, view in hierarchy, visualization widgets, etc.
Responded to an inquiry from the user group regarding property qualifiers in a new SNOMED load on DataQA.
The QA team had executed the automated regression tests against the latest tag and they had passed before submitting the AppScan requests. Tin said he will complete the testing and get started on the report to promote to Stage by the time the Scan completes.
Currently working on getting the 2.6 release working on the DEV data tier.
Reviewing and prioritizing trackers for possible inclusion in the 2.7 release.
|Meta Download Validation App|
|Term Suggestion Form|
Term Suggestion Form 24 release is now live on production.
Resolved a commons-lang jar backward compatibility issue -- commons-lang3-3.1.jar is not compatible with commons-lang-2.4.jar.
|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>|