Scalar Transport 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 Scalar Transport module.

Introduction

Minimum System Requirements

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

  • GCC/Clang C++17 compliant compiler (GCC @ 7.5.0, Clang @ 10.0.1 or greater)

    • Note: Intel compilers are not supported.

  • Memory: 8 GBs of RAM for optimized compilation (16 GBs for debug compilation), 2 GB per core execution

  • Processor: 64-bit x86 or ARM64 (specifically, Apple Silicon)

  • Disk: 30GB

  • A POSIX compliant Unix-like operating system, including the two most recent versions of MacOS and most current versions of Linux.

  • Git version control system

  • Python @ 3.7 or greater

System Purpose

The MOOSE Scalar Transport module purpose is to model mass transfer due to advection, diffusion, and reaction.

System Scope

The MOOSE Scalar Transport module scope is to model mass transfer due to advection, diffusion, and reaction.

Assumptions and Dependencies

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

  • scalar_transport: Multiple-Species
  • 17.1.1The system shall be able to solve for multiple species masss transport with various dissociation and recombination reactions occurring at boundaries

    Specification(s): exo

    Design: DissociationFluxBCBinaryRecombinationBC

    Issue(s): #22442

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 17.1.2The system shall calculate a domain averaged flux consistent with the theoretical value for the surface limited case

    Specification(s): surface_limited

    Design: DissociationFluxBCBinaryRecombinationBC

    Issue(s): #22442

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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.