Abstract: The Australian Department of Defence is on the cross-roads of transitioning from DoDAF Version 1.5 to AUSDAF Version 2.0, which is a variant of DoDAF Version 2.0. Whilst the philosophy between these two versions of the framework are distinctly different, the Systems Engineer (SE) often receives a mix of Defence clients adopting either one of the pseudo architecture standards for specification development. In order to accommodate this spectrum of customers’ methodology recommendations, the aim of this paper is to address the diverse range of clients. Attention is given, not only to the execution of the methodologies, but also to the approaches we take to align with the Australian Defence two pass approval process. In this paper, a tool agnostic process for architecture development is introduced to support most architecture tasks performed in Defence. Furthermore, the process incorporates association of the process artefacts with a few acquisition-based standards, which often used by most systems engineering tasks.