Xfem System Requirements Specification

This template follows INL template TEM-135, "IT System Requirements Specification".

note

This document serves as an addendum to Framework System Requirements Specification and captures information for SRS specific to the Xfem application.

Introduction

System Purpose

The MOOSE is a tool for solving complex coupled Multiphysics equations using the finite element method. MOOSE uses an object-oriented design to abstract data structure management, parallelism, threading and compiling while providing an easy to use interface targeted at engineers that may not have a lot of software development experience. MOOSE will require extreme scalability and flexibility when compared to other FEM frameworks. For instance, MOOSE needs the ability to run extremely complex material models, or even third-party applications within a parallel simulation without sacrificing parallelism. This capability is in contrast to what is often seen in commercial packages, where custom material models can limit the parallel scalability, forcing serial runs in the most severe cases. When comparing high-end capabilities, many MOOSE competitors target modest-sized clusters with just a few thousand processing cores. MOOSE, however, will be required to routinely executed on much larger clusters with scalability to clusters available in the top 500 systems (top500.org). MOOSE will also be targeted at smaller systems such as high-end laptop computers.

The design goal of MOOSE is to give developers ultimate control over their physical models and applications. Designing new models or solving completely new classes of problems will be accomplished by writing standard C++ source code within the framework's class hierarchy. Scientists and engineers will be free to implement completely new algorithms using pieces of the framework where possible, and extending the framework's capabilities where it makes sense to do so. Commercial applications do not have this capability, and instead opt for either a more rigid parameter system or a limited application-specific metalanguage.

System Scope

MOOSE's scope is to provide a set of interfaces for building FEM simulations. Abstractions to all underlying libraries are provided.

Solving coupled problems where competing physical phenomena impact one and other in a significant nonlinear fashion represents a serious challenge to several solution strategies. Small perturbations in strongly-coupled parameters often have very large adverse effects on convergence behavior. These adverse effects are compounded as additional physics are added to a model. To overcome these challenges, MOOSE employs three distinct yet compatible systems for solving these types of problems.

First, an advanced numerical technique called the JFNK method is employed to solve the most fully-coupled physics in an accurate, consistent way. An example of this would be the effect of temperature on the expansion or contraction of a material. While the JFNK numerical method is very effective at solving fully-coupled equations, it can also be computationally expensive. Plus, not all physical phenomena in a given model are truly coupled to one another. For instance, in a reactor, the speed of the coolant flow may not have any direct effect on the complex chemical reactions taking place inside the fuel rods. We call such models "loosely-coupled". A robust, scalable system must strike the proper balance between the various modeling strategies to avoid performing unnecessary computations or incorrectly predicting behavior in situations such as these.

MOOSE's Multiapp system will allow modelers to group physics into logical categories where MOOSE can solve some groups fully-coupled and others loosely-coupled. The Multiapp system goes even further by also supporting a "tightly-coupled" strategy, which falls somewhere between the "fully-coupled" and "loosely-coupled" approaches. Several sets of physics can then be linked together into logical hierarchies using any one of these coupling strategies, allowing for several potential solution strategies. For instance, a complex nuclear reactor model might consist of several tightly-coupled systems of fully-coupled equations.

Finally, MOOSE's Transfers system ties all of the physics groups contained within the Multiapp system together and allows for full control over the flow of information among the various groups. This capability bridges physical phenomena from several different complementary scales simultaneously. When these three MOOSE systems are combined, myriad coupling combinations are possible. In all cases, the MOOSE framework handles the parallel communication, input, output and execution of the underlying simulation. By handling these computer science tasks, the MOOSE framework keeps modelers focused on doing research.

MOOSE innovates by building advanced simulation capabilities on top of the very best available software technologies in a way that makes them widely accessible for innovative research. MOOSE is equally capable of solving small models on common laptops and the very biggest FEM models ever attempted—all without any major changes to configuration or source code. Since its inception, the MOOSE project has focused on both developer and computational efficiency. Improved developer efficiency is achieved by leveraging existing algorithms and technologies from several leading open-source packages. Additionally, MOOSE uses several complementary parallel technologies (both the distributed-memory message passing paradigm and shared-memory thread-based approaches are used) to lay an efficient computational foundation for development. Using existing open technologies in this manner helps the developers reduce the scope of the project and keeps the size of the MOOSE code base maintainable. This approach provides users with state-of-the-art finite element and solver technology as a basis for the advanced coupling and solution strategies mentioned previously.

