2. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 2/19/2018 2:07:25 PM Eastern Standard 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.

2.1 Files compared

#	Location	File	Last Modified
1	OneVA_Pharmacy_CAS_MPDU_Build-2_CIF_Package.zip\OneVA_Pharmacy_CAS_MPDU_Build-2_CIF_Package\CAS MPDU_Build-2_Checklists	product_build_checklist - OneVA Pharmacy CAS MPDU Build-2.docx	Fri Jan 19 04:27:56 2018 UTC
2	OneVA_Pharmacy_CAS_MPDU_Build-2_CIF_Package.zip\OneVA_Pharmacy_CAS_MPDU_Build-2_CIF_Package\CAS MPDU_Build-2_Checklists	product_build_checklist - OneVA Pharmacy CAS MPDU Build-2.docx	Thu Feb 15 21:50:28 2018 UTC

2.2 Comparison summary

Description	Between Files 1 and 2
Description	Text Blocks	Lines
Unchanged	1	554
Changed	0	0
Inserted	0	0
Removed	0	0

2.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

2.4 Active regular expressions

No regular expressions were active.

2.5 Comparison detail

	1	Department of Vetera ns Affairs
	2
	3	Product Bu ild Checkl ist
	4
	5
	6
	7
	8	January 20 18
	9
	10	Version 1. 1
	11
	12
	13
	14	Revision H istory
	15	Date
	16	Version
	17	Descriptio n
	18	Author
	19	10/18/2017
	20	1.0
	21	Product Bu ild Checkl ist Build- 1
	22	Joe McGove rn
	23	01/18/2018
	24	1.0
	25	Product Bu ild Checkl ist Build- 2
	26	Joe McGove rn
	27
	28
	29
	30	Product Bu ild Checkl ist
	31	Applicatio n: OneVA P harmacyVer sion:
	32	Project: C linical An cillary Se rvices (CA S)Patch#: PSD383, PSO7505 , PSS121 9,
	33	X U_8_689
	34	Medic al Permiss ions and D ispensing
	35	Upgra des (MPDU)
	36	Date Revie w Closed:
	37	Review Out come
	38	Item #
	39	Checklist Question
	40	Peer Revie w consists of items 1 -14. Fo rmal Revie w consists of all it ems.
	41	Yes
	42	No
	43	N/A
	44	1
	45	Do all com ponents fo llow the S ystem Desi gn Documen t?
	46	X
	47
	48
	49	2
	50	Do all com ponents sa tisfy the requests o f the Requ irements S pecificati on Documen t?
	51	X
	52
	53
	54	3
	55	Are the Us e Case Spe cification s document ed?
	56	X
	57
	58
	59	4
	60	Is the Int erface Con trol Docum ent comple te and cur rent?
	61
	62
	63	X
	64	5
	65	Are the co mponents r equired fo r the buil d identifi ed?
	66	X
	67
	68
	69	6
	70	Do all com ponents fo llow Produ ct Develop ment Stand ards?
	71	X
	72
	73
	74	7
	75	Is Product Component Testing ( aka Unit T esting) co mplete for each comp onent of t he build?
	76	X
	77
	78
	79	8
	80	Are the re sults of t he Product Component Testing d ocumented?
	81	X
	82
	83
	84	9
	85	Did Produc t Componen t Testing follow Pro duct Devel opment Sta ndards?
	86	X
	87
	88
	89	10
	90	Have the T est Script s been com pleted?
	91	X
	92
	93
	94	11
	95	Do the Tes t Scripts conform to Product D evelopment Standards ?
	96	X
	97
	98
	99	12
	100	Is the Mas ter Test P lan comple ted accord ing to the Test Prep aration pr ocess?
	101	X
	102
	103
	104	13
	105	Is Product Documenta tion avail able for t he build?
	106	X
	107
	108
	109	14
	110	Has the se quence of integratio n of the P roduct Com ponents be en identif ied (see T est Prepar ation Proc ess)? And Documented ?
	111
	112
	113	X
	114	15
	115	Has Compon ent Integr ation test ing been p erformed?
	116	X
	117
	118
	119	16
	120	Has the Co mponent In tegration Test Defec t Log been completed ?
	121	X
	122
	123
	124	17
	125	Has the Co mponent In tegration Test Evalu ation Summ ary been c ompleted?
	126	X
	127
	128
	129	18
	130	Has the Co mponent In tegration Test Execu tion Log b een comple ted?
	131	X
	132
	133
	134	19
	135	Has the So ftware Qua lity Assur ance Revie w Checklis t been sta rted?
	136	X
	137
	138
	139
	140
	141	Review Fin dings Summ ary Instru ctions
	142
	143	A Review F indings Su mmary is a tool crea ted to doc ument and track anom alies and issues ide ntified du ring revie ws.
	144	The Review Findings Summary co ntains the following informati on:
	145
	146
	147	Item
	148	Definition
	149	Review Typ e
	150	Peer Revie w or Forma l Review
	151	Artifact
	152	The catego ry of the artifact u nder revie w, such as : Requirem ents Speci fication D ocument, S oftware De sign Docum ent, Proto type, Code , Document ation (Rel ease Notes , User Man ual, Techn ical Manua l, Install ation Guid e, Securit y Guide), Patch Desc ription (i f released through N ational Pa tch Module ), Master Test Plans , and Test Package.
	153	Author
	154	The person who creat ed the wor k product under revi ew.
	155	Project
	156	The offici al project name.
	157	Applicatio n
	158	The name o f the soft ware appli cation to which this work prod uct pertai ns.
	159	Version
	160	The versio n number o f the soft ware appli cation per tinent to this work product.
	161	Patch
	162	If the sof tware is t o be relea sed via th e National Patch Mod ule, enter the patch number.
	163	Date Revie w Started
	164	The date o f the revi ew meeting .
	165	Date Revie w Closed
	166	The date a ll anomali es, issues and actio n items ar e closed.
	167	Identifier
	168	A unique i dentifier that permi ts identif ication an d sorting; suggested Project a cronym + s equential number (i. e., SUR000 1)
	169	Anomaly Ca tegory
	170	CM=Configu ration Man agement, C O=Coding, CS=Coding Standards, DC=Docume ntation Co ntent, DE= Design, DP =Documenta tion Prese ntation, I A=Integrat ion Agreem ent, PE=Pe rformance, SP=Specif ication, T R=Traceabi lity, TP=M aster Test Plan, TS= Test Scrip t
	171	Anomaly or Issue
	172	Items iden tified and described during th e review.
	173	Resolution
	174	The soluti on for the identifie d anomaly.
	175	Date Resol ved
	176	The date a n issue wa s resolved and the R eview Team agrees it was resol ved correc tly.
	177	Status
	178	The variou s states t hrough whi ch an anom aly passes on the wa y to resol ution and closure. T he anomaly states ar e:
	179	Submitted – when an item is lo gged and r eported fo r repair.
	180	Assigned – when an i tem is ass igned for repair.
	181	Opened – w hen an ano maly is as signed for correctio n.
	182	Deleted – when an it em is orig inally rep orted as a n anomaly, but later deleted b ecause the item is e ither a du plicate or not an an omaly.
	183	Resolved - when an a nomaly is corrected and sent f or review or verific ation.
	184	Re-Opened – when an anomaly is closed an d then reo pened for modificati on.
	185	Returned - when an a nomaly is reviewed, verified a s "incorre ct", and r eturned to author.
	186	Verified - when an a nomaly is reviewed a nd verifie d as "corr ect".
	187	Closed - w hen an ano maly is su ccessfully reviewed and closed with a re solution a nd resolut ion date.
	188	Deferred - when an a nomaly is designated for corre ction at a later dat e.
	189	Duplicated – when an item is a ssessed to be a dupl icate of a prior rec ord.
	190	Escalated – when an item requi res evalua tion by ma nagement.
	191	Note: The statuses l isted abov e reflect the use of Rational ClearQuest for anoma ly trackin g. Manual tracking m ay use a s implified list of st atuses.
	192	Impact
	193	The classi fication o f anomalie s accordin g to their potential damage to the softw are, syste ms, patien t, personn el or oper ating syst ems. They are classi fied in th ree levels :
	194	High Impac t - an err or or abse nce of fun ctionality that may severely j eopardize patient or personnel safety; a dversely i mpacts all users; re presents a significa nt value o r cost; is governed by Congres sional man date; affe cts either a large d atabase or critical data; requ ires Food and Drug A dministrat ion (FDA) certificat ion/approv al; affect s Veterans Integrate d Service Network (V ISN) issue s; or nega tively imp acts the i nterdepend ence of ap plications .
	195	Medium Imp act - an e rror or ab sence of f unctionali ty that ad versely af fects the safety of veteran is sues or us ers of lar ge applica tions, i.e ., Pharmac y, Lab, et c.; repres ents a hig h value or cost; spo nsored or initiated by the Nat ional Prog ram Office ; or negat ively impa cts essent ial operat ional or b usiness pr ocessing.
	196	Low Impact - an erro r or absen ce of func tionality that may c ause opera tor/user i nconvenien ce and min imally aff ects opera tional fun ctionality .
	197
	198	Review Fin dings Summ ary
	199	Artifact: Author: P roject:
	200	Applicatio n: Version : Patch: D ate Review Begun: Da te Review Closed:
	201
	202	Project ac ronym-numb er
	203
	204	Anomaly Ca tegory
	205
	206	Anomaly or Issue
	207	Date Resol ved
	208	Status
	209	Impact
	210
	211
	212	Anomaly or Issue:
	213	Location:
	214	Resolution :
	215
	216
	217
	218
	219
	220	Anomaly or Issue:
	221	Location:
	222	Resolution :
	223
	224
	225
	226
	227
	228	Anomaly or Issue:
	229	Location:
	230	Resolution :
	231
	232
	233
	234
	235
	236	Anomaly or Issue:
	237	Location:
	238	Resolution :
	239
	240
	241
	242
	243
	244	Anomaly or Issue:
	245	Location:
	246	Resolution :
	247
	248
	249
	250
	251
	252
	253	Template R evision Hi story
	254	Date
	255	Version
	256	Descriptio n
	257	Author
	258	April 2014
	259	1.4
	260	Converted to MS Offi ce 2007-20 10 format
	261	Process Ma nagement
	262	October 20 11
	263	1.3
	264	Updated fo rmatting t o current ProPath do cumentatio n standard s
	265	Process Ma nagement
	266	June 2011
	267	1.2
	268	Changed OE D to Produ ct Develop ment, wher e applicab le, and ch anged test plan to m aster test plan
	269	Process Ma nagement
	270	July 2010
	271	1.1
	272	Changed So ftware to System in item 1
	273	Process Ma nagement
	274	June 2009
	275	1.0
	276	Initial Ve rsion
	277	Process Ma nagement