Guiding philosophies
- Demonstrate advanced & innovative capabilities continuously and incrementally.
- Drop capabilities and re-architect if demonstration reveals fundamental flaws.
- Identify critical elements and test them thoroughly
- Define full interfaces backed by reduced, but functional implementations
- Unimplemented components must not lead to failure of code.
Capabilities
The Tethys/LRAUV software development plan is divided in the following sections:
- Modular Architecture
- Simulation
- Vehicle control
- Dependency-based execution within a computation cycle
- Ability to fall-back on abstract alternative to a faulty function input
- Missions including sub-sequences, triggers, and re-entrant states
- Hardware control
- Data transmission and command/control via limited/intermittent/noisy communications channels.
- Actuator failure recovery
- Assisted script generation
- Ship/Shore Side Tools
- Hardening
Progress Symbols
In planning phase, not started, or not working at all
Broken, not working, or working with major bugs
Partially working
Mostly working
Working well (inc'l test, if applicable)
Urgency Symbols (for incomplete items)
!! Required to operate vehicle in water first time (with developer & day estimate)
–HS Required in 2009 for high speed ( followed by developer & day estimate)
–LS Required in 2009 for low speed ( followed by developer & day estimate)
–MM Required in 2009 for multimode (followed by developer & day estimate)
–SO Required in 2009 for science operations (followed by developer & day estimate)
__ Not a requirement, but may be very useful
(developers include MG, BK, and RM)
