ATRAF-driven IMRaD Methodology: Tradeoff and Risk Analysis of Software Architectures Across Abstraction Levels
Amine Ben Hassouna
TL;DR
The paper tackles the misalignment between industrial software-architecture evaluation practices and academic reporting norms by introducing the ATRAF-driven IMRaD Methodology, which maps ATRAF’s spiral evaluation of Software Architectures, Reference Architectures, and Architectural Frameworks to the IMRaD structure. It details how ATRAF’s phases (Scenario and Requirements Gathering, Architectural Views and Scenario Realization, Attribute-Specific Analyses, and Sensitivity/Tradeoff/Risk Analysis) can be presented within Introduction, Methods, Results, and Discussion sections, including artifact selection and reporting guidelines. The methodology defines Light and Full adoption levels to accommodate resource constraints while preserving rigor, and specifies where to place artifacts, reports, and results to ensure traceability and reproducibility. Through future case studies reframing RTSA, RTSRA, and RMAF as IMRaD-formatted academic papers, the work aims to validate generalizability across abstraction levels and strengthen scholarly communication in software architecture research.
Abstract
Software architecture research relies on key architectural artifacts -- Software Architectures, Reference Architectures, and Architectural Frameworks -- that underpin the design and analysis of complex systems. Evaluating these artifacts is essential to assess tradeoffs and risks affecting quality attributes such as performance, modifiability, and security. Although methodologies like the Architecture Tradeoff Analysis Method (ATAM) support software architecture evaluation, their industrial focus misaligns with the IMRaD (Introduction, Methods, Results, Discussion) format prevalent in academic research, impeding transparency and reproducibility. Our prior work introduced the Architecture Tradeoff and Risk Analysis Framework (ATRAF), extending ATAM through three methods -- ATRAM, RATRAM, and AFTRAM, addressing all abstraction levels, using a unified, iterative four-phase spiral model. These phases -- Scenario and Requirements Gathering, Architectural Views and Scenario Realization, Attribute-Specific Analyses, and Sensitivity, Tradeoff, and Risk Analysis -- ensure traceability and coherence. This paper presents the ATRAF-driven IMRaD Methodology, a concise method to align ATRAF's phases with IMRaD sections. This methodology enhances the rigor, transparency, and accessibility of software architecture research, enabling systematic reporting of complex evaluations.