Fluid Properties System Requirement Specification

Introduction

The SRS for Fluid Properties describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.

Dependencies

The Fluid Properties application is developed using MOOSE and is based on various modules, as such the SRS for Fluid Properties is dependent upon the following documents.

Requirements

The following is a complete list for all the functional requirements for Fluid Properties.

  • fluid_properties: Brine
  • F6.1.1The system shall compute properties of brine
  • F6.1.2The system shall compute properties of brine using tabulated water properties
  • fluid_properties: Fp Interrogator
  • F6.2.1The fluid properties interrogator shall output static-state fluid properties for (p, T) input.
  • F6.2.2The fluid properties interrogator shall output static-state fluid properties for (p, T) input in JSON format.
  • F6.2.3The fluid properties interrogator shall output static-state fluid properties for (rho, e) input.
  • F6.2.4The fluid properties interrogator shall output static-state fluid properties for (rho, e) input in JSON format.
  • F6.2.5The fluid properties interrogator shall output static-state fluid properties for (rho, p) input.
  • F6.2.6The fluid properties interrogator shall output static-state fluid properties for (rho, p) input in JSON format.
  • F6.2.7The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object.
  • F6.2.8The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object in JSON format.
  • F6.2.9The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object.
  • F6.2.10The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object in JSON format.
  • F6.2.11The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object.
  • F6.2.12The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object in JSON format.
  • F6.2.13The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object.
  • F6.2.14The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object in JSON format.
  • F6.2.15The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object.
  • F6.2.16The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object in JSON format.
  • F6.2.17The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object.
  • F6.2.18The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object in JSON format.
  • F6.2.19The fluid properties interrogator shall throw an error if an incompatible fluid properties object is supplied.
  • F6.2.20The fluid properties interrogator shall throw an error if an extraneous parameter(s) are supplied.
  • F6.2.21The fluid properties interrogator shall throw an error if an no valid input sets were supplied.
  • fluid_properties: Interfaces
  • F6.3.1The system should produce a warning when a NaN is produced and user required that the execution would not terminate
  • F6.3.2The system should report an error when a NaN is produced by a computation in DEBUG mode, by default
  • F6.3.3The system should not report an error when a NaN is produced by a computation in OPT mode, by default