Public:ARHUDFM Traction: Difference between revisions

From Wiki Furtherium
Line 2,263: Line 2,263:


   bar:0 width:1
   bar:0 width:1
     textcolor:red at:15/11/2024 shift:(-35,-4) text:Pre-Seed
     textcolor:red at:15/09/2024 shift:(-35,-4) text:Pre-Seed
     textcolor:red at:15/11/2025 shift:(-15,-4) text:Seed
     textcolor:red at:15/05/2025 shift:(-15,-4) text:Seed
     textcolor:red at:15/11/2026 shift:(-30,-4) text:round A
     textcolor:red at:15/11/2025 shift:(-30,-4) text:round A
     textcolor:red at:15/11/2028 shift:(-30,-4) text:round B
     textcolor:red at:15/11/2027 shift:(-30,-4) text:round B


   bar:99 width:1
   bar:99 width:1
Line 2,272: Line 2,272:
     textcolor:oceanblue at:01/10/2025 shift:(-25,-4) text:MVP Beta >
     textcolor:oceanblue at:01/10/2025 shift:(-25,-4) text:MVP Beta >
     textcolor:oceanblue at:01/07/2026 shift:(-25,-4) text:MMP Gamma >
     textcolor:oceanblue at:01/07/2026 shift:(-25,-4) text:MMP Gamma >
     textcolor:oceanblue at:01/10/2026 shift:(15,-4) text:Delta >
     textcolor:oceanblue at:01/10/2026 shift:(15,-4) text:MMP Delta >


LineData=
LineData=
Line 2,288: Line 2,288:


}}
}}
...
...


==Future ideas==
==Future ideas==

Revision as of 17:45, 13 July 2024

Traction

U.S. Defense ProgramsU.S. Defense ProgramsPublic:ARHUDFM FAQFurtherium, Inc.Public:ARHUDFM Features Summary
TRL NASA usage DoD usage[1] European Union
1 Basic principles observed and reported Scientific research begins to be translated into applied R&D Basic principles observed
2 Technology concept and/or application formulated Invention begins. Once basic principles are observed, practical applications can be invented Technology concept formulated
3 Analytical and experimental critical function and/or characteristic proof-of concept Active R&D is initiated. This includes analytical studies to produce code and laboratory studies to physically validate analytical predictions of separate technology HW/SW elements Experimental proof of concept
4 Component and/or breadboard validation in laboratory environment Basic technological components are integrated to establish that they will work together. System SW architecture development initiated to include interoperability, reliability, maintainability, extensibility, scalability and security issues Technology validated in lab
5 Component and/or breadboard validation in relevant environment The basic technological HW/SW components are integrated with reasonably realistic supporting elements so that they can be tested in a simulated environment Technology validated in relevant environment (industrially relevant environment in the case of key enabling technologies)
6 System/subsystem model or prototype demonstration in a relevant environment (ground or space) Examples include testing a prototype in a high-fidelity lab environment or a live/virtual experiment or in a simulated operational environment Technology demonstrated in relevant environment (industrially relevant environment in the case of key enabling technologies)
7 System prototype demonstration in a space environment Prototype near, or at, planned operational system. Algorithms run on processor of the operational environment integrated with actual external entities. SW support structure in place. SW releases are in distinct versions. Frequency and severity of SW deficiency reports do not significantly degrade functionality or performance. Verification, Validation and Accreditation (VV&A) completed System prototype demonstration in operational environment
8 Actual system completed and "flight qualified" through test and demonstration (ground or space) Technology and SW has been proven and demonstrated to work in its final form and under expected conditions. In almost all cases, TRL represents the end of true system development. Examples include developmental test and evaluation (T&E) of the system in its intended weapon system to determine if it meets design specifications System complete and qualified
9 Actual system "flight proven" through successful mission operations In almost all cases, this is the end of the last “bugfixing” aspects of system development. Examples include using the system under operational mission conditions. SW releases are production versions and configuration controlled. Frequency and severity of SW deficiencies are at a minimum Actual system proven in operational environment (competitive manufacturing in the case of key enabling technologies; or in space)

Roadmap

redirect Main Article: Public:Business_Tables

Public:ARHUDFM Features Summary

Version 4

Public:ARHUDFM Features Summary

Future ideas

Further reading

FAQ

See also

Public External Sections: Public Wiki Sections: Public Wiki Sections: Not-Public Wiki Sections:

Note: Unless otherwise stated, whenever the masculine gender is used, both men and women are included.

See also product details

Hardware Details: Functional Apps Details: Executive Apps Details: Service Apps Details:


References

  1. Dr. John Niemela and Dr. Matthew Fisher, The Use of Technology Readiness Levels for Software Development

External links