Software Flexibility vs Certification
Architect software to separate safety-critical from updateable functions so patches deploy through automated regression testing without triggering full system reverification.
CyberTRIZ analysis · Space contradiction TSI004 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Software-defined spacecraft can change operating modes, correct defects, add capabilities, and adapt to new mission requirements after launch. However, frequent software changes can invalidate previous verification evidence and create configuration-management challenges. Applying complete certification or assurance processes after every modification can make useful updates prohibitively slow.
Space TRIZ Resolution
Software architecture should separate stable safety-critical functions from configurable and frequently updated capabilities. Modular verification boundaries, controlled interfaces, automated regression testing, staged deployment, and rollback mechanisms allow individual software elements to change without requiring complete system reverification.
Applicable TRIZ Principles
Principle 1 – Segmentation separates stable critical software from updateable functions.
Principle 10 – Prior Action establishes verification and rollback mechanisms before updates are deployed.
Principle 15 – Dynamics allows software capability to evolve within controlled architectural boundaries.
Expected Outcome
Greater software flexibility
Maintained assurance integrity
Faster deployment of updates
Reduced reverification workload
Decision Indicators
Early indicators include:
Minor software modifications require complete system verification.
Necessary updates are delayed because certification effort is excessive.
Critical and noncritical functions share unnecessary dependencies.
Configuration control becomes difficult after repeated updates.
Software improvements are avoided despite clear mission value.