Connecting the V-Model and Axiomatic Design: an analysis how systems engineering methodologies relate

V-Model and Axiomatic Design are two proven systems engineering methodologies to support the design process of complex systems. Both methodologies originated in the late seventies. The V-Model is the more successful of the two, partly due to its simplicity and straightforwardness. AD is more powerful but also more complex. AD has a clear way of requirements management in domains that represent the customer needs, system functionality, physical execution, and manufacturing processes. Both models are generally seen as independent from each other. Also, in teaching courses they are considered two separate methodologies. In this paper it is investigated what the overleap of the V-Model and Axiomatic Design is, and if there can be defined a continuous learning path for (professional) teaching from V-Model to Axiomatic Design. The overlap appears to be quite substantial, the execution process of the V-Model can be seamlessly mapped on the process of Axiomatic Design, making the V-Model mainly a subset of Axiomatic Design. Axiomatic Design contributes to the V-Model. It improves understanding of the V-Model because Axiomatic Design clarifies artifacts that are not consciously embedded in the v-model but are still present.