|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
Scott will send Preston an email with what was done so it can be used to get waivers for the AppScan, 508, and minimized QA test plan/results.
Need a decision on where this functionality is going to go to start creating trackers and scope document.
We have been reviewing the rest of the scope items to make sure 6.3 LexEVS covers our requirements. We did find some compatibility issue with 6.3 and 2.6 browser.
Worked with the Operations team to resolve a few metadata issues found on the Stage tier.
|Meta Download Validation App|
|Term Suggestion Form|
|NCITERM-595||Handle coding schemes with multiple namespaces.|
Tested Version 6.3 LexEVSAPI new jars and identified a backward compatibility issue due to the refactoring of the tree extension. The package name of tree service class was changed when the tree extension API was merged into the core LexEVS API.
|NCITERM-660||UI Testing Utility.|
Provided the QA team a sample output of the selenium code generator.
|NCITERM-654||Value Sets: After performing a simple search in the Released File view, the formatting of the page needs adjustment.|
Assessed the JSP code required to fix the reported problem.
|NCITERM-657||View In Hierarchy: When viewing a concept in Zebrafish, clicking on the View In Hierarchy link does not bring up the Zebrafish Hierarchy Tree.|
This is likely due to multiple namespaces in Zebrafish.
|NCITERM-610||Update caBIG VKC link.|
Identified two welcome pages where changes need to be made to satisfy the feature request.
|NCITERM-620||HGNC View Graph link no longer works.|
Performed trouble-shooting and identified the root cause being that NCBO uses code with an underscore (‘_’) whereas NCI uses ‘:’ instead.
|NCITERM-661||Allow browser startup without value sets.|
Assessed the complexity of implementing the feature request.
|Area of Interest||Details|
|Term Browser 2.6 Release||Continue review fixes and deployment.|
|Report Writer||Develop Project plan for 2.1 release.|
|Term Browser 2.7 Release||Scope development|
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>|