IAPWS95 Requirements Traceability Matrix

This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."

commentnote

This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for RTM specific to the IAPWS95 application.

Introduction

Minimum System Requirements

In general, the following is required for MOOSE-based development:

A POSIX compliant Unix-like operating system. This includes any modern Linux-based operating system (e.g., Ubuntu, Fedora, Rocky, etc.), or a Macintosh machine running either of the last two MacOS releases.

HardwareInformation
CPU Architecturex86_64, ARM (Apple Silicon)
Memory8 GB (16 GBs for debug compilation)
Disk Space30GB

LibrariesVersion / Information
GCC8.5.0 - 12.2.1
LLVM/Clang10.0.1 - 16.0.6
Intel (ICC/ICX)Not supported at this time
Python3.9 - 3.11
Python Packagespackaging pyaml jinja2

System Purpose

IAPWS95 is a module to compute the fluid properties of water using Spline-Based Table lookups (SBTL) for MOOSE applications. SBTL is a fast method of computing properties from pre-generated tables of fluid properties. The IAPWS95 can compute properties such as density, specific heat, or viscosity over the range of validity in pressure and temperature that the input data was defined on. Water fluid properties are useful to perform thermal hydraulic simulations of Light Water Reactors (LWRs) and certain coolant loops in advanced nuclear reactors. LWRs are currently the only type of civilian commercial nuclear reactors in the United States.

System Scope

IAPWS95's scope is somewhat open-ended, as fluid properties are an important but generally not central part of a given simulation.

Assumptions and Dependencies

The IAPWS95 application is developed using MOOSE and is based on various modules, as such the RTM for IAPWS95 is dependent upon the files listed at the beginning of this document.

Pre-test Instructions/Environment/Setup

Ideally all testing should be performed on a clean test machine following one of the supported configurations setup by the test system engineer. Testing may be performed on local workstations and cluster systems containing supported operating systems.

The repository should be clean prior to building and testing. When using "git" this can be done by doing a force clean in the main repository and each one of the submodules:


git clean -xfd
git submodule foreach 'git clean -xfd'

All tests must pass in accordance with the type of test being performed. This list can be found in the Software Test Plan.

Changelog Issue Revisions

Errors in changelog references can sometimes occur as a result of typos or conversion errors. If any need to be noted by the development team, they will be noted here.

Currently, the IAPWS95 development team has not discovered or identified any errors in issue references related to the changelog. This document will be updated if any such issues are discovered.

System Requirements Traceability

Functional Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

Usability Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

Performance Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

System Interface Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

References

No citations exist within this document.