Page History
...
SYSTEMS | |
---|---|
Systems | Discussion Points:
Decision Points: |
LEXEVS UPDATES | |
LexEVS Sprint Status | Current Sprint - Sprint 203 (Jan 30 - Feb 13 2023) 16X237 Agile Development - Sprint Status#16X237AgileDevelopmentSprintStatus-Sprint203
|
Future Planning | Discussion Points: Planning for Mayo team in the coming fiscal year:
|
Technical Debt remediation |
LoE work to be done - Mark to report |
CTS2 Mapping/URI Resolver | Discussion Points:
Decision Points: |
caDSR Query | Have been asking for other standalone terminologies, expected that they will use CTS2 |
Statistics Dashboard | Discussion Points: Yearly report re-sentNeed 28 day report
Decision Points: |
Comparison/Mapping Tool | Discussion Points:
Decision Points: |
EVS transition to virtual machines | Discussion Points:
Decision Points: |
Report Exporter | Discussion Points:
Decision Points: |
AWS Cloud to be in Separate Account | Discussion Points
Decision Points: |
Team Absences | Mayo Team - MSC - Leidos - Mark off Feb 14-24 Systems - |
EVS SERVICE AND ARCHITECTURE GROUP UPDATES | |
EVS Service and Architecture Group | Discussion Points:
Decision Points: |
DATA UPDATES | |
Data | Discussion Points: Flat file modified for PT and syn order
Decision Points: |
BROWSER UPDATES | |
Browser | Discussion Points:
Decision Points: |
QA UPDATES | |
QA | Discussion Points: (see chart) Decision Points: |
TERMINOLOGIES LIFECYCLE REPORT | |
Terminology Updates and Schedule Discussion Points: Decision Points: | |
Mark Benson TPM Update | Priorities are :
|
LexEVS Spring Migration Progress
Technical Debt Related Update | Estimated Effort | Status | Ticket |
---|---|---|---|
Code Inventory | 4 days | Complete | |
Lexevs - update "easy" jars | 2 days | Complete | |
Update ddlutils - research and design | 3 days | In Progress | |
Update ddltils - implementations | 10 days | ||
Lexevs Unit testing | 2 days | ||
CTS2 lexevs-service vulnerability update | 2 days | ||
CTS2 unit testing | 2 days | ||
QA Lexevs / CTS2 | 3 days | ||
Repair QA issues | 2 days | ||
Deployment Lexevs / CTS2 | 5 days (elapsed) | ||
Update LexEVS to Java 11 - research and design | 4 days | ||
LexEVS Java 11 implementation | 5 days | ||
lucene 9 - research and design | 8 days | ||
lucene 9 - implementation | 15 days | ||
LexEVS Java 11 unit testing | 3 days | ||
CTS2 lexevs-service Java 11 - research and design | 3 days | ||
CTS2 lexevs-service Java 11 implementation | 3 days | ||
CTS2 unit testing | 2 days | ||
QA Lexevs / CTS2 | 3 days | ||
Repair QA issues | 2 days | ||
Update Jenkins | 1 day | ||
Deployment Lexevs / CTS2 | 10 days (elapsed) | ||
lexevs-service-rest-docs vulnerability update design | 2 days | ||
lexevs-service-rest-docs vulnerability implementation | 4 days | ||
lexevs-service-rest-docs unit testing | 1 day | ||
lexevs-service-rest-docs QA | 1 day | ||
lexevs-service-rest-docs deployment | 4 days (elapsed) | ||
lexevs-service-rest-docs Java 11 design | 2 days | ||
lexevs-service-rest-docs Java 11 implementation | 3 days | ||
lexevs-service-rest-docs unit testing | 1 day | ||
lexevs-service-rest-docs QA | 1 day | ||
lexevs-system-test design | 4 days | ||
lexevs-system-test implementation | 6 days | ||
lexevs remaining dependency updates - design | 10 days | ||
lexevs remaining dependency updates - implementation | 20 days | ||
CTS2 remaining dependency updates - design | 1 day | ||
CTS2 remaining dependency updates - implementation | 3 days | ||
Unit testing | 2 days | ||
QA | 2 days | ||
Deployment | 5 days (elapsed) | ||
Total Effort (Approximately) | 104 days |
Technical Debt Related Update | Estimated Effort | Status |
---|---|---|
Report Exporter vulnerabilities - design | 4 days | |
Report Exporter vulnerabilities - implementation | 5 days | |
Unit testing | 2 days | |
QA | 2 days | |
Deployment | 5 days (elapsed) |
...