FENIX Software Quality Assurance Documentation

[cticenhour]

Reason

So that FENIX is held to a high software standard (and in order to facilitate easy movement of code to MOOSE when/if desired), software quality assurance documentation should be created and managed as part of the FENIX development process.

This Issue should be the main issue referenced when working with FENIX SQA.

Design

Here, I mean "software quality assurance documents" to mean:

• NQA-1 compliance documents (RTM, SDD, SRS, etc.)
• Code standards documents
• Contribution documents
• Getting started documents
• ....and probably more in this vein that is currently forgotten.

Impact

This will add new documentation to FENIX to make the onboarding and development process easier for the FENIX community.