Produced by Araxis Merge on 3/30/2018 9:10:28 AM Central 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 | CAS_RxSU2_Build-2_Sprint-1.zip\CAS_RxSU2_Build-2_Sprint-1_Checklists | product_build_checklist_CAS_RxSU2_Build-2_Sprint-1.docx | Fri Mar 9 21:15:46 2018 UTC |
2 | CAS_RxSU2_Build-2_Sprint-1.zip\CAS_RxSU2_Build-2_Sprint-1_Checklists | product_build_checklist_CAS_RxSU2_Build-2_Sprint-1.docx | Thu Mar 29 19:50:26 2018 UTC |
Description | Between Files 1 and 2 |
|
---|---|---|
Text Blocks | Lines | |
Unchanged | 1 | 550 |
Changed | 0 | 0 |
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 | Product Bu ild Checkl ist | |
4 | ||
5 | ||
6 | ||
7 | ||
8 | March 201 8 | |
9 | ||
10 | Version 1. 1 | |
11 | ||
12 | ||
13 | ||
14 | Revision H istory | |
15 | Date | |
16 | Version | |
17 | Descriptio n | |
18 | Author | |
19 | 12/19/2017 | |
20 | 1.0 | |
21 | Product Bu ild Checkl ist | |
22 | Joe McGove rn | |
23 | 03/09/2018 | |
24 | 1.1 | |
25 | Product Bu ild Checkl ist | |
26 | Joe McGove rn | |
27 | ||
28 | ||
29 | ||
30 | Product Bu ild Checkl ist | |
31 | Applicatio n: OneVA P harmacyVer sion: Vist A Forum Re lease | |
32 | Project: C linical An cillary Se rvices (CA S)Patch#: OR_3_478, PSO_7_511, PSS_1_221 | |
33 | Pharm acy Update s Phase II (RxSU2) | |
34 | Date Revie w Closed: | |
35 | Review Out come | |
36 | Item # | |
37 | Checklist Question | |
38 | Peer Revie w consists of items 1 -14. Fo rmal Revie w consists of all it ems. | |
39 | Yes | |
40 | No | |
41 | N/A | |
42 | 1 | |
43 | Do all com ponents fo llow the S ystem Desi gn Documen t? | |
44 | X | |
45 | ||
46 | ||
47 | 2 | |
48 | Do all com ponents sa tisfy the requests o f the Requ irements S pecificati on Documen t? | |
49 | X | |
50 | ||
51 | ||
52 | 3 | |
53 | Are the Us e Case Spe cification s document ed? | |
54 | X | |
55 | ||
56 | ||
57 | 4 | |
58 | Is the Int erface Con trol Docum ent comple te and cur rent? | |
59 | ||
60 | ||
61 | X | |
62 | 5 | |
63 | Are the co mponents r equired fo r the buil d identifi ed? | |
64 | X | |
65 | ||
66 | ||
67 | 6 | |
68 | Do all com ponents fo llow Produ ct Develop ment Stand ards? | |
69 | X | |
70 | ||
71 | ||
72 | 7 | |
73 | Is Product Component Testing ( aka Unit T esting) co mplete for each comp onent of t he build? | |
74 | X | |
75 | ||
76 | ||
77 | 8 | |
78 | Are the re sults of t he Product Component Testing d ocumented? | |
79 | X | |
80 | ||
81 | ||
82 | 9 | |
83 | Did Produc t Componen t Testing follow Pro duct Devel opment Sta ndards? | |
84 | X | |
85 | ||
86 | ||
87 | 10 | |
88 | Have the T est Script s been com pleted? | |
89 | ||
90 | X | |
91 | ||
92 | 11 | |
93 | Do the Tes t Scripts conform to Product D evelopment Standards ? | |
94 | X | |
95 | ||
96 | ||
97 | 12 | |
98 | Is the Mas ter Test P lan comple ted accord ing to the Test Prep aration pr ocess? | |
99 | X | |
100 | ||
101 | ||
102 | 13 | |
103 | Is Product Documenta tion avail able for t he build? | |
104 | X | |
105 | ||
106 | ||
107 | 14 | |
108 | 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 ? | |
109 | ||
110 | ||
111 | X | |
112 | 15 | |
113 | Has Compon ent Integr ation test ing been p erformed? | |
114 | X | |
115 | ||
116 | ||
117 | 16 | |
118 | Has the Co mponent In tegration Test Defec t Log been completed ? | |
119 | X | |
120 | ||
121 | ||
122 | 17 | |
123 | Has the Co mponent In tegration Test Evalu ation Summ ary been c ompleted? | |
124 | ||
125 | X | |
126 | ||
127 | 18 | |
128 | Has the Co mponent In tegration Test Execu tion Log b een comple ted? | |
129 | ||
130 | X | |
131 | ||
132 | 19 | |
133 | Has the So ftware Qua lity Assur ance Revie w Checklis t been sta rted? | |
134 | ||
135 | X | |
136 | ||
137 | ||
138 | ||
139 | Review Fin dings Summ ary Instru ctions | |
140 | ||
141 | 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. | |
142 | The Review Findings Summary co ntains the following informati on: | |
143 | ||
144 | ||
145 | Item | |
146 | Definition | |
147 | Review Typ e | |
148 | Peer Revie w or Forma l Review | |
149 | Artifact | |
150 | 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. | |
151 | Author | |
152 | The person who creat ed the wor k product under revi ew. | |
153 | Project | |
154 | The offici al project name. | |
155 | Applicatio n | |
156 | The name o f the soft ware appli cation to which this work prod uct pertai ns. | |
157 | Version | |
158 | The versio n number o f the soft ware appli cation per tinent to this work product. | |
159 | Patch | |
160 | If the sof tware is t o be relea sed via th e National Patch Mod ule, enter the patch number. | |
161 | Date Revie w Started | |
162 | The date o f the revi ew meeting . | |
163 | Date Revie w Closed | |
164 | The date a ll anomali es, issues and actio n items ar e closed. | |
165 | Identifier | |
166 | A unique i dentifier that permi ts identif ication an d sorting; suggested Project a cronym + s equential number (i. e., SUR000 1) | |
167 | Anomaly Ca tegory | |
168 | 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 | |
169 | Anomaly or Issue | |
170 | Items iden tified and described during th e review. | |
171 | Resolution | |
172 | The soluti on for the identifie d anomaly. | |
173 | Date Resol ved | |
174 | The date a n issue wa s resolved and the R eview Team agrees it was resol ved correc tly. | |
175 | Status | |
176 | 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: | |
177 | Submitted – when an item is lo gged and r eported fo r repair. | |
178 | Assigned – when an i tem is ass igned for repair. | |
179 | Opened – w hen an ano maly is as signed for correctio n. | |
180 | 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. | |
181 | Resolved - when an a nomaly is corrected and sent f or review or verific ation. | |
182 | Re-Opened – when an anomaly is closed an d then reo pened for modificati on. | |
183 | Returned - when an a nomaly is reviewed, verified a s "incorre ct", and r eturned to author. | |
184 | Verified - when an a nomaly is reviewed a nd verifie d as "corr ect". | |
185 | Closed - w hen an ano maly is su ccessfully reviewed and closed with a re solution a nd resolut ion date. | |
186 | Deferred - when an a nomaly is designated for corre ction at a later dat e. | |
187 | Duplicated – when an item is a ssessed to be a dupl icate of a prior rec ord. | |
188 | Escalated – when an item requi res evalua tion by ma nagement. | |
189 | 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. | |
190 | Impact | |
191 | 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 : | |
192 | 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 . | |
193 | 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. | |
194 | 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 . | |
195 | ||
196 | Review Fin dings Summ ary | |
197 | Artifact: Author: P roject: | |
198 | Applicatio n: Version : Patch: D ate Review Begun: Da te Review Closed: | |
199 | ||
200 | Project ac ronym-numb er | |
201 | ||
202 | Anomaly Ca tegory | |
203 | ||
204 | Anomaly or Issue | |
205 | Date Resol ved | |
206 | Status | |
207 | Impact | |
208 | ||
209 | ||
210 | Anomaly or Issue: | |
211 | Location: | |
212 | Resolution : | |
213 | ||
214 | ||
215 | ||
216 | ||
217 | ||
218 | Anomaly or Issue: | |
219 | Location: | |
220 | Resolution : | |
221 | ||
222 | ||
223 | ||
224 | ||
225 | ||
226 | Anomaly or Issue: | |
227 | Location: | |
228 | Resolution : | |
229 | ||
230 | ||
231 | ||
232 | ||
233 | ||
234 | Anomaly or Issue: | |
235 | Location: | |
236 | Resolution : | |
237 | ||
238 | ||
239 | ||
240 | ||
241 | ||
242 | Anomaly or Issue: | |
243 | Location: | |
244 | Resolution : | |
245 | ||
246 | ||
247 | ||
248 | ||
249 | ||
250 | ||
251 | Template R evision Hi story | |
252 | Date | |
253 | Version | |
254 | Descriptio n | |
255 | Author | |
256 | April 2014 | |
257 | 1.4 | |
258 | Converted to MS Offi ce 2007-20 10 format | |
259 | Process Ma nagement | |
260 | October 20 11 | |
261 | 1.3 | |
262 | Updated fo rmatting t o current ProPath do cumentatio n standard s | |
263 | Process Ma nagement | |
264 | June 2011 | |
265 | 1.2 | |
266 | Changed OE D to Produ ct Develop ment, wher e applicab le, and ch anged test plan to m aster test plan | |
267 | Process Ma nagement | |
268 | July 2010 | |
269 | 1.1 | |
270 | Changed So ftware to System in item 1 | |
271 | Process Ma nagement | |
272 | June 2009 | |
273 | 1.0 | |
274 | Initial Ve rsion | |
275 | Process Ma nagement |
Araxis Merge (but not the data content of this report) is Copyright © 1993-2016 Araxis Ltd (www.araxis.com). All rights reserved.