Attendees
| Name | Role |
|---|---|
Action Items
| # | Assigned | Description | Date Identified | Due Date | Date Completed | Status |
|---|---|---|---|---|---|---|
| Mayo/Jason | We 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/2014 | A new development server has been procured and is currently being setup. This AI will be closed. |
Progress
| Area of Interest | Details |
|---|---|
| LexEVS 6.2 | LexEVS services are still waiting for approval from Preston to proceed to state. |
| Report Writer | Waiting for the DEV environment to be setup. Currently working on the project plan. |
| Term Browser | Term Browser services are still waiting for approval from Preston to proceed to state. The systems team is currently working on the 2.6 DEV container. |
| Meta Download Validation App | |
| Term Suggestion Form | Term Form DEV and QA environments have been setup. |
| NCIm Browser | Issue with NCIm Browser 2.4 release has been fixed. There was an issue using the local API. It was a lock file issue which was fixed with an update to permissions on a lexevs folder. The AppScan completed with no High or Medium vulnerabilities. |
JIRA Issues
| Issue Number | Description | Status |
|---|---|---|
| NCITERM-604 | Migrate to LexEVSAPI 6.2. | Completed. |
NCIM-202 | Migrate to LexEVSAPI 6.2. | Compared jars in the browser lib folder with those distributed in remote lexevsapi. Updated jars to match with to LexEVSAPI 6.2. |
Schedule Changes
| # | Description | Due Date | Resources | Notes | Risks | Mitigation |
|---|---|---|---|---|---|---|
Planned Activities
| Area of Interest | Details |
|---|---|
| Term Browser 2.6 Release | Continue design activities for new feature requests |
| NCIm Browser 2.5 Release | Deployment to the DEV tier. |
| Report Writer | Develop Project plan for 2.1 release. |
| Term Browser 2.5 Release | Deployment to the Stage tier. |
| Term Form 2.4 Release | Deployment to the DEV tier. |
Risks, Issues, Dependencies
Risks
| # | 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. | |||
Issues
| # | Opened Date | Description | Impact | Assigned | 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> | ||
Dependencies
| Opened Date | Description | Assigned |
|---|---|---|
| . | ||
