NIH | National Cancer Institute | NCI Wiki  

Attendees

NameRole
  
  
  

 

Action Items

 #AssignedDescriptionDate IdentifiedDue DateDate CompletedStatus
 Mayo/JasonWe 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/2014A new development server has been procured and is currently being setup.  This AI will be closed.

Progress

Area of InterestDetails
LexEVS 6.2The external stage environment is now setup and the 6.2 release has been unofficially deployed.
Report WriterWaiting for the DEV environment to be setup.  Development on ongoing.
Term Browser 

Term Browser services are still waiting for approval from QA Lead to proceed  to stage.  QA manager requesting that Metathesaurus Browser and Term Form test results before approving stage deployment.

The systems team is currently working on the 2.6 DEV container.

Meta Download Validation App

Term Suggestion Form

QA testing has been completed and no defects found.  There is still an issue with getting the AppScan done for the Term Form.  The security team is working on getting the AppScan software working.

NCIm Browser

QA testing has been completed and no defects found.  AppScan completed with no high or medium vulnerabilities.

Currently waiting for the Term Form AppScan to complete to get approval to move all applications to stage.


JIRA Issues

Issue NumberDescriptionStatus
NCITERM-625Add NCI Metathesaurus link to browser.Implemented
   

Schedule Changes

 

#DescriptionDue DateResourcesNotesRisksMitigation
       

 Planned Activities

Area of InterestDetails
Term Browser 2.6 ReleaseContinue design activities for new feature requests
NCIm Browser 2.5 Release

Deployment to the DEV tier.

Report WriterDevelop Project plan for 2.1 release.
Term Browser 2.5 ReleaseDeployment to the Stage tier.
Term Form 2.4 ReleaseDeployment to the DEV tier.

Risks, Issues, Dependencies

Risks

Opened DateDue DateDescriptionLikelihood (H, M, L)ImpactAssignedStatusMitigation Strategy
 04/10/14 Deployments have been taking long periods of time. There is a lot of overhead getting through the itersH H Speaking with members of the QA team to find ways to streamline the testing/deployment processFinding ways to better integrate the development and QA team. Spoke to EVS Tools TPM requesting the correct communication channels.
         

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