ML20100J226

From kanterella
Jump to navigation Jump to search
Rev 2 to Core Protection Calculation/Control Element Assembly Calculator Sys Phase I Software Verification Test Rept
ML20100J226
Person / Time
Site: Palo Verde Arizona Public Service icon.png
Issue date: 09/30/1984
From:
ABB COMBUSTION ENGINEERING NUCLEAR FUEL (FORMERLY
To:
Shared Package
ML17298B596 List:
References
CEN-217(V)-NP, CEN-217(V)-NP-R02, CEN-217(V)-NP-R2, NUDOCS 8412100256
Download: ML20100J226 (22)


Text

.

4 PALO VERDE NUCLEAR GENERATING STATION UNIT 1 DOCKET 50-528 CEN-217(V)-NP REVISION 02

'{

d: ,

'i CPC/CEAC SYSTEM.

PHASE I SOFTWARE VERIFfCAYION TEST REPORT i SEPTEMBER, 1984 ,

Combustion Engineering, Inc.

Nuclear Power Systems Power Systems Group I Windsor, Connecticut t

k O

A

LEGAL NOTICE This report was prepared as an account of work sponsored by Combustion Engineering, Inc. Neither Combustion Engineering nor any person acting on its behalf:

A. Makes any warranty or representation, express or implied including the 6

warranties or fitness for a particular purpose or merchantability, with respect to the accuracy completeness, or usefulness of the information contained in this report, or that the use of any information, apparatus, method or process disclosed in this report may not infringe privately o owned rights; or B. Assumes any liabilities with respect to the use of, or for damages resulting from the use of, any information, apparatus, method or process disclosed in this report.

e o

O l Page 2

~ ~ -

ABSTRACT Phase I Design Qualification Testing is performed on the DNBR/LPD Calculator System to verify that CPC and CEAC software modifications have been properly implemented.

3 This report presents the Phase I Test results for the Arizona Nuclear Power Project, PVNGS-1 Plant CPC/CEAC System Software, Revision 01. l The Phase I Testing was performed according to previously issued procedures 4

(Reference 2). The test results indicate that the CPC and CEAC software modifications have been properly implemented.

i 0

I

> Page 3 i

i TABLE OF CONTENTS SECTION TITLE PAGE NO.

1.0 INTRODUCTION

AND

SUMMARY

6 1.1 Objective of Phase I Testing 6 1.2 Results 6

, 1.3 Conclusions 6 1.4 Prerequisites 6 2.0 APPLICATION PROGRAM TESTING 7 2.1 Test Configuration 7 2.2 Test Cases 7 2.3 Test Execution and Results 8 3.0 EXECUTIVE TESTING 16 3.1 Test Configuration 16 3.2 Test Cases 16 3.3 Test Execution and Results 16 4.0 PHASE I TEST RESULTS

SUMMARY

20 5.0 -REFERENCES 21 ,

0 Page 4

_~ __. _.

LIST OF TABLES TABLE- TITLE PAGE NO.

2-1 CEAC Single Channel Hardware Configuration for Phase I Executive / Application Program Testing 10

, 2-2 Application Programs Tested with the Automated Phase I Testing Program 11 3-1 CPC Single Channel Hardware Configuration for Phase I Executive Program Testing 17 LIST OF FIGURES FIGURE TITLE PAGE NO.

2-1 CEAC Single Channel Memory Map for CPC System Software Phase I Testing 12 2-2 CEAC Single Channel Memory Map for CEAC System ~

Software Phase I Testing 14 3-1 CPC and CEAC Single Channel Memory Map for CPC/CEAC Executive Phase I Testing 18 N

Page 5

1.0 INTRODUCTION

AND

SUMMARY

This document sumarizes the results of the Phase I Design Qualification Testing of changes to the CPC and CEAC software Rev.

01 for PVNGS-1. The programs affected by these changes, which are described in Reference 1, were required to undergo Phase I Testing in accordance with Reference 2. The changes reflect the implementation of Software Change Requests 611, 612, 617-619, 623 and 626-628. These changes were made in accordance with Reference 2.

  • The tests reported herein were conducted on the CPC/CEAC Single Channel Test facility in Windsor. A discussion of the test configuration, test methodology, and test results are presented in this document.

1.1 OBJECTIVE OF PHASE I TESTING The objective of Phase I Design Qualification Testing is to verify the correct implementation of the Core Protection Calculator System (i.e., both CPC and CEAC) software.

1.2 RESULTS Analysis of the Phase I Design Qualification Tests demonstrated that the software changes had been correctly implemented to meet the system functional requirements.

1.3 CONCLUSION

S CPC System Phase I Testing was performed in the prescribed manner as described by Phase I Test Procedures. The Phase I testing was adequate to meet all of the test objectives. The success of the Phase I Testing demonstrates the adequacy of the CPC/CEAC software implementation.

l 1.4 PREREQUISITES Before formal Phase I T'esting was initiated, the following prerequisites were satisfied:

l* 1. Programmer debug testing was performed on the module changes to remove all obvious errors.

. 2. The programs were integrated into complete software systems and absolute core images were generated on the CPC permanent mass storage medium (floppy disks).

l l

l Page 6

--.---.----,d.,

2.0 APPLICATION PROGRAM TESTING The CPC and CEAC application programs were tested in accordance with the CPC/CEAC Phase I Test Procedure. This section discusses the actual test configuration, test cases, and test execution and results.

  • Phase I Test runs used Disks #S340 as the PVNGS-1 Rev. 01 software reference disk.

Disk #S340 and it's backup copy, #S341 were initially created on i

August 14, 1984 for Phase I testing.

  • On August 21,1984 disk #S340 was regenerated after it was identified that the system monitor task of the Executive required a change. A byte by byte comparison was made between disk #S340 and its original backup #S341. This comparison emonstrated the disks to be identical other than the sector containing the SYSMONI program. This change did not affect Phase I testing of the application programs and, thus, testing done previously to the application programs (August 15,1984) was valid.

2.1 TEST CONFIGURATION Phase I Testing of the CPC and CEAC application programs was performed on the CEAC Single Channel Unit. For the purpose of this testing, the Single Channel Unit was configured with the hardware complement listed in Table 2-1. The software configuration for the application progrt.ms Phase I Testing is shown in Figure 2-1 (CPC) and Figure 2-2 (CEAC), Memory was loaded with this configuration by the following procedure:

1. The integrated CPC or CEAC system was loaded from tu PVNGS-1 Rev. 01 Reference Disk #5340.
2. The Automated Phase I Testing Software was loaded from magnetic tape, overlaying the CPC/CEAC Executive and unused portions of memory.
3. The Interdata Hexadecimal Debug Program, CLUB, was loaded from magnetic tape, overlaying any unused portion of memory.

The Automated Phase I Testing software was then used, with CLUB, to test the programs listed in Table 2-2.

~

2.2 TEST CASES 2.2.1 Inputs Phase I Test case inputs for the CPC/CEAC application programs were generated in accordance with the CPC/CEAC Phase I Test Procedure.

Sufficient test cases were chosen to exercise each functional branch Page 7

_ .. - - - - -  :.. : . = ~ . - - - . - = .- = : - -- -

i l

in the application programs. However, several branches were not exercised because assigned constant values made it impossible to l branch on certain conditions. All coding that cannot be executed, because of constant assignments, was verified by inspection to assure correct implementation.

2.2.2 Expected Results Expected results for the CPC and CEAC application programs Phase I Test cases were generated by two methods. The preferred method for generation of expected results utilized the CPC FORTRAN Simulation w Code. Test cete inputs were stored on magnetic tape and entered into the Simulation Code. The FORTRAN Code calculated the expected results and stored them on magnetic tape in a format acceptable to the automated Phase I Testing Program. In scme instances, such as input / output handling, the FORTRAN Code does iot simulate the operational system software. In these cases, the expected results 2

were hand calculated by the test engineer based on the system functional requirements, the programer's flowcharts, and the system c

data base document. The results were then manually entered on-magnetic tape in a format acceptable to the Automated Phase I Testing Program. .

2.3 TEST EXECUTION AND RESULTS When test case inputs had been selected and expected results had been generated, the test engineer prepared the test tape to be read 5y the Automated Phase I Testing Program. The test case inputs overlayed the portion of memory where data is accessed by the software module under test. After each set of inputs overlayed appropriate memory locations, the software module under test was

! executed and the actual CPC results were compared to the expected results by the-Automated Phase I Testing Program. Whenever the actual value differed from the expected value by more than 0.1 i

percent, an analysis of the error was performed by the test engineer to assure that the deviation was not caused by a coding error.

t Documentation generated by the Automated Phase I Testing Program consisted of listings which contain input and output differences.

r For several of the modules tested, it was not obvious which branches in the code were taken when observing the outputs. When tracing

(

through a portion of code, the location of each critical instruction i

was printed when that instruction was executed, which enabled the-test engineer to verify that each functional branch was taken. A

, Phase I Test Log was used to maintain a daily account of testing activities.

. The SCR's generated affected FLOWCON, UPDATPRG, UPDATCON, POWERPRG, STATCPRG,STATCCON,TRIPSQCON,CPCEXEC,CEACDSP,CEACDC1,CEACPFC.

i I

i Page 8

, _ __-~ _

These changes, in conjunction with the data-base modification described in reference 1, required Phase I testing of the FLOW, UPDATE, POWER j STATIC and TRIP application programs, the Executive program, CEAC penalty factor program and the CEAC display program.

Phase I Testing]. [was Phaseperformed I Testing ofonthe the CPC application Executive Systen was programs on

, [_~formedon[- )).

per _

Tests in the Penalty Factor program were run on [:- _

No software errors were found. TestsontheDisplayprogramwere_;].

run on [_ []. No software errors were found.

It was concluded that Phase I testing revealed no coding errors in the CPC and CEAC application programs.

b e

9 Page 9

TABLE 2-1 CEAC SINGLE CHANNEL HARDWARE CONFIGURATION FOR PHASE I EXECUTIVE / APPLICATION PROGRAM TESTING I

p i..

o l

i

! Page 10 l

m TABLE 2-2 APPLICATION PROGRAMS TESTED WITH THE AUTOMATED PHASE I TESTING PROGRAM I

I l

l l

i Page 11 t . - - , ,

,: _ . ,. . . . . _ . . .n..-.., -

FIGURE 2-1 CEAC SINGLE CHANNEL MEMORY MAP FOR CPC SYSTEM SOFTWARE PHASE I TESTING w

a O

i 4

Page 12

-~ , -, e,, e- , -- -a --,-- e--- + - , .,,r,. - . . . , ,,, - - ,,, ,,y--,-- , g -

k T

P,,

- FIGURE 2-1(Cont'd.)

ar

. ne

~

J' i- .g. ,

'l i

4 t.

Page 13 iuA - .

..:.u.. _ _ _2__ _ _ -_;__ __ --

N FIGURE 2-2 CEAC SINGLE CHANNEL MEMORY MAP FOR CEAC SYSTEM SOFTWARE PHASE I TESTING

+

J a

i s

! Page 14

" * < t ~ -nc,-- ,,, ,w-+ -e,O, , , ,, ,,. ,y- , , , _ ,_, , , , _ , , , _

k

g. - ,; .a.---..
i. -

i.

- 2 .

FIGURE 2-2.(Cont'd.).

l-.

i.

i-a-

1

s. .

t t

'I .

j.

I r

t-r k- .S e

.i 4

- e a

4 t

i'

.k

<~-

i ,_

.t.'

W

+f .

4 ." .

j' {

i

,n -

T -

1 t

4-4 --

4 ,.

T J -.

1 1

Y .t t

I j-. .

Page 15 i

f' r

Y

+ -,--se-+4' n -

w.e , ., - , ,, , ,r,,,s- -w-..n, - . - r,rv ,,,-m ,v,-wwww - m m-m, y , .w , ,, egg w w ,-m n ,mm ,. -,- p w, y -c p n. -

3.0 EXECUTIVE TESTING-The CPC/CEAC Executive software was tested in accordance with the CPC/CEAC Executive Phase I Test Procedure. This section discusses the actual test configuration, test cases, and test execution and results. Prior to formal Phase I testing on August 21, 1984 a change to the system monitor task of the Executive (SYSMON1) was identified (SCR #617) and disk #S340 was regenerated. A byte by byte comparison was made between disk #S340 and its backup #S341 and demonstrated that all sectors, other than the sector containing the changed program, were identical-and, thus, the Phase I testing previously performed on application programs was valid.

3.1 TEST CONFIGURATION Phase I testing of the CPC/CEAC Executive was performed on the CPC and CEAC Single Channel Units. For the purpose of this testing, the Single Channel Facility was configured with the hardware complement i listed in Tab'le 2-1 (CEAC) and Table 3-1 (CPC). This hardware configuration is functionally identical to the as-built CPC/CEAC design.

The software configuration for the Executive Phase I Testing is shown in Figure 3-1. Memory was loaded with this configuration by the following procedure: .

1. An integrated CPC/CEAC system was loaded from PVNGS-1 Rev. 01 Reference Disk #S340 (the entire image was loaded although only the Executive system is tested).
2. The Interdata Hexadecimal Debug Program, CLUB, was loaded from magnetic tape overlaying an unused area in memory.

The prescribed test cases were then set up and executed using the CLUB program to test the Executive software.

3 3.2 TEST CASES f

The CPC/CEAC Executive Phase I Test Cases are described in the i Executive Phase I Test Procedure. Sufficient test cases were chosen to exercise each functional branch of the Executive system.

. 3.3 TEST EXECUTION AND RESULTS For testing of the CPC/CEAC Executive, the debug program, CLUB, was used to insert test case inputs into memory, to insert breakpoints to trace and intercept code executions and to examine results.

Documentation produced as a result of Executive Phase I Testing consists of the CLUB teletype printouts, initialed and dated by the test engineer.

~~

The CPC/CEAC Executive was tested on . No software errors were detected. -- --

Page 16 J

-wy -v,-- +, w ,,e ----w~,--s---r~

TABLE 3-1 CPC SINGLE CHANNEL HARDWARE CONFIGURATION FOR PHASE I EXECUTIVE PROGRAM TESTING

=

=

=

N e

l Page 17

J FIGURE 3-1 CPC AND CEAC SINGLE CHANNEL MEMORY MAP FOR CPC/CEAC EXECUTIVE PHASE I TESTING a

t

[

{

Page 18

7 - . _ _ . _ _ . _ _ . . . _ _ _ _ . _ _ _ - _ _ - - . - _ - . _ . . _ - - - . _

FIGURE 3-1(Continued)

+

9 Page 19

~ -

4.0 . PHASE I TEST RESULTS

SUMMARY

Phase I testing of the CPC and CEAC software for PVNGS-1 Cycle 1 (Rev. 01) was performed in accordance with Reference 2. Test results conclude that the data-base modifications outlined in reference 1, and software modifications to those programs listed in section 2.3 were correctly implemented.

4 Page 20

5.0 REFERENCES

1. " Schedule Status for Pelo Verde Cycle 1 CPC Software Revision,"

June 26, 1984, IEC-84-1388, J. J. Valerio.

2.- CPC Protection Algorithm Software Change Procedure CEN39(A)-P, Revision 02, December 21, 1978.

P r

Page 21