A complete list of available 3rd Party Software can be found in the FSA TRM Standards List
(internal FSA use only). This TRM (Technical Reference Model) contains software items that have been classified into one of 6 different dispositions:
Recommended (recommended for use) - Products or technologies recommended for use.
Baseline (in use today) - Products or technologies currently allowed, but not supported.
Containment (no new development) - Products or technologies slated for limited investment (use).
Emerging (under evaluation) - Products or technologies to be evaluated.
Dependent (a dependency for something else) - Products or technologies likely in use (as a dependency), but not necessarily recommended.
Retirement (to be eliminated) - Products or technologies slated for de-investment.
The majority of 3rd Party Software that is delivered as a jar file is managed via Maven in the Nexus repository. The repository can be accessed via two methods (internal FSA use only): Nexus Search GUI
or Nexus Index
. Contact the Architecture Office
if you have questions about any of the items in Nexus or the TRM spreadsheet, or if you need something added to the repository. Requests to add artifacts to the repository will generally fall into one of two categories:
1. Artifact Upgrades - minor version upgrades of existing artifacts where the item is currently available in another central Maven repository. Getting the artifact added to Nexus could be as simple as providing the Artifact ID, Group ID, and the requested version number.
2. Emerging Artifacts
- as stated above, these are products or technologies that need to be evaluated, with the intent of eventually changing the disposition to Recommended or Containment, depending on the results of the evaluation. To request an Emerging Artifact, send an email to the AO. The questions that should be addressed in the email are documented in the Artifact Request Email
. Additionally, Emerging Artifacts require the completion of an Architectural Decision (AD)
after the evaluation period.
Note: The expectation for the AD is that, at a minimum, a source of contact is documented for the new technology. The amount of effort put into the AD may vary.
New software download requests may require certification by the IO Lab. These requests are independent of Maven. See the Software Acquisition Summary
(internal FSA use only) for specific details.
The items listed below are considered approved software, but are not available in Nexus:
These links are protected by eAuthentication and restricted to FSA employees and contractors with eAuthentication Level 2 access.