l.EDT 620551 JAN 1 7 1997 ENGINEERING DATA TRANSMITTAL

2. To: (Receiving Organization) 3 . From: (Or ig ina t ing Organization) 4 . Related ED1 No.: WRAP 1 Engineer ing WRAP 1 Engineering N/A 5. Proj. /Prog./Dept. /Div.: 6. Design Authority/ Design AgentKag. 7. Purchase Order NO.:

Org code 32620 J. R. Weidert N/A Engr.:

8. Or ig ina tor Remrks: 9 . Equip./Companent NO.:

approval. 10. System/BLdg./Facil i ty:

11. Receiver Remarks: 11A. Design Baseline Document? [ ] Yes [ X I NO 12. Major Assm. Dug. No.:

DMS Release 2 Q u a l i t y Assurance Plan f o r rev iew and WRAP 1 DMS

DMS/2336W/WRAP 1

N/A 13. P e r m i t p e r m i t Appl ica t ion NO.:

I 14. Required Response Date:

15. DATA TRANSMITTED (F ) (G) ( H ) ( I ) Approval Reason Origi- Recsiv

Desio. nstDr e, lAl IC1 ID1

NO. NO NO. natoi Trans- Disoa- Disno- Item IEl Title or Description of Data

Transmined IBI DocumentlDrawing No.

I I I 1 1 HNF-SD-W026-QAPP- I I 0 I DMS QA Plan

I -- 16 KEY

Approval Designator IF) Reason lor Transmittal I G i Oisposition IHI & ill

E. S. Q, 0 or NiA 1 . Approval 4 Review 1 Approved 4. Rsviewed nolcomment lsee WHC-CM-3-5. 2 . Release 5. Posf-Review 2 Appmvsd Wlcomment 5 Reviewed wlcomment Sec.12 71 3 Information 6 . Diet. (Rs~eipf Acknaw Required) 3. Disapproved wlcomment 6 Receipt acknowledged

17 SlGNATURElOlSTRlBUTlON (See Approval Designator for requmed .ignaluresl

[I Approved u/comnents

BD-7400-172-2 ( 0 5 / 9 6 ) GEF097

@ HNF-SD-W026-QAPP-002, Rev. 0

DMS Release 2 Quality Assurance (QA) Plan

J . R . Weidert Rust Federal Serv ices o f Hanford Inc . , Richland, WA 99352 U.S. Department o f Energy Contract DE-AC06-87RL10930

EDT/ECN: 620551 UC : Org Code: 32620 Charge Code: A4033 B&R Code: To ta l Pages: 6

Key Words: DMS, QA Plan, Data Management System, Release 2

Abs t rac t : Th i s document de f i nes the QA a c t i v i t i e s t h a t w i l l be pursued d u r i n g t h e development o f t he WRAP 1 DMS Release 2 sof tware.

Orac le i s a trademark of Oracle Corporat ion FedEx i s a trademark o f Ferdera l Exoress Corporat ion

TRADEMARK DISCLAIMER. Reference here in t o any spec i f i c c m r c i a l product, process, or serv ice by t rade name, trademark, manufacturer, o r otheruise. does not necessar i ly c o n s t i t u t e or imply i t s endorsement, r e c m n d a t i o n , or favor ing by the Uni ted States Goverment or any agency thereof or i t s con t rac to rs o r subcontractors.

P r in ted in the Uni ted States of America. To ob ta in copies o f t h i s document, contact : UHC/BCS Docunent Contro l Services, P.O. Box 1970, Mai ls top H6-08, Richland UA 99352, Phone (509) 372-2420; Fax (509) 376-4989.

Approved for Public Release

A-6400-073 (10/95) GEF321

DMS RELEASE 2 QUALITY ASSURANCE Manual HNF-SD-W026-QAPP-002 (QA) PLAN Revision 0

Page 1 Of4 Issue Date January 9, 1997

1.0 Purpose

This Quality Assurance (QA) Plan will be used to manage the in-process quality of the DMS Release 2 development software. QA reviews will provide an opportunity to catch and resolve programming bugs while the code is still in a state of development, rather than after the fact when rework and debug could be more time consuming and troublesome. QA reviews also provide a source of additional insights regarding the selected problem solutions and general programming efficiencies which can be reviewed by the programmer for their potential to make the delivered product better.

2.0 Software QA

2.1 Screen QA Process

2.1.1 General

Screen "source code" is considered lo be the necessary combination of ORACLE*FORMS 4.5 code and associated stored procedures, triggers, etc which combine to make a screen function as specified.

All screen source code will undergo QA review by a "third party" ORACLE programmer. Comments received from the QA review will be addressed during revisions to the development copy of the source code. Once this is completed, the screen will be considered ready for user functional testing as part of the related module testing sequence (see the DMS Release 2 Test Plan).

A separate BDM office will be used to perform QA Reviews. The INTERNET will be used to transmit source code to that office and to receive QA comments.

Software undergoing the QA process will be managed within the guidelines of the DMS Configuration Management Plan. A QA directory will be used to store all software while it is undergoing QA review.

~~

DMS RELEASE 2 QUALITY ASSURANCE Manual HNF-SD-W026-QAPP-002 (QA) PLAN Revision 0

Page 2 O f 4 Issue Date January 9, 1997

2.1.2 Review Steps

ACTIVITY

Programmer completes screen and programmer level testing

Source code tile is placed in QA directory

Snurce code tile is attachzd to INTERNET message for transmission

Latest copy of specs and any other pertinent information is sent to QA reviewer by either FEDEX nr INTERNET message

Comments received from QA review

Correction.. completed

MANAGEMENT CONTROL

Tech Lead approvcs for transfer to QA review

~~

CMiQA manager asslimes CM control (11 version

CMiQA inanager is provided copy of transmission message

CMiQA manager will prnvide FEDEX sen;ice or receive copy of transmission mBSSd2e

CMiQA manager approves release of version for correction wcwk

Tech Lead verities correctiiins completed

RESULT

I ) Source code tile is placed in QA directory 2) Source code file is attached to INTERNET message fnr transmission 3) Programmer provides latest copy of specs, with mark ups 4) Tech Lead marks check off hlock nn CM check list