MOOSE's developers work openly with other package developers to make sure that cutting-edge technologies are available through MOOSE, providing researchers with competitive research opportunities. MOOSE maintains a set of objects that hide parallel interfaces while exposing advanced spatial and temporal coupling algorithms in the framework. This accessible approach places developmental technology into the hands of scientists and engineers, which can speed the pace of scientific discovery.

System Overview

System Context

MOOSE is a command-line driven application. This is typical for a high-performance software that is designed to run across several nodes of a cluster system. As such, all of the usage of the software is through any standard terminal program generally available on all supported operating systems. Similarly, for the purpose of interacting through the software, there is only a single user, "the user", which interacts with the software through the command-line. MOOSE does not maintain any back-end database or interact with any system daemons. It is a executable, which may be launched from the command line and writes out various result files as it runs.

Figure 1: Usage of MOOSE and MOOSE-based applications.

System Functions

Since MOOSE is a command-line driven application, all functionality provided in the framework is operated through the use of standard UNIX command line flags and the extendable MOOSE input file. The framework is completely extendable so individual design pages should be consulted for specific behaviors of each user-defined object.

User Characteristics

Framework Developers: These are the core developers of the framework. They will be responsible for following and enforcing the appropriate software development standards. They will be responsible for designing, implementing and maintaining the software.
Developers: A Scientist or Engineer that utilizes the framework to build his or her own application. This user will typically have a background in modeling and simulation techniques and/or numerical analysis but may only have a limited skill-set when it comes to object-oriented coding and the C++ language. This is our primary focus group. In many cases these developers will be encouraged to give their code back to the framework maintainers.
Analysts: These are users that will run the code and perform various analysis on the simulations they perform. These users may interact with developers of the system requesting new features and reporting bugs found and will typically make heavy use of the input file format.

Assumptions and Dependencies

The Xfem application is developed using MOOSE and is based on various modules, as such the SRS for Xfem is dependent upon the files listed at the beginning of this document.

References

ISO/IEC/IEEE 24765:2010(E). Systems and software engineering—Vocabulary. first edition, December 15 2010.

@manual{ISO-systems-software,
    author = "24765:2010(E), ISO/IEC/IEEE",
    title = "Systems and software engineering---Vocabulary",
    edition = "First",
    year = "2010",
    month = "December 15"
}

ASME NQA-1. ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications. first edition, August 31 2009.

@manual{ASME-NQA-1-2008,
    author = "NQA-1, ASME",
    title = "ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications",
    orginization = "American Socieity of Mechanical Engineers",
    year = "2009",
    month = "August 31",
    edition = "First"
}

Definitions and Acronyms

This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.

Definitions

- Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).

Acronyms

Acronym	Description
FEM	Finite Element Method
INL	Idaho National Laboratory
JFNK	Jacobian-Free Newton-Krylov
LGPL	GNU Lesser General Public License
MOOSE	Multiphysics Object Oriented Simulation Environment
NQA-1	Nuclear Quality Assurance Level 1
POSIX	Portable Operating System Interface
SRS	Software Requirement Specification

System Requirements

- A POSIX compliant Unix including the two most recent versions of MacOS and most current versions of Linux. - 4 GB of RAM for optimized compilation (8 GB for debug compilation), 2 GB per core execution - 100 GB disk space - C++17 compatible compiler (GCC, Clang) - Python 3.7+ - Git

Functional Requirements

xfem: Bimaterials
9.1.1The XFEM module shall have the capability to calculate mechanical response in two glued, layered materials with the interface location and material properties applied to on each side of the boundary determined by a level set function.
9.1.2The XFEM module shall have the capability to calculate mechanical response in a composite material matrix with an inclusion with the location of the inclusion boundary and material properties applied to the matrix and inclusion determined by a prescribed level set function.
9.1.3The system shall have the capability to calculate the mechanical response in two glued, layered materials with the interface location and automatic differentiation material properties applied to on each side of the boundary determined by a level set function.
9.1.4The XFEM module shall have the capability to calculate mechanical response in a composite material matrix with an inclusion with the location of the inclusion boundary and material properties applied to the matrix and inclusion determined by a prescribed level set function using automatic differentiation.

xfem: Checkpoint
9.2.1The XFEM module shall support outputting of checkpoint files.

