3. EPMO Open Source Coordination Office Redaction File Detail Report

Produced by Araxis Merge on 6/12/2018 11:43:17 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.

3.1 Files compared

#	Location	File	Last Modified
1	VPR_1_7.zip\VPR_1_7	VPR_1_7 Primary Developer Checklist.docx	Wed Apr 25 17:58:04 2018 UTC
2	VPR_1_7.zip\VPR_1_7	VPR_1_7 Primary Developer Checklist.docx	Fri Jun 8 20:17:35 2018 UTC

3.2 Comparison summary

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

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

3.4 Active regular expressions

No regular expressions were active.

3.5 Comparison detail

	1	Primary De veloper Re view Check list
	2
	3	Department of Vetera ns Affairs
	4	February 2 017
	5	Version 1. 0
	6
	7	Revision H istory
	8	Date
	9	Version
	10	Descriptio n
	11	Author
	12
	13
	14
	15
	16
	17
	18
	19
	20	M Code Pri mary Devel oper’s Che cklist
	21	Use this c hecklist t o complete the prima ry develop er’s activ ities incl uding any additional items dir ected by y our Develo pment Mana ger or Tea m Leader.
	22	It is the developer’ s responsi bility to complete t he checkli st and ass ure that i s sent to the Projec t Manager.
	23	If a new t est versio n is requi red to add ress issue s identifi ed by revi ews or tes ting, a ne w Primary Developer Checklist, along wit h other it ems listed in item 1 1, will be resubmitt ed to the Project Ma nager.
	24	Patch Numb er and Ide ntity of R esponsible Person
	25	Test Versi on and Dat e Complete d
	26	Patch Numb er: VPR1 .07
	27	Test Versi on: v1
	28	Completed by: Melani e Buechler
	29	Date Check list Compl eted: 2/2/ 2018
	30
	31	#
	32	Primary De veloper’s Checklist
	33	OK/NA
	34	Entry of NA Require s Comments
	35	1
	36	Request an d receive approval f rom the DB A for all Data Dicti onary (DD) changes b efore the patch is s ent to SQA . Submissi ons for Da ta Diction ary approv als are se nt to VA O IT OED Vis tA DBA.
	37	NA
	38	No DD chan ges
	39	2
	40	Request an d receive approval f or all new or update d Integrat ion Contro l Registra tions (ICR s) before the patch is sent to SQA. Sub missions f or ICR app roval are sent to OI T PD Integ ration Con trol Regis trations.
	41	NA
	42	No new ICR s
	43	3
	44	Request an d receive approval f rom the HL 7 Messagin g Coordina tor, if ap plicable, before the patch is sent to SQ A. Submis sions for HL7 Messag ing approv al are sen t to VA OI T PD ADC T A Messagin g Administ ration.
	45	NA
	46	No HL7
	47	4
	48	Review all necessary component s of the p atch for c ompliance with the D epartment of Veteran s Affairs M Programm ing Standa rds and Co nventions (SAC).
	49	OK
	50
	51	5
	52	Run ^XINDE X before c reating th e build an d check fo r errors t hat might be reporte d. You may want to o ptionally run ^%RCHE CK.
	53	OK
	54
	55	6
	56	Validate t hat Requir ed Builds are proper ly documen ted in the KIDS Buil d and list ed as Asso ciated Pat ches in th e National Patch Mod ule entry. For exam ples, refe rence the National P atch Modul e Patch Te mplate pro vided in P roPath.
	57	OK
	58
	59	7
	60	Some appli cations li ke Kernel, FileMan, CMOP, and others are installed in non-ty pical VIST A Instance s that do not run al l VISTA ap plications . As a res ult, their patches c annot be b undled wit h other ap plication builds.
	61
	62	If this is a multi-p roduct rel ease, conf irm that t his build does not i nclude pat ches that cannot be bundled.
	63
	64	NA
	65	Not multi- product
	66	8
	67	Update the National Patch Modu le with al l necessar y informat ion and la test build .
	68	OK
	69
	70	9
	71	Install th e patch fr om the Nat ional Patc h Module i n another account to verify th e build in stalls cor rectly. T his includ es, but is not limit ed to, the following items:
	72	No errors upon insta llation.
	73	Environmen t Checks a re success ful.
	74	Pre-Instal lation Rou tines are successful .
	75	Post Insta llation Ch ecksums ma tch the Na tional Pat ch Module patch desc ription.
	76	^DDs are u pdated cor rectly.
	77	Menus and Options ar e updated correctly.
	78	Other comp onents are installed correctly .
	79	Data Conve rsions are successfu l.
	80	Post Insta llation fu nctions ar e successf ul.
	81	ad hoc tes ting of af fected pac kage optio ns and fun ctions per formed aft er install ation is s uccessful.
	82	OK
	83
	84	10
	85	Validate t hat the in stallation instructi ons are ac curate in the Instal lation Gui de and/or Patch Desc ription.
	86	OK
	87
	88	11
	89	Create the patch-tra cking mess age on FOR UM. Includ e the test sites, SQ A Analyst, the OED R elease Coo rdinator, and other team membe rs.
	90
	91
	92	12
	93	Complete t he Product Component Testing p hase, incl uding a te st of all modificati ons.
	94	A capture of the tes t results is require d. A copy is submit ted to the Project M anager and if reques ted to SQA .
	95
	96
	97	13
	98	Upon compl etion, the following items wil l be submi tted to th e Project Manager vi a Outlook:
	99	Primary De veloper Ch ecklist
	100	FORUM Patc h Tracking Message N umber
	101	Data Dicti onary Appr oval Messa ge
	102	Location o f the host file, if being rele ased via a host file
	103	Installati on Guide ( when appli cable)
	104	HL7 Messag ing Approv al (when a pplicable)
	105	OED Testin g Service Report (wh en applica ble)
	106
	107	The Projec t Manager will notif y SQA that the patch is ready for review via Outlo ok.
	108	OK
	109