EVS Focus Meeting Minutes - 09 September 2015

Attendees

#	Assigned	Description	Date Identified	Due Date	Date Completed	Status
						.

Area of Interest	Details
LexEVS	The systems team shutdown the 6.0, 6.1 and 6.2 containers with all the URL's now pointing to the 6.3 container. Leaving the 5.1 production and stage container up. Stage will be shutdown when the latest data is deployed.
Report Writer	Need a decision on where this functionality is going to go to start creating trackers and scope document.
Term Browser	AppScan completed in 5 days with 3 cross site scripting vulnerabilities. Continuing QA testing. QA Team opened a couple of tickets, one of which was already fixed by Kim (partonomy tree). Having issue with the back button sporadically on Term Browser
Meta Download Validation App
NCIm Browser	Working on Scope Document and PTE for NCIm browser 2.6 release.

Issue Number

Description

Status

NCITERM-691

View In Hierarchy tree node expand/collapse issue.

Resolved a tree node expansion issue.

Improved tree node expansion performance.

NCIM-207

Migrate to LexEVSAPI 6.3.

Identified the difference between metabrowser v2.5 and LexEVSAPI 6.3 library folders.

Removed eclipse jars, protégé.jar and protege-owl.jar from v2.6 library folder.

#	Description	Due Date	Resources	Notes	Risks	Mitigation

Area of Interest	Details
Term Browser 2.7 Release	Test and deployment of the 2.7 release.
NCIm Browser 2.6 Release	Planning for development of 2.6 release.

#	Opened Date	Due Date	Description	Likelihood (H, M, L)	Impact	Assigned	Status	Mitigation Strategy
	09/10/2015			H	H		AppScan are taking long periods of time to complete. For Term browser, the minimum has been 5 days.	We are working on both the code base and configuration of the scan to try to improve performance. We are also looking at open source code scanners that could possibly be used ahead of the AppScan to at least limit the number appscans required.

Opened Date	Description	Impact	Status
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>