xfem: Corner Nodes Cut
9.3.1The XFEM module shall have the capability of cutting directly through multiple nodes of a single QUAD4 element in 2D.
9.3.2The XFEM module shall be able to perform mesh cuts on any combination of the edges of elements and through elements including allowing cuts that go through the nodes on the same mesh.
9.3.3The XFEM module shall have the capability of perfoming mesh cuts on the edges of elements such that only two new nodes are generated to separate the previously connected elements.
9.3.4The XFEM module shall be capable of propagating an existing crack front along a prescribed cut in 2D.

xfem: Crack Tip Enrichment
9.4.1The XFEM module shall have the capability to include near-tip enrichment functions in 2D mechanics simulations.
9.4.2The XFEM module shall have the capability to include near-tip enrichment functions in 3D mechanics simulations.

xfem: Diffusion Xfem
9.5.1The XFEM Module shall have the capability to run 2D diffusion problems with prescribed values on the domain boundary (Dirichlet conditions) with a fixed position discontinuous interface through mesh elements.
9.5.2The XFEM Module shall have the capability to run 2D diffusion problems with prescribed solution values on the domain boundary (Dirichlet conditions) and prescribed boundary flux values (Neumann conditions) with a fixed position discontinuous interface defined by a geometric cut user object.
9.5.3The XFEM Module shall have the capability to run 2D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a level set function with the level set variable being a Moose Variable.
9.5.4The XFEM Module shall have the capability to run 2D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a prescribed level set function with the level set variable being a Moose AuxVariable.
9.5.5The XFEM Module shall have the capability to run 3D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a prescribed level set function with the level set variable being a Moose AuxVariable.

xfem: Init Solution Propagation
9.6.1The XFEM module shall retain the values of auxiliary variables on child nodes and elements after running the cutting algorithm, and initialize solution variables on newly created nodes with values from parent nodes in parallel

xfem: Mechanical Constraint
9.7.1The XFEM module shall permit applying a glued constraint across the XFEM interface for 2D solid mechanics problems.

xfem: Moment Fitting
9.8.1The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D solid mechanics problems
9.8.2The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D problems with a 4-point integration rule
9.8.3The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D problems with a 6-point integration rule

xfem: Moving Interface
9.9.1The XFEM module shall provide an ability to specify whether an XFEM cut surface should be healed independently for individual interfaces
9.9.2The XFEM module shall not output summary information on mesh changes when debug_output_level=0
9.9.3The XFEM module shall output summary information on mesh changes when debug_output_level=1
9.9.4The XFEM module shall output detailed information on mesh changes when debug_output_level=2
9.9.5The XFEM module shall output detailed information on mesh changes when debug_output_level=3
9.9.6The XFEM module shall provide an ability to solve bi-material mechanics problems where a moving material interface is defined by an XFEM surface, which is defined by a prescribed level set field.
9.9.7The XFEM module shall provide an ability to solve bi-material mechanics problems where a moving material interface is defined by an XFEM surface, which is defined by a prescribed level set field, while using the automatic differentiation capability.
9.9.8The XFEM module shall provide an ability to solve bi-material mechanics problems at finite strain where a moving material interface is defined by an XFEM surface, which is defined by a prescribed level set field.
9.9.9The XFEM module shall provide an ability to modify subdomain IDs based on an XFEM interface.
9.9.10The XFEM module shall provide an ability to solve bi-material diffusion problems where a moving material interface is defined by an XFEM surface, which is defined by a prescribed level set field.
9.9.11The XFEM module shall provide an ability to solve bi-material diffusion problems where a moving material interface is defined by an XFEM surface, which is defined by a prescribed level set field, while using automatic differentiation.
9.9.12The XFEM module shall provide an ability to solve a simple 2d phase transition problem in which the phase boundary is defined by and XFEM surface and the interface velocity depends on the jump of variables and gradients across the interface.
9.9.13The XFEM module shall provide an ability to solve a simple 3d phase transition problem in which the phase boundary is defined by and XFEM surface and the interface velocity depends on the jump of variables and gradients across the interface.
9.9.14The XFEM module shall provide an ability to solve a 2d simple phase transition problem in which the phase boundary is defined by and XFEM surface and the interface velocity depends on the jump of variables and gradients across the interface using the automatic differentiation capability.
9.9.15The XFEM module shall provide an ability to cut one block with a moving circle surface mesh in 2D.
9.9.16The XFEM module shall provide an ability to cut one block with a moving cylinder surface mesh in 3D.
9.9.17The XFEM module shall accurately solve 1D, xy problems with homogeneous material properties with a moving interface determined by a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.18The XFEM module shall accurately solve 1D, xy problems with material properties and a moving interface dependent on a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.19The XFEM module shall accurately solve 1D, xy problems with a moving interface separating two discrete materials prescribed by a user defined level set function with problem results verified using the Method of Manufactured Solutions.
9.9.20The XFEM module shall accurately solve 1D, rz problems with homogeneous material properties with a moving interface determined by a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.21The XFEM module shall accurately solve 1D, rz problems with material properties and a moving interface dependent on a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.22The XFEM module shall accurately solve 2D, xy problems with homogeneous material properties with a moving interface determined by a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.23The XFEM module shall accurately solve 2D, xy problems with material properties and a moving interface dependent on a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.24The XFEM module shall accurately solve 2D, rz problems with homogeneous material properties with a moving interface determined by a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.
9.9.25The XFEM module shall accurately solve 2D, rz problems with material properties and a moving interface dependent on a user prescribed level set function, and problem results are verified using the Method of Manufactured Solutions.

