Produced by Araxis Merge on 4/23/2019 12:14:41 PM Central Daylight Time. See www.araxis.com for information about Merge. This report uses XHTML and CSS2, and is best viewed with a modern standards-compliant browser. For optimum results when printing this report, use landscape orientation and enable printing of background images and colours in your browser.
| # | Location | File | Last Modified |
|---|---|---|---|
| 1 | C:\AraxisMergeCompare\Pri_un\CCRS\ccra-6.3.0\ccra-6.3.0\artifacts\Build_3\Sprint_1\docs | Build 3 S1-3 T5 WIS v02.xlsx | Wed Mar 20 03:15:56 2019 UTC |
| 2 | C:\AraxisMergeCompare\Pri_re\CCRS\ccra-6.3.0\ccra-6.3.0\artifacts\Build_3\Sprint_1\docs | Build 3 S1-3 T5 WIS v02.xlsx | Wed Apr 17 04:45:26 2019 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 1 | 58 |
| Changed | 0 | 0 |
| Inserted | 0 | 0 |
| Removed | 0 | 0 |
| Whitespace | |
|---|---|
| Character case | Differences in character case are significant |
| Line endings | Differences in line endings (CR and LF characters) are ignored |
| CR/LF characters | Not shown in the comparison detail |
No regular expressions were active.
| 1 | SHEET: She et1 | |
| 2 | Index,Pre- Req,Priori ty,Points, Target Spr int,Swim L ane Text,W I Story Te xt,Accepta nce Text,T asks, | |
| 3 | 1,1,3,1,Re ferral Sch ema & Pre- Authorizat ion change s,S5-CS023 -As a CCRS Developer , I need t o continue to synchr onize the CCRS Refer ral schema with the changing C CRA schema , includin g notifica tion of ot her intern al CCRS te ams, so th at CCRS ca n continue to proces s new and update ref errals fro m CCRA.,At end of sp rint, the most recen t JSON fil e sent by CCRA, with new schem a changes, can still be import ed into CC RS.,Schema changes, Java chang es, Unit T ests, Deve loper Test ing, Inter -Team coor dination, Review of CCRS nneds w/r/t CCR A, Communi cations wi th CCRA on prioritie s, Documen tation cha nges, TC, TS, TE, De mo Prep, B A Review, | |
| 4 | 2,1,5,3,2, Referral S chema & Pr e-Authoriz ation chan ges,S5-CS0 23-As a CC RS Develop er, I need to contin ue to sync hronize th e CCRS Ref erral sche ma with th e changing CCRA sche ma, includ ing notifi cation of other inte rnal CCRS teams, so that CCRS can contin ue to proc ess new an d update r eferrals f rom CCRA., At end of sprint, th e most rec ent JSON f ile sent b y CCRA, wi th new sch ema change s, can sti ll be impo rted into CCRS.,Sche ma changes , Java cha nges, Unit Tests, De veloper Te sting, Int er-Team co ordination , Review o f CCRS nne ds w/r/t C CRA, Commu nications with CCRA on priorit ies, Docum entation c hanges, TC , TS, TE, Demo Prep, BA Review , | |
| 5 | 3,2,10,3,3 ,Referral Schema & P re-Authori zation cha nges,S5-CS 023-As a C CRS Develo per, I nee d to conti nue to syn chronize t he CCRS Re ferral sch ema with t he changin g CCRA sch ema, inclu ding notif ication of other int ernal CCRS teams, so that CCRS can conti nue to pro cess new a nd update referrals from CCRA. ,At end of sprint, t he most re cent JSON file sent by CCRA, w ith new sc hema chang es, can st ill be imp orted into CCRS.,Sch ema change s, Java ch anges, Uni t Tests, D eveloper T esting, In ter-Team c oordinatio n, Review of CCRS nn eds w/r/t CCRA, Comm unications with CCRA on priori ties, Docu mentation changes, T C, TS, TE, Demo Prep , BA Revie w, | |
| 6 | 4,6,3,1.5, Referral S chema & Pr e-Authoriz ation chan ges,S5-CS0 23-As a CC RS Develop er, I need to implem ent connec tivity fro m CCRA to a higher e nvironment in CCRS ( SQA) so th at testing data is a vailable., At the end of sprint , we have connectivi ty between existing CCRA SQA e nvironment and the m atching CC RS SQA env ironment. Risk: CCRA not achie ving appro val for co nnectivity of produc tion data from TIC t o AITC,Coo rdination with CCRA/ TIC (far s ide), Coor dination w ith ESE/AI TC (local side), Coo rdination with ESCCB (special network co nnection e xceptions - tunnel/v pn VA to c loud), SFT P configur ation, Lin ux account creation, Connectio n troubles hooting, D ocumentati on, TC, TS , TE, Demo Prep, BA Review, | |
| 7 | 5,4,11,5,3 ,Referral Schema & P re-Authori zation cha nges,S5-CS 023-As a C CRS Develo per, I nee d to imple ment conne ctivity fr om CCRA to the highe st environ ments in C CRS (PP, P rod) so th at testing and produ ction data is availa ble.,At th e end of s print, we have conne ctivity be tween exis ting CCRA PP/Prod en vironments and the m atching CC RS PP/Prod environme nts. Risk: CCRA not achieving approval f or connect ivity of p roduction data from TIC to AIT C, | |
| 8 | 6,2,3,1,Re place simp le duplica te removal w/ Referr al Status/ Update tra cking (Tea m 4 to use version i n effect o n “date of service” of line it em),S5-CS0 23-As a CC RS Develop er, I need to design the schem a changes to handle Referral u pdates sen t from CCR A (additio n/removal of content , correcti ons, cance llations) so that th e busines s rules en gine has a vailable i nformation from the referral t hat was in effect at the time of treatme nt.,At the end of th e sprint t he ICD is updated., Plan for S chema chan ges, Plan for Java c hanges, In ter-Team c oordinatio n, Documen tation cha nges, TC, TS, TE, De mo Prep, B A Review, | |
| 9 | 7,6,7,8,2, Replace si mple dupli cate remov al w/ Refe rral Statu s/Update t racking (T eam 4 to u se version in effect on “date of service ” of line item),S5-C S023-As a CCRS Devel oper, I ne ed to impl ement the schema cha nges to ha ndle Refer ral update s sent fro m CCRA (ad dition/rem oval of co ntent, cor rections, cancellati ons), as w ell as the initial J ava code c hanges, so that the business rules engi ne has ava ilable inf ormation f rom the re ferral tha t was in e ffect at t he time of treatment .,At the e nd of the sprint, we can show that we im port all u pdates to referrals and use a multi-colu mn key for uniquenes s. We also show the date range s differen t versions of Referr als are in effect fo r., | |
| 10 | 8,7,12,5,3 ,Replace s imple dupl icate remo val w/ Ref erral Stat us/Update tracking ( Team 4 to use versio n in effec t on “date of servic e” of line item),S5- CS023-As a CCRS Deve loper, I n eed to com plete the Java code changes to handle Re ferral upd ates sent from CCRA (addition/ removal of content, correction s, cancell ations) so that the business rules engi ne has ava ilable inf ormation f rom the re ferral tha t was in e ffect at t he time of treatment .,At the e nd of the sprint, we work with the Busin ess Rules engine tea m (Team 4) to show t hat the re ferral in effect for the right time peri od is prop erly check ed based o n the serv ice date o f the proc edure perf ormed for the patien t., | |
| 11 | 9,3,5,1,In terface Or chestratio n / Integr ation w/ T eam 4,S5-C S009-As a CCRS Devel oper, I ne ed to desi gn and dev elop a pro of-of-conc ept Kafka implementa tion to op timize the orchestra tion of ex ternal dat a aggregat ion into t he CCRS da tabase so that CCRS can meet t he target of nominal 24 hour t urnaround from recei ving EDI d ata to not ifying the responsib le party t hat paymen t is appro ved.,At th e end of t he sprint, we show t hat Kafka is able to schedule work and t ransition from one c omponent t o another. ,Installat ion, Confi guration, Deployment , Integrat ion librar y, Integra tion with an existin g Interfac e, Unit Te sts, Devel oper Testi ng, Docume ntation, T C, TS, TE, Demo Prep , BA Revie w, | |
| 12 | 10,9?,8,3, 1.5,Interf ace Orches tration / Integratio n w/ Team 4,S5-CS009 -As a CCRS Developer , I need t o design t he initial granulari ty pattern for Kafka so that C CRS Interf ace design ers can pr operly lin k their co de into th e Kafka co ntrol logi c so that CCRS can m eet the ta rget of no minal 24 h our turnar ound from receiving EDI data t o notifyin g the resp onsible pa rty that p ayment is approved., At the end of the sp rint, we s how that K afka is se nding, rec eiving and tracking message qu eues at th e target g ranularity .,Inter-Te am coordin ation, int erface mod ification, configura tion, depl oyment, de veloper te sting, doc umentation , TC, TS, TE, Demo P rep, BA Re view, | |
| 13 | 11,10,13,5 ,3,Interfa ce Orchest ration / I ntegration w/ Team 4 ,S5-CS009- As a CCRS Developer, I need to implement control l ogic for K afka in CC RA so that CCRS can meet the t arget of n ominal 24 hour turna round from receiving EDI data to notifyi ng the res ponsible p arty that payment is approved. ,At the en d of the s print, we show that Kafka is p ushing mes sages into the ccrab atch java code which the ccrab atch java code uses as a work queue., | |
| 14 | 12,11,14,3 ,3,Interfa ce Orchest ration / I ntegration w/ Team 4 ,S5-CS009- As a CCRS Developer, I need to document configurat ion of ccr abatch in Kafka so t hat the VA can insta ll/configu re Kafka a nd that CC RS can mee t the targ et of nomi nal 24 hou r turnarou nd from re ceiving ED I data to notifying the respon sible part y that pay ment is ap proved.,At the end o f the spri nt, show o ur contrib utions to the Kafka installati on guide., | |
| 15 | 13,12,15,3 ,3,Interfa ce Orchest ration / I ntegration w/ Team 4 ,S5-CS009- As a CCRS Developer, I need to deploy Ka fka and th e ccrabatc h configur ation to S QA so that the we ca n test the installat ion guide and so th at CCRS ca n meet the target of nominal 2 4 hour tur naround fr om receivi ng EDI dat a to notif ying the r esponsible party tha t payment is approve d.,At the end of the sprint, s how Kafka and CCRA p roperly in teracting in SQA., | |
| 16 | 14,4,3,1,E merging is sue: SEOC v2 – More formal SEO C schema c oming,S5-C S023-As a CCRS Devel oper, I wa nt to prot otype the [SEOC] sch ema in CCR S so that we are mor e prepared for devel oping a co nnection t o the SEOC repositor y when it comes onli ne.,At the end of th e sprint, show new S EOC schema in DB.,Do cumentatio n, Communi cations wi th CCRA, C ommunicati ons with S EOC repres entatives, Schema pr ototype, p rototype i mplementat ion, Inter -team revi ew, docume ntation, T C, TS, TE, Demo Prep , BA Revie w, | |
| 17 | 15,14,9,3, 2,Emerging issue: SE OC v2 – Mo re formal SEOC schem a coming,S 5-CS023-As a CCRS De veloper, I want to f urther dev elop the [ SEOC] sche ma in CCRS so that w e are more prepared for develo ping a con nection to the SEOC repository when it c omes onlin e.,At the end of the sprint, s how update s to SEOC schema in DB., | |
| 18 | 16,15,16,3 ,3,Emergin g issue: S EOC v2 – M ore formal SEOC sche ma coming, S5-CS023-A s a CCRS D eveloper, I want to further de velop the [SEOC] sch ema in CCR S so that we are mor e prepared for devel oping a co nnection t o the SEOC repositor y when it comes onli ne.,At the end of th e sprint, show updat es to SEOC schema in DB., | |
| 19 | 21,Emergin g issue: p re-certifi cation/pre -approval – source o f data (se parate fro m current CCRA pre-a uthorizati on block w hich is a subset of the SEOC), | |
| 20 | 22,Emergin g issue: p re-certifi cation/pre -approval – source o f data (se parate fro m current CCRA pre-a uthorizati on block w hich is a subset of the SEOC), | |
| 21 | 23,Emergin g issue: p re-certifi cation/pre -approval – source o f data (se parate fro m current CCRA pre-a uthorizati on block w hich is a subset of the SEOC), | |
| 22 | 24,Emergin g issue: p re-certifi cation/pre -approval – source o f data (se parate fro m current CCRA pre-a uthorizati on block w hich is a subset of the SEOC), | |
| 23 | 25,Emergin g issue: p re-certifi cation/pre -approval – source o f data (se parate fro m current CCRA pre-a uthorizati on block w hich is a subset of the SEOC), | |
| 24 | ||
| 25 | ||
| 26 | SHEET: She et2 | |
| 27 | ||
| 28 | ||
| 29 | SHEET: She et3 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.