Produced by Araxis Merge on 3/20/2018 11:05:04 AM 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 | movecoachdroid_P3.zip\Docs | MAP_RSD.docx | Thu Mar 15 17:27:32 2018 UTC |
2 | movecoachdroid_P3.zip\Docs | MAP_RSD.docx | Thu Mar 15 20:27:13 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 10 | 2232 |
Changed | 9 | 26 |
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 | Department of Vetera ns Affairs | |
2 | ||
3 | ||
4 | Mobile App lications (MA) | |
5 | ||
6 | ||
7 | Requiremen ts Specifi cation Doc ument | |
8 | ||
9 | ||
10 | ||
11 | ||
12 | ||
13 | ||
14 | ||
15 | ||
16 | ||
17 | August 201 4 | |
18 | Increment 4 - Versio n 1.3 | |
19 | ||
20 | Revision H istory | |
21 | Note: The revision h istory cyc le begins once chang es or enha ncements a re request ed after t he Require ments Spec ification Document h as been ba selined. | |
22 | ||
23 | Date | |
24 | Version | |
25 | Descriptio n | |
26 | Author | |
27 | 08/04/2014 | |
28 | 1.3 | |
29 | Incorporat ed some fe edback fro m a review of versio n 1.2 | |
30 | MAP | |
31 | 07/10/2014 | |
32 | 1.2 | |
33 | The follow ing change s have bee n incorpor ated: | |
34 | Added the Enterprise Wide Non- Functiona l Requirem ents (EWNF R) to the document. | |
35 | Added the increment to the tit le page. | |
36 | Remove the addendum for each a pplication . | |
37 | MAP | |
38 | 03/12/2014 | |
39 | 1.1 | |
40 | Tech Write r Review | |
41 | MAP | |
42 | 03/11/2014 | |
43 | 1.0 | |
44 | Inititial Document | |
45 | MAP | |
46 | Artifact R ationale | |
47 | The Requir ements Spe cification Document (RSD) reco rds the re sults of t he specifi cation gat hering pro cesses car ried out d uring the Requiremen ts phase. The RSD i s generall y written by the fun ctional an alyst(s) a nd should, in additi on to User Stories, provide in formation used to cr eate the t est plan a nd test sc ripts. It should be updated fo r each inc rement. | |
48 | The level of detail contained in this RS D should b e consiste nt with th e size and scope of the projec t. It is n ot necessa ry to fill out any s ections of this docu ment that do not app ly to the project. T he resourc es necessa ry to crea te and mai ntain this document during the life cycl e of a lar ge project should be acknowled ged and cl early refl ected in p roject sch edules. Do not dupli cate data that is al ready defi ned in ano ther docum ent or a s ection in this docum ent; note in the sec tion where the infor mation can be found. | |
49 | ||
50 | Table of C ontents | |
51 | ||
52 | Introducti on4 | |
53 | Purpose4 | |
54 | Scope4 | |
55 | References 4 | |
56 | Overall De scription4 | |
57 | Accessibil ity Specif ications4 | |
58 | Business N eeds4 | |
59 | Design Con straints S pecificati on4 | |
60 | Disaster R ecovery Sp ecificatio n4 | |
61 | Non-Functi onal Speci fications4 | |
62 | Functional Specifica tions5 | |
63 | Graphical User Inter face (GUI) Specifica tions5 | |
64 | Multi-divi sional Spe cification s5 | |
65 | Performanc e Specific ations5 | |
66 | Quality At tributes S pecificati on5 | |
67 | Code Revie w5 | |
68 | Verificati on and Val idation (V &V)5 | |
69 | Reliabilit y Specific ations5 | |
70 | Scope of I ntegration 5 | |
71 | Security a nd Privacy Specifica tions5 | |
72 | System Fea tures6 | |
73 | Usability Specificat ions6 | |
74 | User Inter face Speci fications6 | |
75 | VA Brandin g Specific ations6 | |
76 | Patient Sa fety Speci fications6 | |
77 | General Sp ecificatio ns7 | |
78 | Applicable Standards 7 | |
79 | 3.1.1.Data and Termi nology Sta ndards Com pliance7 | |
80 | Interfaces 7 | |
81 | Legal, Cop yright, an d Other No tices7 | |
82 | Purchased Components 7 | |
83 | Defect Sou rce (TOP 5 )7 | |
84 | User Class character istics7 | |
85 | Appendicie s8 | |
86 | Appendix A – 508 Acc essibility (OIT) Spe cification s8 | |
87 | Non-Functi onal Requi rements8 | |
88 | Appendix B – Code Re view Speci fications1 6 | |
89 | Guidance16 | |
90 | Appendix C – V&V Spe cification s16 | |
91 | Guidance16 | |
92 | Appendix D – Privacy and Appli cation Dat a Security (OIA) Spe cification s 16 | |
93 | Guidance16 | |
94 | Non-Functi onal Requi rements16 | |
95 | Appendix E – Enterpr ise Securi ty Specifi cations17 | |
96 | Guidance17 | |
97 | Non-Functi onal Requi rements17 | |
98 | Appendix F – Usabili ty Specifi cations18 | |
99 | Guidance18 | |
100 | Non-Functi onal Requi rements18 | |
101 | Appendix G – User In terface Sp ecificatio ns23 | |
102 | Non-Functi onal Requi rements23 | |
103 | Appendix H – VA Bran ding (OPIA ) Specific ations26 | |
104 | Non-Functi onal Requi rements26 | |
105 | Appendix I – Patient Safety (O IT) Specif ications28 | |
106 | Guidance28 | |
107 | Non-Functi onal Requi rements29 | |
108 | Appendix J – General Specifica tions30 | |
109 | Non-Functi onal Requi rements30 | |
110 | Appendix K – Data an d Terminol ogy Standa rds Compli ance (OIA) Specifica tions31 | |
111 | Guidance31 | |
112 | Non-Functi onal Requi rements32 | |
113 | Approval S ignatures3 3 | |
114 | ||
115 | ||
116 | INTRODUCTI ON | |
117 | Purpose | |
118 | The Mobile Applicati ons (MA) P rogram-Lev el Require ments Spec ification Document ( RSD) speci fies the e nterprise- wide non-f unctional requiremen ts (NFRs) and techno logies to be impleme nted by th e various mobile app lication p rojects wi thin the p rogram. Th e intended audience is both th e business community , , and th e develope r who will provide t he softwar e and hard ware that will make up the MA solutions. | |
119 | 1.2. Scope | |
120 | The scope of this do cument cov ers the st andard non -functiona l requirem ents that may apply to the var ious proje cts within the MA pr ogram. The functiona l requirem ents and p roject-spe cific NFRs for each applicatio n are loca ted in the project-s pecific RS D - Addend um. The no n- functio nal requir ements and guidance captured i n the appe ndices of this docum ent were c reated wit h the coop eration, i nput and f eedback of the vario us complia nce bodies . The ente rprise-wid e non-func tional req uirements are captur ed and mai ntained in the Enter prise-Wide Non-Funct ional Requ irements ( EWNFR) JIR A project. | |
121 | 1.3. Refer ences | |
122 | Enterprise -Wide Non- Functional Requireme nts Projec t: https:/ DNS . URL /browse/EW NFR | |
123 | OVERALL DE SCRIPTION | |
124 | Accessibil ity Specif ications | |
125 | This secti on contain s all of t he enterpr ise-level 508 non-fu nctional r equirement s and guid ance that may be app licable to the vario us applica tions with in the MA program. A pplication -specific 508 non-fu nctional r equirement s are loca ted in the Applicati on-Specifi c Non-Func tional Req uirements (NFRs) sec tion of th e applicat ion’s RSD – Addendum . Enterpri se NFRs th at have be en incorpo rated into the desig n of the a pplication are locat ed in the Enterprise -Wide Non- Functiona l Requirem ents (NFRs ) section of the app lication’s RSD – Add endum. | |
126 | The listin g of enter prise 508 NFRs is lo cated in A ppendix A – 508 Acce ssibility (OIT) Spec ifications of this do cument. | |
127 | Business N eeds | |
128 | The busine ss needs f or each ap plication are locate d in the B usiness Ne eds sectio n of the a pplication -specific RSD Addend um. | |
129 | Design Con straints S pecificati on | |
130 | The design constrain t specific ations for each appl ication ar e located in the App lication S pecific No n-Function al Require ments (NFR s) section of the ap plication specific R SD – Adden dum. | |
131 | Disaster R ecovery Sp ecificatio n | |
132 | This secti on is not applicable to the MA program. | |
133 | Non-Functi onal Speci fications | |
134 | ||
135 | The docume nt specifi cations fo r each app lication a re located in the Ap plication- Specific N on- Functi onal Requi rements (N FRs) secti on of the applicatio n specific RSD – Add endum. | |
136 | Functional Specifica tions | |
137 | The functi onal speci fications for each a pplication are locat ed in the Functional Requireme nts sectio n of the a pplication specific RSD. | |
138 | Graphical User Inter face (GUI) Specifica tions | |
139 | The GUI sp ecificatio ns for eac h project are locate d in the A pplication -Specific Non-Functi onal Requi rements (N FRs) secti on of the applicatio n specific RSD. | |
140 | Multi-divi sional Spe cification s | |
141 | This secti on is not applicable to mobile applicati ons. | |
142 | Performanc e Specific ations | |
143 | The perfor mance spec ifications for each applicatio n are loca ted in the Applicati on-Specifi c Non- Fun ctional Re quirements (NFRs) se ction of t he applica tion speci fic RSD – Addendum. | |
144 | Quality At tributes S pecificati on | |
145 | The qualit y attribut e specific ations for each appl ication ar e located in the App lication-S pecific No n-Function al Require ments (NFR s) section of the ap plication specific R SD – Adden dum. | |
146 | Code Revie w | |
147 | This secti on contain s all of t he enterpr ise level code revie w guidance that is a pplicable to all of the applic ations wit hin the MA program. | |
148 | The listin g of enter prise code review gu idance is located in Appendix B – Code R eview Spec ifications of this d ocument. | |
149 | Verificati on and Val idation (V &V) | |
150 | This secti on contain s all of t he enterpr ise level V&V non-fu nctional r equirement s and guid ance that may be app licable to the vario us applica tions with in the MA program. A pplication -specific V&V non-fu nctional r equirement s are loca ted in the Applicati on Specifi c Non-Func tional Req uirements (NFRs) sec tion of th e applicat ion’s RSD – Addendum . Enterpri se NFRs th at have be en incorpo rated into the desig n of the a pplication are locat ed in the Enterprise -Wide Non- Functiona l Requirem ents (NFRs ) section of the app lication’s RSD – Add endum. | |
151 | The listin g of enter prise V&V NFRs is lo cated in A ppendix C – V&V Spec ifications of this d ocument. | |
152 | Reliabilit y Specific ations | |
153 | The reliab ility spec ifications for each applicatio n are loca ted in the Applicati on-Specifi c Non- Fun ctional Re quirements (NFRs) se ction of t he applica tion’s RS D – Addend um. | |
154 | Scope of I ntegration | |
155 | The scope of integra tion for e ach applic ation is l ocated in the Mobile Applicati on Informa tion secti on of the applicatio n’s RSD. | |
156 | Security a nd Privacy Specifica tions | |
157 | ||
158 | This secti on contain s all of t he enterpr ise-level security a nd privacy non-funct ional requ irements a nd guidanc e that may be applica ble to the various a pplication s within t he MA prog ram. | |
159 | Applicatio n-specific security and privac y non-func tional req uirements are locate d in the A pplication -Specific Non-Functi onal Requi rements (N FRs) secti on of the applicatio n’s RSD. E nterprise NFRs that have been incorporat ed into th e design o f the appl ication ar e located in the Ent erprise-Wi de Non-Fun ctional Re quirements (NFRs) se ction of t he applica tion’s RSD – Addendu m. | |
160 | The listin g of enter prise secu rity and p rivacy NFR s is locat ed in Appe ndix E – E nterprise Security S pecificati ons and Ap pendix D – Privacy a nd Applica tion Data Security ( OIA) Speci ficationso f this doc ument. | |
161 | System Fea tures | |
162 | The system s features for each applicatio n are loca ted in the System Fe atures sec tion of th e applicat ion-specif ic RSD. | |
163 | Usability Specificat ions | |
164 | This secti on contain s all of t he enterpr ise-level usability non-functi onal requi rements an d guidance that mayb e applicab le to the various ap plications within th e MA progr am. Applic ation- spe cific usab ility non- functional requireme nts are lo cated in t he Applica tion-Speci fic Non- F unctional Requiremen ts (NFRs) section of the appli cation’s R SD – Adden dum. Enter prise NFRs that have been inco rporated i nto the de sign of th e applicat ion are lo cated in t he Enterpr ise- Wide Non-Functi onal Requi rements (N FRs) secti on of the applicatio n’s RSD – Addendum. | |
165 | The listin g of enter prise Usab ility NFRs is locate d in Appen dix F – Us ability Sp ecificatio nsof this document. | |
166 | User Inter face Speci fications | |
167 | This secti on contain s all of t he enterpr ise level user inter face non-f unctional requiremen ts and gui dance that maybe app licable to the vario us applica tions with in the MA program. A pplication specific user inter face non-f unctional requiremen ts are loc ated in th e Applicat ion Specif ic Non- Fu nctional R equirement s (NFRs) s ection of the applic ation’s RS D – Addend um. Enterp rise NFRs that have been incor porated in to the des ign of the applicati on are loc ated in th e Enterpri se- Wide N on-Functio nal Requir ements (NF Rs) sectio n of the a pplication ’s RSD – A ddendum. | |
168 | The listin g of enter prise User Interface NFRs is l ocated in Appendix G – User In terface Sp ecificatio ns of this document. | |
169 | VA Brandin g Specific ations | |
170 | This secti on contain s all of t he enterpr ise-level VA brandin g non-func tional req uirements and guidan ce that ma ybe applic able to th e applicat ion within the MA pr ogram. App lication-s pecific VA branding non-functi onal requi rements ar e located in the App lication-S pecific No n- Functio nal Requir ements (NF Rs) sectio n of the a pplication ’s RSD – A ddendum. E nterprise NFRs that have been incorporat ed into th e design o f the appl ication ar e located in the Ent erprise- W ide Non-Fu nctional R equirement s (NFRs) s ection of the applic ation’s RS D – Addend um. | |
171 | The listin g of enter prise VA B randing NF Rs is loca ted in App endix H – VA Brandin g (OPIA) S pecificati ons of thi s document . | |
172 | Patient Sa fety Speci fications | |
173 | ||
174 | This secti on contain s all of t he enterpr ise-level patient sa fety non-f unctional requiremen ts and gui dance that may be ap plicable t o the appl ication wi thin the M A program. Applicati on-specifi c patient safety non -functiona l requirem ents are l ocated in the Applic ation-Spec ific Non- Functional Requireme nts (NFRs) section o f the appl ication’s RSD – Adde ndum. Ente rprise NFR s that hav e been inc orporated into the d esign of t he applica tion are l ocated in the Enterp rise- Wide Non-Funct ional Requ irements ( NFRs) sect ion of the applicati on’s RSD – Addendum. | |
175 | The listin g of enter prise pati ent safety NFRs is l ocated in Appendix I – Patient Safety (O IT) Specif ications o f this doc ument. | |
176 | General Sp ecificatio ns | |
177 | This secti on contain s all of t he enterpr ise-level general no n-function al require ments that may be ap plicable t o the vari ous applic ations wit hin the MA program. Enterprise NFRs that have been incorpora ted into t he design of the app lication a re located in the En terprise-W ide Non-Fu nctional R equirement s (NFRs) s ection of the applic ation’s RS D – Addend um. | |
178 | The listin g of enter prise gene ral NFRs a re located in Append ix J – Gen eral Spec ifications of this d ocument. | |
179 | APPLICABLE STANDARDS | |
180 | 3.1.1. Dat a and Term inology St andards Co mpliance | |
181 | The table below cont ains all t he enterpr ise-level data and t erminology non-funct ional requ irements t hat may be applicabl e to the a pplication within th e MA progr am. Applic ation- spe cific data and termi nology non -functiona l requirem ents are l ocated in the Applic ation- Spe cific Non- Functional Requireme nts (NFRs) section o f the appl ication’s RSD – Adde ndum. Ente rprise NFR s that hav e been inc orporated into the d esign of t he applica tion are l ocated in the Enterp rise-Wide Non-Functi onal Requi rements (N FRs) secti on of the applicatio n’s RSD – Addendum. | |
182 | The listin g of enter prise Data and Termi nology Sta ndards NFR s is locat ed in Appe ndix K – D ata and Te rminology Standards Compliance (OIA) Spe cification s of this document. | |
183 | INTERFACES | |
184 | The interf aces for e ach applic ation are located in the the a pplication -specific SDD – Adde ndum. | |
185 | LEGAL, COP YRIGHT, AN D OTHER NO TICES | |
186 | The legal, copyright and other notices f or each ap plication are locate d in the M obile Appl ication In formation section of the appli cation-spe cific RSD – Addendum . | |
187 | PURCHASED COMPONENTS | |
188 | This secti on is not applicable to mobile applicati ons. | |
189 | Defect Sou rce (TOP 5 ) | |
190 | Defect sou rce inform ation is l ocated in the defect log docum ent for ea ch applica tion. | |
191 | USER CLASS CHARACTER ISTICS | |
192 | The genera l characte ristics of the inten ded users for each a pplication are locat ed in the Mobile App lication I nformation section o f the appl ication-sp ecific RSD . | |
193 | ||
194 | APPENDICIE S | |
195 | Appendix A – 508 Acc essibility (OIT) Spe cification s | |
196 | Non-Functi onal Requi rements | |
197 | ||
198 | Key | |
199 | Summary | |
200 | Acceptance Criteria ID | |
201 | EWNFR-521 | |
202 | As a proje ct team, w e must be sure that where a sc reen title is provid ed, a clea r title is presented on all sc reens, oth erwise we will not b e Section 508 compli ant. | |
203 | EWNFR-634 | |
204 | EWNFR-520 | |
205 | As a proje ct team, w e must be sure that the readin g order of the appli cation con tent is lo gical, oth erwise we will not b e Section 508 compli ant. | |
206 | EWNFR-633 | |
207 | EWNFR-519 | |
208 | As a proje ct team, w e must pro vide the e quivalent text for a ll non-tex t elements including sound and images, o therwise w e will not be Sectio n 508 comp liant. | |
209 | EWNFR-632 | |
210 | EWNFR-518 | |
211 | As a proje ct team, w e must use actual te xt when te chnology a llows inst ead of ima ges of the text, oth erwise we will not b e Section 508 compli ant. | |
212 | EWNFR-631 | |
213 | EWNFR-517 | |
214 | As a proje ct team, w e must ens ure that w hen using non-decora tive image s, informa tive alter native tex t is provi ded to the user, oth erwise we will not b e 508 comp liant. | |
215 | EWNFR-630 | |
216 | EWNFR-516 | |
217 | As a proje ct team, w e must avo id duplica ting infor mation in alternativ es, otherw ise we wil l not be S ection 508 compliant . | |
218 | EWNFR-629 | |
219 | EWNFR-515 | |
220 | As a proje ct team, w e must ens ure that a ll interac tions with a control is what t he user ex pects it t o be, othe rwise we w ill not be Section 5 08 complia nt. | |
221 | EWNFR-628 | |
222 | EWNFR-514 | |
223 | As a proje ct team, w e must mak e sure tha t all of t he control s that hav e accessib le input m ethods for the contr ols, have a specific set of be haviors an d are adeq uately sup ported, ot herwise we will not be Section 508 compl iant. | |
224 | EWNFR-627 | |
225 | EWNFR-513 | |
226 | As a proje ct team, w e must mak e sure tha t while us ing logica l navigati on scrolli ng occurs as needed, otherwise we will n ot be Sect ion 508 co mpliant. | |
227 | EWNFR-626 | |
228 | EWNFR-512 | |
229 | As a proje ct team, w e must be sure to pr ovide suff icient siz e for the element on the touch screen, o therwise w e will not be Sectio n 508 comp liant. | |
230 | EWNFR-625 | |
231 | ||
232 | ||
233 | Key | |
234 | Summary | |
235 | Acceptance Criteria ID | |
236 | EWNFR-511 | |
237 | As a proje ct team, w e must pro vide inact ive space around ele ments on t he touch s creen, oth erwise we will not b e Section 508 compli ant. | |
238 | EWNFR-624 | |
239 | EWNFR-510 | |
240 | As a proje ct team, w e must ens ure that a ll actions on a touc h screen a re trigger ed on remo val and no t with the initial t ouch, othe rwise we w ill not be Section 5 08 complia nt. | |
241 | EWNFR-622, EWNFR-623 | |
242 | EWNFR-509 | |
243 | As a proje ct team, w e must be sure that we do not overlap ac tive eleme nts in tou ch focus a reas, othe rwise we w ill not be Section 5 08 complia nt. | |
244 | EWNFR-621 | |
245 | EWNFR-508 | |
246 | As a proje ct team, w e must be sure that we are abl e to move focus away from focu sable comp onents, ot herwise we will not be Section 508 compl iant. | |
247 | EWNFR-620 | |
248 | EWNFR-507 | |
249 | As a proje ct team, w e must be sure that element te xt has the same mean ing within context, otherwise we will no t be Secti on 508 com pliant. | |
250 | EWNFR-619 | |
251 | EWNFR-506 | |
252 | As a proje ct team, w e must be sure that element te xt has the same mean ing when o ut of cont ext, other wise we wi ll not be Section 50 8 complian t. | |
253 | EWNFR-618 | |
254 | EWNFR-505 | |
255 | As a proje ct team, w e must ens ure access to altern ative inpu t methods, otherwise we will n ot be Sect ion 508 co mpliant. | |
256 | EWNFR-617 | |
257 | EWNFR-504 | |
258 | As a proje ct team, w e must be sure that content th at gives t he user an alternati ve to non- accessibl e content, also prov ide an equ ivalent fu nctionalit y, otherwi se we will not be Se ction 508 compliant. | |
259 | EWNFR-616 | |
260 | EWNFR-503 | |
261 | As a proje ct team, w e must be sure to pr ovide the ability fo r the user to contro l the font size, oth erwise we will not b e Section 508 compli ant. | |
262 | EWNFR-615 | |
263 | EWNFR-502 | |
264 | As a proje ct team, w e must use consisten t labels f or common elements, otherwise we will no t be Secti on 508 com pliant. | |
265 | EWNFR-614 | |
266 | EWNFR-501 | |
267 | As a proje ct team, w e must use consisten t labels f or images, otherwise we will n ot be Sect ion 508 co mpliant. | |
268 | EWNFR-613 | |
269 | EWNFR-500 | |
270 | As a proje ct team, w e must use consisten t labels f or control s, otherwi se we will not be Se ction 508 compliant. | |
271 | EWNFR-612 | |
272 | ||
273 | ||
274 | Key | |
275 | Summary | |
276 | Acceptance Criteria ID | |
277 | EWNFR-499 | |
278 | As a proje ct team, w e must ens ure that s hape and l ocation ar e not the only ways hierarchy is communi cated, oth erwise we will not b e Section 508 compli ant. | |
279 | EWNFR-611 | |
280 | EWNFR-498 | |
281 | As a proje ct team, w e must ens ure that s hape and l ocation ar e not the only ways informatio n is commu nicated, o therwise w e will not be Sectio n 508 comp liant. | |
282 | EWNFR-610 | |
283 | EWNFR-497 | |
284 | As a proje ct team, w e cannot o nly rely o n sensory characteri stics when providing instructi ons, other wise we wi ll not be Section 50 8 complian t. | |
285 | EWNFR-609 | |
286 | EWNFR-496 | |
287 | As a proje ct team, w e must mak e sure tha t artifact elements are not ex posed to a ssistive t echnologie s, otherwi se we will not be Se ction 508 compliant. | |
288 | EWNFR-608 | |
289 | EWNFR-495 | |
290 | As a proje ct team, w e must mak e sure tha t duplicat e content is not exp osed to as sistive te chnologies , otherwis e we will not be Sec tion 508 c ompliant. | |
291 | EWNFR-607 | |
292 | EWNFR-494 | |
293 | As a proje ct team, w e must mak e sure tha t decorati ve content is not ex posed to a ssistive t echnologie s, otherwi se we will not be Se ction 508 compliant. | |
294 | EWNFR-606 | |
295 | EWNFR-493 | |
296 | As a proje ct team, w e must mak e sure tha t hidden c ontent is not expose d to assis tive techn ologies, o therwise w e will not be Sectio n 508 comp liant. | |
297 | EWNFR-605 | |
298 | EWNFR-492 | |
299 | As a proje ct team, w e must be sure that all applic ations do not interf ere with A ssistive T echnology, otherwise we will n ot be Sect ion 508 co mpliant. | |
300 | EWNFR-604 | |
301 | EWNFR-491 | |
302 | As a proje ct team we must ensu re that co ntrols are correctly identifie d as they are intend ed to be, and the “s tate” is c orrectly i dentified, otherwise we will n ot be Sect ion 508 co mpliant. | |
303 | EWNFR-603 | |
304 | EWNFR-490 | |
305 | As a proje ct team, w e must mak e sure tha t non- dec orative co ntent supp orts acces sibility, otherwise we will no t be Secti on 508 com pliant. | |
306 | EWNFR-602 | |
307 | EWNFR-489 | |
308 | As a proje ct team, w e must mak e sure tha t all cont rols suppo rt Accessi bility, ot herwise we will not be Section 508 compl iant. | |
309 | EWNFR-601 | |
310 | ||
311 | ||
312 | Key | |
313 | Summary | |
314 | Acceptance Criteria ID | |
315 | EWNFR-488 | |
316 | As a proje ct team, w e must ens ure that t ime based sessions a re accessi ble, other wise we wi ll not be Section 50 8 complian t. | |
317 | EWNFR-600 | |
318 | EWNFR-487 | |
319 | As a proje ct team, w e must ens ure that i t is possi ble for al l enhancem ents to op erate simu ltaneously , even if they are n ot all bei ng used, o therwise w e will not be Sectio n 508 comp liant. | |
320 | EWNFR-599 | |
321 | EWNFR-486 | |
322 | As a proje ct team, w e must pla ce any tex t that giv es instruc tions at t he beginni ng of a fo rm, otherw ise we wil l not be S ection 508 compliant . | |
323 | EWNFR-598 | |
324 | EWNFR-485 | |
325 | As a proje ct team, w e must be sure to pr ovide expl icit label s for all form eleme nts, other wise we wi ll not be Section 50 8 complian t. | |
326 | EWNFR-597 | |
327 | EWNFR-484 | |
328 | As a proje ct team, w e must ens ure that m ulti-part controls a re accessi ble, other wise, we w ill not be Section 5 08 complia nt. | |
329 | EWNFR-596 | |
330 | EWNFR-483 | |
331 | As a proje ct team, w e must pro vide conte xt for mul ti-part co ntrols, ot herwise we will not be section 508 compl iant. | |
332 | EWNFR-595 | |
333 | EWNFR-482 | |
334 | As a proje ct team, w e must ens ure that w e clearly indicate a ll form fi eld constr aints, oth erwise we will not b e Section 508 compli ant. | |
335 | EWNFR-594 | |
336 | EWNFR-481 | |
337 | As a proje ct team, w e must ens ure that w e are suff iciently d escribing all elemen ts, otherw ise we wil l not be S ection 508 compliant . | |
338 | EWNFR-593 | |
339 | EWNFR-480 | |
340 | As a proje ct team, w e must ens ure that a ll control s can be f ocused, ot herwise we will not be Section 508 compl iant. | |
341 | EWNFR-592 | |
342 | EWNFR-479 | |
343 | As a proje ct team, w e must ens ure that a ll element s can rece ive focus, otherwise we will n ot be Sect ion 508 co mpliant. | |
344 | EWNFR-591 | |
345 | EWNFR-478 | |
346 | As a proje ct team we must ensu re that we use inter active ele ments on a page in a logical f ocus order , otherwis e, we will not be Se ction 508 compliant. | |
347 | EWNFR-590 | |
348 | EWNFR-477 | |
349 | As a proje ct team, w e must mak e sure tha t when usi ng keyboar d focus, w e clearly indicate i nteraction , otherwis e we will not be Sec tion 508 c ompliant. | |
350 | EWNFR-589 | |
351 | EWNFR-476 | |
352 | As a proje ct team, w e must ens ure that n avigation is visuall y indicate d, otherwi se we will not be | |
353 | EWNFR-588 | |
354 | ||
355 | ||
356 | Key | |
357 | Summary | |
358 | Acceptance Criteria ID | |
359 | ||
360 | Section 50 8 complian t. | |
361 | ||
362 | EWNFR-475 | |
363 | As a proje ct team, w e must ens ure that t he focus i s not forc ibly shift ed when in putting in formation, otherwise we will n ot be Sect ion 508 co mpliant. | |
364 | EWNFR-587 | |
365 | EWNFR-474 | |
366 | As a proje ct team, w e must ens ure that t he focus i s set logi cally when pop alert s close, o therwise w e will not be Sectio n 508 comp liant. | |
367 | EWNFR-586, EWNFR-718 | |
368 | EWNFR-473 | |
369 | As a proje ct team, w e must ens ure that t he focus i s set logi cally when a module opens, oth erwise we will not b e Section 508 compli ant. | |
370 | EWNFR-585, EWNFR-719 | |
371 | EWNFR-472 | |
372 | As a proje ct team, w e must ens ure that w hen focus changes oc cur that t he context has not c hanged, ot herwise we will not be Section 508 compl iant. | |
373 | EWNFR-584 | |
374 | EWNFR-471 | |
375 | As a proje ct team, w e must pro vide sugge stions to the user w hen they r eceive err or message s whenever they are known when using the Android/i OS platfor ms, otherw ise we wil l not be S ection 508 compliant . | |
376 | EWNFR-583 | |
377 | EWNFR-470 | |
378 | As a proje ct team, w e must ens ure that w e provide a way to p revent err ors in fin ancial dat a on the A ndroid/iOS platforms , otherwis e we will be Section 508 compl iant. | |
379 | EWNFR-582 | |
380 | EWNFR-469 | |
381 | As a proje ct team, w e must ens ure that w e provide error prev ention for legal com mitments o n the Andr oid/iOS pl atforms, o therwise w e will not be Sectio n 508 comp liant. | |
382 | EWNFR-581 | |
383 | EWNFR-468 | |
384 | As a proje ct team, w e must ens ure that w e provide a way to p revent err ors on inf ormation t hat is sub mitted on the Androi d/iOS plat forms, oth erwise we will not b e Section 508 compli ant | |
385 | EWNFR-580 | |
386 | EWNFR-467 | |
387 | As a proje ct team, w e must ens ure that w e provide a consiste nt way to implement and alert mechanism on the And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant. | |
388 | EWNFR-579 | |
389 | EWNFR-466 | |
390 | As a proje ct team, w e must ens ure that w e provide a consiste nt strateg y to imple ment an er ror mechan ism on the Android/i OS platfor ms, otherw ise we wil l not be S ection 508 compliant . | |
391 | EWNFR-578 | |
392 | EWNFR-465 | |
393 | As a proje ct team, w e must ens ure that w e provide a clear in dication o f errors o n the Andr oid/iOS ap plication platforms, otherwise we | |
394 | EWNFR-577 | |
395 | ||
396 | ||
397 | Key | |
398 | Summary | |
399 | Acceptance Criteria ID | |
400 | ||
401 | will not b e Section 508 compli ant. | |
402 | ||
403 | EWNFR-464 | |
404 | As a proje ct team, w e must ens ure that e rror messa ge have a platform s pecific al ert or the focus is moved to t he error m essage aft er submitt ing of an action, ot herwise we will not be Section 508 compl iant. | |
405 | EWNFR-575, EWNFR-576 | |
406 | EWNFR-463 | |
407 | As a proje ct team, w e must ens ure that w e provide a non-anim ated way t o step thr ough or co ntrol anim ation on A ndroid/iOS platform applicatio ns, otherw ise we wil l not be S ection 508 compliant . | |
408 | EWNFR-574 | |
409 | EWNFR-462 | |
410 | As a proje ct team, w e must ens ure that d ecorative animations settle wi thin 5 sec onds on th e Android/ iOS platfo rm applica tions, oth erwise we will not b e Section 508 compli ant. | |
411 | EWNFR-573 | |
412 | EWNFR-461 | |
413 | As a proje ct team, w e must ens ure that s creen tran sitions se ttle withi n 5 second s on the A ndroid/iOS platform applicatio ns, otherw ise we wil l not be S ection 508 compliant . | |
414 | EWNFR-572 | |
415 | EWNFR-460 | |
416 | As a proje ct team, w e must ens ure that e lements fl ash in a s afe thresh old on And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant. | |
417 | EWNFR-571 | |
418 | EWNFR-459 | |
419 | As a proje ct team, w e must ens ure that e lements bl ink in a s afe thresh old on And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant. | |
420 | EWNFR-570 | |
421 | EWNFR-458 | |
422 | As a proje ct team, w e must ens ure that a uto updati ng dynamic content c an be hidd en on Andr oid/iOS pl atform app lications, otherwise we will n ot be Sect ion 508 co mpliant. | |
423 | EWNFR-569 | |
424 | EWNFR-457 | |
425 | As a proje ct team, w e must ens ure that a uto- updat ing dynami c content can be sto pped on An droid/iOS platform a pplication s, otherwi se we will not be Se ction 508 compliant. | |
426 | EWNFR-568 | |
427 | EWNFR-456 | |
428 | As a proje ct team, w e must ens ure that a uto- updat ing dynami c content can be pau sed on And roid/iOS p latform ap plications , otherwis e we will not be 508 compliant . | |
429 | EWNFR-567 | |
430 | EWNFR-455 | |
431 | As a proje ct team, w e must ens ure that w e make ass istive tec hnologies aware of a ny content changes t o the Andr oid/iOS ap plications in real | |
432 | EWNFR-566 | |
433 | ||
434 | ||
435 | Key | |
436 | Summary | |
437 | Acceptance Criteria ID | |
438 | ||
439 | time, othe rwise we w ill not be Section 5 08 complia nt. | |
440 | ||
441 | EWNFR-454 | |
442 | As a proje ct team, w e must ens ure conten t that is animated i s describe d in audio or text o n the Andr oid/iOS pl atforms, o therwise w e will not be Sectio n 508 comp liant. | |
443 | EWNFR-565 | |
444 | EWNFR-453 | |
445 | As a proje ct team, w e must ens ure that t he removal of on-scr een compon ents are p roperly ex posed to a ssistive t echnology on the And roid/iOS M edia Platf orms. | |
446 | EWNFR-564 | |
447 | EWNFR-452 | |
448 | As a proje ct team, w e must ens ure that t he additio n of on-sc reen compo nents are properly e xposed to assistive technology on the An droid/iOS platforms, otherwise , we will not be 508 compliant . | |
449 | EWNFR-563 | |
450 | EWNFR-451 | |
451 | As a proje ct team, w e must ens ure that w hen White on Black i s enabled on the iOS platform, that an a cceptable contrast i s provided within th e applicat ion color settings, otherwise we will no t be Secti on 508 Com pliant. | |
452 | EWNFR-562 | |
453 | EWNFR-450 | |
454 | As a proje ct team, w e must ens ure that w hen colors from the OS are not used, tha t we provi de a varie ty of colo r contrast selection , otherwis e we will not be Sec tion 508 c ompliant. | |
455 | EWNFR-561 | |
456 | EWNFR-449 | |
457 | As a proje ct team, w e must ens ure that w e provide a sufficie nt color c ontrast wh en using t ext and te xt images on the And roid/iOS P latform, o therwise w e will not be Sectio n 508 comp liant. | |
458 | EWNFR-560 | |
459 | EWNFR-448 | |
460 | As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing withou t needing additional interacti on from th e user on the Androi d/iOS plat forms, oth erwise we will not b e Section 508 compli ant. | |
461 | EWNFR-559 | |
462 | EWNFR-447 | |
463 | As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing, can a lso do so without us ing color on-screen on the And roid/iOS p latforms, otherwise we will no t be Secti on 508 com pliant. | |
464 | EWNFR-558 | |
465 | EWNFR-446 | |
466 | As a proje ct team, w e must ens ure that a nything th at uses co lor to con vey a mean ing, can a lso do so without us ing color in the con tent, on t he Android /iOS platf orms, othe rwise we w ill not be | |
467 | EWNFR-557 | |
468 | ||
469 | ||
470 | Key | |
471 | Summary | |
472 | Acceptance Criteria ID | |
473 | ||
474 | Section 50 8 complian t | |
475 | ||
476 | EWNFR-445 | |
477 | As a proje ct team, w e must ens ure that w e are not using colo r and text formattin g as the o nly way to commun icate sele ction on t he Android /iOS platf orms, othe rwise we w ill not be 508 compl iant. | |
478 | EWNFR-556 | |
479 | EWNFR-444 | |
480 | As a proje ct team, w e must ens ure that w e are not using colo r and text formattin g as the o nly means of communi cating inf ormation o n the Andr oid/iOS pl atforms ot herwise we will not be Section 508 compl iant. | |
481 | EWNFR-555 | |
482 | EWNFR-443 | |
483 | As a proje ct team, w e must pro vide trans cripts or audio trac ks of vide o-only pre sentations being use d on the A ndroid/iOS platforms , otherwis e we will not be Sec tion 508 c ompliant. | |
484 | EWNFR-528 | |
485 | EWNFR-442 | |
486 | As a proje ct team, w e much pro vide synch ronized ca ptions for all multi media cont ent on the Android/i OS platfor ms, otherw ise we wil l not be 5 08 complia nt. | |
487 | EWNFR-527 | |
488 | EWNFR-441 | |
489 | As a proje ct team, w e must pro vide a tex t transcri pt for pre sentations that use audio-only on Androi d/iOS plat forms, oth erwise we will not b e 508 comp liant. | |
490 | EWNFR-526 | |
491 | EWNFR-440 | |
492 | As a proje ct team, w e must be sure that visual mul timedia co ntent is a dequately described in the aud io portion when usin g the Andr oid/iOS pl atforms, o therwise t he softwar e will not be Sectio n 508 comp liant. | |
493 | EWNFR-525 | |
494 | EWNFR-439 | |
495 | As a proje ct team, w e must ens ure that i nformation provided with audio is not th e only way to indica te an erro r on the A ndroid/iOS platforms , otherwis e we will not be Sec tion 508 c ompliant. | |
496 | EWNFR-524 | |
497 | EWNFR-438 | |
498 | As a proje ct team, w e must ens ure that i nformation provided with audio is not th e only way to indica te complet ion of a t ask when u sing an An droid /iOS platforms , otherwis e we will not be Sec tion 508 c ompliant. | |
499 | EWNFR-523 | |
500 | EWNFR-437 | |
501 | As a proje ct team, w e must ens ure audio functional ity does n ot disrupt the text to speech of assisti ve technol ogies for Android/iO S platform s otherwis e we will not be Sec tion 508 c ompliant. | |
502 | EWNFR-522 | |
503 | ||
504 | ||
505 | Appendix B – Code Re view Speci fications | |
506 | Guidance | |
507 | ||
508 | ID | |
509 | Guidance | |
510 | EWNFR-705 | |
511 | Guidance: Developmen t teams sh ould revie w the CWE/ SANS Top 2 5 Most Dan gerous Sof tware Erro rs. | |
512 | EWNFR-704 | |
513 | Guidance: Developmen t teams sh ould revie w the OWAS P Top Ten list. | |
514 | EWNFR-703 | |
515 | Guidance: (If applic able) Deve lopment te ams must p erform the IV&V High Risk and High Prior ity applic ation Revi ew process . | |
516 | EWNFR-702 | |
517 | Guidance: If Applica ble, devel opment tea m must per form the V &V Secure Code Revie w Process. | |
518 | EWNFR-701 | |
519 | Guidance: Developmen t teams mu st obtain automatic static ana lysis tool s from the VA SwA Pr ogram Offi ce. | |
520 | EWNFR-700 | |
521 | Guidance: Developmen t team mus t scan the ir applica tions duri ng both th e developm ent and th e A&A proc esses (for example: during com ponent tes ting). | |
522 | Appendix C – V&V Spe cification s | |
523 | Guidance | |
524 | ||
525 | ID | |
526 | Guidance | |
527 | EWNFR-669 | |
528 | Guidance: To meet th e requirem ents for V &V test in take, the functional requireme nts, busin ess rule l ogic and c ompliance requiremen ts have be en tested. | |
529 | EWNFR-665 | |
530 | Guidance: Test scrip ts and tes t results are docume nted accor ding to Pr oPath guid ance. | |
531 | EWNFR-663 | |
532 | As a proje ct team, w e must be sure to pr ovide a bu siness own er waiver if our Mob ile Applic ation is n ot free of all criti cal and hi gh defects , otherwis e we will not meet t he criteri a for entr ance into V&V. | |
533 | EWNFR-660 | |
534 | Guidance: The Mobile Applicati on is free of all Le vel-1 (Cri tical) and Level 2 ( High) defe cts prior to submitt ing to V&V . | |
535 | Appendix D – Privacy and Appli cation Dat a Security (OIA) Spe cification s | |
536 | Guidance | |
537 | ||
538 | Key | |
539 | Guidance | |
540 | EWNFR-315 | |
541 | Guidance: All data e ntered by the Vetera n into the applicati on (and tr ansmitted to the VA) is covere d by a Pri vacy Act o r records otherwise our applic ation risk s non-appr oval from the Privac y and Secu rity compl iance grou p. | |
542 | Non-Functi onal Requi rements | |
543 | ||
544 | ||
545 | ID | |
546 | Non-Functi onal Requi rement | |
547 | Acceptance Criteria ID | |
548 | EWNFR-312 | |
549 | See Descri ption for Full Req: As a Proje ct Team, w e must inc lude an En d User Lic ense Agree ment (EULA ) | |
550 | EWNFR-326, EWNFR-327 | |
551 | EWNFR-316 | |
552 | As a Proje ct Team, w e must inc lude an En d User Lic ense Agree ment (EULA ) that sta tes that t he VA will receive t he data en tered by t he Veteran on the de vice our a pplication risks non -approval from the P rivacy and Security compliance group. | |
553 | EWNFR-331 | |
554 | EWNFR-314 | |
555 | As a Proje ct Team, w e must ens ure that a ll data en tered by t he Veteran into our applicatio n (but not transmitt ed to the VA) is sec urely stor ed on the user’s dev ice | |
556 | EWNFR-329 | |
557 | EWNFR-313 | |
558 | See Descri ption for Full Req: As a Proje ct Team, w e must inc lude an En d User Lic ense Agree ment (EULA ) | |
559 | EWNFR-328 | |
560 | EWNFR-321 | |
561 | As a Proje ct Team, w e must ens ure that u ser accoun t informat ion is not transferr ed to our applicatio n otherwis e our appl ication ri sks non-ap proval fro m the Priv acy and Se curity com pliance gr oup. | |
562 | EWNFR-338 | |
563 | EWNFR-318 | |
564 | As a Proje ct Team, w e must ens ure that V A data pul led from a VA databa se and dis played to a VA Provi der is not stored on the devic e otherwis e our appl ication ri sks non-ap proval fro m the Priv acy and Se curity com pliance gr oup. | |
565 | EWNFR-333, EWNFR-715 | |
566 | Appendix E – Enterpr ise Securi ty Specifi cations | |
567 | Guidance | |
568 | ||
569 | ID | |
570 | Guidance | |
571 | EWNFR-698 | |
572 | Guidance: All applic ations and services should be written in complianc e with OWA SP guideli nes which VA Securit y referenc es for bes t practice s in web a pplication security. | |
573 | EWNFR-720 | |
574 | Guidance: All applic ations mus t obtain s ignoff of the SSP Ad dendum and load the signed SSP Addendum into the R isk Vision . | |
575 | Non-Functi onal Requi rements | |
576 | ||
577 | ID | |
578 | Non-Functi onal Requi rement | |
579 | Acceptance Criteria ID | |
580 | ||
581 | ||
582 | EWNFR-711 | |
583 | See Descri ption for Full Req.: As a Proj ect Team, we must en sure that all Modera te and Low issues re maining in our appli cation at initial re lease for both the F ortify and WASA/MASA scans mus t be captu red in a P lan of Act ion and Mi lestones ( POA&M) rep ort | |
584 | EWNFR-713 | |
585 | EWNFR-712 | |
586 | As a Proje ct Team, w e must ens ure that o ur applica tion passe s a WASA/M ASA scan w here there are no Cr itical or High issue s reported so that o ur applica tion succe ssfully co mpletes th e Enterpri se Securit y complian ce process . | |
587 | EWNFR-714 | |
588 | EWNFR-699 | |
589 | As a Proje ct Team, w e must ens ure that o ur applica tion passe s a Fortif y scan (Co de Review) where the re are no Critical o r High iss ues report ed so that our appli cation suc cessfully completes the Enterp rise Secur ity compli ance proce ss. | |
590 | EWNFR-716 | |
591 | Appendix F – Usabili ty Specifi cations | |
592 | Guidance | |
593 | ||
594 | ID | |
595 | Guidance | |
596 | EWNFR-48 | |
597 | Guidance: Enhance th e user’s e xperience with our a pplication by using consistent screen te rms within the appli cation. | |
598 | EWNFR-46 | |
599 | To enhance the user’ s experien ce with th e applicat ion, creat e and use a consiste nt screen flow model within ou r applicat ion so tha t our appl ication wi ll. | |
600 | EWNFR-41 | |
601 | Guidance: To enhance the user’ s experien ce with th e applicat ion, defin e and adhe re to a mo del for th e design e lements wi thin the a pplication . | |
602 | EWNFR-20 | |
603 | Guidance: Usability testing mu st occur i n a dedica ted test e nvironment that is s eparate fr om both th e developm ent and pr oduction e nvironment s. | |
604 | Non-Functi onal Requi rements | |
605 | ||
606 | ID | |
607 | Non-Functi onal Requi rement | |
608 | Acceptance Criteria ID | |
609 | EWNFR-366 | |
610 | As a Proje ct Team, w e must pro vide Info button so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
611 | EWNFR-367 | |
612 | EWNFR-365 | |
613 | As a Proje ct Team, w e must ens ure color usage with in our app lication r eflects pu rpose of o ur applica tion so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion. | |
614 | EWNFR-368, EWNFR-369 | |
615 | EWNFR-70 | |
616 | As a Proje ct Team, w e must pro vide an in dicator fo r non-visi ble text t hat prompt s the user to scroll so that o ur applica tion will enhance th e user’s e xperience with our | |
617 | EWNFR-142 | |
618 | ||
619 | ||
620 | ID | |
621 | Non-Functi onal Requi rement | |
622 | Acceptance Criteria ID | |
623 | ||
624 | applicatio n. | |
625 | ||
626 | EWNFR-69 | |
627 | As a Proje ct Team, w e must not use terms that repr esent gend er so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
628 | EWNFR-140, EWNFR-141 | |
629 | EWNFR-68 | |
630 | As a Proje ct Team, w e must pro vide conte xt specifi c Help so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
631 | EWNFR-139, EWNFR-364 | |
632 | EWNFR-67 | |
633 | As a Proje ct Team, w e must mak e sure tha t the erro r messages within th e applicat ion are co nsistently used and displayed so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
634 | EWNFR-138 | |
635 | EWNFR-66 | |
636 | As a Proje ct Team, w e must mak e sure tha t the erro r messages within th e applicat ion contai n specific instructi on on how to recover from an e rror so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion. | |
637 | EWNFR-137 | |
638 | EWNFR-65 | |
639 | As a Proje ct Team, w e must mak e sure tha t the erro r messages within th e applicat ion contai n specific instructi on on the meaning of error so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
640 | EWNFR-136 | |
641 | EWNFR-64 | |
642 | As a Proje ct Team, w e must mak e sure tha t the erro r messages within th e applicat ion are in user-cent ric langua ge so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
643 | EWNFR-135 | |
644 | EWNFR-63 | |
645 | As a Proje ct Team, w e must def ine a logi cal tab or der throug h fields o n a screen when the default ta b order is not suffi cient for our applic ation so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation. | |
646 | EWNFR-134 | |
647 | EWNFR-62 | |
648 | As a Proje ct Team, w e must mak e sure tha t the diff erence bet ween statu s icons an d clickabl e icons is visually different so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
649 | EWNFR-133 | |
650 | ||
651 | ||
652 | ID | |
653 | Non-Functi onal Requi rement | |
654 | Acceptance Criteria ID | |
655 | EWNFR-60 | |
656 | As a Proje ct Team, w e must aut o-complete (if appli cable to o ur applica tion) defa ult values in entry fields (wh en possibl e) so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
657 | EWNFR-131, EWNFR-361 , EWNFR-36 2, EWNFR-3 63 | |
658 | EWNFR-59 | |
659 | As a Proje ct Team, w e must pro vide “whit e space” b etween sta tus icons and screen content o therwise o ur applica tion risks non- appr oval from the Usabil ity compli ance group . | |
660 | EWNFR-130 | |
661 | EWNFR-58 | |
662 | As a Proje ct Team, w e must use icons tha t are easi ly recogni zable by u sers so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion. | |
663 | EWNFR-129, EWNFR-360 | |
664 | EWNFR-57 | |
665 | As a Proje ct Team, w e must app ly alterna te row sha ding for l engthy tab les within the appli cation so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
666 | EWNFR-128, EWNFR-359 | |
667 | EWNFR-56 | |
668 | As a Proje ct Team, w e must use consisten t model fo r data ent ry fields so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
669 | EWNFR-125, EWNFR-126 , EWNFR-12 7 | |
670 | EWNFR-55 | |
671 | As a Proje ct Team, w e must use consisten t elements to sort d ata within the appli cation so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
672 | EWNFR-124 | |
673 | EWNFR-54 | |
674 | As a Proje ct Team, w e must use consisten t elements to filter data with in the app lication s o that our applicati on will en hance the user’s exp erience wi th our app lication. | |
675 | EWNFR-123 | |
676 | EWNFR-53 | |
677 | As a Proje ct Team, w e must dis play field labels cl ose to the ir corresp onding ent ry element s on the s creen so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation. | |
678 | EWNFR-122 | |
679 | EWNFR-52 | |
680 | As a Proje ct Team, w e must pro vide a vis ual indica tor for al l required fields so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication. | |
681 | EWNFR-121 | |
682 | EWNFR-51 | |
683 | As a Proje ct Team, w e must pro vide field entry too l tips at the field location o n the scre en so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
684 | EWNFR-119, EWNFR-120 | |
685 | ||
686 | ||
687 | ID | |
688 | Non-Functi onal Requi rement | |
689 | Acceptance Criteria ID | |
690 | EWNFR-50 | |
691 | As a Proje ct Team, w e must all ow users t o print (i f applicab le) from t heir curre nt locatio n (if appl icable) wi thin the a pplication so that o ur applica tion will enhance th e user’s e xperience with our a pplication . | |
692 | EWNFR-118 | |
693 | EWNFR-29 | |
694 | As a Proje ct Team, w e must avo id using a cronyms/ab breviation s so that our applic ation will enhance t he user’s experience with our applicatio n. | |
695 | EWNFR-85, EWNFR-86 | |
696 | EWNFR-28 | |
697 | As a Proje ct Team, w e must lef t align th e labels f or fields so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
698 | EWNFR-84 | |
699 | EWNFR-27 | |
700 | As a Proje ct Team, w e must lef t align pa ge/section titles to anchor ti tles in co nsistent l ocations o n all wind ows/screen s so that our applic ation will enhance t he user’s experience with our applicatio n. | |
701 | EWNFR-82, EWNFR-83 | |
702 | EWNFR-26 | |
703 | As a Proje ct Team, w e must use simple an d consiste nt button labels so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
704 | EWNFR-77, EWNFR-78, EWNFR-79, EWNFR-80, EWNFR-81 | |
705 | EWNFR-25 | |
706 | As a Proje ct Team, w e must use mixed cas e text wit hin the ap plication so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
707 | EWNFR-74, EWNFR-75, EWNFR-76 | |
708 | EWNFR-24 | |
709 | As a Proje ct Team, w e must lef t align co lumn heade rs so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
710 | EWNFR-73 | |
711 | EWNFR-23 | |
712 | As a Proje ct Team, w e must lef t align co ntent in t able cells so that o ur applica tion will enhance th e user’s e xperience with our a pplication . | |
713 | EWNFR-72 | |
714 | EWNFR-32 | |
715 | As a Proje ct Team, w e must pro vide visua l separati on between the navig ation spac e and the main-conte nt area so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication. | |
716 | EWNFR-90, EWNFR-91 | |
717 | EWNFR-31 | |
718 | As a Proje ct Team, w e must use the color s red and green only for statu s driven c ontent wit h our appl ication so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication. | |
719 | EWNFR-88, EWNFR-89 | |
720 | ||
721 | ||
722 | ID | |
723 | Non-Functi onal Requi rement | |
724 | Acceptance Criteria ID | |
725 | EWNFR-30 | |
726 | As a Proje ct Team, w e must pro vide “Help ” informat ion and/or a tooltip when we u se acronym s/abbrevia tions due to screen space limi tations so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication. | |
727 | EWNFR-87 | |
728 | EWNFR-45 | |
729 | As a Proje ct Team, w e must pla ce critica l informat ion in the top porti on of the screen so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
730 | EWNFR-112 | |
731 | EWNFR-44 | |
732 | As a Proje ct Team, w e must use consisten t location s when pla cing navig ation elem ents so th at our app lication w ill enhanc e the user ’s experie nce with o ur applica tion. | |
733 | EWNFR-111 | |
734 | EWNFR-43 | |
735 | As a Proje ct Team, w e must mak e sure tha t text is sized to b e readable so that o ur applica tion will enhance th e user’s e xperience with our a pplication . | |
736 | EWNFR-110 | |
737 | EWNFR-40 | |
738 | As a Proje ct Team, w e must pro vide visua l indicato rs for col umn sortin g behavior s so that our applic ation will enhance t he user’s experience with our applicatio n. | |
739 | EWNFR-104 | |
740 | EWNFR-39 | |
741 | As a Proje ct Team, w e must pro vide stand ard sort b ehavior (b ased on da ta within the table) for all c olumn tabl es so that our appli cation wil l enhance the user’s experienc e with our applicati on. | |
742 | EWNFR-103 | |
743 | EWNFR-38 | |
744 | As a Proje ct Team, w e must use standard date and t ime select ion widget s that are device sp ecific so that our a pplication will enha nce the us er’s exper ience with our appli cation. | |
745 | EWNFR-100, EWNFR-101 , EWNFR-10 2 | |
746 | EWNFR-37 | |
747 | As a Proje ct Team, w e must alw ays use vi sible radi o buttons for all si mple binar y options so that ou r applicat ion will e nhance the user’s ex perience w ith our ap plication. | |
748 | EWNFR-99 | |
749 | EWNFR-35 | |
750 | As a Proje ct Team, w e must mak e drop-dow n selectio n box widt hs appropr iate for t he content so that o ur applica tion will enhance th e user’s e xperience with our a pplication . | |
751 | EWNFR-96, EWNFR-97 | |
752 | EWNFR-34 | |
753 | As a Proje ct Team, w e must hav e a consis tent style for text hyperlinks within ou r applicat ion so tha t our appl ication wi ll enhance the user’ s experien ce with ou r applicat ion. | |
754 | EWNFR-94, EWNFR-95 | |
755 | ||
756 | ||
757 | ID | |
758 | Non-Functi onal Requi rement | |
759 | Acceptance Criteria ID | |
760 | EWNFR-33 | |
761 | As a Proje ct Team, w e must hav e field le vel valida tion and n otificatio ns for mis sing and i nvalid inf ormation o n the same page so t hat our ap plication will enhan ce the use r’s experi ence with our applic ation. | |
762 | EWNFR-92, EWNFR-93 | |
763 | EWNFR-47 | |
764 | As a Proje ct Team, w e must use consisten t screen e lements wi thin our a pplication so that o ur applica tion will enhance th e user’s e xperience with our a pplication . | |
765 | EWNFR-114 | |
766 | Appendix G – User In terface Sp ecificatio ns | |
767 | Non-Functi onal Requi rements | |
768 | ||
769 | ID | |
770 | Non-Functi onal Requi rement | |
771 | Acceptance Criteria ID | |
772 | EWNFR- 188 | |
773 | As a Proje ct Team, w e must avo id the use of vertic ally stack ed control s so that the user c an easily select the control w ith their fingertip. | |
774 | EWNFR-228 | |
775 | EWNFR- 187 | |
776 | As a Proje ct Team, w e must pro vide an in put indica tor for ac tive text entry fiel ds so that the user is aware t hat the ap plication is expecti ng input. | |
777 | EWNFR-227 | |
778 | EWNFR- 186 | |
779 | As a Proje ct Team, w e must use tappable elements t hat are 44 x44 points or larger so that t he user ca n easily s elect the element wi th their f ingertip a nd avoid a n incorrec t element selection by the use r. | |
780 | EWNFR-226 | |
781 | EWNFR- 185 | |
782 | See Descri ption for full requi rement - A s a Projec t Team, we must allo w the user to adjust | |
783 | EWNFR-224, EWNFR-225 | |
784 | EWNFR- 184 | |
785 | As a Proje ct Team, w e must not allow for the conte nt of the screens wi thin the a pplication to take u p 80% of m ore of any screen wi thin the a pplication so that t he focus o f the scre en serves the applic ations pur pose. | |
786 | EWNFR-223 | |
787 | EWNFR- 183 | |
788 | As a Proje ct Team, w e must use an indica tor when a list is s crollable so that th e user is aware that there is more infor mation to be display ed on the screen. | |
789 | EWNFR-222 | |
790 | EWNFR- 181 | |
791 | As a Proje ct Team, w e must mak e sure the entire na me of our applicatio n is visib le when th e applicat ion icon t hat is dis played on the user’s device so that the full name of the app lication i s evident. | |
792 | EWNFR-220 | |
793 | ||
794 | ||
795 | ID | |
796 | Non-Functi onal Requi rement | |
797 | Acceptance Criteria ID | |
798 | EWNFR- 180 | |
799 | As a Proje ct Team, w e must use short nam es for men us items t hat will n ot be trun cated when displayed on the us er’s devic e so that the purpos e of the m enu items are eviden t and user ’s memory load is mi nimized. | |
800 | EWNFR-219 | |
801 | EWNFR- 179 | |
802 | As a Proje ct Team, w e must use the link name to in dicate the destinati on of the link so th at the pur pose of th e link is simply und erstood. | |
803 | EWNFR-217, EWNFR-218 | |
804 | EWNFR- 178 | |
805 | As a Proje ct Team, w e must mak e sure tha t the titl e of any m odal scree n represen ts the tas k being pe rformed on the scree n so that the purpos e of the s creen is s imply unde rstood. | |
806 | EWNFR-216 | |
807 | EWNFR- 177 | |
808 | See Descri ption for full requi rement - A s a Projec t Team, we must make sure that when a li st of opti ons | |
809 | EWNFR-215 | |
810 | EWNFR- 176 | |
811 | As a Proje ct Team, w e must giv e the user a choice to complet e the task or abando n the task presented on a moda l screen i s used so that a cle ar choice for exit a nd control over acti ons for th e user. | |
812 | EWNFR-214 | |
813 | EWNFR- 175 | |
814 | See Descri ption for full requi rement - A s a Projec t Team, we must use clear indi cators tha t instruct s the user how to mo ve forward | |
815 | EWNFR-213 | |
816 | EWNFR- 170 | |
817 | As a Proje ct Team, w e must mak e sure tha t the scre ens of our applicati on adapt t o the orie ntation (p ortrait/la ndscape) o f the devi ce so that the appli cation wil l be consi stent with the user’ s expectat ions. | |
818 | EWNFR-208 | |
819 | EWNFR- 169 | |
820 | As a Proje ct Team, w e must mak e sure tha t we creat e our icon s based on the stand ards of th e device s o that the re is cons istency in the appli cation and we can av oid confus ion. | |
821 | EWNFR-206, EWNFR-207 | |
822 | EWNFR- 168 | |
823 | As a Proje ct Team, w e must mak e sure tha t our appl ication pr operly rec ognizes an y standard physical gestures o f the devi ce so that confusion can be av oided by k eeping wel l tested, well estab lished ges ture stand ards. | |
824 | EWNFR-205 | |
825 | EWNFR- 166 | |
826 | As a Proje ct Team, w e must pro vide a rem aining pro cessing ti me indicat or for tas ks that wi ll take lo nger than 10 seconds so that t he user is aware the applicati on is proc essing inf ormation. | |
827 | EWNFR-202 | |
828 | ||
829 | ||
830 | ID | |
831 | Non-Functi onal Requi rement | |
832 | Acceptance Criteria ID | |
833 | EWNFR- 165 | |
834 | As a Proje ct Team, w e must pro vide a pro cessing in dicator fo r all task s, regardl ess of the ir duratio n, so that the user is aware t he applica tion is pr ocessing i nformation . | |
835 | EWNFR-201 | |
836 | EWNFR- 164 | |
837 | As a Proje ct Team, w e must pro vide immed iate feedb ack (.25) following user input activitie s so that the user i s aware th e applicat ion has re cognized t he user’s input. | |
838 | EWNFR-200 | |
839 | EWNFR- 163 | |
840 | As a Proje ct Team, w e must use consisten t screen m ovement th roughout t he applica tion so th at consist ency exist s and user s do not h ave an add itional co gnitive lo ad to dete rmine how to perform functions . | |
841 | EWNFR-199 | |
842 | EWNFR- 162 | |
843 | As a Proje ct Team, w e must use consisten t scrollin g througho ut the app lication s o that con sistency e xists and users do n ot have an additiona l cognitiv e load to determine how to per form funct ions. | |
844 | EWNFR-198 | |
845 | EWNFR- 161 | |
846 | As a Proje ct Team, w e must pre sent the c ontent of the applic ation cons istently t hroughout the applic ation so t hat consis tency exis ts and use rs are abl e to easil y find inf ormation. | |
847 | EWNFR-197 | |
848 | EWNFR- 159 | |
849 | As a Proje ct Team, w e must adh ere to the standard navigation practices implement ed by the VA so that consisten cy exists and users do not hav e an addit ional cogn itive load to determ ine differ ent naviga tion metho ds. | |
850 | EWNFR-195 | |
851 | EWNFR- 158 | |
852 | As a Proje ct Team, w e must adh ere to the standard navigation practices of the de vice’s web -browser s o that con sistency e xists and users do n ot have an additiona l cognitiv e load to determine different navigation methods. | |
853 | EWNFR-194 | |
854 | EWNFR- 157 | |
855 | As a Proje ct Team, w e must adh ere to the standard navigation practices of the pl atform’s o perating s ystem so t hat consis tency exis ts and use rs do not have an ad ditional c ognitive l oad to det ermine dif ferent nav igation me thods. | |
856 | EWNFR-193 | |
857 | EWNFR- 156 | |
858 | As a Proje ct Team, w e must adh ere to the standard navigation of the de vice so th at consist ency exist s and user s do not h ave an add itional co gnitive lo ad to dete rmine diff erent navi gation met hods. | |
859 | EWNFR-192 | |
860 | ||
861 | ||
862 | ID | |
863 | Non-Functi onal Requi rement | |
864 | Acceptance Criteria ID | |
865 | EWNFR- 154 | |
866 | As a Proje ct Team, w e make sur e that the screens w ithin the applicatio n are prop erly linke d so they refer to t he same en counter so that our applicatio n will enh ance the u ser’s expe rience wit h our appl ication. | |
867 | EWNFR-190 | |
868 | EWNFR- 153 | |
869 | See Descri ption for Full Req: As a Proje ct Team, w e make sur e that the screens w ithin the applicatio n are prop erly linke d so they refer to t he same pa tient | |
870 | EWNFR-189 | |
871 | Appendix H – VA Bran ding (OPIA ) Specific ations | |
872 | Non-Functi onal Requi rements | |
873 | ||
874 | ID | |
875 | Non-Functi onal Requi rement | |
876 | Acceptance Criteria ID | |
877 | EWNFR-238 | |
878 | As a Proje ct Team, w e must use the VA Mo bile logo on all ele ctronic me dia associ ated with our applic ation othe rwise our applicatio n risks no n-approval from the VA Brandin g complian ce group. | |
879 | EWNFR-268, EWNFR-269 , EWNFR-27 0, EWNFR-2 71, EWNFR- 683 | |
880 | EWNFR-234 | |
881 | As a Proje ct Team, w e must use the VA Me morial log o (If appl ication is sponsored by NCA) p rovided on the VA Mo bile Brand ing websit e otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
882 | EWNFR-261, EWNFR-682 | |
883 | EWNFR-677 | |
884 | See Descri ption for Full Req.: As a Proj ect Team, we must en sure our g raphics us e the appr opriate dp i for mobi le devices to ensure that grap hics are c onsistentl y of a goo d resoluti on and are not blurr y or pixel ated | |
885 | EWNFR-692 | |
886 | EWNFR-231 | |
887 | As a Proje ct Team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Mob ile logo i nto our ap plication otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up. | |
888 | EWNFR-250, EWNFR-251 , EWNFR-25 2, EWNFR-6 79, EWNFR- 680 | |
889 | EWNFR-239 | |
890 | As a Proje ct Team, w e must use the fonts listed wi thin the V A Branding Style Gui de for app lication c hiclets, s plash scre ens and co ntent othe rwise our applicatio n risks no n- approva l from the VA Brandi ng complia nce group. | |
891 | EWNFR-272, EWNFR-273 , EWNFR-27 4 | |
892 | ||
893 | ||
894 | ID | |
895 | Non-Functi onal Requi rement | |
896 | Acceptance Criteria ID | |
897 | EWNFR-237 | |
898 | As a Proje ct Team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Mem orial logo into our applicatio n otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
899 | EWNFR-266, EWNFR-267 | |
900 | EWNFR-676 | |
901 | As a Proje ct Team, w e must VA brand all mobile pag es within the applic ation usin g the resp onsive tem plate docu mented in the latest VA Brandi ng Style G uide other wise our a pplication risks non -approval from the V A Branding complianc e group. | |
902 | EWNFR-691 | |
903 | EWNFR-242 | |
904 | As a Proje ct Team, w e must cre ate the sp lash scree n for our applicatio n using th e requirem ents liste d in the l atest VA B randing St yle Guide otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up. | |
905 | EWNFR-285, EWNFR-286 , EWNFR-28 7, EWNFR-2 88, EWNFR- 289, EWNFR -290, EWNF R-291 | |
906 | EWNFR-230 | |
907 | As a Proje ct Team, w e must use the VA Ad ministrati on logo pr ovided in VA Mobile Style Guid e otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
908 | EWNFR-248, EWNFR-249 | |
909 | EWNFR-235 | |
910 | As a Proje ct Team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Hea lth logo i nto our ap plication otherwise our applic ation risk s non-appr oval from the VA Bra nding comp liance gro up. | |
911 | EWNFR-262, EWNFR-263 | |
912 | EWNFR-241 | |
913 | See Descri ption for Full Req.: As a Proj ect Team, we must cr eate the c hicklet fo r our appl ication us ing the ap propriate requiremen ts (based on adminis tration) l isted in t he latest VA Brandin g Style Gu ide | |
914 | EWNFR-277, EWNFR-278 , EWNFR-27 9, EWNFR-2 80, EWNFR- 281, EWNFR -282, EWNF R-283, EWN FR-284, EW NFR-687 | |
915 | EWNFR-232 | |
916 | As a Proje ct Team, w e must use the VA He alth logo (If applic ation is s ponsored b y VHA) pro vided on t he VA Mobi le Brandin g website otherwise our applic ation risk s non- app roval from the VA Br anding com pliance gr oup. | |
917 | EWNFR-259 | |
918 | EWNFR-243 | |
919 | As a Proje ct Team, w e must nam e our appl ication in a manner that descr ibes the f unctionali ty of the applicatio n otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
920 | EWNFR-292, EWNFR-293 , EWNFR-68 8, EWNFR-6 89 | |
921 | ||
922 | ||
923 | ID | |
924 | Non-Functi onal Requi rement | |
925 | Acceptance Criteria ID | |
926 | EWNFR-678 | |
927 | See Descri ption for Full Req.: As a Proj ect Team, we must en sure our i mages use the approp riate dpi for mobile devices t o ensure t hat graphi cs are con sistently of a good resolution and are n ot blurry or pixelat ed | |
928 | EWNFR-693 | |
929 | EWNFR-236 | |
930 | As a Proje ct Team, w e must ref erence the latest av ailable VA Branding Graphics S tyle guide when inco rporating the VA Ben efits logo into our applicatio n otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
931 | EWNFR-264, EWNFR-265 | |
932 | EWNFR-240 | |
933 | As a Proje ct Team, w e must use the appro priate adm inistratio n color pa lette desc ribed in t he latest VA Brandin g Style Gu ide otherw ise our ap plication risks non- approval from the V A Branding complianc e group. | |
934 | EWNFR-275, EWNFR-276 , EWNFR-68 4, EWNFR-6 85, EWNFR- 686 | |
935 | EWNFR-233 | |
936 | As a Proje ct Team, w e must use the VA Be nefits log o (If appl ication is sponsored by VBA) p rovided on the VA Mo bile Brand ing websit e otherwis e our appl ication ri sks non- a pproval fr om the VA Branding c ompliance group. | |
937 | EWNFR-260, EWNFR-681 | |
938 | EWNFR-675 | |
939 | As a Proje ct Team, w e must VA brand all web pages within the applicati on using t he respons ive templa te documen ted in the latest VA Branding Style Guid e otherwis e our appl ication ri sks non-ap proval fro m the VA B randing co mpliance g roup. | |
940 | EWNFR-690 | |
941 | Appendix I – Patient Safety (O IT) Specif ications | |
942 | Guidance | |
943 | ||
944 | ID | |
945 | Guidance | |
946 | EWNFR-395 | |
947 | Guidance: Software p rogramming calls for data, res ources, an d services , are tran sactional, traceable and with clear indi cations of success a nd failure . | |
948 | EWNFR-653 | |
949 | Guidance: The user i nterface i mplements requiremen ts that ar ticulate u ser decisi on making needs base d on ident ifying rel evant user s, informa tion, task s, and tim ing - and relationsh ips betwee n them. | |
950 | EWNFR-379 | |
951 | Guidance: The user i nterface a rticulates requireme nts that c apture wha t informat ion users need to be able to e nter so th at informa tion is sh ared, reco rded, and utilized b y the syst em. | |
952 | ||
953 | ||
954 | EWNFR-350 | |
955 | Guidance: The team e ngages Pat ient Safet y speciali st during our develo pment phas e. | |
956 | EWNFR-383 | |
957 | Guidance: A confirma tion reque st is pres ented to t he user wh en a safet y critical action th at can't b e undone i s taken. | |
958 | EWNFR-377 | |
959 | Guidance: The import ant inform ation need ed to comp lete safet y critical actions i s displaye d to the u ser in a m anner that helps the user noti ce it. For instance, by its po sition on a screen o r font cha racteristi cs (e.g. c olor, bold or underl ine etc.) | |
960 | EWNFR-347 | |
961 | Guidance: Documentat ion of a c onceptual model and use cases for patien t safety c ritical ta sks have b een create d and sent to Inform atics Pati ent Safety for revie w. | |
962 | EWNFR-349 | |
963 | Guidance: Documentat ion of an independen t clinical expert re view is pr ovided to Informatic s Patient Safety. | |
964 | EWNFR-656 | |
965 | Guidance: There is a mechanism in place that will help the u ser unders tand abnor mal system results b y explaini ng why it is abnorma l. | |
966 | EWNFR-352 | |
967 | Guidance: There is a mechanism in place that will allow the team to co llect post -deploy pa tient safe ty issues. | |
968 | EWNFR-397 | |
969 | Guidance: All screen s/pages ar e uniquely identifie d within t he applica tion. | |
970 | EWNFR-351 | |
971 | Guidance: Pilot test ing is con ducted and documente d in the p ost deploy ment envir onment. | |
972 | EWNFR-348 | |
973 | Guidance: A list of patient sa fety criti cal data a nd tasks h as been do cumented a nd sent to Informati cs Patient Safety fo r review. | |
974 | EWNFR-378 | |
975 | Guidance: The contex t for safe ty critica l values m ust be com municated to reduce the likeli hood it is missed or misinterp reted. | |
976 | EWNFR-385 | |
977 | Guidance: Programmin g calls th at fail wh en trying to support a user ac tion cause a message to be sen t to the u ser and th e text pre sented des cribes the error. | |
978 | EWNFR-391 | |
979 | Guidance: There is a way for t he user to get help with safet y critical tasks. | |
980 | EWNFR-373 | |
981 | Guidance: There is a mechanism in place that will allow the team to co llect post -deploy pa tient safe ty issues. | |
982 | EWNFR-396 | |
983 | Guidance: There is a mechanism in place that captu res use er rors, allo ws the use r to volun tarily rep ort advers e events a nd (if app licable) a llows for network me ssaging to be monito red. | |
984 | Non-Functi onal Requi rements | |
985 | ||
986 | ID | |
987 | Non-Functi onal Requi rement | |
988 | Acceptance Criteria ID | |
989 | EWNFR-398 | |
990 | As a Proje ct Team, w e must uni quely iden tify appli cation dia log boxes so that we can suppo rt problem reporting and monit or system usage afte r | |
991 | EWNFR-429 | |
992 | ||
993 | ||
994 | ID | |
995 | Non-Functi onal Requi rement | |
996 | Acceptance Criteria ID | |
997 | ||
998 | deployment . | |
999 | ||
1000 | EWNFR-399 | |
1001 | See Descri ption of F ull Guidan ce: Patien t Safety r epresentat ives are g iven the i nformation they need ... | |
1002 | ||
1003 | EWNFR-375 | |
1004 | As a Proje ct Team, w e must (if applicabl e) only pr ovide writ e access t o EHR data when nece ssary so t hat we can prevent t he user fr om enterin g incorrec t data int o our appl ication. | |
1005 | EWNFR-640 | |
1006 | EWNFR-394 | |
1007 | As a Proje ct Team, w e must pro vide a mec hanism to report sof tware issu es so that we can mo nitor syst em usage a fter deplo yment. | |
1008 | EWNFR-425 | |
1009 | EWNFR-374 | |
1010 | See Descri ption for Full Req: As a Proje ct Team, w e must pre vent incor rect data entry | |
1011 | EWNFR-639 | |
1012 | EWNFR-376 | |
1013 | As a Proje ct Team, w e must (if applicabl e) only pr ovide modi fy access to EHR dat a when nec essary so that we ca n prevent the user f rom enteri ng incorre ct data in to our app lication. | |
1014 | EWNFR-641 | |
1015 | EWNFR-382 | |
1016 | Guidance: The user i nterface a rticulates requireme nts that c apture wha t informat ion users need to be able to r etrieve so that info rmation is shared, r ecorded, a nd utilize d by the s ystem. | |
1017 | ||
1018 | EWNFR-386 | |
1019 | As a Proje ct Team, w e must (wh en possibl e) ensure that user actions ar e undoable so that o ur applica tion will allow our users to c orrect err ors and ea sily retur n to their tasks. | |
1020 | EWNFR-417 | |
1021 | EWNFR-390 | |
1022 | As a Proje ct Team, w e must pro vide a way for our u sers to im mediately obtain hel p from som eone with specific m edical or psychiatri c knowledg e so that our users can mitiga te the eff ects of gu idance tha t is not s ufficient for the us er’s curre nt needs. | |
1023 | EWNFR-647 | |
1024 | EWNFR-388 | |
1025 | As a Proje ct Team, w e must inc lude “why it happene d” informa tion in er ror feedba ck so that our appli cation wil l allow ou r users to correct e rrors and easily ret urn to the ir tasks. | |
1026 | EWNFR-646 | |
1027 | Appendix J – General Specifica tions | |
1028 | Non-Functi onal Requi rements | |
1029 | ||
1030 | ID | |
1031 | Non-Functi onal Requi rement | |
1032 | Acceptance Criteria ID | |
1033 | ||
1034 | ||
1035 | EWNFR-710 | |
1036 | As a Proje ct Team we must ensu re that ou r applicat ion gives the user t he ability to choose (from wit hin the ap plication) to return to the La unchpad on ce the app lication i s exited s o that a c ommon exit procedure is used f or all mob ile applic ations. | |
1037 | EWNFR-745, EWNFR- 74 6, EWNFR-7 47 | |
1038 | EWNFR-708 | |
1039 | As a Proje ct Team, w e must inc lude a Hel p tab or b utton with in our app lication s o that the user can quickly lo cate impor tant infor mation to assist the m in using our appli cation. | |
1040 | EWNFR-742, EWNFR- 74 3, EWNFR-7 44 | |
1041 | EWNFR-707 | |
1042 | As a Proje ct Team, w e must inc lude the v ersion num ber of the applicati on on the About tab so that th e use will know whic h version of the app lication t hey are us ing. | |
1043 | EWNFR-748, EWNFR-749 | |
1044 | EWNFR-696 | |
1045 | As a Proje ct Team we must ensu re that a Splash Scr een is dis played upo n first us e of the a pplication by the us er so that we can sh are import ant inform ation with and let t he user kn ow the app lication i s loading. | |
1046 | EWNFR-739, EWNFR- 74 0, EWNFR-7 41 | |
1047 | EWNFR-695 | |
1048 | As a Proje ct Team, w e must inc lude an Ab out tab or button wi thin our a pplication so that t he user ca n quickly locate imp ortant inf ormation a bout our a pplication . | |
1049 | EWNFR-736, EWNFR- 73 7, EWNFR-7 38 | |
1050 | EWNFR-694 | |
1051 | As a Proje ct Team, w e must ens ure that f ollowing 1 5 minutes of inactiv ity by the current u ser our ap plication time-outs so that ou r applicat ion effici ently used the limit ed resourc es that ma ybe availa ble to the user. | |
1052 | EWNFR-732, EWNFR- 73 3, EWNFR-7 34, EWNFR- 735 | |
1053 | Appendix K – Data an d Terminol ogy Standa rds Compli ance (OIA) Specifica tions | |
1054 | Guidance | |
1055 | ||
1056 | ID | |
1057 | Guidance | |
1058 | EWNFR-540 | |
1059 | Guidance: It is reco mmended th at the pro ject team document h ow all cli nical data is stored within th e applicat ion. This is so the informatio n can quic kly and ef ficiently be provide d to the D ata and Te rminology Standards compliance group. | |
1060 | EWNFR-539 | |
1061 | Guidance: It is reco mmended th at the pro ject team document h ow all cli nical data is captur ed within the applic ation. Thi s is so th e informat ion can qu ickly and efficientl y be provi ded to the Data and Terminolog y Standard s complian ce group. | |
1062 | EWNFR-533 | |
1063 | Guidance: It is reco mmended th at the pro ject team documents other clin ical data elements t hat are el igible for submissio n. This is so the in formation can quickl y and effi ciently be provided to the Dat a and Term inology St andards co mpliance g roup. | |
1064 | ||
1065 | ||
1066 | Non-Functi onal Requi rements | |
1067 | ||
1068 | ID | |
1069 | Non-Functi onal Requi rements | |
1070 | Acceptance Criteria ID | |
1071 | EWNFR-532 | |
1072 | As a Proje ct Team, w e must ide ntify othe r clinical data elem ents that are eligib le for sub mission to the Data and Termin ology comp liance gro up so that the docum entation w e submit f or the com pliance re view is co mplete and accurate. | |
1073 | EWNFR-545 | |
1074 | EWNFR-531 | |
1075 | As a Proje ct Team, w e must fol low the RX Norm stan dard for p harmacy te rms so tha t the clin ical data and termin ology used within ou r applicat ion confor ms to nati onal stand ards. | |
1076 | EWNFR-544 | |
1077 | EWNFR-530 | |
1078 | As a Proje ct Team, w e must fol low the LO INC standa rd for lab oratory te rms so tha t the clin ical data and termin ology used within ou r applicat ion confor ms to nati onal stand ards. | |
1079 | EWNFR-543 | |
1080 | EWNFR-529 | |
1081 | As a Proje ct Team, w e must fol low the SN OMED stand ard for cl inical ter ms so that the clini cal data a nd termino logy used within our applicati on conform s to natio nal standa rds. | |
1082 | EWNFR-542 | |
1083 | ||
1084 | APPROVAL S IGNATURES | |
1085 | ||
1086 | ||
1087 | From: Blen PII | |
1088 | Sent: Mond ay, August 04, 2014 6:40 PM | |
1089 | To: PII | |
1090 | Cc: PPII | |
1091 | Subject: R E: Mobile Applicatio ns Require ments Spec ification Document ( RSD) **Sig natures Re quired** | |
1092 | ||
1093 | ||
1094 | ||
1095 | Lynn Blend ell, Integ rated Proj ect Team ( IPT) Chair / IT Prog ram Manage r | |
1096 | concur. | |
1097 | ||
1098 | From: PII | |
1099 | Sent: Wedn esday, Aug ust 06, 20 14 3:52 PM | |
1100 | To: PII | |
1101 | Cc: PII | |
1102 | Subject: R E: Mobile Applicatio ns Require ments Spec ification Document ( RSD) **Sig natures Re quired** | |
1103 | ||
1104 | ||
1105 | ||
1106 | Concur. | |
1107 | Shawn Hard enbrook, B usiness Sp onsor | |
1108 | ||
1109 | ||
1110 | From:
|
|
1111 | Sent: Tues day, Augus t 12, 2014 1:11 PM | |
1112 | To: PII | |
1113 | Cc: Nelson , PI) | |
1114 | Subject: R E: Mobile Applicatio ns Require ments Spec ification Document ( RSD) **Sig natures Re quired** | |
1115 | I concur. | |
1116 | ||
1117 | ||
1118 | Paul Manci ni, Projec t Manager | |
1119 | ||
1120 | ||
1121 | From: PII | |
1122 | Sent: Wedn esday, Aug ust 06, 20 14 3:50 PM | |
1123 | To: PII | |
1124 | conCcucr: PII | |
1125 | Subject: R E: Mobile Applicatio ns Require ments Spec ification Document ( RSD) **Sig natures Re quired** | |
1126 | ||
1127 | ||
1128 | ||
1129 | Daniel McC une, Proje ct Manager |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.