xfem: Pressure Bc
9.10.1The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 2D
9.10.2The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 3D
9.10.3The XFEM module shall permit application of pressure boundary conditions to inclined XFEM cut surfaces in 2D
9.10.4The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 2D finite deformation simulations

xfem: Second Order Elements
9.11.1The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using TRI6 elements.
9.11.2The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD8 elements.
9.11.3The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD9 elements.
9.11.4The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD9 elements when the XFEM cutting plane is prescribed using a level set field.
9.11.5The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using TET10 elements when the XFEM cutting plane is prescribed using a level set field.
9.11.6The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using HEX20 elements when the XFEM cutting plane is prescribed using a level set field.
9.11.7The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using HEX27 elements when the XFEM cutting plane is prescribed using a level set field.
9.11.8The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using QUAD8 elements.
9.11.9The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using QUAD9 elements.
9.11.10The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using TRI6 elements.

xfem: Side Integral
9.12.1The XFEM module shall properly integrate quantities on sides of cut elements that are intersected by the cutting plane in 2D
9.12.2The XFEM module shall properly integrate quantities on sides of cut elements that are intersected by the cutting plane in 3D

xfem: Single Var Constraint 2D
9.13.1The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a propagating XFEM interface for one variable.
9.13.2The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a propagating XFEM interface for one variable in a problem with another variable that does not have a constraint across that interface.
9.13.3The XFEM module shall provide an ability to apply zero-jump, zero-flux-jump constraints across a propagating XFEM interface for two variables.
9.13.4The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint on a stationary interface for one variable.
9.13.5The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump (defined by a Real value) constraint on a stationary interface for one variable.
9.13.6The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump (defined by a function) constraint on a stationary interface for one variable.
9.13.7The XFEM module shall provide an ability to apply a nonzero-jump (defined by a Real value), zero-flux-jump constraint on a stationary interface for one variable.
9.13.8The XFEM module shall provide an ability to apply a nonzero-jump (defined by a function), zero-flux-jump constraint on a stationary interface for one variable.
9.13.9The XFEM module shall provide an ability to apply a nonzero-jump, nonzero-flux-jump constraint on a stationary interface for one variable.
9.13.10The XFEM module shall provide an ability to apply a two-sided equal value constraint on a stationary interface for one variable.

xfem: Single Var Constraint 3D
9.14.1The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.
9.14.2The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.
9.14.3The XFEM module shall provide an ability to apply a nonzero-jump, zero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.
9.14.4The XFEM module shall provide an ability to apply a nonzero-jump, nonzero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.

xfem: Solid Mechanics Basic
9.15.1The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the average stress in the element at the crack tip exceeds a critical value.
9.15.2The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the average stress in the element at the crack tip exceeds a critical value defined by the value of a field variable.
9.15.3The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the stress at any of the quadrature points in the element at the crack tip exceeds a critical value defined by the value of a field variable.
9.15.4The XFEM module shall permit definition of a stationary crack in a 3D mechanics model with XFEM, where the crack is defined using a rectangular cutting plane by RectangleCutUserObject
9.15.5The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject and allowed to propagate with growth speeds determined by the fatigue cracking Paris law
9.15.6The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject and allowed to propagate with growth directions determined by the maximum hoop stress law
9.15.7The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject
9.15.8The XFEM module shall permit definition of a stationary crack in a 3D mechanics model with XFEM, where the crack is defined using an elliptical cutting plane by EllipseCutUserObject
9.15.9The XFEM system shall permit computation of fracture domain integrals in 3D mechanics problems where a stationary embedded circular crack is defined by a cutting plane geometry and points along the crack front for the domain integral are explicitly specified.
9.15.10The XFEM system shall permit computation of fracture domain integrals in 3D mechanics problems where a stationary embedded circular crack is defined by a cutting plane geometry and points along the crack front for the domain integral provided by a class that derives from CrackFrontPointsProvider.
9.15.11The XFEM system shall permit branched cracks to be represented in 2D by sequentially cutting a 4-noded quadrilateral element by two prescribed evolving cutting planes
9.15.12The XFEM system shall permit branched cracks to be represented in 2D by sequentially cutting a 3-noded triangle element by two prescribed evolving cutting planes
9.15.13The XFEM system shall provide an accessor function to the crack_tip_origin_direction_map

