19. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 5/8/2017 10:03:21 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.

19.1 Files compared

#	Location	File	Last Modified
1	var-utility-web-Release-1.0.0-Branch.zip\MHED_VAR_DOCS	Utility_v1_RSD+Addendum.docx	Mon May 8 15:44:30 2017 UTC
2	var-utility-web-Release-1.0.0-Branch.zip\MHED_VAR_DOCS	Utility_v1_RSD+Addendum.docx	Mon May 8 18:54:52 2017 UTC

19.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	4	376
Changed	3	10
Inserted	0	0
Removed	0	0

19.3 Comparison options

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

19.4 Active regular expressions

No regular expressions were active.

19.5 Comparison detail

	1	Utility_v1 _RSD Adden dum
	2	VAR Utilit y
	3	Work Effor t Under Sc heduling E nhancement s Contract
	4	Includes Utility Re lease v 1. 0.0
	5
	6	Requiremen ts Specifi cation Doc ument - Ad dendum
	7	1.Introduc tion
	8
	9	Name of Mo bile Appli cation
	10	VAR Utilit y
	11	Name of JI RA Project
	12	VAR Utilit y v1
	13	Web addres s where mo bile appli cation can be viewed
	14
	15	Descriptio n of Mobil e Applicat ion
	16	Utility pr ovides aut horized sc heduling c lerk users with the ability to configure the offer ings displ ayed in VA R for a gi ven facili ty. Config urable par ameters in clude cust om message s, the abi lity to su bmit an ap pointment request fo r a given service, a nd patient history l imit requi rements pe r service.
	17	Date
	18	RSD/ARD MA Addendu m Version
	19	Author
	20	Descriptio n of Docum ent Change
	21	Associated BRD Versi on
	22	Associated Concept/S cope Versi on
	23	Other Asso c.
	24	Other Asso c.
	25	11/12/201 5
	26	1.0
	27	Jennifer Zinck
	28	Initial Ve rsion
	29	Utility_v 1_Business Requireme nts Docume nt (BRD)
	30
	31
	32
	33
	34
	35
	36
	37
	38
	39
	40
	41
	42
	43
	44
	45
	46
	47
	48
	49
	50	Applicatio n Owner/An alyst/PM C ontact Inf ormation
	51	Applicatio n Owner/An alyst Name /Point of Contact (POC)
	52	Jennifer Zinck
	53	VA E-Mail Address
	54	PII
	55	Phone Numb er
	56	PII
	57	Developer Organizati on/Company
	58	ASMR
	59	Contract S tart Date
	60	9/28/2015
	61	Contract E nd Date
	62	9/27/2015
	63	Web and Mo bile Solut ions PM or POC
	64
	65	VA E-Mail Address
	66
	67	Phone Numb er
	68
	69	VA Product Developme nt PM or P OC
	70
	71	VA E-Mail Address
	72
	73	Phone Numb er
	74
	75	1.1 Purpos e
	76	This RSD A ddendum sp ecifies th e function s, user st ories, and technolog y that are to be imp lemented b y the Sche duling Adm inistratio n Utility. The purpo se of the RSD Addend um is to c apture and articulat e the Func tional and Non-Funct ional Requ irements ( NFRs) of t he Schedul ing Admini stration U tility. Th e intended audience is both th e business community , who supp lies and a pproves th e requirem ents, and the develo per who wi ll provide the softw are and ha rdware tha t will mak e up the S cheduling Administra tion Utili ty]. This document s erves as t he baselin e to furth er define the scope of the Sch eduling Ad ministrati on Utility and verif y the qual ity of the solution.
	77	1.2 Scope
	78
	79	Utility_v1 _Business Requiremen ts Documen t (BRD)
	80
	81	1.3 Refere nces
	82	Enterpris e-Wide Non -Functiona l Requirem ents Proje ct: https: / DNS /browse/EW NFR
	83	MAP RSD: h ttp:// DNS /warboard/ ProjectDoc s/MobileDe velopment( MD)/MAP_RS D.pdf
	84	MAP VAMF S DD: http:/ / DNS /warboard/ ProjectDoc s/MobileDe velopment( MD)/MAP_VA MF_SDD.pdf
	85	Utility_v1 .0.0_Syste m Design D ocument (S DD) Addend um
	86	Utility_v1 _Business Requiremen ts Documen t (BRD)
	87	2.Overall Descriptio n
	88	2.1.Access ibility Sp ecificatio ns
	89	The listin g of enter prise 508 NFRs that are applic able to th is applica tion are l ocated in Appendix A – 508 Acc essibility (OIT) Spe cification s of of th e MAP RSD.
	90	2.2.Busine ss Rules S pecificati on
	91	Intended A udience (U ser) for M obile Appl ication:
	92	Veteran
	93	Caregiver
	94	Provider
	95	Public
	96	Business N eeds
	97	Describe a nd/or mode l the expe cted workf low:
	98	Reference the wiki f or flow di agrams.
	99	Describe a ll Busines s Needs: Reference the BRD: Utility_v1 _Business Requiremen ts Documen t (BRD)
	100	Ref. ID
	101	Need
	102	Business V alue
	103	1.
	104
	105
	106	2.
	107
	108
	109	3.
	110
	111
	112	What laws / regulati ons cover the implem entation o f the ap p? (To ens ure compli ance)
	113	What is th e expected & maximum size of t he user ba se?
	114	2.3.Design Constrain ts Specifi cation
	115	Design con straints r epresent m andated de sign decis ions. Exam ples: CCOW complianc e, softwar e language s, softwar e process requiremen ts, prescr ibed use o f developm ental tool s, archite ctural and design co nstraints, purchased component s, and cla ss librari es.
	116	Transport Layer Secu rity (TLS) – XML/JSO N used. XM L provides a mechani sm to impo se constra ints on th e storage layout and logical s tructure.
	117	2.4.Disast er Recover y Specific ation
	118	If DR is c overed in a separate document, provide t he link. O r state NA if DR is not applic able.
	119	2.5.Docume ntation Sp ecificatio ns
	120	Describe r equirement s for user documenta tion, help systems, help about notices, installati on guide, security g uide, impl ementation guide, an d any othe r forms of documenta tion.
	121	2.6.Functi onal Speci fications
	122	Describe t he unique functional specifica tions for this app. Functional specifica tions can include fe ature sets , capabili ties, and security. Provide th e URLs in the table below.
	123
	124	Requiremen ts
	125	EPIC ID/Na me
	126	FEATURE ID /Name
	127	USER STORY ID/Name
	128	Associated USER STOR Y Acceptan ce Criteri a
	129	VAR-1753 Schedulin g Administ ration Uti lity
	130
	131	Reference app RTM
	132	Reference app RTM
	133
	134
	135
	136
	137
	138
	139
	140
	141
	142
	143
	144
	145	2.7.Graphi cal User I nterface ( GUI) Speci fications
	146	Document t he GUI spe cification s. If thes e are cont ained in a nother doc ument, pro vide the U RL.
	147	2.8.Multi- divisional Specifica tions
	148	This secti on will be not appli cable unle ss there i s a VistA component to the app .
	149	Use this s ection to document t he multi-d ivisional specificat ions to en sure that all applic ations wil l operate in a multi -divisiona l or multi -site envi ronment wh ile fully supporting local hea lth care d elivery.
	150	2.9.Perfor mance Spec ifications
	151	This secti on should identify d ynamic num eric speci fications placed on the softwa re or on h uman inter action wit h the soft ware as a whole. Num erical spe cification s may incl ude:
	152	The number of simult aneous use rs to be s upported.
	153	Dynamic nu meric spec ifications should in clude the numbers of transacti ons and ta sks and th e amount o f data to be process ed within certain ti me periods for both normal and peak work load condi tions.
	154	2.10.Quali ty Attribu tes Specif ication
	155	Indicate a ny specifi cations th at enhance the suppo rtability, maintaina bility, po rtability, testabili ty, or reu sability o f the app being deve loped. Thi s may incl ude coding standards , naming c onventions , class li braries, m aintenance access, a nd mainten ance utili ties.
	156	The follow ing are fo und in the MAP RSD:
	157	listing of enterpris e code rev iew guidan ce is loca ted in App endix B – Code Revie w Specific ations
	158	listing of enterpris e Verifica tion & Val idation (V &V) NFRs i s located in Appendi x C – V&V Specificat ions
	159	listing of enterpris e User Int erface NFR s is locat ed in Appe ndix G – U ser Interf ace Specif ications
	160	listing of enterpris e VA Brand ing NFRs i s located in Appendi x H – VA B randing (O PIA) Speci fications
	161	listing of enterpris e patient safety NFR s is locat ed in Appe ndix I – P atient Saf ety (OIT) Specificat ions
	162	listing of enterpris e general NFRs are l ocated in Appendix J – General Specifica tions
	163	listing of enterpris e Data and Terminolo gy Standar ds NFRs is located i n Appendix K – Data and Termin ology Stan dards Comp liance (OI A) Specifi cations
	164	2.11.Relia bility Spe cification
	165	Specify th e level of reliabili ty require d for the specific a pp. Exampl es:
	166	Availabili ty – perce ntage of t ime availa ble (xx.xx %), hours of use, ma intenance access, de graded mod e operatio ns, and si milar.
	167	Accuracy – precision (resoluti on) and ac curacy (by a known s tandard) t hat is req uired in t he systems output.
	168	Bugs – Thi s is categ orized in terms of m inor, sign ificant, a nd critica l bugs: th e specific ation(s) m ust define what is m eant by a “critical” bug. For example, c omplete lo ss of data or comple te inabili ty to use certain pa rts of the functiona lity of th e system.
	169	2.12.Scope Integrati on
	170	If the app is indepe ndent and completely self-cont ained, it should be so stated here.
	171	If the app is a comp onent of a larger sy stem, then this sect ion should relate th e specific ations of that large r system t o function ality of t he softwar e and shou ld identif y interfac es between that syst em and the software.
	172	Specify th e use of o ther requi red softwa re product s and any interfaces with othe r applicat ions or ot her system s such as commercial off-the-s helf (COTS ) or natio nal databa ses. Provi de:
	173	Integratio n Agreemen t (IA) num ber as app ropriate
	174	Product na me
	175	Version nu mber
	176	Purpose of the inter facing sof tware as r elated to this softw are produc t
	177	Definition of the in terface in terms of message co ntent and format (HL 7, Electro nic Data I nterchange , etc.)
	178	A block di agram show ing the so ftware int erfaces an d major co mponents o f the larg er system, interconn ections, a nd externa l interfac es can be helpful.
	179	2.13. Sec urity Spec ifications
	180	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 fications of the MAP RSD.
	181	Describe a ny additio nal app-sp ecific sec urity spec ifications or includ e URL if d escribed i n the BRD or Concep t Paper.
	182	2.14. Syst em Feature s
	183	A list of system fea tures and their desc riptions i s describe d in the M AP VAMF SD D and the VAR Utilit y SDD Adde ndum.
	184	2.15. Usab ility Spec ifications
	185	Include ap p-specific usability non-funct ional requ irements t hat affect usability . Include Enterprise NFRs that have been incorpora ted into t he design of the app lication. The follow ing list c ontains ex amples of usability specificat ions:
	186	Training – Specify t ime requir ed for a n ormal user s and powe r users to become pr oductive
	187	Performanc e measures – Specify task time s for typi cal tasks
	188	The listin g of enter prise Usab ility NFRs is locate d in Appen dix F – Us ability Sp ecificatio ns of the MAP RSD
	189	3.Purchase d Componen ts
	190	Describe a ny compone nts purcha sed for us e in the s ystem/proj ect, any a pplicable licensing or usage r estriction s, and any associate d compatib ility/inte roperabili ty or inte rface stan dards.
	191	4.Estimati on
	192	Detail the estimatio n approach for the p roject. If the proje ct chooses to use fu nction poi nt estimat ion, provi de the URL to the FP C Workbook .
	193	Template u pdated 7/1 5/2015