Reactor 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 Reactor module.

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.7 - 3.11
Python Packagespackaging pyaml jinja2

System Purpose

The MOOSE Reactor module provides an interface and libraries for creating meshes for nuclear reactor systems.

It is intended to be used using other MOOSE ecosystem codes (including MOOSE-wrapped applications) to perform the physics solve as it does not contain any physics. Thus, the Reactor module uses the same object-oriented design as MOOSE in order to make simulation design and new development straightforward for engineers and researchers.

System Scope

The scope of the Reactor module is to provide a set of utilities for building reactor meshes for finite element or finite volume simulations. The modules relies on the MOOSE framework for utilities that are common with other applications.

It covers several reactor types, mostly those with geometry that are axially extruded or close to being so. This includes: liquid metal fast reactors, prismatic high temperature reactors, some variations of micro reactors and pressurized water reactors. Every design variation of each advanced reactor type cannot be covered by the module. It covers the meshing and rotation of control drum in certain reactors.

The system contains, generally, a base set of mesh generators and meshing utilities. Reactor module developers work with framework and other module and application developers to ensure that the Reactor module provides adequate capability to support ongoing and prospective research opportunities involving advanced reactors.

Assumptions and Dependencies

The Reactor module is developed using MOOSE and can itself be based on various MOOSE modules, as such the RTM for the Reactor module 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.

The changelog for all code residing in the MOOSE repository is located in the MOOSE RTM.

System Requirements Traceability

Functional Requirements

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.