|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
The AppScan request for CTS2 on QA was submitted last week. Security team said it was starting on Tuesday morning.
I will need to put in a ticket for deployment to stage after the scan passes.
Need a decision on where this functionality is going to go to start creating trackers and scope document.
Working on some fixes to the automated testing application. The use of SSL caused some issues that we are now fixing.
The update to the application has been sent to the QA team to test out.
Received results back with 400+ high vulnerabilities. With this error we are seeing that all of the value sets are failing. We have a fix for this error in which we hope will speed up the appscans in the future.
|Meta Download Validation App|
|Term Suggestion Form|
Evaluated the effort of expanding the automated test application to the NCIm Browser. Effort for the NCIm browser should be considerably less than Term Browser.
|NCITERM-682||Contains search failed on search strings containing a colon character.|
This is believed to be a LexEVSAPI bug. See: [LEXEVS-1023] above.
|NCITERM-659||Unit test framework.|
Developed a Junit framework for testing key utility classes.
|NCITERM-677||Add ncicp:subsource-name field to the display of FULL_SYN in Synonym tab|
Added a subsource name column to the FULL_SYN table.
The user group decided that there is no immediate need for this feature.
NCI EVS browsers not working outside NIH firewall
|The View Graph link is implemented using iframe. It fails when the browser switches from HTTP to HTTPS/SSL|
|NCITERM-683||Searching HL7 (V3 R2.36) by code, 10458:BRTH, results in a HTTP 404 error.|
Performed trouble shooting and found that the EntityDescription holding the preferred name of the concept is null. Will modify the code to handle such special cases.
|Area of Interest||Details|
|Term Browser 2.7 Release||Continue development of the 2.7 release.|
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>|