|#||Assigned||Description||Date Identified||Due Date||Date Completed||Status|
|Area of Interest||Details|
Deploying 6.3 to the DEV 6.3 container to test to see if the Term Browser 2.6 release is compatible. If everything goes well then we will redeploy 6.3 on the 6.2 DEV container and then continue on the 6.2 containers for QA, Stage, and Prod.
Preston agreed that this sounds like a patch release. 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.
Participated in a discussion of new report generation requirements. There is a need to implement a new capability for generating CSV formatted reports based on coding scheme search results as shown in the term browser.
Need a decision on where this functionality is going to go to start creating trackers and scope document.
The Term Browser 2.6 Production deployment is tentatively scheduled for Friday morning between 8 and 10AM.
We reviewed the remaining Term Browser trackers for the 2.7 release and priorities. The initial priority is the automated testing trackers.
|Meta Download Validation App|
|Term Suggestion Form|
|NCITERM-595||Handle coding schemes with multiple namespaces.|
Tested lexevs-tree-2.1.0.jar using an npo test coding scheme.
|NCITERM-601||OWL2 annotation features.|
Assessed JSP and backend utility classes that need to be modified for rendering OWL2 annotations (i.e., property qualifiers) in Terms & Properties and Synonyms tabs.
|NCITERM-660||UI Testing Utility.|
Designed methods for generating test cases (i.e., ResolvedConceptReference objects) for coding schemes, including mappings and resolved value set coding schemes.
|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>|