Shifted Boundary Method 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 Requirement Traceability Matrix (RTM) specific to the Shifted Boundary Method 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
GCC9.0.0 - 13.3.1
LLVM/Clang14.0.6 - 19
Intel (ICC/ICX)Not supported at this time
Python3.10 - 3.13
Python Packagespackaging pyaml jinja2

System Purpose

errorerror:Missing Template Item: "system-purpose"

Summarize the reason(s) for the system being developed or modified.

The document must include the "system-purpose" template item, this can be included by adding the following to the markdown file (sqa/shifted_boundary_method_rtm.md):

!template! item key=system-purpose
Include text (in MooseDocs format) regarding the "system-purpose" template item here.
!template-end!

System Scope

errorerror:Missing Template Item: "system-scope"

Delineate the following:

  1. Identify the product(s) to be produced by name (Network Infrastructure, Host DBMS, Report Generator, HPC Server, etc.)

  2. Explain what the product(s) will, and, if necessary, will not do

  3. Describe the application of the product being specified, including relevant benefits, objectives, and goals.

commentnote

Be consistent with similar statements in higher level specifications (e.g., business requirements specification).

The document must include the "system-scope" template item, this can be included by adding the following to the markdown file (sqa/shifted_boundary_method_rtm.md):

!template! item key=system-scope
Include text (in MooseDocs format) regarding the "system-scope" template item here.
!template-end!

Assumptions and Dependencies

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

errorerror:Missing Template Item: "log-revisions"

If errors are found in issue references related to the changelog (e.g., commit history), these should be noted here. The commit in which the incorrect issue reference occurs should be listed, and the correct issue should be added alongside each entry. Relevant links to all items are required. An example of this is shown below:

MOOSE CommitIncorrect Referenced IssueCorrect Referenced Issue
48db61idaholab/sockeye#19845idaholab/sockeye#130

The document must include the "log-revisions" template item, this can be included by adding the following to the markdown file (sqa/shifted_boundary_method_rtm.md):

!template! item key=log-revisions
Include text (in MooseDocs format) regarding the "log-revisions" template item here.
!template-end!

System Requirements Traceability

Functional Requirements

  • shifted_boundary_method: Activeelementfractiontest.Unit Tests
  • 18.5.1The system shall compute the fraction of a quadrilateral element occupied by the physical domain when the element is fully inside, fully outside, or cut in half by the true boundary.

    Specification(s): unit_square

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • shifted_boundary_method: Classifypartialelementtest.Unit Tests
  • 18.6.1The system shall classify fully active and fully inactive elements independently of partial-element options.

    Specification(s): fully_active_or_inactive

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.6.2The system shall assign the intercepted subdomain to partial elements when intercepted-element marking is enabled.

    Specification(s): mark_intercepted

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.6.3The system shall classify partial elements by comparing their inactive fraction with the lambda threshold.

    Specification(s): lambda_threshold

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.6.4The system shall apply partial-element classification when all nodes are active but the active fraction is not one.

    Specification(s): enclosed_surface

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.6.5The system shall determine element inactivity from active fraction and the endpoint and interior values of the lambda threshold.

    Specification(s): inactive_predicate

    Design: InterceptedElementModifier

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • shifted_boundary_method: Orientedboundingboxtest.Unit Tests
  • 18.7.1The system shall write an oriented three-dimensional bounding box as a mesh containing a first-order hexahedral element whose vertices coincide with the corners of the box.

    Specification(s): write_3d_box

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.7.2The system shall write an oriented two-dimensional bounding box as a mesh containing a first-order quadrilateral element whose vertices coincide with the corners of the box.

    Specification(s): write_2d_box

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.7.3The system shall write a ray along the shortest axis of an oriented bounding box as a mesh containing a first-order line element.

    Specification(s): write_ray

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.7.4The system shall report geometry, projected coordinates, and point containment for an axis-aligned oriented bounding box.

    Specification(s): axis_aligned_queries

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.7.5The system shall report projected coordinates and point containment in the local basis of a rotated oriented bounding box.

    Specification(s): rotated_queries

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.7.6The system shall initialize the corners and centroid of an oriented bounding box constructed without geometric data at the origin.

    Specification(s): default_construction

    Design: AdaptiveRayContainmentCheck

    Issue(s): #33397

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • shifted_boundary_method: Sbmsurfacedistancetest.Unit Tests
  • 18.9.1The system shall compute the normal distance vector from a point to a first-order line element when the normal projection of the point lies within the element.

    Specification(s): edge_projection

    Design: UnsignedDistanceToSurfaceMesh

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.9.2The system shall compute the distance vector from a point to the nearest endpoint of a first-order line element when the normal projection of the point lies outside the element.

    Specification(s): edge_node_fallback

    Design: UnsignedDistanceToSurfaceMesh

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.9.3The system shall compute the direction and magnitude of the distance vector from a point to a tilted first-order line element.

    Specification(s): tilted_edge

    Design: UnsignedDistanceToSurfaceMesh

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.9.4The system shall compute the normal distance vector from a point to a first-order triangular surface element when the normal projection of the point lies within the element.

    Specification(s): triangle_projection

    Design: UnsignedDistanceToSurfaceMesh

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.9.5The system shall compute distance vectors from points on and off a tilted first-order triangular surface element to their nearest points on the element.

    Specification(s): tilted_triangle

    Design: UnsignedDistanceToSurfaceMesh

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • shifted_boundary_method: Watertighttest.Unit Tests
  • 18.10.1The system shall identify open and closed two-dimensional boundary loops as non-watertight and watertight, respectively.

    Specification(s): two_d_open_and_closed_geometry

    Design: SBMSurfaceMeshBuilder

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

  • 18.10.2The system shall identify open and closed three-dimensional boundary surfaces as non-watertight and watertight, respectively.

    Specification(s): three_d_open_and_closed_geometry

    Design: SBMSurfaceMeshBuilder

    Issue(s): #31937

    Collection(s): FUNCTIONAL

    Type(s): GoogleTest

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.