JR141997/2 EFUG,NEERING DATA TRANSMITTAL “ 03’7 “DT...

JR141997/2 EFUG,NEERINGDATA TRANSMITTAL “%. 1of __!_

03’7 “DT 6207892. To: (Receiving Organization) I 3. Fran: (Originating Organization) I 4. Related EDT No.:

I Distribution 1spent Nuc,[Ftjalb,a+inn<

!ar Fuel N/A.-,”,””..”!,;

5. Proj.lPrc.g .lDept.lD iv.: 6. Desi g“ Authori tyl Oesi g“ Age”tlCog, 7. Purchase Order No.:Engr.:

Spent Nuclear Fuel Project A. L. Pitner NfA8. Originator Rmrks: EcI. in. /Cmner,t No.:

Approval and Release. Aaci Litv: I

‘N/A11.Receiver Remarks: 11A. Design Baseline Oocunent? [] Yes [x] NO 12. Major AsSm. Dug. No. :

{01 DocutnentlDrawin.a No.

HNF-SD-SNF-TP-0341

OATA TRANSMITTEO (F) (G) (H)(c) (D) Approval R....” Origi.

Sheet Rev. (El litle or Dc.swiptbn of Data De ,ici. f., rut.,No. No. Tra”#,nltted “at., Trans. Disc...

nlittd .Iti.n

o TEST PLAN FOR SURFACE 2 1AND SUBSURFACE N/AEXAMINATIONS OFK EAST ANO K WESTFUEL ELEMENTS

(G) I (H, I(K) Slonatura (1) Dme (M) MS!N 1

APPr.val De.iu. ator IFI Reason for Tra”.mind (G) Disposition [H) & II)

E, S, 0, D ., WA 1. APPrczval 4 Review

(s.. WHC-CM-3-5,

1. Approved 4. Reviewed rmlcmmmt2. %1..s. 5, Post-Review 2. Aw.roved wlcmment

S.., 12.71 3. Information5. Rwiewad w/cornnw.t

6, Dkt. (Receipt Ackmw. Required) 3. Disapproved wbanmmnt 6. Rao.ipt acknowladfpd

17. SIGNATURE/D ISTRIWTlON(See Ac.c.ro.el De.ionatw for required signatures)

I

-“=

(K) Siwwum (L) Data (M) MSIN

I Desimi Authoritv

Oesi w Agmt

11 QT. Mgr. R. P. W&q HO-40 3 R. U. Stevens L1-03

3 b R3-15 3 L. A. Laurence HO-40

3 S. A. Chastai” HO-40

J . Abrefah P7- 27 k~ ~ S. J. Make... tio-40

‘;” W*19.

Y/Y/,J21. 00E APPROVAL (if requi red)

Ctrl. No.A. L. Pit..,

~; ;~~; .,cm”tsSignature of EDT Date Authorized Representative Date Design A“thoritylOriginator

[1 Oi sspproved Wccim.zntsfar Receiving Orgmmatmn CoQnizmt Manager

BD-7400 -172-2 (05196) GEF097

BD-7W172.1

. .—.-.-A . . — ~.— —-

ENGINEERING CHANGE NOTICE1.ECN (use no. frcdII p9, : )

of 2 627883 —6. Design 17. cost Inpact 18. ScheduLe lnpa.t (days)

VerificationRequired

ENGINEERING cONSTRUCT10N

[] Yes Additicmat [] $ Additiona( [] $ 1nprovement [1[x] No Savings $ Savings [] $ DC lay

9. Change Iwct Review: [ndfcate the related docunents (other than the engineering documents i dent i f fed on Side 1)that uil L be affected by the change described in BLock 13. Enter the affected documsnt &r in B Lock 20.

WD/DD [x] Seismic/Str.** Analysis [1 Tm!k Calibration Manual[1

.ncfio.al De.km Cdtd.[1

StmsslDe*i.a. Rerrwt[1

H.skh Fhysics Procedure[1

)Pe,ming Slmclficado”[1

Interface Control Drawhm[1

?-r.. MuhiP~ LJ.WLl*tiw

%tiedttv Specif**tion[1

calibration F’r.cedum[1 ‘“”t ‘Ced”’”’’’mtii””i”” i 1

>“ceptud Design Report[1

I.atallationFrcmd.re [1 Cnrnp.an.nt Index[1

iq.ipnwnt Spec.[1

Maintmmnce Fr.xedure[1

ASME Coded item[1

:O”st. Spec.[1

Engi”eedw Frooedtwa[1

Human Factor consideration[1

%Curoment SW’..[1

Omratha I..**.[1

Cwnwter software[1

demdorInformation[1

Owrtic-a Fmcedure[1

Electric Circuit Schedule[1

>h4 M.””al[1

cwmf.~m.d saf.t~ Rwiwm..t[1

lCRS Fm.ed.re[1

:sARIsAR[1

IEFD Dmwing[1

Procem Control MmIuWFfa”[1

5.fet” EmJIPrne”t List[1

Cell Armnwmmt Drawing[1

t+acese F{. w Chart[1

RadiatlmWork Permti[1

Essemtid Material Specific.ti.an[1

Purchm. Req.ieiti.a.[1

E“um.rnent.l Impact statement[1

Fat. hoc. Sanw Schedule[1

Tickler file[1

E“vironmentd RrIporl[1

ln*oecti.” u.”[1

u*.,,* ManualWHC-SD-WM-U M-03!

[x]

Envlrc.”nmntd POrmit[1

Invmtow Adjustment Request[1 [1

20. Dther Affected Oocunents: (NDTE: Docuxents I isted tel.u !di lL rwt be revised N this ECN. ) Signatures btonindicate that the signing organization has been notified of other affected kcunents (isted be(ow.

Oocunent NAr/Rev isi on Oocunent Nmberl Revi sion Doasnent NLJT&r Revi Si on

WHC-SD-WM-ATP-I75 Rev.O

21. ApprovaLs

Signature

Design Agent 14ana9erlS. G. Sterl in9/ ,.&&

cog. Eng./J. S. Jechl ~#’~~ ~

cog. Hgr.lR. L. UelS..l/,~*

QA/lA. L. Hermansenl ‘~% -P

Safety

%viron.

)ther/D. G. Hert/ ~~ y~ *

Signature‘&qJj &

Oesi w Agent/M. U. Thorntonlp

PE 1

9A

Safety

Oesign

Environ.

other

DEPARTMENT DF ENERGY

S i9iWture or a Cent rot Nui+xr thattracks the ApprOva L SiWNure

ADD1TIONAL

A-7900 -013-3 (05/%) GEF096

HNF-SD-WM-ATP-175, Rev. 2

Acceptance Test Procedure For TheMaster Equipment List (MEL) DatabaseSystem -- Phase I

M. W. ThorntonFluor Daniel NorthwestP. O. Box 1050Richland, WA 99352U.S. Department of Energy Centract DE-ACO6-87RL1O93O

EDT/ECN: -#ltX%Y627883 UC: 605Org Code: 77820 Charge Code: N12A48&R Code: EW3120071 Total Pages: M45

&d

Key Words: Acceptance Test Procedure

Abstract: Approval and release of the Acceptance Test Procedure for theMaster Equipment List (MEL) Phase I

TRADEMARK DISCLAIMER. Reference herel n to any specl f1c commercl al product, process, or

service by trade name, trademark, manufacturer, or otherwl se, does not necessarl ly

constitute or lmply Its endorsement, recormnendatlon, or favoring by the United States

Government or any agency thereof or 1ts contractors or subcontractors.

Printed 1n the United States of !merlca. To obta]n copies of thls document, contactWHC/BCS Document Control Services, P.O. Box 1970, MaI1stop H6-08, R1chland WA 99352, Phone

(509) 372-2420, Fax (509) 376-4989.

- ?.. mp~ ~o199DATE

HN4FOFID

STA.3 ~ R:L~A(jg ID

L21’

/d

Re~ase Approval ‘bate Release amp

Approved for Public Release

A-6400-073 (10/95) GEF321

RECORDOF REVISION(1) Document Number

HNF-SD-WM-ATP-175 Page 1

[2) Title

!cceptance Test Procedure (ATP) for the Master Equipment List (MEL) Database System ---’base1

CHANGE CONTROL RECORD

(3)Authorized for Release

(4) Oescrlptlon of Change Replace, Add, and OeleteRevlslon Pages (5) cog.

Engr,(6) Cog. Mgr Oate

o (7) Related EDT Number js 6118(I7 JB Jech RL Nelson

1 ECN is 627878 - Complete rewrite of Master JB Jech RL NelsonEquipment List (MEL) Database System --Phase 1

As of 1/7/97 Document Number was changed,,

from WHC-SD-WM-ATP-175 to HNF-SD-WM-ATP-175 A# AA ,/u%Ld2 R~ ECN is 627883 See Section 13a for changes JB RL Nelson ‘w’

HNF-SD-WM-ATP-175 Revision 2: Page -i

ACCEPTANCE TEST PROCEDURE

FOR THE

MASTER EQUIPMENT LIST (MEL)DATABASE SYSTEM--PHASE I

Revision 2

Prepared by:

S. G. Sterling &M. W. ThorntonData Automation Engineering & Services

Fluor Daniel Northwest

and

D. L. MarquezInfoTech West

November 1996

Prepared for:Lockfreed Martin Hanford Corporation

P.O. Box 1500Rkhland, Washlrrgton 99352

UNCLASS1FIJ2J2 HNF-SD-WM-ATP-175 Revision2: Page -ii

TABLE OF CONTENTS

SECTION PAGE

1.0

2.0

3.0

4.0

5.0

6.0

7.0

INTRODUCTION . . . . . . . . . . . . . . 1I.l purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1I.z scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.30verview . . . . . . . . . . . . . . . . . . . . . . 11.4 Deftitions, . . . . . . . . . . . . . . . . . . . 1

TESTPLAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1 TestItesns 32.2 S0ftwareVersionControl. . . . . . . . . . . . 32.3 DhisionofTests. . . . . . . . . . . . . . . . . . . . . . . 32.4FeaturestoTest/NotTest... . . . . . . . . . . . . . . . . . . . . . . . . . . 32.5 Designated Testers . . . . . . . . . . . . . . . . . . . . . 32.6 Preparation, ,., . . . . . . . . . . . . . . . . . . . . . . . . . ...42.7 DeHverabl= . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...42.8 Acceptance Criteria . . . . . . . . . . . . . . . . . . . . . 42.9 Testing Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42.10 EnvirosunentafNeeds . . . . . . . . . . . . . . . . 52.11 Respmsibfities . . . . . . . . . 52.12 Staffing, Tr-gandQuW1cations . . . . . . . . . . . . . . . . . . 52.13 RisksandContingencies. . . . . . . . . . . . . . 6

TESTDESIGN . . . . . . . . . . . . . 63.1 Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63.2P=/FtiCriteria . . . . . . . . . . . . . . . . . . . . . . . ...6

3.2.1 Data Criteria . . . . . . . . . 63.2.2 ReportFormatCnteria . . . . . . . . . . . . . . . . . . . . 7

TESTPROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

TESTPROBLEMREPORT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

ACCEPTANCETESTREPORT. . . . . . . . . . . . . . . . . . . . . . 7

REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

APPENDIXA ACCEPTANCE TEST PROCEDURE RECORD (SINGLE-USER) A-1

APPENDIXB ACCEPTANCE TEST PROCEDURE RECORD (MULTI-USER) B-1

LISTOFTABLES

Table l. OrganizationafReaponsibilities Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

YNCLASSIFIED HNF-SD-WM-ATP-175 Revision2: Page -1

ACCEPTANCE TEST PLANFOR THE

MASTER EQUfPMENT LIST (MEL) DATABASE SYSTEM

1.0 INTRODUCTION

1.1 Purpose

The Waste Remediation System/. ./Facilities Configuration Management Integration group has requesteddevelopment of a system to help resolve many of the difficulties associated with management of masterequipment list information. This project has been identified as Master Equipment List (MEL) data6ase system.Further definition is contained in the system requirements specification (SRS), reference 7.

1.2 Scope

This document satisfies the requirement for acceptance plaoning and acceptance testing as stated in theMEL Work Plan, reference 6.

After the acceptance testing has been completed, an Acceptance Test Report (ATR) describing the resultsof testing shall be issued.

1.3 Overview

This Acceptance Test Procedure (ATP) provides test plan information and defines the test procedures forthe MEL. It includes the requirements and criteria as taken from the SRS, reference 7. The ATP has beenprepared following the WHC-CM-3- 10 “Software Practices” (ref. 3) guidelines. The ATP shall serve as thetesting document to eosure the specific requirements of the MEL are met with regard to assurance of theaccuracy and quality of data managed with MEL,

1.4 Defistiona

The following are abbreviations and definition of terms used in this document:

ADDAESATPATRDOEECNEDTFDNWMELHLANLMHCOTPOTRQAPc

Approval DesignatorData Automation Engineering & Services Department/Fluor Daniel NorthwestAcceptance Test PlanAcceptance Test ReportDepartment of EnergyEngineering Change NoticeEngineering Data TransmittalFhror Daniel Northwest, Inc.Master Equipment Lkt (MEL) database systemHanford Local Area NetworkLockheed Martin Hanford CorporationOperability Test ProcedureOperability Test ReportQuality AssurancePersonal Computer

UNCLASSlFIED HNF-SD- WM-ATP- 175 Revision2: Page -2

RCR Review Comment RecordSc Safety ClassSCR Software Change RequestSRS System Requirements SpecificationTS Test Specifications

~-- The use of quality-affecting computer sOftware. prOgrams, mOdels, or other cOmputer items toperform engineering design analysis, calculation, scientific analysis, data acquisition or to operate hardware orfacilities.

~54.. -- Defined in WHC-CM-3-5, section 12.7 (Ref. 2)

~ -- A set of computer codes, procedures, roles, and associated documentation and datapertaining to the operation of computer systems. Thk includes user-provided inatmctiona and data thatimplement preprogrammed algorithms in control systems; computer codes and data that shall reside in firmware,and when specified by the cognizant mansger, user-provided irrstructiom and data used by commercial softwaresuch as spread sheet and database packages.

uter Software/Sv~ -- The documentation of essential requirements(functions, performance, design constraints and attributes) of the computer soflware and ita external interfaces.

!2atake -- A generic term referring tO the stOrage of data by a computer in a certain data structure.

~ -- Previously the project Cognizant Engineer under WHC-CM-6- 1, Standard Engineering Practices(ref. 5) and WHC-CM-3-1O, Software Practices (ref. 3.) was the lead engineer in the organization charteredwith developing the product. Implementing procedure deviation is contained in ICFKH-CM-SRM 1.2D 1,

1s. Procedures. and 1~, reference 11)

~ineerine Practices -- Documented management methods (ref. 5) which estzblish the reamer and the order forthe performance of common configuration management practices relating to engineering tasks.

~ -- Respomible engineer withhr the performing development organization that assumes DesignAgent Engineer responsibility for development of the system.

Mfetv Class -- Defined in WHC-CM-4-46 (see ref. 1.)

~ -- Documented management methods (3) which establish the reamer and the order for theperformance of common configuration management practices relating to software and systems engineerirrg tasks.

~ -- Responsible engineer delegate of the system owner, Has responsibility for the system asdefined by WHC-CM-6-1, Standard Engineering Practices, for the facility and user. Implementing proceduredeviation is contained in ICFKWCM-SRM 1.2D1, ~~ , reference 11)

Qual@ Record--A completed document that furnishes evidence of the quality of items and/or activities affectingquality.

UNCLASSIFIED HNF-SD-WM-ATP-175 Revision2: Page -3

2.0 TEST PLAN

2.1 Test Items

This ATP is designed to test the functional requirements of the MEL and to determine whether or notthey have been satisfied based on the defined Testing and Acceptance Criteria. The functional requirements canbe found in the System Requirements Specification for Master Equipment Lkt (MEL) database system (Ref. 7),Section 3.0 “SPECIFIC REQUIREMENTS”. The test criteria is contained in Section 3.6.6, “Testing andAcceptance Criteria” of the same document. The requirements and criteria have been mapped into theprocedures and test cases provided herein. Other related tests may also be performed.

2.2 Software Version Control

The software under test will be controlled. When the software is readied for acceptance testing, theversion will be recorded and released. Backups of the released software will be prepared on optical discs andstored by the DAES Manager.

It is recognized that the ATP maybe executed more than once if necessary due to the magnitude ofchanges required in the software. The version of the software will be incremented per the ConfigurationManagement Plan (ref. 9) as changes are made. Each version that undergoes acceptance testing will berecorded, released, and copied to optical disc.

Software Revision Records are signed and kept in the project files, 1200 Jadwin, Suite 16, Room 11

2.3 Division of Teata

The ATP is designed to be performed in two parts - a single-user test which emphasizes the details of thesystem fimctionality, and a multi-user test which focuses on the system’s ability to support multiple concurrentusers utilizing specific sets of functions. Some tests in these two parts will overlap by testing the same systemfunctions. The single-user test will be performed with version 1.32 of the MEL Phase L The multi-user test willbe performed on version 1.33. The version change accounts for minor updates made to correct isolatedproblems found in the single user test that will be retested in the multi-user test.

The single-user part of the ATP will be performed prior to the multi-user test with enough time betweenthem to resolve problems encountered.

2.4 Features to Teat/Not Test

Each test/test-case listed in the Acceptance Test Procedure & Record (Appendix A) identifies the Testerby the name of the Design Authority representative, or as ‘Deferred’ by that representative, or as “MultipleUsers”. Those marked by the representative’s name will be performed in the single-user part of the ATP.Those marked as “Multiple Users” will be performed in the multi-user part of the ATP. Those marked as“Deferred” will not be performed.

Deferrals are indicated where test cases will not be performed until a later version of the software.These test cases are included in the ATP for completeness. The SCR log includes a list of specific timctions thatare being deferred to future versions, and why. In general, these deferrals are the decision of the customerbased upon available time, budget, and priority of need.

2.5 Designated Testera

The single-user ATP will be performed by a Design Authority (LMHC, Facilities ConfigurationManagement Integration) representative and will be witnessed by a Design Agent (FDNW, Data Automation

UNc LASSIFIED HNF-SD-WM-ATP-175 Revision 2: Page-4

Engineering) representative. Together, these keytesters will record thetest findings. llremulti-use rtestwillbeconducted jointly bytiesame representatives witianadditional5 to 10testers selected bythe Design Authorityrepresentative. Alltesters will record test findings. The ATRwill beprepared bythe key testers.

2.6 Preparation

Testers will beprepared forexecuting the ATP. Thekeytesters, performing thesingle-user ATP, willhave considerable experience with thesofiware application as beh testers. Themulti-user ATPtesters have beentrained specifically fortheir roles infesting. Thetraining wasa4-hour session (20fthemwith6t08participants each) including written materials, hands-on experience using the pre-test version of the software.Trainees were instructed on use of the software, their roles in the test, and how to prepare problem reports.

Thetraining materials were designed tomeettie requirements of~RS Training. ATWRS Trainingrepresentative reviewed and accepted these materials for pre-release use and participated in these early trainingsessions. These modules, and the User Guide forthe MEL version 1.0, will be the basis of the User Guide forversion 2.O. Due to schedule constraints, the customer hasagreed todefer tirralpreparation of the User Guideuntil after tierelease ofversion 2.O-to reincluded ina subsequent release within thenext6 months. Thesemodules will also be the basis for the formal Training Plan and Modules currently under development.

2.7 Deliverable

The following items shall be delivered by the key testers upon completion of the acceptance testing forMEL.

1) An Acceptance Test Procedure Record

2) Any problem reports completed by the testers.

3) An Acceptance Test Report complete with the Acceptance Test Procedure Record and problemreports completed during acceptance testing.

4) Problem reports will be recorded in the Software Change Request (SCR) database established forthe MEL project.

2.8 Acceptance Criteria

All testa shall be performed according to criteria defined on the test procedure record without anyunresolved functional exceptiona. Test results shall beapproved bythe Change Control Board (CCB) defined intbe MEL Configuration Management Plan, reference 9.

2.9 Testing Taska

Hardware Se@

■ The required hardware shall be setup and available prior to the performance of the ATP,Minimum equipment is specified as a PC-compatible with 486/33 processor, 8 mb of randomaccess memory and 30 mb of free hard disk space.

Soft are Setm2w

■ All required software shall be installed per appropriate installation procedures.

UNCLASS lFIED HNF-SD-WM-ATP- 175 Revision 2: Page -5

MEL Ddabas.e

■ The databases shall be loaded only with initial master data sets so that onfy known data is in thedatabase.

■ The database and application software shall have been previously configured for the ATP teststations.

■ At completion of the ATP, all tiles shall be emptied because the data input during this test is onlytest data and has no value outside the test. The master data sets shall also be emptied and theMEL loaded with verifiable data.

2.10 Environmental Needs

The equipment needed to perform acceptance testing is as follows:

a) Configured Personal Computer (PC) workstation.

b) Attachment to the site HLAN.

c) Established user account on the server with appropriate access rights.

d) A LaserJet III or higher and paper for the printer.

e) General office supplies for testing support.

2.11 Reaponaibfitiea

Organizations involved with MEL Acceptance Testing are those listed in the Configuration ManagementPlan. reference 9.

Table 1. Organizational Responsibilities Matrix.

DESCRIPTION ESQI..I Design LeadQA Authority Engineer

1. Acceptance Test Plan 3,4 2,3,4 1,2,3,4

2. Acceptance Test 2 1,2

3. Acceptance Test Report 3,4 2,3,4 1,2,3,4

1 = Initiates2 = Provides Input3 = Reviews4 = Approves

2.12 Staftlmg, Tr-g and Qrrafifications

UNcLASSIFIED HNF.SD-WM-ATP-175 Revision 2: Page-6

Testing persomel shall be from within or a contractor to Data Automation Engineering & Services(DAES), and Plant Configuration &Drawings (PC&D). Testers shall beindependent (not involved withtheimplementation of the sub-component being tested).

The tester shall have some familiarity with the Windows environment and a minimum one yearexperience with database applicationa. This inchrdes theability tosuccessfully use windows, check boxes, menubars, etc. However, this ATPisdesigned sotesters shall need mintial training of the MEL application.

During acceptance testing, any questions that arise regarding the use of the MEL system shall beanswered as needed by the development team.

2.13 Riskamrd Contingencies

Acceptance testing shall be performed on test data in a version and data set separated from liveproduction system and data.

3.0 TEST DESIGN

3.1 Approach

This acceptance test procedure and associated acceptance test procedure record was based and istraceable tothe SRS. Foreach identifiable andtraceable requirement, there areoneor more test items, eachidentified with aTest IDnumber (e.g. T1.003) and test item description. For each test item, there are one ormore test procedures. Each test procedure hasa procedure ID and test procedure description. Also for each testitem, there areoneor more test cases. Foreach test case, there isatest case IDandtest case description. Eachtest case is tested, andthetest result @ass or fail, )date, time, andinitials oftester isplaced ontheacceptincetest procedure record.

The acceptance testing of the specific requirements for MEL is to be to the best extent possible withoutumecessary retesting. Allspecific requirements for MELareto detested.

This ATPiswritten togivethe tester flexibility inselecting test data. Anydata that isusedto test thesystem shall be documented by the tester into the test log. Thepurpose ofjournalizing test data is to ensure thesystem ismaintaining andreporting correct data. Thetester irresponsible foremuring that alldatameem tiedata requirements listed inthe requirements document. Thetester isalsoresponsible forenauring that thedatsisreported according totierequirements document fortie Master Equipment List (MEL) database system. Anydata inputs tiatcreate asystem error shall also bedocumented by the tester. This shall provide information tohelp the developmental team track the error and perform the necessary corrections.

Hold points are not defined for this test. If testing must stop due to a failure that inldbits further testing,the test can be placed on hold. The decision to restart the test from the hold point will be made by CCB basedupon the charrges made to correct the impasse.

3.2 Paas/Fail Criteria

If a particular test case meets the functional requirement, based on criteria shown or referenced, it shallpass. If a particular test case does not meet all of the functional requirement, it shall be failed. On review, theCCB may disposition any test case.

3.2.1 Data Criteria

UNcLASSIFIEQ HNF-SD- WM-ATP- 175 Revision2: Page-7

All criteria for data can be found in section 3.6.1 “Data” of the SRS for MEL (Ref. 7) and Appendix Aof the same document.

3.2.2 Report Format Criteria

All report format criteria can be found in section 3.2.4 “Report Functions” of the SRS for MEL (Ref. 7).

4.0 TEST PROCEDURES

Test procedures are specified in the acceptance test procedure record. Pass/fail, date, time, and testerinformation shall be recorded on tbe acceptance test procedure record to be provided to tbe tester. The testprocedure record shall be treated as a quality record.

5.0 TEST PROBLEM REPORT

Any test failures shall be documented on a System Change Request/Problem Report as described in theMEL Configuration Management Plan, reference9. Tbesheet shall be filled outindetail, witbthe SCR/PRnumber recorded under “test result” ontheacceptance test procedure record.

6.0 ACCEPTANCE TEST REPORT

Upon completion of the Acceptance Test and recording of the results, an Acceptance Test Report (ATR)will be prepared for review and approval. The ATR will include;

7.0

1,

2.

3.

. A summary description of the test results,

. A copy of the SCR log which will record all problems,

. Definitions of terms used in the SCR log,

. Conditions for release of the software to become version 2.0, and

. An explanation of how final exceptions will be resolved, retested, and passed.

REFERENCES

WHC-CM-4-46, Non-N~, February 1996.

WHC-CM-3-5, Document Cent 01and Records Mimagement MaIuuI.rSection 12.7, Rev.0, ''Approval of Enviromental, Safety, and Quali~Affecting Documen@'',Febmaryl, 1994.

WHC-CM-3- 10, soft are PracticuSP-3,3, Rev. ~, “Testing,’’January3l, 1993.SP-6.1, Rev.0, “DocumentControl,’’J anuary3l, 1993.SP-6.2, Rev.0, “SoftwareControl,’’J anuary31, 1993.SP-6.3, Rev.0, “ChangeRequesta ndProblemR eport,’’January31, 1993.Appendix J, Rev. O, “SystemTestDocumentation,’’J amrary3l, 1993.

UNCLASS IFIED HNF.SD-WM-ATP- 175 Revision 2: Page -8

4.

5.

6.

7,

8.

9.

10

WHC-CM-4-2, Quality Assurance [email protected], Rev. 5, “Design Control,:’ September 30, 1993.QR-19.0, Rev, 1, “Sotlware Quality Assurance Requirements, ” September 30, 1993.

WHC-CM-6-1, standard ~ Pra ctices.EP-2.2, Rev. 7, “Engineering Document Change Control”, August 5, 1994.EP-4. 1, Rev. 5, “Design Verification Requirements”, May 27, 1994.

w;c-sDy~-~Dp-012oftware Develo~ (Work Pl~-Phase I , Rev. O, J. B. Jech,

November, 1995.

wgc_sD-ti&-csR~-023Svstem Rea~n For The Master E@ument List - Phase 1,

Rev. 1, J. B. Jech, April, 1995.

W~C-SD-M-SDD-065, ~gn Description for the Master J@@mLL&, C. D. StarghiO andM. W. Thornton, Rev A, TBD.

W~-SD-~-CSCM-033 W Eaui~ment List C~, S. G. Sterling,Rev. O, March 1996 ‘

ICFKH-CM-SRM 1.2D1, Hs. Proced~, October 25, 1996.

LJNCL.4SSI FIED HNF-SD-I%?VLATP-175 Revision 2: Page -A- I

APPENDIX A ACCEPTANCE TEST PROCEDURE RECORD (SINGLE-USER)

HNF-SD-VVM-ATP-I75, Rev. 2Page A-2

Master Equipment List DatabasePhase 1

Acceptance Test Procedure & Record

Version 1.3211/21/96

Approvedfor Use J. B. Jech, Engineer (Owner’sRepresentative)

Approved:for use ~

Data AutomationEngineeringand Services, Fluor Daniel Northwest, Inc.

Approved :for Use S. G. Sterling, Manager,~

Fluor Daniel Northwest, Inc.



Requirement ID: R3.1, B3

Requirement Ref: SRS 3.1 (bullet 3), Gen Reqs (Ace Criteria #3)

Requirement Description : The MEL Phase 1 Application code shall provide comments to support futurecode changes.

HNF-SD-Wvf-ATP-175, Rev. 2Page A-3

r----Test ID: TI .001Test Item Description : MEL Phase 1 Application as a whole.

Proc ID Test Procedure Description

P1.olo Manually review and inspect the appropriate documentation.

PLO12 Eoreach test case, perform test, record test results (Pass/FaO), date tested, andmltlals of testers. Enter comments m the CommentLogsheet.

Test Case ID Test Case Description Test Result -]

[r~~fl~~~{$p~~~~$~~~de ‘Overi~readabi’iWandc’ariWofthecOmmentsthat ~fl~]~JBJEcH

Tester1

Requirement ID: R3.1, W


Requirement Description : The MEL Phase 1 Application shall have user-friendly features integratedthroughout the Db.

Master Equipment List Database HNF-SD-VV?VI-ATP-l75, Rev. 2Phase 1 Page A4


Requirement ID: R3. I B5

Requirement Ref: SRS 3.1 (bullet 5), Gen Reqs (Ace Criteria #M)

Requirement Description: The MEL Phase 1 Application shall support a multiple user and multiple taskenvironment.

Master Equipment List Database HNF-SD-WM-ATP-175, Rev. 2Phase 1 Page A-5


/ Test ID: T1 .003 ITest Item Description : MEL Phase 1 Application as a whole (supports Multiple Tasks).

Operate the application exercising appropriate functions and features.

For each test case, perform test, record test results (Logsheet.

Pass/t all), datetested, andmttjals attesters. Lntercomments m the Comment

Master Equipment List Database HNF-SD-WM-ATP-l 75, Rev. 2Phase 1 Page A6


Requirement ID: R3.I , B6


Requirement Description : The MEL Phase 1 Application shall support query selections/ modifications andprint query-selected reports.

Master Equipment List Database HNF-SD-VW-ATP-175, Rev. 2Phase 1 Page A-7


Requirement ID: R3.1, B7Requirement Ref: SRS 3.1 (bullet 7), Gen Reqs (Ace Criteria #6)Requirement Description : The MEL Phase 1 Application shall operate efficiently in the HLAN environment

Master Equipment List Database HNF-SD-Wfvl-ATP-l 75, Rev. 2Phase 1 Page A~


Test ID : T1 .023Test Item Description : MEL Phase 1 Application as a whole (supports HLAN standard/ESOE environment operation efficiency).

Proc ID~

P1.ool OperatesystemintheHLAN standard/ESOEenvironment.TV.012 FOr each teSt case, perform test, record test results (P

Logsheet.ass/Fall), date tested, and mmals ot testers triter comments m the Comment

.

Verify the user can log on to HLAN standard/ESOE environment. JB JECHe user can launch the applcabon, log on, and ensure the application IS

operable.JB JECH

e system can manage Itself by dlsplaymg system resources and conbnue tobe operable in the HLAN standard/ESOE environment.

JB JECH

Requirement ID: R3.1, B8

Requirement Ref: SRS 3.1 (bullet 8), Gen Reqs (Ace Criteria #7, 8)

Requirement Description: The MEL Phase 1 Application shall support control access using passwords,

Master Equipment List Database HNF-SD-WM-ATP-I 75, Rev. 2Phase 1 Page A-9


Test ID: T1.014Test Item Description : Privilege as a Data Entry User.

Proc ID 1 Test Procedure Description

PI.002 [Launchapplicationusingacceasprivilege. IP[.003 [operatetheappkat!onexercmg appropriatefunctionsandfeatures.71004 Enternewmformatlonmthe MEL Phasel Appkatlon.Wo12 I oreach test case, perform test, record test results(P

Logsheet.ass/Fall), date tested, andmtlals oftestera. kntercomments mthe~omment

Test Case Description -- Tester

Verify the user can launch the application, log on, and ensure the application isoperable. mm ‘BJECH

Master Equipment List Database HNF-SD-WM-ATP-I 75, Rev. 2Phase 1 Page A-1 1..—--


Master Equipment List Database HNF-SD-WM-ATP-I 75, Rev. 2Phase 1 Paae A-12




Requirement ID: R3.I , B9

Requirement Ref: SRS 3.1 (bullet 9), Gen Reqs (Ace Criteria # 7,9,10,16,17)

Requirement Description : The MEL Phase 1 Application shall have System Administrative features.

Master Equipment List Database HNF-SD-WM-ATP-l 75, Rev. 2Phase 1 Page A-14


Test ID : TI .001Test Item Description : MEL Phase 1 Application as a whole.

Proc ID i Test Procedure Description

PI.003 JOperate the application exercising appropriate functions and features. I-Plo12 Foreach test case, perform test, record test results(P ass/Fall), d

Logsheet.ate tested, andmltlal softesters. tntercomments m the Comment

Requirement ID: R3.2 (3.2.1)

Requirement Ref: SRS 3.2.1, Sys Admin Functions (Ace Criteria #7, 8, 18)

Requirement Description : The MEL Phase 1 Application shall have System Administrative features.

Master Equipment List Database HNF-SD-WIA-ATP-I 75, Rev. 2Phase 1 Page A-15



Requirement Ref: SRS 3.2.2, Data lnpuUUpdate Functions (Ace Criteria #12,13)

Requirement Description : The user shall be able to enter new data (via popup windows), modify existingdata (via folders), and import “Label Table” data into the MEL Phase 1 Db.


HNF-SD-WM-ATP-I 75, Rev. 2Page A-16


~ Test ID: T1.012Test Item Description : Data Input (Entry) Functions. Add additional information to an existing record/enter new records.

Proc ID I Test Procedure Description 1PI.004 ~Enter new information in the MEL Phase 1 Application.

-PI.012 t-or each test case, perform test, record test results (Pass/Fall), date tested, and mtlais O! testers. Enter comments m tLogsheet.

he Comment

Master Equi~nw:: :ist Database HNF-SD-WM-ATP-l 75, Rev. 2Page A-1?..—--

Acceptsnce Test Procedure & Record

Test ID : TI.013Test Item Description : Data Edit (Update) Functions. Update information to an existing record.


PIO05 Select and edit information via appropriate folders or windows. 1

TJI012 For each test caae, pertorm test, record test results (Pass/Fall), date teated, and mtlals of testers. triter comments m the CommentLogsheet.

Master Equipm:;: \ist Datebase HNF-SD-WVI-ATP-1 75, Rev. 2Page A-18


Test ID : TI .020Test Item Description : Importing Data Procedures/Functions. I



PI.012 For each test case, perform test, record test results (Pass/Fa!l), date tested, and mltlals of testers. triter comments m the COMMentLogsheet.

-1 Test Case Description jTest Result -~ Tester

llVerifv that data from sDecific tables can be imoorted via the conversion orooram. n II llmFFFR PFR .IR .IFCH I

Requirement ID : R3.2 (3.2.3)

Requirement Ref: SRS 3.2.3, Query /Retrieve Functions (Ace Criteria #5)

Requirement Description : The MEL Phase 1 Application shall have query and retrieval functions.

Test ID: T1.O1OTest Item Description : One or more tester-chosen query selections for tester-chosen privileges.

FTest Procedure Description

Operate the application exercising appropriate query functions.

-!+012 bor each test case, perform test, record test results (Pass/Fall), date tested, and mltlals of testers. Enter comments m the CommentLogsheet.

Master Equi~::;: I/et Database



Requirement Ref: SRS 3.2.4, Report Functions (Ace Criteria #5)

Requirement Description : The MEL Phase 1 Application shall have reporting functions to the screen andprinter.

HNF-SD-WM-ATP-l 75, Rev. 2Page A-19

Test Item Description : One or more tester-chosen reporting selections for tester-chosen privileges.

~

PI.008 Operate the application exercising appropriate reportinglprinting functions.

PI.012 Foreach test case, pertorm test, record test results( Pass/Fall), dLogsheet.

ate tested, andtmhalso ttesters. Enter comments m the Comment


Requirement Ref: SRS 3.2.5, Multi-Use Functions (Ace Criteria W)

Requirement Description : The MEL Phase 1 Application shall support a multiple user environment.

Master Equipment List Database HNF-SD-WM-ATP-I 75, Rev. 2Phase 1 Paqe A-20


Test ID : T1 022Test Item Description: MEL Phase 1 Application as a whole (supports Multiple Users).


PI.003 Operate the application exercising appropriate functions and features.

PI.012 Foreach test case, pertorm test, record test results (Pass/Fatl), dLogsheet.

atetested, andmlbalso ftesters. kntercomments m the Comment

Test Case ID Test Case Description Test Result OateKlme Tester

CI.009 ~levels can be logged on concurrently.

MULTIPLE USERS

CI.304 Verify the operation oft he system IS mteractwe, prowdmg IrrIMedlate processing ofactions.

MULTIPLE USERS


Requirement Ref: SRS 3.2,6, BackUp Functions (Ace Criteria 14)

Requirement Description : The MEL Phase 1 Application shall have menu options for backup support.

Test ID: TI .004Test Item Description : MEL Phase 1 Application as a whole (supports Backups).

Proc 10 Test Procedure Description

P1.ol 1 ~

PI.012 Foreach test case, pertorm test, record test results(PLogsheet.

ass/Fad), date tested, and mlt!als of testers. Enter comments m the Comment

Test Case ID Test Result Date/Time Tester

C1.002 Verify that the HLAN Administrator is providing backup support per System Admin.instructions.

DEFER PER JB JECH

C1.0U3 Verify that the menu Options provide backup support DEFER PER JB JECH




Requirement Ref: SRS 3.3.1, User Interfaces (Ace Criteria #1, 13)Requirement Description : The user shall be able to interface with the MEL Phase 1 Application through use

of menu/mouse driven selections, on-line help, and pop-up windows.

HNF-SD-WM-ATP-1 75, Rev. 2Page A-21

Test Item Description : MEL Phase 1 Application as a whole (supports User-Friendly Interface).

_ Test Procedure Description

Operate the application exercising appropriate functions and features.P1.olz FOr each teSt case, perform test, record test results (

Logsheet.I-’ass/t-ail), date tested, and mltlals of testers. Enter comments m the Comment


Requirement Ref: SRS 3.3.2, Hardware Interfaces

Requirement Description : The MEL Phase 1 Application shall operate on the minimium hardwarerequirements of a IBM PC488/33, 8Mb main processor memory and 30 meg freehard disk space.

Master Equipment List Database HNF-SD-W?vl-ATP-175, Rev. 2Phase 1 Page A-22


Test ID : T1 .005Test Item Description : MEL Phase 1 Application as a whole (supports Minimum Hardware Requirements).

Proc ID Teat Procedure Description

PI.009 Use a minimum system as specified in the requirements.PI.012 Foreach test case, perform test, record test results(P ass/Fall), d

Logsheet.atetested, andmltlals of testers. Enter comments m the Comment

Test Case ID Test Case Description Test Result DateTlme Tester

C1.004 Verify with the developer that by design, test item meets requirements.-CT.U05 Verify with t

JB JECHhe beta testers thatth e apphcatlon can be mstslled and IScompatible

1

JB JECHand operable using minimum hardware requirements.


Requirement Ref: SRS 3.3.4, Communications Interfaces (Ace Criteria #6, 15)

Requirement Descflption: The MEL Phase lApplication shall beaccessible viathe HMN. Installafionofthe system shall setup and be compatible with the uset’s computer environment

Test ID: TI .006Test Item Deactiption : MEL Phase 1 Application as a whole (supports HLAN Standard/ESOE Environment).

Proc ID I Test Procedure Description

P1.ool ~Operate system in the HLAN standard/ESOE environment.

PIO12 I-or each test case, perform test, record test resuits(P ass/Fall), dLogsheet.

atetested, andm!tlals of testers. Enter comments m the comment

~Test Case ID Test Case Description Test Result pj Tester

CI.006 Verify the application can install and is compatible with the HLAN standard/ESOEcomputer environment.

JB JECH

CI.201 Verify the user can launch the apphcation, log on, and ensure the apphcatlon IS

operable.JB JECH



Requirement ID: R3.4

Requirement Ref: SRS 3.4, Performance Requirements (Ace Criteria #4)

Requirement Description : The MEL Phase 1 Application shall meet reponse times of< 2 sees for inputledits,<30secs fordataqueries, <l rein/page forre-porting, and< 1 min for startup.Times for multi-use is 6-10 users (data entry& editing) and 25-50 users (quey &reports).

HNF-SD-WM-ATP-I 75, Rev. 2Page A-23

Test Item Description : MEL Phase 1 Application as a whole (supports Adequate Response Times).


PI.003 Operate the application exercising appropriate functions and features.PI.012 For each test case, perform test, record test results (P

Logsheet.ass/Fall), date tested, and mltlals of testers. Enter comments m the Comment

Test Case ID Test Case Description Test Result~ Date~me ~ Tester

CI.007 Ensure test cases are performed and accepted. ! t JB JECH-C1.304 Verity Me operation of the system IS mteractwe, provldmg Immediate processing of

actions.JB JECH

)


Requirement Ref: SRS 3.5.1, Standards Compliance (Ace Criteria # 19, 20)

Requirement Description : The MEL Phase 1 Application shall have the appropriate documentation thatmeets qualty affecting software requirements.

Master Equipment List Database HNF-SD-WM-ATP-1 75, Rev. 2Phase 1 Page A-24


/ Test ltern Descnption: MEL Phasel Application asawhole (supports Standard Compliance)

I Proc ID Test Procedure Description


-PI 012 Foreach test case, pertorm test, record test results(P ass/Fail), dLogsheet.

ate tested, andmlbals of testers. Enter comments m the Comment

I

Test Case ID Test Case Description ~Test Result PI

cl .007

Tester

Ensure test cases are performed and accepted. 1 I JB JECH-C1.O1O Manually verity system (Wahty Assurance documentation are wrtten and approved. I DEFER PER JB JECH

1


Requirement Ref: SRS 3.6.4, Reliability/ Recovery (Ace Criteria # 9,10,16,17)

Requirement Description : The MEL Phase 1 Application shall be reliable during normal operationinteraction. Failure torestad ortorecover data dutinga system failure is notcritical. Forrecove~, anactlvi~log andsystem adminfeatures and functionsshall be available.


HNF-SD-WM-ATP-175, Rev. 2Page A-25


Test ID : TI .009Test Item Description : MEL Phase 1 Application as a whole (supports Reliability/ Recove~ of Db).


Pi.oo3 Operate the application exercising appropriate functions and features,

W.012 i-or each test case, perform test, record test results (Pass/Fall),Logsheet.

date tested, and mtlals of testers. knter comments m the CommentM


Requirement Ref: SRS 3.6.7, Training (Ace Criteria #1 )

Requirement Description : The MEL Phase 1 Application shall have on-line help functions to minimize thetraining involved for users.


HNF-SD-WM-ATP-l 75, Rev. 2Page A-26


Test ID : TI .021Test item Description : MEL Phase 1 Application as a whole (supports On-Line Help).


PI.003 Operate the application exercising appropriate functions and features.

-PI.012 Foreach test case, perform test, record test results(P ass/Fall), date tested, and mlhals attesters. tntercommenfs mthe GommentLoqsheet.

IJNCLAWJFIE D HNF-SD-WM-ATP-175 Revision 2: Page -B- 1

APPENDIX B ACCEPTANCE TEST PROCEDURE RECORD (MULTI-USER)

HNF-SD-WM-ATP-l 75, Rev. 2, Page B-2

MASTER EQUIPMENT LIST DATABASEPHASE 1, VERSION 1.33

MULTI-USERACCEPTANCE TEST PROCEDURE & RECORD

AN ATTACHMENT TO: MASTER EQUIPMENT LIST DATABASEPHASE 1, VERSION 1.32

ACCEPTANCE TEST PROCEDURE & RECORDWHC-SD-WM-ATP-175, REV. 1

PERFORMED BY:

FACILITY CONFIGURATION MANAGEMENT INTEGRATION

Approved for Use: J. B. Jech Date:

Approved for Use: M. W, Thornton Date:


MASTER EQUIPMENT LIST - MULTI-USER ACCEPTANCE TEST PROCEDURETEST CASE/TIME ASSIGNMENTS

December 9,1996 (9:00 am -12:00 pm)

Time

Name 8:00 8:15 8:30 8:45 9:00 9:15 9:30 9:45 10:00 10:15 10:30 10:458:15 8:30 8:45 9:00 9:15 9:30 9:45 10:00 10:15 10:30 10:45 11:00

Baker- 1a-d 1a-d lh-lj 1h- lj BREAK 2 2 2 2 BREAK 7 7RO

Douka-LA la-ld le lf lg BREAK 3a-3f 3a-c 4 5 5 8a, f, h, 8a, f, h,3g-i i,j, k i,j, k

Duerr- 3a-3f 3a-c 4 4 BREAK 1a-d la-d lb-j 1h-j 2 2 2PiRls 3g-i

Fordharn- 3a-f 3a-c 4 4 BREAK 1a-d 1a-d lb-j 1h-j 2 2 2PINPISP 3g-I

Geiss - 7 7 2 2 2 BREAK 1a-d 1a-d 1h-j lb-j 3a-f 3a-fPiNP

Jech-SA 3 3 3 4 4 BREAK 1a-d 1a-d 1e-g 1e-g 8a, f, h, 8a, f, h,

i,j, k i,j, k

Weddle - 1a-d la-d Ih-j 1h-j BREAK 2 2 3a-3f 3a-c 4 4 7a, 7e-fRN 3g-i

White- 1a-d 1a-d lb-j lb-j BREAK 7 7 2 2 BREAK SC, d, e SC, d, eRO

Wyatt- 1a-d la-d lb-j lb-j BREAK 2 2 3a-f 3a-c 4 SC, d, e SC, d, eNPISP 3g-i

Access Control:-Edit Data by Folder: Pointer (P), Safety (S), Reference (R), NamePlate (NP), Specifications (SP).-Adnirr Levels: Label Administrator (LA) is accessible to EIN Related Fields, System Administrator (SA) is accessible to All Functions.-Read Only (RO) is accessible to view information no editing.

HNF-SD-WM-ATP-I 75, Rev. 2, Page B-4

MASTER EQUIPMENT LIST - MULTI-USER ACCEPTANCE TEST PROCEDURETEST CASE/TIME ASSIGNMENTS

December 9,1996 (8:00 am -12:00 pm)

rest Case Description

[) Perform a) Build a query for an EIN and four fields. For tbe four tields’ value, select All Values.Queries b) View results and select one of the fields’ values to narrow the results. Define the value of the field in the query

setup and execute.c) View results and verify that the defined value is part of tbe result. Continue to define fields to narrow down adata set. Veri& that the functions Collapse and Expand work.d) Write down the query built as parameters are defined, to assist in verifying the results.

e) Export tbe query results to a .db tile. Verify it can be retrieved in Paradox.f) Export the query results to a .txt tile. Verify it can be retrieved in WordPerfect.g) Save the query results to Reports. Print out the appropriate Folder reports (s) using the Query Results EIN List.

h) Save the query to (Save Query) in order to retrieve it later. Veri@ it can be retrieved.i) Retrieve the saved query, build upon it, execute it, and resave it (Save Query As) with a different filename.j) Verify there are two saved query tiles.

!) Reporting a) Without building a query, select three Folder reports to print.b) Select 5 EINs to print for each of the Folder reports.c) Print two Folder reports to the printer and print one to the screen.d) Verify that the 5 EINs printed out in the appropriate Folder reports.e) In View, manually verify for two Folder reports (for each data field) that the data printed out exactly what is

presented on the screen.f) Veri~ that the Folder report can be exported to a .txt file and retrieved.


3) Edit Session a) Perform a Quick Search to locate an EIN (system) that needs editing.b) Begin an edit session and verify all information is required to proceed. Note the “Reminder.c) Verify that an edit session cannot begin unless the right mouse button is initiated.

Simzle Reeord Edits:d) Verify that changes can he made for a single record, hut leave one field unchanged (will still be locked).e) Do not release the session. Verify while you’re still in Edit, that the Padlock icon enables the Locks and

Changes Pending form and that the record can be re-edited. Verify the changes are present. Click Folders icon.f) Verify that from the Edit Menu, “View Changes”, enables the Changes Pending form and that the record can be

re-edited again. Verify on the Folder that the fields are blue. Exit from Edit mode.

New Record Edits:g) Verify that changes can be made for a multi-record (i.e., procedures field). Enter 2 new records (procedure

numbers). Verify on the Folder that the fields are blue (temporarily - until record moves to Changes Pending).h) Verify on 2 more new records that immediately after inserting that the change can be posted individually.i) Verify on the 2 new records that after entering it AND moving off the cell that it cannot be posted. Verify that

from the Edit Menu, “View New Records”, enables the New Record Pending form. Verify that in this form thatthe new record cannot be re-edited. Exit from Edit mode.

4) Release Session a) Click on the Padlock icon and veri~ that it enables the Locks and Changes Pending form.b) Veri@ that pending changes and locks can be viewed by Session.c) By User, verify that the pending changes and locks are correct values and post. Click on Folders icon.d) By Session, veri~ that the pending changes and locks are correct values and post. Click on Folders icon.e) In View, verify that once posted, each of the values are no longer colored blue.t) Verifk that in Change Log that the changes are smesent.


5) Label Admin. Creatinv a new EINa) Begin an edit session and verify all information is required to proceed.b) Verify that a new EIN can be created and exported to a .db tile. Verify it can be retrieved in Paradox.c) Verify that the new EIN can be posted to the Locks and Changes Pending form. From there release the session

hy posing.d) Verify that tbe EIN can be located using Quick Search and begin an edit session to add more information to the

Folders.e) Veri~that the`new record' isenabled from the Edit menu. Verify that information can beinsertedin allthe

Folders, all fields. Add Woforeach of themulti-record fields (i.e., procedures, drawing nos.).f) Postthe pending changes andveri~that theinformation ispresent in View.ag) Begin an edit session and veri~ all information is required to proceed.h) Markone individual record ina Folder fordeletion. Delete therecord viathe Edit Menu.i) Mark an entire EIN record for deletion and delete via the Edit Menu in the Eaui~ment Identification area.

6) System Admin.

7) Read Only

a) Veri~ edit sessions are recorded in the Change Control Activity form.b) Verify the fields, Time and User are correct.c) Edit the Definitions List. Veri@ that the drop-down lists are updated.d) Perform refresh test with a new EIN that has been posted by the Label Admin.e) Mark an EIN record and multi-record for deletion. Post individually. Delete the full EIN from the Edit menu

and verify that it is no longer present.f) Change the access level of one User from an editing privilege to a Read Only (see Sk).

a) Perform a Quick Search to locate a set of EINs.b) View all Folders.c) Veri@ that the buttons and icons on the toolbar are functional.d) Verify that editing privileges are not available.e) Identify specific fields and their values for EINs that could be used in a Find.t) Verifv that Derforminz a Find and Find Next functions work.

HNF-SD-WM-ATP-l 75, Rev, 2, Page B-7

1)ConflictingTest Cases

a) 2 Testers - Mark a full EIN locked (do not post) and verify that it can be queried.b) 2 Testers - Perform a Find on a specific field and at the same time set that field up as part of a query and

execute.c) 2 Testers - Perform a Quick Search on the same EIN.d) 2 Testers - Perform the same query setup and execute it at the same time.e) 2 Testers - View the Change Log while another person posts an edit. Verify it updates after a Refresh.~ 2 Testers - Have both users enable an edit session and attempt to edit the same EIN, using different Folders, and

then the same Folder, and then tbe same Field.g) SA/LA - Perform a Refresh test of a newly created and posted EIN.h) SALA - Perform a Refresh test of a newly created and posted record in an EIN.i) SA/LA - Perform a Refresh test of a newly deleted EIN.j) SA/Tester - Change a user’s privilege in the middle of an edit session to Read Only. Verify that when the User

exits MEL and logs back on that the new privilege is present.

~otes:J During the test cases, if there is a time that the system is not responding to an mouse click hit the ESC button.J For each Test Case in #8, please write ont the resnlts.] Remember for each problem occurrence, complete the Problem Report form. Write ont each step that made you think there was aproblem.

JR141997/2 EFUG,NEERING DATA TRANSMITTAL “ 03’7 “DT...

Documents

Transcript of JR141997/2 EFUG,NEERING DATA TRANSMITTAL “ 03’7 “DT...