Some units in types.ads are defined as floating-point types and others
as signed integer types. Start using the dimension system in GNAT on
floating-point units. Next step is to see if there is a benefit in using
floating-point types instead of signed integer types for the input and
output types, so that we can use the standard dimension system. Otherwise,
we could use a signed integer type with the Dimension_System aspect as
the root type for all these signed integer types.

Description of the architecture at multi-system level (layer 0).
Description of the incremental approach to architecture development.
Fail-safe design rationale, considerations on fault tolerance and development assurance.

Fix typos

This document provides a selection of regulatory safety objectives from CS 25 Amendment 18 (2016), the European airworthiness regulation for large aéroplanes  (FAR 25 in the US).. 
It is the entry point to carry out the safety case on muXAV using the Overarching Properties and their satisfiability criteria.
The document also provides the Accepted Means of Compliance associated to the selected CS paragraphs. It is intended to provide material supporting assessment of the OPs and criteria as a candidate AMC against CS/FAR 25.1309. and AMC 25.1309.

Updated after June workshop

The Air vehicle level Functional Hazard Analysis  (AFHA) identifies the Failure Conditions (FCs), their effects, and the severity classes of these effects. 
It is an input of many activities pertaining to the safety assessment process. In particular, it is requested for performing the Preliminary  Air vehicle level Safety Assessment (PASA).
The Failure Conditions are also requested when evaluating satisfiability of the Overarching Properties