xfem: Switching Material
9.16.1The XFEM module shall provide an ability to switch materials for one stationary cut.
9.16.2The XFEM module shall provide an ability to switch materials for one moving cut.
9.16.3The XFEM module shall allow switching materials based on the side of an interface for a single moving cut defined using a mesh as the cutting object.
9.16.4The XFEM module shall provide an ability to switch materials for two stationary cuts.
9.16.5The XFEM module shall provide an ability to switch materials for two moving cuts.

Usability Requirements

Performace Requirements

System Interfaces

System Operations

Human System Integration Requirements

MOOSE is a command line driven application which conforms to all standard terminal behaviors. Specific human system interaction accommodations shall be a function of the end-user's terminal. MOOSE does support optional coloring within the terminal's ability to display color, which may be disabled.

Maintainablity

- The latest working version (defined as the version that passes all tests in the current regression test suite) shall be publicly available at all times through the repository host provider. - Flaws identified in the system shall be reported and tracked in a ticket or issue based system. The technical lead will determine the severity and priority of all reported issues and assign resources at his or her discretion to resolve identified issues. - The software maintainers will entertain all proposed changes to the system in a timely manner (within two business days). - The core framework in its entirety will be made publicly available under the LGPL version 2.0 license.

Reliability

The regression test suite will cover at least 80% of all lines of code at all times. Known regressions will be recorded and tracked (see Maintainablity) to an independent and satisfactory resolution.

System Modes and States

MOOSE applications normally run in normal execution mode when an input file is supplied. However there are a few other modes that can be triggered with various command line flags as indicated here:

Command Line Flag	Description of mode
`-i <input_file>`	Normal execution mode
`--split-mesh <splits>`	Read the mesh block splitting the mesh into two or more pieces for use in a subsequent run
`--use-split`	(inplies -i flag) Execute the the simulation but use pre-split mesh files instead of the mesh from the input file
`--yaml`	Output all object descriptions and available parameters in YAML format
`--json`	Output all object descriptions and available parameters in JSON format
`--syntax`	Output all registered syntax
`--registry`	Output all known objects and actions
`--registry-hit`	Output all known objects and actions in HIT format
`--mesh-only` (implies -i flag)	Run only the mesh related tasks and output the final mesh that would be used for the simulation
`--start-in-debugger <debugger>`	Start the simulation attached to the supplied debugger

note

The list of system-modes may not be extensive as the system is designed to be extendable to end-user applications. The complete list of command line options for applications can be obtained by running the executable with zero arguments. See the command line usage.

Phyisical Characteristics

MOOSE is software only with no associated physical media. See System Requirements for a description of the minimum required hardware necessary for running a MOOSE-based application.

Environmental Conditions

Not Applicable

System Security

MOOSE based applications have no requirements or special needs related to system-security. The framework is designed to run completely in user-space with no elevated privileges required nor recommended.

Information Management

The core framework in its entirety will be made publicly available on an appropriate repository hosting site. Backups and security services will be provided by the hosting service.

Polices and Regulations

MOOSE-based applications must comply with all export control restrictions.

System Life Cycle Sustainment

MOOSE-based development follows various agile methods. The system is continuously built and deployed in a piecemeal fashion since objects within the system are more or less independent. Every new object requires a test, which in turn requires an associated requirement and design description. Some MOOSE-based development teams follow the NQA-1 standards.

Packaging, Handling, Shipping and Transportation

No special requirements are needed for packaging or shipping any media containing MOOSE source code. However, some MOOSE-based applications maybe be export controlled in which case all export control restrictions must be adhered to when packaging and shipping media.

Verification

The regression test suite will employ several verification tests using comparison against known analytical solutions, the method of manufactured solutions, and convergence rate analysis.

Introduction
System Overview
References
Definitions and Acronyms
System Requirements
Verification