Porous Flow Requirements Traceability Matrix
This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."
This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for RTM specific to the Porous Flow module.
!sqa dependencies suffix=rtm category=porous_flow
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.
| Hardware | Information |
|---|---|
| CPU Architecture | x86_64, ARM (Apple Silicon) |
| Memory | 8 GB (16 GBs for debug compilation) |
| Disk Space | 30GB |
| Libraries | Version / Information |
|---|---|
| GCC | 9.0.0 - 12.2.1 |
| LLVM/Clang | 10.0.1 - 19 |
| Intel (ICC/ICX) | Not supported at this time |
| Python | 3.10 - 3.13 |
| Python Packages | packaging pyaml jinja2 |
System Purpose
The purpose of the MOOSE Porous Flow module is to provide functionality to support simulations for fluid and heat flow in porous media. Typical usage examples include groundwater flow, geothermal modeling, geological storage of , and long-term mineralization due to geochemical reactions. The Porous Flow module can be easily coupled with other physics modules in MOOSE.
System Scope
By simply adding pieces of physics together in an input file, the Porous Flow module enables the user to model problems with any combination of fluid, heat, geomechanics and geochemistry.
Assumptions and Dependencies
The Porous Flow module is developed using MOOSE and can itself be based on various MOOSE modules, as such the RTM for the Porous Flow 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
!sqa requirements link=True collections=FUNCTIONAL category=porous_flow
Usability Requirements
!sqa requirements link=True collections=USABILITY category=porous_flow
Performance Requirements
!sqa requirements link=True collections=PERFORMANCE category=porous_flow
System Interface Requirements
!sqa requirements link=True collections=SYSTEM category=porous_flow