Source code is "frozen" until comments come hack froin QA review

Message is transmitted to QA reviewer

Specs are provided to QA TeVleWer

Source code is moved ti, development for correction wnrk

I ) Tech Lead marks check off. block on CM check list. 2) Source code is placed imder version control in the appropriate development library

2.1.3 Review Schedule

The Screen QA Schedule is attached. Programmers have these work tasks embedded in their respective portions of the Project Plan. If any change in the schedule is required, the CM/QA manager must be notified so the change can be coordinated with the QA reviewer.

DMS RELEASE 2 QUALITY ASSURANCE Manual HNF-SD-W026-QAPP-002 (QA) PLAN Revision 0

Page 3 O f 4 Issue Date Januarv 9. 1997

2.1.4 Coordination

The CM/QA manager will ensure that the following is provided for the QA reviewer:

DMS specifications DMS data base Test records (using the same 12 drums being used by the DMS developers) Updated specifications for each screen Point of contact and team coordination

2.2 Non-Screen Source Code

Source Code for DMSCOM Messages, Reports, SCRs, and any test scripts will not be sent out for "third party" review. These will undergo a combination of internal peer review and user testing which will preclude the need for formal QA review.

2.2.1 DMSCOM Messages.

DMSCOM messages are considered too interlinked with the DMS system as a whole, to be able to explain to a third party reviewer. These will be tested as an extension of integration testing with the PCS and in conjunction with other development programmers who will be interacting with the messages. The Team Technical Lead will perform QA review over any messages that do not perform properly during integration testing and will work with the message programmer to resolve noted problems.

2.2.2 Reports.

Reports are considered straight forward interactions with the data base using the ORACLE Report Writer software. These will undergo a cycle of prototype-user review-update-user test. The Team Technical Lead will work with the report programmer to resolve technical problems prior to user acceptance of the final report.

2.2.3 SCRs

SCRs will be completed, reviewed, and implemented into production within the procedures specified in the DMS Configuration Management Plan.

DMS RELEASE 2 QUALITY ASSURANCE Manual HNF-SD-W026-QAPP-002 (QA) PLAN Revision 0

Page 4 o f 4 Issue Date January 9, 1997

2.2.4 Test Scripts

Any test script code produced is considered to be "throw away" code necessary to support the associated testing cycle. It will be tested by the programmer and is not considered to need the formality of QA control.

Task Name TASK 3 . REL 2 I s 1 PRIORITY MODULES (Thru Shop Tesl)

Data Review Module I DMSSIZOI Processed Waste NDA Data Review 8. Mod

Code QA ReviewiDebug 1 -1 DMSS1202 Compacted Drum NDA Dala Review

i - Code QA ReviewiDebug !

7 DMSS1211. Verllficalion of NDA Data

Code QA ReviewlDebug 4

1 DMSS1212 Comparison of NDA Cert ika l ion &Verification Data

I Code OA ReviewlOebug 1

DMSS1231 Verification Data Review Screen

Code OA ReviewlOebug

Shipping Module

SCR #089: Screens GO2 8 904 (Task 5 Work)

Solid Waste

199G 1 Qlr 1. 1997 I Qtr2. 1997 I Qlr3.1997 1 Qlr4 .1997 I Qtr 1. 1998 I Qtr 2. 1998 1 Ofr3.1998 . I ~ D / J 1 1 I L { I A / M I J I J l n l s / O I N I D J ~ T I H ~ A ~ M I J 1 J I A ( !

2/26

2%

-4 2/11

O X

11/27 r,

111127 0%

12/17 0%

111 8] 12117

0%

1 w 12/26 0%

2/18 8 12/26 0%

18 w 1\10 0%

In 1 1/10 0%

In w 1/24 0%

1/21 0 1124 0 %

in 2r 0%

1/14 1/20 0%

1/21 1/28

0%

-

"cl: Solid Waste Rolled Up Progress - , 11/5/96

C:it;csl Task Progress Rolled Up Critical Task ~~ I

Page 1 I - __