4. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 7/13/2017 3:41:29 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.

4.1 Files compared

#	Location	File	Last Modified
1	Genisis_v3.zip\Release 3_Docs	Genisis2_Release 3_Master_Test_Plan_Checklist_06162017.docx	Wed Jun 28 20:38:24 2017 UTC
2	Genisis_v3.zip\Release 3_Docs	Genisis2_Release 3_Master_Test_Plan_Checklist_06162017.docx	Wed Jul 12 17:32:44 2017 UTC

4.2 Comparison summary

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

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

4.4 Active regular expressions

No regular expressions were active.

4.5 Comparison detail

	1	Master Tes t Plan Che cklist
	2	Genomic In formation System for Integrate d Science 2
	3	(Genisis2) Technical Services
	4	Release 3
	5
	6	June 2017
	7	Document V ersion 1.0
	8	Department of Vetera ns Affairs
	9
	10	Document R evision Hi story
	11	Date
	12	Revision
	13	Descriptio n
	14	Author
	15	04/26/2017
	16	Draft
	17	Initial En tries
	18	Booz Allen Hamilton
	19	05/12/2017
	20	1.0
	21	Release 2
	22	Booz Allen Hamilton
	23	06/16/2017
	24	1.0
	25	Release 3
	26	Booz Allen Hamilton
	27
	28
	29	Master Tes t Plan Che cklist
	30	Program: V AHCS Milli on Veteran Program ( MVP)Versio n: Release 3
	31	Applicatio n: Genomic Informati on System for Integr ated Scien ce Genisis 2 (Genisi s2)Patch # : N/A
	32	Date Revie w: 06/16/2 017
	33
	34	Item #
	35	Checklist Question
	36	Yes
	37	No
	38	N/A
	39	1.
	40	Does the M aster Test Plan conf orm to the Master Te st Plan te mplate?
	41	X
	42
	43
	44	2.
	45	Is the Mas ter Test P lan tailor ed in a re asonable m anner?
	46	X
	47
	48
	49	3.
	50	Are the sc ope and ob jectives f or the tes ting clear ly defined ?
	51	X
	52
	53
	54	4.
	55	Are the fe atures to be tested and featur es not to be tested clearly de fined?
	56	X
	57
	58
	59	5.
	60	Is the tes t strategy consisten t with the scope and objective s of the t esting?
	61	X
	62
	63
	64	6.
	65	If iterati ve develop ment is pe rformed, d oes the pl an address testing u pon the co mpletion o f the iter ation? Is an Iterati on test Pl an referen ced?
	66	X
	67
	68
	69	7.
	70	Are the re sponsibili ties for c reating an d maintain ing the te st environ ment adequ ately spec ified?
	71	X
	72
	73
	74	8.
	75	Has the cr eation, ac quisition and popula ting of te st data be en adequat ely addres sed?
	76	X
	77
	78
	79	9.
	80	Have tests for the e nterprise requiremen ts of the applicatio n been pla nned? Secu rity, priv acy and Se ction 508 requiremen ts?
	81	X
	82
	83
	84	10.
	85	Are all th e testing deliverabl es listed?
	86	X
	87
	88
	89	11.
	90	Are traini ng needs a ddressed?
	91	X
	92
	93
	94	12.
	95	Does the s chedule ad dress the size, comp lexity and importanc e of the t esting?
	96	X
	97
	98
	99	13.
	100	Are risks that may j eopardize the testin g effort s pecified h ere or in a tracking tool?
	101	X
	102
	103
	104	14.
	105	Are key te sting term s and acro nyms defin ed in the plan?
	106	X
	107
	108
	109	15.
	110	Is there a mechanism in place to track c hanges to the Master Test Plan ?
	111	X
	112
	113
	114	16.
	115	Is this Ma ster Test Plan feasi ble?
	116	X
	117
	118
	119	17.
	120	Is there a mechanism in place to tract d efects?
	121	X
	122
	123
	124	Genomic In formation System for Integrate d Science 2
	125	(Genisis2) Technical Services
	126	Review Fin dings Summ ary Instru ctions
	127
	128	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.
	129
	130	The Review Findings Summary co ntains the following informati on:
	131
	132	Item
	133	Definition
	134	Review Typ e
	135	Peer Revie w or Forma l Review
	136	Artifact
	137	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 ), Test Pl ans, and T est Packag e.
	138	Author
	139	The person who creat ed the wor k product under revi ew.
	140	Project
	141	The offici al project name.
	142	Applicatio n
	143	The name o f the soft ware appli cation to which this work prod uct pertai ns.
	144	Version
	145	The versio n number o f the soft ware appli cation per tinent to this work product.
	146	Patch
	147	If the sof tware is t o be relea sed via th e National Patch Mod ule, enter the patch number.
	148	Date Revie w Started
	149	The date o f the revi ew meeting .
	150	Date Revie w Closed
	151	The date a ll anomali es, issues and actio n items ar e closed.
	152	Identifier
	153	A unique i dentifier that permi ts identif ication an d sorting; suggested Project a cronym + s equential number (i. e., SUR000 1)
	154	Anomaly Ca tegory
	155	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=T est Plan, TS=Test Sc ript
	156	Anomaly or Issue
	157	Items iden tified and described during th e review.
	158	Resolution
	159	The soluti on for the identifie d anomaly.
	160	Date Resol ved
	161	The date a n issue wa s resolved and the R eview Team agrees it was resol ved correc tly.
	162	Status
	163	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:
	164	Submitted – when an item is lo gged and r eported fo r repair.
	165	Assigned – when an i tem is ass igned for repair.
	166	Opened – w hen an ano maly is as signed for correctio n.
	167	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.
	168	Resolved - when an a nomaly is corrected and sent f or review or verific ation.
	169	Re-Opened – when an anomaly is closed an d then reo pened for modificati on.
	170	Returned – when an a nomaly is reviewed, verified a s "incorre ct", and r eturned to author.
	171	Verified – when an a nomaly is reviewed a nd verifie d as "corr ect".
	172	Closed – w hen an ano maly is su ccessfully reviewed and closed with a re solution a nd resolut ion date.
	173	Deferred – when an a nomaly is designated for corre ction at a later dat e.
	174	Duplicated – when an item is a ssessed to be a dupl icate of a prior rec ord.
	175	Escalated – when an item requi res evalua tion by ma nagement.
	176	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.
	177	Impact
	178	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 :
	179	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 .
	180	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); r epresents a high val ue or cost ; sponsore d or initi ated by th e National Program O ffice; or negatively impacts e ssential o perational or busine ss process ing.
	181	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 .
	182
	183	Genomic In formation System for Integrate d Science 2 (Genisis 2) Technic al Service s
	184	Review Fin dings Summ ary
	185
	186	Applicatio n: Genisis 2Release: Release 3D ate Review Begun: N/ A
	187	Author: Bo oz Allen H amiltonPat ch: N/A Da te Review Closed: Ju ne 16, 201 7
	188
	189	Project Ac ronym-Numb er
	190	Anomaly Ca tegory
	191	Anomaly or Issue
	192	Date Resol ved
	193	Status
	194	Impact
	195	Rational # 487928
	196	UI
	197	Data Desti nation Man ager Role: The filte r for the Requestor columns on the Data Destinatio n Manager Request Pa ge does no t filter p roperly. R efer to TC 0006.
	198	6/2/2017
	199	Closed
	200	Minor
	201	Rational#
	202	53663
	203	UI
	204	DDM & DSM Roles: Neg ative resp onse butto ns in the Action col umn on the Request P age allows the user to advance the workf low withou t entering required comments.
	205	TBD
	206	Open (Sche duled for Release 4)
	207	Minor
	208
	209