Software Technology Readiness

From Earth Science Information Partners (ESIP)
Revision as of 14:06, February 5, 2020 by Dan Keyes (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)


Current Technology Readiness Level (TRL) definitions are largely considered to be unusable for software projects and for integration of HW and SW. The other motivation is driving improvements in way we put things together to create an operational capability.


To produce formal documentation (guidance, formal recommendations or another artifact artifact/model) which clearly addresses the lack of information related to software technology readiness. The recent Operational Readiness Guidance (ORL) guidance [0] produced by the ESIP Disasters Lifecycle Cluster is a good example of how this kind of thing doesn’t need to be overly complex as long as the intent is clearly communicated and suitably purposed… which current guidance is not!



  • Latest News 1
  • Latest News 2



Get Involved

  • Contact Chair:
    • Lewis McGibbney, Chair
    • Kel Markert, Co-Chair