Produced by Araxis Merge on 5/8/2017 10:03:07 PM Eastern 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 | var-utility-web-Release-1.0.0-Branch.zip\MHED_VAR_DOCS | System+Design+Document+(SDD)+Addendum.docx | Mon May 8 15:40:59 2017 UTC |
| 2 | var-utility-web-Release-1.0.0-Branch.zip\MHED_VAR_DOCS | System+Design+Document+(SDD)+Addendum.docx | Mon May 8 18:13:10 2017 UTC |
| Description | Between Files 1 and 2 |
|
|---|---|---|
| Text Blocks | Lines | |
| Unchanged | 1 | 574 |
| 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 | System Des ign Docume nt (SDD) A ddendum | |
| 2 | Mobile App lication S ystem Desi gn Documen t (SDD) Ad dendum | |
| 3 | The System Design Do cument (SD D) is a du al-use doc ument that provides the concep tual desig n as well as the as- built desi gn. This d ocument wi ll be upda ted as the product i s built, t o reflect the as-bui lt product . Per the Project Ma nagement A ccountabil ity System (PMAS) Gu ide, the S DD with co nceptual d esign is r equired pr ior to the Milestone 1 Review. The as-bu ilt for ea ch deliver y must be incorporat ed prior t o the Mile stone 2 Re view. | |
| 4 | **Replace the blue i nstruction al text in the vario us fields and tables below** | |
| 5 | Mobile App lication I nformation | |
| 6 | Project In crement / Release De signation: <insert – example: MBB Nation al Release , or MoveC oachMobile v2> | |
| 7 | Product Ve rsion: x. x (do not need minor version u nless this is known) | |
| 8 | ||
| 9 | ||
| 10 | Veteran | |
| 11 | Care Giver | |
| 12 | Provider | |
| 13 | Public | |
| 14 | Intended A udience fo r Mobile A pplication | |
| 15 | ||
| 16 | ||
| 17 | ||
| 18 | ||
| 19 | ||
| 20 | Question | |
| 21 | Yes | |
| 22 | No | |
| 23 | If Yes, wh at informa tion / dat a | |
| 24 | If yes, th en identif y any cons umer or so urce syste m(s) for t he data | |
| 25 | Does the u ser enter informatio n or data into the m obile appl ication? | |
| 26 | ||
| 27 | ||
| 28 | ||
| 29 | ||
| 30 | Does Mobil e Applicat ion store informatio n or data entered by the User? If yes, w here is it stored? | |
| 31 | ||
| 32 | ||
| 33 | ||
| 34 | ||
| 35 | Does Mobil e Applicat ion transm it/push da ta entered outside o f the VAMF to VA? | |
| 36 | ||
| 37 | ||
| 38 | ||
| 39 | ||
| 40 | Does Mobil e Applicat ion pull d ata from a VA Databa se (extern al to VAMF )? | |
| 41 | ||
| 42 | ||
| 43 | ||
| 44 | ||
| 45 | Does the M obile Appl ication st ore in the VAMF or o n the devi ce data pu lled from a VA Datab ase? | |
| 46 | ||
| 47 | ||
| 48 | ||
| 49 | ||
| 50 | ||
| 51 | This appli cation can be classi fied as on e of the f ollowing: | |
| 52 | Mobile App lication C lassificat ion (Only one box ma y be check ed) | |
| 53 | Mark with X | |
| 54 | 1 – Very Low: Mobil e Applicat ion does n ot use VA Resource | |
| 55 | ||
| 56 | 2 – Low: Read only access to VA Resourc e(s) (No P II / PHI) | |
| 57 | ||
| 58 | 3 – Mediu m: Write a ccess to V A Resource (s) | |
| 59 | ||
| 60 | 4 – High: Read and/ or Write a ccess of s ensitive d ata to VA Resource(s ) (Include s PII/PHI/ other sens itive) | |
| 61 | ||
| 62 | ||
| 63 | Applicatio n Design | |
| 64 | Provide de sign infor mation, di agrams, et c. about t he mobile applicatio n. Include : | |
| 65 | Diagram sh owing arch itecture | |
| 66 | Diagram sh owing the components of the ap p | |
| 67 | Descriptio n / diagra m of data flows if a ppropriate - for exa mple, show flows to external s ystems, se rvices wit hin the VA MF, etc. | |
| 68 | ||
| 69 | ||
| 70 | ||
| 71 | Device's O S | |
| 72 | Native | |
| 73 | Hybrid | |
| 74 | Web-Only | |
| 75 | OS version supported | |
| 76 | Targeted d evices (iP hone, iPad , Samsung model...) | |
| 77 | Estimated Storage Re quired for Device | |
| 78 | iOS | |
| 79 | ||
| 80 | ||
| 81 | ||
| 82 | ||
| 83 | ||
| 84 | ||
| 85 | Android | |
| 86 | ||
| 87 | ||
| 88 | ||
| 89 | ||
| 90 | ||
| 91 | ||
| 92 | Windows 8 | |
| 93 | ||
| 94 | ||
| 95 | ||
| 96 | ||
| 97 | ||
| 98 | ||
| 99 | ||
| 100 | Technologi es, Librar ies, and T ools Used in the App | |
| 101 | Version | |
| 102 | On the TRM ? (If not, provide a link to t he waiver) | |
| 103 | HTML5 | |
| 104 | 5 | |
| 105 | Yes | |
| 106 | Cordova | |
| 107 | 2.9 | |
| 108 | Yes | |
| 109 | Backbone | |
| 110 | Etc. | |
| 111 | ||
| 112 | MongoDB | |
| 113 | <version> | |
| 114 | No - <inse rt URL to MongoDB wa iver> | |
| 115 | ||
| 116 | ||
| 117 | ||
| 118 | ||
| 119 | Data Archi tecture | |
| 120 | Add a tabl e like the below for listing N oSQL data collection s stored. This is sa mple data- -replace i t with you r own: | |
| 121 | Ref # | |
| 122 | NoSQL Coll ection | |
| 123 | Descriptio n of data collection | |
| 124 | Source of data | |
| 125 | Structure | |
| 126 | 1 | |
| 127 | BPR.User | |
| 128 | The bprUse r collecti on enumera tes the Ve terans or Service me mbers who have used the applic ation. | |
| 129 | MVI, VIERS | |
| 130 | var bprUse rSchema = new db.mon goose.Sche ma({userId : String,e dipi: Stri ng,** othe r fields d eleted to make this shorterser viceStatus : {type: S tring,enum : ['VETERA N','ACTIVE _DUTY']},u serState: {state: {t ype: Strin g,enum: [' ELIGIBLE', 'NOT_ELIGI BLE','CONS ENT','NOT_ CONSENT',' REVIEW_REQ UESTED','R EVIEWED_NO T_ELIGIBLE ','PARTICI PANT']},la stUpdated: Date} | |
| 131 | ||
| 132 | ||
| 133 | ||
| 134 | ||
| 135 | ||
| 136 | ||
| 137 | Add tables like this for Relat ional tabl es: | |
| 138 | Column Nam e | |
| 139 | Data Type | |
| 140 | Nullable | |
| 141 | Descriptio n | |
| 142 | PK | |
| 143 | FK | |
| 144 | CODE | |
| 145 | varchar(25 5) | |
| 146 | N | |
| 147 | Auth Code granted to client | |
| 148 | Y | |
| 149 | N | |
| 150 | AUTHENTICA TION | |
| 151 | BLOB | |
| 152 | Y | |
| 153 | Serialized OAuth Aut henticatio n object | |
| 154 | N | |
| 155 | N | |
| 156 | ||
| 157 | ||
| 158 | ||
| 159 | ||
| 160 | ||
| 161 | ||
| 162 | ||
| 163 | Provide so me volume / sizing i nformation for each collection / table: | |
| 164 | Table or C ollection | |
| 165 | Number of Rows / Ent ries | |
| 166 | Estimated Size per E ntry | |
| 167 | Total Disk (minus ov erhead for indexes, etc) | |
| 168 | CODE | |
| 169 | 1 per app | |
| 170 | 1024 bytes | |
| 171 | 1024 bytes | |
| 172 | PERSON | |
| 173 | 1000 users | |
| 174 | 2048 bytes | |
| 175 | 2MB | |
| 176 | etc. | |
| 177 | ||
| 178 | ||
| 179 | ||
| 180 | Laws / reg ulations t hat direct the imple mentation of the app ? | |
| 181 | <insert he re> | |
| 182 | Expected c oncurrent and maximu m size of the user b ase? | |
| 183 | User Categ ory | |
| 184 | Total Numb er of User s | |
| 185 | Concurrent Users | |
| 186 | Veterans | |
| 187 | any OEF - 1M+ | |
| 188 | 1000 | |
| 189 | Interface Design | |
| 190 | Existing V AMF Interf aces Used | |
| 191 | (This sect ion means VAMF servi ces alread y deployed in produc tion for t his app) | |
| 192 | Interface Name (incl . version number) | |
| 193 | Data Used by Mobile App | |
| 194 | Source of Data | |
| 195 | Data Retri eved - pro vide speci fic data e lements us ed by this app | |
| 196 | Auth Servi ces 4.0 | |
| 197 | Authentica tion Respo nse | |
| 198 | DSLogon | |
| 199 | First name , last nam e, EDIPI | |
| 200 | ||
| 201 | ||
| 202 | ||
| 203 | ||
| 204 | ||
| 205 | ||
| 206 | ||
| 207 | ||
| 208 | New/Update d VAMF Int erfaces Ad ded | |
| 209 | This secti on should contain se rvices tha t are bein g deployed with this app - RES Tful / oth er web ser vices that become pa rt of the VAMF servi ce invento ry, but ar e not avai lable in p roduction yet. | |
| 210 | Interface Name (incl . version #) | |
| 211 | Data Used by Mobile App | |
| 212 | Source of Data | |
| 213 | Included i n Program- Level SDD? | |
| 214 | Consult Se rvices | |
| 215 | XXX Table | |
| 216 | CDW | |
| 217 | No | |
| 218 | ||
| 219 | ||
| 220 | ||
| 221 | ||
| 222 | Add rows a s needed | |
| 223 | ||
| 224 | ||
| 225 | ||
| 226 | For all se rvices not currently in the Pr ogram-Leve l SDD, pro vide the d ocumentati on here th at should be include d - servic es, reques t data, re sponse dat a, etc. | |
| 227 | <Insert de sign of Co nsult Serv ices here> | |
| 228 | ||
| 229 | Dependenci es/SLA | |
| 230 | For exampl e, you are reliant o n a VA sys tem to imp lement som ething for you, incl uding supp orting tes ting: | |
| 231 | Project De pendency | |
| 232 | Point of C ontact Inf ormation | |
| 233 | Describe D ependency | |
| 234 | ||
| 235 | ||
| 236 | ||
| 237 | ||
| 238 | ||
| 239 | ||
| 240 | ||
| 241 | ||
| 242 | ||
| 243 | ||
| 244 | Traceabili ty | |
| 245 | EPIC | |
| 246 | FEATURE | |
| 247 | USER STORY | |
| 248 | DESIGN COM PONENT | |
| 249 | ||
| 250 | ||
| 251 | ||
| 252 | ||
| 253 | ||
| 254 | ||
| 255 | ||
| 256 | ||
| 257 | ||
| 258 | ||
| 259 | ||
| 260 | ||
| 261 | ||
| 262 | Developer & PM Conta ct Informa tion | |
| 263 | Developer Name/Point of Contac t (POC) | |
| 264 | VA E-Mail Address | |
| 265 | Phone Numb er | |
| 266 | ||
| 267 | ||
| 268 | ||
| 269 | Developer Organizati on/Company | |
| 270 | Contract S tart Date | |
| 271 | Contract E nd Date | |
| 272 | ||
| 273 | ||
| 274 | ||
| 275 | Web and Mo bile Solut ions PM or POC | |
| 276 | VA E-Mail Address | |
| 277 | Phone Numb er | |
| 278 | ||
| 279 | ||
| 280 | ||
| 281 | VA Product Developme nt PM or P OC | |
| 282 | VA E-Mail Address | |
| 283 | Phone Numb er | |
| 284 | ||
| 285 | ||
| 286 | ||
| 287 |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.