NIH | National Cancer Institute | NCI Wiki  




Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus


Area of InterestDetails
LexEVSPut in a ticket to create at LexEVS 6.4 DEV container.  This will be a new container on DEV.  Once the browsers are deployed to production we can replace this with the regular DEV environment.  This is important to accurately test the performance of 6.4 because the new DEV environment will have the indexes stored on a share drive instead of local.  This is a big hit on performance.
Report Writer

Need a decision on where this functionality is going to go to start creating trackers and scope document.

Term Browser 

We passed the appscan on QA and are deployed to the Stage tier.  Automated tests passed.

QA team put in a ticket for the appscan on Stage.

We notified the MedDRA group about the stage deployment so they can test out the new interface.

Term Suggestion Applicaton
Updated the CDISC_Multi_Term_Request.xls and configuration files. 
NCIm Browser

Continued development on the 2.6 release.

JIRA Issues

Issue NumberDescriptionStatus

Term Browser AppScan Performance.

Resolved all XSS vulnerability item identified in appscan reports.


UI Testing Utility.

Implemented initial capability.

NCIM-209AppScan Performance.


  • Schedule Changes


#DescriptionDue DateResourcesNotesRisksMitigation
  •  Planned Activities

Area of InterestDetails
Term Browser 2.7 ReleaseTest and deployment of the 2.7 release.
NCIm Browser 2.6 ReleasePlanning for development of 2.6 release.
  • Risks, Issues, Dependencies

  • Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation 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.
  • Issues

 #Opened DateDescriptionImpactAssignedStatus
 7/17/2014Deployment 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/2014Getting 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>
  • Dependencies

Opened DateDescriptionAssigned
  • No labels