The whole development process is a large set of processes that are multiple and interdependent in terms of work products. In this context, SOAR was conceived to allow for creating process instances in consonance with whole SoS development process. For this, we established an interface with inputs and outputs that must be adequately dealt in the general development process. Our approach is compatible with the general process for SoS development from DoD, which describes a general development process at systems engineering level that reflects the current the state-of-the-art in Acknowledged SoS projects. The figure below represents how SOAR can be executed in the context of an iterative and evolutionary development cycle of Acknowledged SoS projects. At the central strip, the architecting processes are executed receiving the general context analysis performed at system engineering level and delivering to implementation stages the SoS validated architecture with its different layers, i.e., physical, organizational, software, etc. SOAR is conceived to support the architecting process at software layer and its activities are performed at this stage, delivering the respective software architecture. Despite the communication with other external processes of SoS development is considered in SOAR structure, software architecture is the central concern to be encompassed in SOAR instances.