RMIS View/Print Document Cover Sheet/67531/metadc664313/... · Westinghouse Hanford Company - Document Control Services P.O. Box 1970, Mailstop H6-08, ... content profile consisting

"" RMIS View/Print Document Cover Sheet""

This document was retrieved from the Boeing ISEARCH System.

Accession #: Dl96050351

Document #: SD-WM-CSRS-027

TitlelDesc: SYSTEM PROGRAM MGMT PLAN FOR THE TMAD CODE

A

SEP 0 5 ~ ~ ~ @ G I N E E R I N G DATA TRANSMITTAL

13. From: (Originating Organizetion) 2. To: (Rscaivinp Orpsnization)

Pegs 1 of L 1, EDT N! 7 0 0 6 8 5 4. Related EDT No.:

Dis t r ibu t ion

5. Proj.lProg.lDept.1Div.:

Approval / Release

Nuclear Analysis and Charac te r iza t ion

SH Finfrock

7. Purchase Order No.:

8. Cog. Engr.:

10. Systsm/Eldg./Facility: l------

IAI Item No.

1

I 12. Major Assm. Dwg. No.:

181 DocumantIDrewing No. (C1:pt ID' IE) Title or Description of Data Transmitted NO.

WHC-SD-WM-CSRS-027 All 0 System Program Management Plan f o r the TMAD Code

11. Receiver Remarks:

Impact Level IF1

1, 2, 3, or 4 (sea MRP 5.431

13. ParmitIPsrmit Application No.: 7

Raason for Transmittal (GI Disposition (HI & (I1

1. Approval 4. Review 1. Approved 4. Reviewed nolcommant 2. Release 5. Post-Review 2. Approved wlcomment 5. Reviewed wlcomment 3. Information 6. Dist. (Receipt Acknow. Required1 3. Disapproved wlcomment 6. Receipt acknowledged

H . Tof fer 20.

& Date

z-7 Cognizant ~ancig 'er

I 14. Required Response Data:

21. DOE APPROVAL ( i f required)

Ltr No. 0 Approved

0 Approved wicomments

0 Disapproved wicornrnenls

- IF1

Impact Level

__ -

(GI

R * W O " for

Trans- mittal

-

-

- IH)

Oripi- "ator Dispo- stion

-

16. KEY

I I

(GI (HI SlGNATURElDlSTRlBVTlON

(Sea Impact Level for rewired sianaturesl (GI (HI 17. .

iK1 Signature iL1 Data (MI MSlN

Env. T ) n I I

I n d . Rev: Rd&%$ Yh- 38

119, SH Finfrock 18.

(Jl Name IKI Signature ILI Date (MI MSlN Disp.

I I

.. ,

RELEASE AUTHORIZATION

Document Number: WHC-SD-WM-CSRS-027, Rev. 0

Document Title:

Release Date: 9/1/95

System Requirements Specification for the TMAD Code

This document was reviewed following the procedures described in WHC-CM-3-4 and is:

APPROVED FOR PUBLIC RELEASE

WHC Information Release Administration Specialist: 4

9/1/95 ”

C. WILLINGHAM

TRADEMARK D I S C L A I M E R . Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise, does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof or its contractors or subcontractors.

This report has been reproduced from the best available copy. paper copy. this report, contact:

Available in Printed in the United States of America. To obtain copies of

Westinghouse Hanford Company - Document Control Services P . O . Box 1970, Mailstop H6-08, Richland, WA 99352 Telephone: (509) 372-2420; Fax: (509) 376-4989

A-6001-400.2 ( 0 9 / 9 4 ) WEF256

SUPPORTING DOCUMENT I 1. T o t a l Pages z/ 2. T i t l e

System Program Management P l a n f o r t h e TMAD Code 5. Key Uords

Neut ron probe TMAD

3. Number 4. Rev NO.

WHC-SD-WM-CSRS-027 0 6. Author

Name: S c o t t H. F i n f r o c k

s1gnatute

Organizat ionlcharge Code 8M720 / N2546

7. Abstract

T h i s document i s i n t e n d e d t o meet, i n p a r t , t h e q u a l i t y assurance documenta t ion requ i remen ts f o r t h e development o f s o f t w a r e a s o u t l i n e d i n WHC-CM-3-10, " S o f t w a r e P r a c t i c e s . " S p e c i f i c a l l y , t h i s document w i l l s e r v e as t h e System P r o j e c t Management P l a n and t h e Systein C o n f i g u r a t i o n Management P l a n .

8. R E L E A S E STAMP

A-6L00-073 ( 0 8 / 9 L ) V E F 1 2 I

WHC-SO-WM-CSRS-027 Rev. 0

CONTENTS

1.0 INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 PURPOSE . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1 . 2 SCOPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 ~ ~~ . . . . . . ~ . . . 1 . 3 O V E R V I E W . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1 . 4 DELIVERABLES . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.5 DEFIN IT IONS . . . . . . . . . . . . . . . . . . . . . . . . . 4

2.0 PROJECT ORGANIZATION . . . . . . . . . . . . . . . . . . . . . . . . 4 2.1 PROCESSMODEL . . . . . . . . . . . . . . . . . . . . . . . . 4 2 .2 ORGANIZATIONAL STRUCTURE . . . . . . . . . . . . . . . . . . . 4 2 .3 ORGANIZATIONAL BOUNDARIES AND INTERFACES . . . . . . . . . . . 5 2 . 4 RESPONSIB IL IT IES . . . . . . . . . . . . . . . . . . . . . . . 5

3.0 MANAGERIAL PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . 5 3 . 1 MANAGEMENT OBJECTIVES AND P R I O R I T I E S . . . . . . . . . . . . . 5 3 . 2 ASSUMPTIONS. DEPENDENCIES. AND CONSTRAINTS . . . . . . . . . . 5 3.3 ACCEPTANCE CRITERIA- . . : . I . . . . . . . . . . . . . . . . 6 3 . 4 R ISK MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . 6 3 . 4 MONITORING AN0 CONTROLLING MECHANISMS . . . . . . . . . . . . 6 3 . 5 STAFFINGPLAN . . . . . . . . . . . . . . . . . . . . . . . . 6

4 . 0 TECHNICAL PROCESS . . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1 METHODS, TOOLS, AND TECHNIQUES . . . . . . . . . . . . . . . . 6 4 .2 DOCUMENTATION . . . . . . . . . . . . . . . . . . . . . . . . 7 4 . 3 SYSTEM CONFIGURATION MANAGEMENT PLAN . . . . . . . . . . . . . 7 4 . 4 ACQUISIT ION . . . . . . . . . . . . . . . . . . . . . . . . . 10 4 . 5 DATA MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . 10

5.0 WORK PACKAGES, SCHEDULE, AND BUDGET . . . . . . . . . . . . . . . . 10

6.0 VERIFICATION AND VALIDATION . . . . . . . . . . . . . . . . . . . . 11

7 . 0 REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

APPENDIX A - PROJECT PLANNING CHECKLIST . . . . . . . . . . . . . . . . . A-1

i v

1. M i 1 estones


L I S T OF FIGURES

. . . . . . . . . 3

WHC-SD-WM-CSRS-027 Rev. 0

PROJECT MANAGEMENT PLAN FOR THE TMAD CODE

1.0 INTRODUCTION

T h i s document i s i n t e n d e d t o meet, i n p a r t , t h e q u a l i t y assurance documenta t ion r e q u i r e m e n t s f o r t h e development o f s o f t w a r e as o u t l i n e d i n WHC-CM-3-10, S o f t w a r e Prac t ices . S p e c i f i c a l l y , t h i s document w i l l se rve as t h e System P r o j e c t Management P lan (SPMP) and t h e System C o n f i g u r a t i o n Management P1 an (SCMP) .

1.1 PURPOSE

The TMAD code (named f o r t a n k m o i s t u r e and anomaly d e t e r m i n a t i o n ) w i l l be used t o e v a l u a t e d a t a f rom probe ( t y p i c a l l y n e u t r o n ) scans o f waste tanks . These scans c o n s i s t o f a s e r i e s o f d a t a p o i n t s , each measured a t a d i f f e r e n t v e r t i c a l p o s i t i o n i n t h e waste. The measured d a t a w i l l be compared t o benchmark d a t a f rom computer models o f t h e response o f t h e probes t o t a n k waste. The benchmark d a t a w i l l r e p r e s e n t a range o f m o i s t u r e c o n t e n t s and anomal ies (such as a i r - o r w a t e r - f i l l e d a n n u l i a round t h e probes) as w e l l as d i f f e r e n t d e t e c t o r t y p e s . The code w i l l d e t e r m i n e wh ich benchmark model p r o v i d e s t h e c l o s e s t match t o t h e scan d a t a a t each p o i n t and w i l l make e s t i m a t e s , based on these comparisons, o f t h e m o i s t u r e c o n t e n t o f t h e waste i n t h e v i c i n i t y o f t h e probe l o c a t i o n and o f any anomal ies t h a t m i g h t be p r e s e n t .

The r e s u l t s o f t h i s code w i l l be used t o e v a l u a t e t h e m o i s t u r e c o n c e n t r a t i o n i n t h e t a n k waste a g a i n s t minimum m o i s t u r e r e q u i r e m e n t s e s t a b l i s h e d f o r t h e s a f e s t o r a g e o f f e r r o c y a n i d e and o r g a n i c watch l i s t t anks . Wh i le t h e code w i l l n o t be used t o d i r e c t l y c o n t r o l any a c t i v i t y i n v o l v i n g t h e t a n k s (eng ineers w i l l r e v i e w b o t h t h e raw d a t a and t h e code r e s u l t s ) , t h e p o t e n t i a l e x i s t s f o r i t s use t o become i n g r a i n e d t o t h e p o i n t t h a t a s e r i o u s f l aw i n t h e code c o u l d r e s u l t i n an e r roneous d e c i s i o n r e g a r d i n g t a n k maintenance o r o p e r a t i o n s . As a r e s u l t , t h e code i s deemed " q u a l i t y a f f e c t i n g " and w i l l be s u b j e c t t o t h e h i g h e r q u a l i t y assurance requ i remen ts a s s o c i a t e d w i t h t h a t d e s i g n a t i o n .

1.2 SCOPE

The end r e s u l t s o f t h i s p r o j e c t w i l l i n c l u d e t h e TMAD code, one o r more benchmark d a t a l i b r a r i e s , and a l l a s s o c i a t e d q u a l i t y assurance documenta t ion . The code w i l l accept two ( o r more) scans o f a t a n k and produce a m o i s t u r e c o n t e n t p r o f i l e c o n s i s t i n g o f t h e b e s t e s t i m a t e a t each p o i n t i n t h e scans. The code w i l l be a p p l i c a b l e t o a l l o f t h e Han fo rd S i t e waste t a n k s as w e l l as t o o t h e r media f o r wh ich scans and benchmark d a t a e x i s t .

1

7'


1.3 OVERVIEW

The sa fe maintenance, and e v e n t u a l decommissioning, o f t h e s i n g l e - s h e l l was te t a n k s i s a t t h e c o r e o f t h e H a n f o r d S i t e m i s s i o n . r e c o g n i z e d t h a t some of t h e t a n k s have l e a k e d and t h a t t h e r e i s t h e p o t e n t i a l f o r more t a n k s t o deve lop l e a k s . p r o m p t l y so t h a t e f f o r t s can be t a k e n t o m i n i m i z e t h e impac ts o f t h o s e l e a k s . A v a r i e t y o f approaches have been t r i e d i n o r d e r t o d e t e r m i n e whether a t a n k was l e a k i n g , i n c l u d i n g gamma scans o f t h e waste and n e u t r o n probe measurements i n t h e s o i l u n d e r l y i n g t h e t a n k s . These t e c h n i q u e s have been c o n s i d e r e d adequate b u t l e s s t h a n i d e a l . R e c e n t l y , concerns have been r a i s e d t h a t t h e waste, i f a l l o w e d t o d r y ou t , c o u l d b e capab le o f e x o t h e r m i c r e a c t i o n s . I n o r d e r t o ensure t h a t adequate m o i s t u r e l e v e l s wou ld be m a i n t a i n e d i n t h e t a n k s , i t has been necessary t o d e v e l o p techn iques t h a t c o u l d more a c c u r a t e l y measure t h o s e m o i s t u r e l e v e l s . T h i s has been a c o m p l i c a t e d and c h a l l e n g i n g p roposa l and many approaches were e v a l u a t e d . s e l e c t e d as one o f t h e methods f o r f u r t h e r development.

The n e u t r o n probe de te rm ines t a n k m o i s t u r e l e v e l s by c o n t i n u o u s l y e m i t t i n g n e u t r o n s i n t o t h e s u r r o u n d i n g waste and t h e n r e c o r d i n g how many o f them a r e t h e r m a l i z e d and r e f l e c t e d back t o t h e p robe . The measured response i s t h e n compared t o computer models o f t h e waste (benchmark d a t a ) t o de te rm ine t h e m o i s t u r e l e v e l t h a t wou ld produce t h e measured response. U n f o r t u n a t e l y , because o f u n c e r t a i n t i e s (anomal ies) i n t h e s t r u c t u r e and chemica l makeup o f t h e waste, t h i s method w i l l n o t i d e n t i f y a un ique s o l u t i o n b u t r a t h e r a f a m i l y o f p o s s i b l e s o l u t i o n s . c o n t e n t , two o r more scans produced b y d e t e c t o r s w i t h d i f f e r e n t m o i s t u r e responses must be used and t h e r e s u l t s c r o s s - r e f e r e n c e d . These d i f f e r e n t d e t e c t o r t y p e s a r e c r e a t e d by v a r y i n g t h e d i s t a n c e between t h e d e t e c t o r and e m i t t e r and by f i l t e r i n g o u t some o r a l l o f t h e low-energy n e u t r o n s t h a t r e t u r n t o t h e d e t e c t o r ( t h e r e b y emphas iz ing t h e h igh-energy n e u t r o n s ) .

I t has l o n g been

It i s d e s i r a b l e t o i d e n t i f y l e a k i n g t a n k s

U l t i m a t e l y t h e n e u t r o n p robe was

I n o r d e r t o o b t a i n a p r e c i s e e s t i m a t e o f t h e m o i s t u r e

Because t h e r e a r e a w ide range o f p o s s i b l e m o i s t u r e c o n t e n t s , anomal ies, and d e t e c t o r t ypes , t h e prob lem o f c r o s s - r e f e r e n c i n g and d e t e r m i n i n g t h e b e s t e s t i m a t e o f t h e m o i s t u r e c o n t e n t becomes v e r y i n v o l v e d . I t i s p o s s i b l e t o s o l v e t h i s p rob lem u s i n g c a l c u l a t o r s o r spreadsheet s o f t w a r e b u t t h e process i s v e r y t e d i o u s and c o u l d n o t be comple ted i n a t i m e l y manner. It was dec ided, t h e r e f o r e , t o deve lop a computer program t o automate t h e process .

. Work on t h i s p r o j e c t was i n i t i a t e d i n t h e f a l l o f 1984 w i t h a l l work schedu led t o be completed by September 30, 1995. E s t i m a t e d r e s o u r c e r e q u i r e m e n t s a r e 0 .5 s t a f f y e a r s .

1.4 DELIVERABLES

The p r i m a r y d e l i v e r a b l e s f o r t h i s p r o j e c t a r e t h e TMAD code i t s e l f , t h e s u b s i d e r y code LIBMAKR, t h e d a t a l i b r a r y t o be used by TMAD, a r e p o r t d e s c r i b i n g t h e r e s u l t s o f a p r e l i m i n a r y a p p l i c a t i o n o f t h e code, and t h e r e q u i r e d q u a l i t y assurance documen ta t i on . S p e c i f i c a l l y , t h e q u a l i t y assurance documenta t ion s h a l l i n c l u d e a P r o j e c t Management P lan , a Des ign Requirements and D e s c r i p t i o n document, a T e s t i n g and V a l i d a t i o n document, and a U s e r ' s Guide.

The m a j o r m i l e s t o n e s and d e l i v e r a b l e s a r e shown i n F i g u r e 1.

2


Figure 1. Milestones.

5 6

i:

c a L

1

3


1.5 D E F I N I T I O N S

The f o l l o w i n g d e f i n i t i o n s w i l l h e l p t o unders tand t h e n e u t r o n probe measurement p rocess and t h e TMAD code.

TMAD - The name o f t h e code b e i n g deve loped i s TMAD. The name was d e r i v e d f r o m t h e ph rase " t a n k m o i s t u r e and anomaly d e t e c t i o n . "

N e u t r o n p robe - The n e u t r o n probe i s a d e v i c e c o n s i s t i n g o f a n e u t r o n e m i t t e r and a n e u t r o n d e t e c t o r . The d e v i c e i s l owered t o t h e b o t t o m o f a l i q u i d o b s e r v a t i o n w e l l and then s l o w l y r a i s e d . Wh i le i t i s b e i n g r a i s e d , i t i s c o n t i n u o u s l y e m i t t i n g n e u t r o n s . number o f n e u t r o n s p e r second r e a c h i n g t h e d e t e c t o r a r e measured.

I t t y p i c a l l y c o n s i s t s o f a s e r i e s o f p a i r s o f d a t a p o i n t s , w i t h each p a i r c o n s i s t i n g o f a d e p t h and a d e t e c t o r response.

A t p rede te rm ined i n t e r v a l s t h e

Scan - A scan i s t h e raw d a t a reco rded by t h e n e u t r o n ( o r o t h e r t y p e ) p robe

L i q u i d o b s e r v a t i o n w e l l - A l i q u i d o b s e r v a t i o n w e l l i s a p i p e , c l o s e d a t t h e bo t tom and open a t t h e t o p , t h a t has been i n s e r t e d i n t o t h e waste. I t a l l o w s probes t o be lowered i n t o t h e t a n k w i t h o u t coming i n t o d i r e c t c o n t a c t w i th t h e waste. T h i s a v o i d s t h e need t o decon tamina te t h e probe a f t e r e v e r y scan.

MCNP - MCNP i s t h e name o f t h e code t h a t w i l l be used t o model t h e d e t e c t o r response i n t h e waste tank, t h e r e b y p r o d u c i n g t h e benchmark d a t a . name i s d e r i v e d f rom t h e phrase "Monte C a r l o N - P a r t i c l e . "

The

2.0 PROJECT ORGANIZATION

T h i s s e c t i o n o u t l i n e s t h e p r o j e c t o r g a n i z a t i o n f o r t h e develoment o f t h e TMAD code.

2 .1 PROCESS MODEL

T h i s P r o j e c t Management P lan was deve loped f o l l o w i n g t h e g u i d e l i n e s o f WHC-CM-3-10 and t h e P r o j e c t Management P lan c h e c k l i s t ( see Appendix A) .

2.2 ORGANIZATIONAL STRUCTURE

T h i s p r o j e c t w i l l be c a r r i e d o u t by t h e N u c l e a r A n a l y s i s and C h a r a c t e r i z a t i o n (NAC) group. The manager o f NAC (Hans T o f f e r ) w i l l be t h e Cogn izant Manager f o r t h e p r o j e c t and w i l l be r e s p o n s i b l e f o r a s s i g n i n g s t a f f i n g and a p p r o v i n g comple ted work b e f o r e i t i s r e l e a s e d t o t h e cus tomer . S c o t t F i n f r o c k w i l l be t h e System Deve loper and t h e Code Cus tod ian f o r t h e comple ted code

4


2.3 ORGANIZATIONAL BOUNDARIES AND INTERFACES

T h i s p r o j e c t was a u t h o r i z e d and funded b y Gary Dukelow, Manager, Tank Waste Remedia t ion System S a f e t y E n g i n e e r i n g . He i s t h e customer f o r t h i s work and w i l l be r e s p o n s i b l e f o r t h e f i n a l acceptance o f t h e completed work.

A l l work on t h e p r o j e c t w i l l be conducted by s t a f f o f t h e NAC group. T h i s g roup r e p o r t s t o S a f e t y A n a l y s i s and N u c l e a r E n g i n e e r i n g . i n t e r f a c e f o r t h e p r o j e c t w i l l be w i t h t h e n e u t r o n probe development team, wh ich w i l l p r o v i d e t h e benchmark and scan d a t a t h a t t h e code w i l l o p e r a t e on. T h i s p r o j e c t i s headed b y Todd Watson, an NAC s c i e n t i s t . The t a s k o f independant r e v i e w o f t h e code documenta t ion w i l l be ass igned t o Ra lph Crowe, a member o f t h e NAC group who i s knowledgable i n b o t h t a n k waste m o i s t u r e measurement and code developement and documenta t ion b u t who i s n o t p a r t o f t h e a c t u a l code development work. Q u a l i t y assurance r e v i e w o f t h e code documenta t ion w i l l be per fo rmed by P h i l Edwards.

A p r i m a r y

2 . 4 RESPONSIBILITIES

S c o t t F i n f r o c k , a member o f t h e NAC group, w i l l be r e s p o n s i b l e f o r a l l aspec ts o f t h e code development and d e l i v e r y . Todd Watson, a l s o o f NAC, w i l l be r e s p o n s i b l e f o r d e l i v e r y o f t h e benchmark and scan d a t a r e q u i r e d f o r t e s t i n g t h e code and f o r some o f t h e a n a l y s i s o f t h e r e s u l t s o f t h e p r e l i m i n a r y a p p l i c a t i o n o f t h e code.

3.0 MANAGERIAL PROCESS

T h i s s e c t i o n d e s c r i b e s t h e manager ia l o b j e c t i v e s and requ i remen ts f o r t h e p r o j e c t .

3.1 MANAGEMENT OBJECTIVES AND PRIORITIES

The p r i m a r y management goa l f o r t h i s p r o j e c t i s t o have a f u l l y f u n t i o n i n g and t e s t e d v e r s i o n o f t h e code r e a d y f o r f i e l d a p p l i c a t i o n b y t h e end o f f i s c a l y e a r 1995. Progress on t h e p r o j e c t w i l l be m o n i t o r e d b y o r a l s t a t u s r e p o r t s a t b i w e e k l y meet ings ( a s scheduled by t h e cus tomer) i n c o n j u n c t i o n w i t h t h e n e u t r o n probe development p r o j e c t .

3.2 ASSUMPTIONS, DEPENDENCIES, AND CONSTRAINTS

The p r i m a r y assumpt ion o f t h i s p r o j e c t i s t h a t t h e d i f f e r e n t n e u t r o n probes under development , p o s s i b l y i n c o n j u n c t i o n w i t h t h e e l e c t r o - m a g n e t i c i n d u c t i o n (EMI) p robe, w i l l p r o v i d e nleasurments t h a t can be c r o s s - r e f e r e n c e d ( b y means o f t h e TMAD code) t o p r o v i d e a u n i q u e i n t e r p r e t a t i o n o f t h e m o i s t u r e c o n t e n t o f t h e waste. T h i s assumpt ion has been v a l i d a t e d t o a l a r g e e x t e n t u s i n g l a b o r a t o r y t e s t s and computer inode l ing .


The c o m p l e t i o n o f t h i s p r o j e c t depends on t h e a v a i l a b i l i t y o f a comple te benchmark d a t a s e t , a p r o j e c t t h a t i s b e i n g conducted c o n c u r r a n t l y . l e s s e r e x t e n t i t a l s o depends on t h e a v a i l a b i l i t y and r e l i a b i l i t y o f t h e a c t u a l scan da ta , wh ich i s necessary f o r v a l i d a t i n g t h e code.

To a

3 . 3 ACCEPTANCE CRITERIA

The TMAD code w i l l be t e s t e d f o r a c c e p t a b i l i t y on c o m p l e t i o n . The t e s t i n g c r i t e r i o n w i l l be i t s a b i l i t y t o rep roduce hand c a l c u l a t i o n s o f t h e waste m o i s t u r e c o n t e n t and anomaly s i z e t o t h r e e s i g n i f i c a n t d i g i t s . D e v i a t i o n s i n excess o f t h a t a r e a c c e p t a b l e o n l y i f t h e y can be shown t o be a r e s u l t o f approved changes i n t h e a l g o r i t h m f r o m what i s used f o r t h e hand c a l c u l a t i o n s . Some d i f f e r e n c e s a r e a n t i c i p a t e d a s t h e code w i l l use a second o r d e r c u r v e f i t w h i l e t h e hand c a l c u l a t i o n s use l i n e a r i n t e r p o l a t i o n . The acceptance c r i t e r i o n must be met f o r sample p o i n t s r e p r e s e n t i n g 0.0, 5.0, 10.0, 20.0, and 50.0 p e r c e n t m o i s t u r e c o n t e n t . I n a d d i t i o n , t e s t i n g must be per fo rmed on one p o i n t f rom a c t u a l scan d a t a .

3 . 4 RISK MANAGEMENT

On ly one s i g n i f i c a n t r i s k f a c t o r has been i d e n t i f i e d f o r t h i s p r o j e c t : t h e c o m p l e t i o n o f t h e necessary documenta t ion . Because code development i s schedu led t o c o n t i n u e i n t o J u l y o f 1995, t h e r e w i l l be o n l y two months a t t h e end o f t h e p r o j e c t i n wh ich t o comple te a l l necessary documen ta t i on and r e v i e w s . C o n s i d e r a b l e a t t e n t i o n w i l l need t o be g i v e n t o t h i s t a s k i n o r d e r t o a v o i d i m p a c t i n g t h e p r o j e c t ' s c o m p l e t i o n d a t e .

3 . 4 MONITORING AND CONTROLLING MECHANISMS

The p r i m a r y m o n i t o r i n g and r e p o r t i n g mechanism f o r t h i s p r o j e c t w i l l be t h e ( a p p r o x i m a t e l y ) b i w e e k l y meet ings conducted by t h e cus tomer f o r t r a c k i n g p r o g r e s s on t h e n e u t r o n probe development. r e p o r t s w i l l be p resen ted and compared t o t h e m i l e s t o n e s p r e s e n t e d i n t h i s document. r e v i e w s o f t h e code and i t s a s s o c i a t e d q u a l i t y assurance documen ta t i on .

A t t h e s e mee t ings o r a l s t a t u s

Adherence t o t h i s p r o j e c t p l a n w i l l be t r a c k e d t h r o u g h independant

3.5 STAFFING PLAN

T h i s p r o j e c t r e q u i r e s one person, w o r k i n g a p p r o x i m a t e l y h a l f - t i m e , f o r a p p r o x i m a t e l y one y e a r . development and f a m i l i a r w i t h t h e p r i n c i p l e s o f t h e n e u t r o n probe.

The person needs t o be exper ienced w i t h s o f t w a r e

4.0 TECHNICAL PROCESS

4.1 METHODS, TOOLS, AND TECHNIQUES

The f o l l o w i n g methods, t o o l s , and techn iques have been s p e c i f i e d f o r t h i s p r o j e c t .

6


. The code w i l l

The code w i l l language, u s i n g good programming p r a c t i c e s .

w o r k s t a t i o n , however, machine dependencies w i l l be avo ided t o t h e e x t e n t p o s s i b l e .

be deve loped u s i n g t h e WHC-CM-3-10 l i f e c y c l e model.

be w r i t t e n u s i n g t h e F o r t r a n computer programming

. The t a r g e t p l a t f o r m w i l l be a S i l i c o n G r a p h i c s I n c o r p o r a t e d ( S G I )

.

4.2 DOCUMENTATION

The f o l l o w i n g documents w i l l be produced f o r t h i s p r o j e c t :

P r o j e c t Management Plan

Sof tware Requirements S p e c i f i c a t i o n and Des ign D e s c r i p t i o n

U s e r ' s Guide.

So f tware V e r i f i c a t i o n and V a l i d a t i o n Repor t

These documents w i l l be r e l e a s e d as S u p p o r t i n g Documents ( S D ' s ) and each w i l l be s u b j e c t t o independant r e v i e w and Q u a l i t y Assurance a p p r o v a l . Crowe o f t h e NAC group w i l l se rve as t h e independant r e v i e w e r .

Ralph

4.3 SYSTEM CONFIGURATION MANAGEMENT PLAN

T h i s s e c t i o n p r o v i d e s t h e Code Management Procedures t h a t w i l l be used t o m a i n t a i n t h e TMAD code. These procedures have been deve loped i n accordance w i t h WHC-CM-3-10 and a r e i n tended t o ensure t h a t a l l use rs a r e access ing t h e a p p r o p r i a t e v e r s i o n o f t h e code, no u n a u t h o r i z e d changes a r e made i n t h e code, and a h i s t o r i c a l r e c o r d i s m a i n t a i n e d o f a l l v e r s i o n s ( i n c l u d i n g superseded v e r s i o n s ) o f t h e code. T h i s p l a n w i l l be p u t i n p l a c e b e f o r e t h e r e l e a s e of t h e code f o r i n s t a l l a t i o n and o p e r a t i o n a l use.

4.3.1 C o n f i g u r a t i o n I d e n t i f i c a t i o n

C o n f i g u r a t i o n c o n t r o l i s necessary t o ensure t h a t t h e c o r r e c t v e r s i o n o f t h e code i s b e i n g used. I t a l s o p r o v i d e s t r a c e a b i l i t y i n t h e e v e n t t h a t an e r r o r i s f ound i n t h e code.

The i n i t i a l r e l e a s e o f t h e code s h a l l be i d e n t i f i e d as v e r s i o n 1.0, where t h e ' 1 ' i s t h e ma jo r r e v i s i o n number and t h e ' 0 ' i s t h e m ino r r e v i s i o n number. There s h a l l a l s o be a r e l e a s e d a t e a s s o c i a t e d w i t h t h e v e r s i o n number. The v e r s i o n number and t h e r e l e a s e d a t e s h a l l be c l e a r l y shown i n t h e t e x t o f t h e code, i n t h e i n t e r a c t i v e o u t p u t o f t h e code, and i n any o u t p u t f i l e s produced by t h e code.


Any change i n t h e code, no m a t t e r how m i n o r , must be accompanied by a new v e r s i o n number. The new v e r s i o n number s h a l l be e s t a b l i s h e d i n one o f two ways: (1) e i t h e r t h e m ino r r e v i s i o n number w i l l be i nc remen ted by 1 o r ( 2 ) t h e m a j o r r e v i s i o n number w i l l be i nc remen ted by 1 and t h e m i n o r r e v i s i o n number w i l l be s e t t o 0. The Code Cus tod ian s h a l l d e c i d e wh ich method t o use, b u t t y p i c a l l y t h e second method i s used when t h e m o d i f i c a t i o n s u b s t a n t i a l l y changes t h e f u n c t i o n a l i t y , t h e o r e t i c a l f o u n d a t i o n , o r use o f t h e code. Any o t h e r m o d i f i c a t i o n would use t h e f i r s t method.

4.3.2 C o n f i g u r a t i o n C o n t r o l

A l l aspec ts o f c o n f i g u r a t i o n c o n t r o l w i l l be t h e r e s p o n s i b i l i t y o f t h e Code Cus tod ian . The Code Custod ian a l o n e w i l l have change c o n t r o l a u t h o r i t y and w i l l be r e s p o n s i b l e f o r r e c e i v i n g , p r o c e s s i n g , app rov ing , and r e c o r d i n g change r e q u e s t s . m e e t i n g t h e system requ i remen ts as s p e c i f i e d i n t h e System Requirements and Des ign D e s c r i p t i o n document, t h e change must be approved by t h e Cogn izant Ma.nager and t h e Customer. r e p o r t . A l l change r e q u e s t s and p rob lem r e p o r t s shou ld be made d i r e c t l y t o t h e code c u s t o d i a n .

I n t h e even t t h a t t h e change w i l l r e s u l t i n t h e code n o t

Any use r may i n i t i a t e a change r e q u e s t o r p rob lem

Every a c t i o n by t h e Code Cus tod ian t h a t d i r e c t l y a f f e c t s t h e code s h a l l be r e c o r d e d i n t h e Code Logbook i n t h e fo rm o f a l e t t e r , t y p i c a l l y f r o m t h e Code Cus tod ian t o t h e Cogn izant Manager. Such a c t i o n s i n c l u d e ( b u t a r e n o t l i m i t e d t o ) a s s i g n i n g a new Code Cus tod ian , chang ing t h e l o c a t i o n o f c o n t r o l l e d f i l e s , changing t h e code i t s e l f , and chang ing t h e code documen ta t i on .

I f a change i s made i n t h e code o r i n t h e computer system on wh ich i t i s implemented (such as an o p e r a t i n g system upgrade) r e q u i r i n g t h e code t o be recomp i led , t h e n a p r e c u r s o r y code v e r i f i c a t i o n t e s t s h a l l be pe r fo rmed ( a s d e f i n e d i n t h e System V e r i f i c a t i o n and V a l i d a t i o n R e p o r t ) . The r e s u l t s o f t h i s t e s t s h a l l be documented i n t h e logbook. I f t h e r e s u l t s show a change o f g r e a t e r t h a n 10% o v e r t h e p r e v i o u s r e s u l t f o r t h e same t e s t , t h e n i t w i l l be necessary t o p e r f o r m a comple te r e v a l i d a t i o n o f t h e code (as d e f i n e d i n t h e System V e r i f i c a t i o n and V a l i d a t i o n R e p o r t ) . T h i s w i l l r e q u i r e t h a t t h e System V e r i f i c a t i o n and V a l i d a t i o n Repor t be r e i s s u e d .

. A n y t i m e a new v e r s i o n o f t h e code i s r e l e a s e d t h e Code Cus tod ian s h a l l document t h e changes a s s o c i a t e d w i t h i t . T h i s c o u l d be a s s i m p l e as a s i n g l e l e t t e r r e p o r t i n c l u d e d i n t h e logbook. o r a s c o m p l i c a t e d as a comple te r e v i s i o n o f a l l o f t h e code documents. Any documenta t ion t h a t becomes i n a c c u r a t e o r i n s u f f i c i e n t f o r r e g u l a r use o f t h e code, a s a r e s u l t o f changes t o t h e code, must be updated. The Code Cus tod ian s h a l l d e t e r m i n e t h e degree and n a t u r e o f documenta t ion r e q u i r e d t o accot i ip l ish t h i s . I n any event , t h e u s e r s s h a l l be i n fo rmed o f any changes i n t h e usage o f t h e code o r i n t e r p r e t a t i o n o f code r e s u l t s . The u s e r s s h a l l a l s o be i n f o r m e d any t i m e t h e r e i s a r e v i s i o n t o one o f t h e f o l l o w i n g documents:

. System Requirements S p e c i f i c a t i o n and Des ign D e s c r i p t i o n . V e r i f i c a t i o n and V a l i d a t i o n Repor t . U s e r ' s Manual

a


An e l e c t r o n i c copy o f t h e source code s h a l l be m a i n t a i n e d f o r each v e r s i o n o f t h e code. manner as t h e source code f o r t h e c u r r e n t v e r s i o n , as d e s c r i b e d i n S e c t i o n s 4 .3 .5 and 4.3.6.

These f i l e s s h a l l be m a i n t a i n e d i n t h e same p l a c e and

4.3.3 C o n f i g u r a t i o n S t a t u s Accoun t ing

Any r e l e a s e o f a new v e r s i o n o f t h e code must be documented i n t h e logbook. T h i s must i n c l u d e t h e v e r s i o n number, t h e d a t e o f r e l e a s e , t h e document number ( w i t h r e v i s i o n number s p e c i f i e d ) o f t h e c u r r e n t v e r s i o n o f each o f t h e Q u a l i t y Assurance documents, a b r i e f d e s c r i p t i o n o f t h e changes, and a l i s t o f any Change Requests o r Problem R e p o r t s t h a t went i n t o t h e new v e r s i o n .

4.3.4 A u d i t s and Reviews

When i t i s necessary t o r e - r e l e a s e one o f t h e q u a l i t y assurance documents a s s o c i a t e d w i t h t h i s p r o j e c t , t h a t document m u s t a g a i n go t h r o u g h independant r e v i e w and q u a l i t y assurance approva l .

4.3.5 Access C o n t r o l

The source code f i l e s s h a l l be i n e l e c t r o n i c f o r m a t and t h e l o c a t i o n o f t h e f i l e must be documented i n t h e code logbook. I f p o s s i b l e , t h e f i l e shou ld have access c o n t r o l l i m i t e d t o t h e Code Cus tod ian (and System A d m i n i s t r a t o r s o f t h e system t h e f i l e i s s t o r e d on i f a p p l i c a b l e ) . To p r e v e n t u n a u t h o r i z e d e x e c u t a b l e s f rom b e i n g c r e a t e d , t h e source code s h a l l n o t be d i s t r i b u t e d o r r e l e a s e d i n e l e c t r o n i c fo rm. Excep t ions t o t h i s r u l e may be a u t h o r i z e d by t h e Cogn izant Manager. s p e c i f i c i n d i v i d u a l s , as needed, b u t t h i s i s d i s c o u r a g e d . I f a u s e r needs t o know d e t a i l s o f a code, a r e q u e s t shou ld be made t o t h e Code Cus tod ian .

Hard c o p i e s o f t h e source code may be d i s t r i b u t e d t o

The e x e c u t a b l e f i l e s h a l l be s t o r e d i n t h e same manner as t h e source code f i l e , excep t t h a t i t must have access l i m i t s a l l o w i n g i t t o be executed by t h e u s e r s . Only t h e Code Cus tod ian (and system a d m i n i s t r a t o r s o f t h e system t h e f i l e i s s t o r e d on i f a p p l i c a b l e ) shou ld have w r i t e access t o t h e f i l e .(if p o s s i b l e ) . The same peop le s h o u l d a l s o be t h e o n l y ones t o have read access t o t h e f i l e ( t o p r e v e n t t h e p r o p a g a t i o n o f c o p i e s o f t h e e x e c u t a b l e ) . It may be necessary , however, because o f system l i m i t a t i o n s , t o g i v e t h e use rs r e a d access. I f t h i s i s t h e case, t h e o p e r a t i n g p rocedures g i v e n t o t h e use rs s h a l l s t a t e t h a t t h e u s e r s h a l l o n l y copy t h e code i f necessa ry t o execute i t and t h e copy s h a l l be d e l e t e d immed ia te l y a f t e r use .

The d a t a l i b r a r i e s s h a l l be s t o r e d i n t h e same manner a s t h e e x e c u t a b l e excep t t h a t i t i s necessary f o r t h e u s e r s t o have r e a d access t o t h e d a t a l i b r a r i e s . The o p e r a t i n g procedures g i v e n t o t h e u s e r s s h a l l s t a t e t h a t t h e u s e r s h a l l o n l y access t h e i d e n t i f i e d d a t a l i b r a r y f i l e s and s h a l l n o t make any copy o f t hose f i l e s .

9


The Code Custod ian s h a l l e s t a b l i s h and m a i n t a i n a l i s t o f q u a l i f i e d u s e r s . T h i s i s necessary so t h a t t h e Code C u s t o d i a n w i l l know who t o c o n t a c t i n t h e e v e n t t h e r e i s a change t o t h e code. and d a t a f i l e s shou ld be l i m i t e d t o t h e s e u s e r s i f p o s s i b l e .

A l s o , access t o t h e e x e c u t a b l e

On some computer systems i t may n o t be p o s s i b l e t o s t r i c t l y l i m i t access, b u t s t e p s can be t a k e n t o p r e v e n t i n a d v e r t e n t u n a u t h o r i z e d access. i s recommended t h a t a s c r i p t f i l e be c r e a t e d and t h e u s e r s i n s t r u c t e d t o run t h i s r a t h e r t h a n r u n n i n g t h e e x e c u t a b l e f i l e d i r e c t l y . When t h e s c r i p t f i l e i s run i t w i l l check t h e u s e r ' s name a g a i n s t t h e l i s t o f q u a l i f i e d u s e r s . I f t h e name i s found, t h e s c r i p t f i l e w i l l r u n t h e e x e c u t a b l e f i l e . O the rw ise a message w i l l be p r i n t e d i n s t r u c t i n g t h e u s e r on how t o g a i n access. The minimum q u a l i f i c a t i o n s f o r u s e r s s h a l l be approved by t h e Cogn izant Manager and r e c o r d e d i n t h e code logbook.

It

4.3.6 Backup and Recovery

A l l o f t h e f i l e s i d e n t i f i e d i n S e c t i o n 4 . 3 . 5 s h a l l be backed up. Backup s h a l l be accompl ished by m a i n t a i n i n g a s e p e r a t e copy o f each f i l e . l o c a t i o n o f t h e backup copy s h a l l be i d e n t i f i e d i n t h e code logbook. backup copy may n o t r e s i d e on t h e same p h y s i c a l computer system as t h e p r i m a r y copy. I f p o s s i b l e , access t o t h e backup copy s h o u l d be l i m i t e d t o t h e Code C u s t o d i a n (and System A d m i n i s t r a t o r s o f t h e system t h e f i l e i s s t o r e d on i f a p p l i c a b l e ) . A h a r d copy o f t h e c u r r e n t v e r s i o n o f t h e source code must be m a i n t a i n e d and t h e l o c a t i o n i d e n t i f i e d i n t h e logbook.

I n t h e e v e n t t h a t one o f t h e c o p i e s o f t h e f i l e s i d e n t i f i e d i n S e c t i o n 4 . 3 . 5 i s d e s t r o y e d o r c o r r u p t e d , r e c o v e r y s h a l l be accompl ished by t h e code c u s t o d i a n i m m e d i a t e l y making a d u p l i c a t e o f t h e s u r v i v i n g copy and s t o r i n g i t as s p e c i f i e d i n t h e p r e c e d i n g paragraph.

The The

I f t h e e x e c u t a b l e was d e s t r o y e d then, a f t e r r e p l a c i n g t h e f i l e w i t h a copy o f t h e backup f i l e , t h e code c u s t o d i a n s h a l l p e r f o r m a p r e c u r s o r y code v e r i f i c a t i o n t e s t as d e s c r i b e d i n S e c t i o n 4 . 3 . 2 . Once t h e t e s t has been completed, a l l r e g i s t e r e d u s e r s s h a l l be n o t i f i e d o f t h e e v e n t and t h e r e c o v e r y .

4.4 ACQUISITION

No a c q u i s i t i o n s a r e p lanned f o r t h i s p r o j e c t

4.5 DATA MANAGEMENT

No s i t e w i d e d a t a management i s s u e s o r s t r a t e g i e s have been i d e n t i f i e d as b e i n g i m p o r t a n t f o r t h i s p r o j e c t o t h e r t h a n c o n f i g u r a t i o n and access c o n t r o l (see S e c t i o n 4 . 3 ) .

5.0 WORK PACKAGES, SCHEDULE, AND BUDGET

The r e s o u r c e requ i rements f o r t h i s p r o j e c t a r e d e s c r i b e d i n S e c t i o n 3 .6 .

10


6.0 VERIFICATION AND VALIDATION

The v e r i f i c a t i o n and v a l i d a t i o n t a s k s a s s o c i a t e d w i t h t h i s p r o j e c t a r e d e s c r i b e d i n t h e V e r i f i c a t i o n and V a l i d a t i o n Repor t .

7.0 REFERENCES

WHC-CM-3-10, Sof tware P r a c t i c e s , Westinghouse Hanford Company, R i c h l a n d , Washington.

11


APPENDIX A

PROJECT PLANNING CHECKLIST

A- 1


APPENDIX A - PROJECT PLANNING CHECKLIST

PLANNED Y E S NO NA COMMENT

1.0 CONCEPT PHASE 1.1 Tasks Work a u t h o r i z a t i o n i d e n t i f i e d C a p i t a l f u n d s requ i remen ts i d e n t i f i e d Data A d m i n i s t r a t i o n C o u n c i l e a r l y n o t i f i c a t i o n S i t e Statement o f S t r a t e g y i n p u t p r e p a r e d Approval requ i remen ts o f documents de te rm ined System concept p repared Acceptance c r i t e r i a o b t a i n e d DOE s i t e s surveyed f o r s u i t a b l e s o l u t i o n V&V concept phase a c t i v i t i e s per fo rmed P r o j e c t f i l e and i s s u e l o g i n i t i a t e d 1.2 Reviews D a t a A d m i n i s t r a t i o n C o u n c i l concept r e v i e w System concept r e v i e w RL MIS Board r e v i e w 1.3 P r o d u c t s System concept documenta t ion

2.0 REQUIREMENTS DEFINITION 2 .1 Tasks P r o j e c t management p l a n p r e p a r e d System requ i remen ts s p e c i f i c a t i o n p r e p a r e d System v e r i f i c a t i o n and v a l i d a t i o n p l a n prepared Approval r e q u i r e m e n t s o f documents de te rm ined Bus iness process , d a t a , and event model p repared Request f o r i n f o r m a t i o n prepared 2.2 Reviews P r o j e c t management p l a n r e v i e w System r e q u i r e m e n t s s p e c i f i c a t i o n r e v i e w System v e r i f i c a t i o n and v a l i d a t i o n p i a n r e v i e w 2.3 P r o d u c t s P r o j e c t management p l a n System requ i remen ts s p e c i f i c a t i o n System v e r i f i c a t i o n and v a l i d a t i o n o l a n Request f o r i n f o r m a t i o n Computer S e c u r i t y E v a l u a t i o n f o r m h - - -

A-2


PLANNED YES NO NA COMMENT

3.0 REQUIREMENTS ANALYSIS 3.1 Tasks System requirements specification analysis Additional software requirements documented Acceptance criteria prepared Conceptual design prepared ADP a c q u i s i t i o n / i m p l e r n e n t a t i o n plan started Change control authority documented Cost and schedule estimate for remainder

o f project requested or prepared Project management plan update

- Cost and schedule refined Data dictionary updated Staff members qualifications documented Staff members training needs identified V & V requirements phase activities performed Test plan prepared (system and acceptance) Project file and issue log updated 3 . 2 Reviews Project management plan review System requirements specification review Conceptual design/alternatives review Data Administration Council requirements review 3 . 3 Products System requirements specifications Alternatives analysis documentation Acceptance criteria Test plan (system and acceptance) User documentation Project management plan updated Data dictionary refined

4.0 PRELIMINARY DESIGN 4.1 Tasks Approval requirements of documents determined Logical process and logical data model prepared Avail able software and hardware determined ADP software and hardware acquisition plan

Preliminary design description prepared RFP prepared Request for Proposal submitted to I R M

Ac q u i s i t i on P 1 ann i n y /Sit 1) p o i" t Project management p l a n updated

- Cost and schedule refined Computer Security Evaluation form updated

when appropriate

completed and submitted for processing

X X X X

- - - -

X X X

- - -

X X X X

__ - - -

A-3



4 . 2 Reviews RL M I S Board r e v i e w P r e l i m i n a r y d e s i g n r e v i e w RFP r e v i e w P r o j e c t management p l a n r e v i e w 4.3 Produc ts ADP acquisition/implementation p l a n P r e l i m i n a r y d e s i g n d e s c r i p t i o n P r e l i m i n a r y d e s i g n r e v i e w r e c o r d s RFP P r o j e c t management p l a n (updated) Computer S e c u r i t y E v a l u a t i o n f o r m (upda ted )

5.0 DETAIL DESIGN 5.1 Tasks Approva l r e q u i r e m e n t s o f documents de te rm ined D e t a i l d e s i g n d e s c r i p t i o n p repared P h y s i c a l p rocess & p h y s i c a l d a t a model

S i t e d a t a d i c t i o n a r y updated System database r e g i s t e r e d w i t h Data

T e s t p l a n updated (component and i n t e g r a t i o n ) Manual fo rms and e l e c t r o n i c f o r m s p repared O p e r a t i o n s ( p r o d u c t i o n ) c r i t e r i a e s t a b l i s h e d T e s t d e s i g n p repared (component, i n t e g r a t i o n ,

system, and acceptance) Convers ion s p e c i f i c a t i o n s p repared P r o j e c t management p l a n updated

- Cost and schedu le r e f i n e d User t r a i n i n g p l a n n i n g p repared Company p o l i c i e s and procedures changes

C a p i t a l f u n d i n g r e q u i r e m e n t s r e v i s e d V & V d e s i g n phase a c t i v i t i e s per fo rmed P r o j e c t f i l e and i s s u e l o g updated 5.2 Reviews System d e t a i l d e s i g n r e v i e w D e t a i l d e s i g n r e v i e w Data A d m i n i s t r a t i o n Counc i l d e s i g n review T e s t p l a n s and t e s t d e s i g n r e v i e w

p repared

Standards and A d m i n i s t r a t i o n

i d e n t i f i e d

X - - -


P L A N N E D YES NO N A COMMENT

5.3 Products

X X X

X

X

System detail design description - - - Design review records - - - Physical data model and physical process model - - - Conversion specifications - - - Test plan and test design

User documentation (updated) - - -

X - - -

X - - - Training plan

6 .0 IMPLEMENTATION PHASE 6 . 1 Tasks Approval requirements o f documents determined Software programming Software walkthroughs Test cases prepared (component, integration,

Test procedures prepared (component, integration,

Software components released to test Test execution (component) Conversion software coded and tested Operation and maintenance documentation

V & V implementation phase activities performed Project file and issue log updated 6.2 Reviews User documentation review Code walkthroughs Test cases and procedures review 6.3 Products Software components Conversion software Test case and procedures documentation

(component, integration, system) User documentation (updated) Operation and maintenance documentation Training materials User procedures

system, and acceptance)

and system)

prepared

X X - -

X -

X X X

- - -

X -

X - __

X __

__ X X

__ -

A- 5


PLANNED Y E S NO NA COMMENT

7.0 INTEGRATION AND SYSTEM TESTING 7.1 Tasks Approva l r e q u i r e m e n t s o f documents de te rm ined I s s u e l o g i t e m s r e s o l v e d T e s t p rocedures p repared (acceptance) So f tware r e l e a s e d f o r t e s t i n g System c o n f i g u r a t i o n management p l a n p repared T e s t e x e c u t i o n ( c o n v e r s i o n s o f t w a r e ) T e s t e x e c u t i o n ( i n t e g r a t i o n ) T e s t e x e c u t i o n (sys tem) T r a i n i n g m a t e r i a l s v e r i f i e d P h y s i c a l d a t a and process models updated ADP equipment i n s t a l l e d and t e s t e d 7 .2 Reviews Acceptance t e s t p rocedures r e v i e w T e s t r e a d i n e s s r e v i e w System c o n f i g u r a t i o n management p l a n r e v i e w 7.3 Produc ts T e s t r e s u l t s ( i n t e g r a t i o n , system) T e s t p rocedures documenta t ion (acceptance) System c o n f i g u r a t i o n management p l a n

8.0 ACCEPTANCE TESTING 8.1 Tasks T e s t e x e c u t i o n (acceptance) V & V t e s t phase a c t i v i t i e s per fo rmed P r o j e c t f i l e and i s s u e l o g updated 8.2 Reviews 8.3 P roduc ts T e s t r e s u l t s (acceptance) User documenta t ion (updated) T e s t summary r e p o r t

9.0 INSTALLATION AND CHECKOUT PHASE (CERTIFICATION) 9 .1 Tasks

X X

X

System i n s t a l l e d Convers ion s o f t w a r e e x e c u t i o n Data c o n v e r s i o n v e r i f i e d System i n s t a l l a t i o n v a l i d a t e d

A- 6

WHC-SD-WI4-CSRS-027 Rev. 0

User training performed User procedures in place Initial operation runs evaluated Service level agreement for maintenance V&V installation and checkout phase activities

Software configuration control plan prepared Final V&V report prepared Project file and i s s u e l o g updated Post-Disaster Recovery plan prepared 9 .2 Reviews Instal 1 at ion review Acceptance review Data Administration Council closeout 9.3 Products Sy s tern i n s t a1 1 at i o t i package Software released for operation V&V final report Customer buy-off Project file Post-Disaster Recovery plan Software configuration control plan

performed


A- I