eXtensible Flight System (XFS) Design Strategies
Conventional Wisdom
Separate data busses for each connection
Flight deck and sensors from same vendor
Pilot determines state
Vendor keeps source code and test artifacts proprietary
Aircraft specific hardware and software changes
Complex, highly integrated single applications
Software written for specifichardware
Avilution XFS Approach
Unified data buses with redundancy
Vendor agnostic including physical interface
Software determines state
Source code and test artifacts shared with customer
Aircraft specific hardware and software configuration
Collection of simple and stand-alone micro services
Software written to be agnostic to h/w and O/S