On the use of metamodeling for relating requirements and architectural design decisions

  • Authors:
  • Diego Dermeval;Jaelson Castro;Carla Silva;João Pimentel;Ig Ibert Bittencourt;Patrick Brito;Endhe Elias;Thyago Tenório;Alan Pedro

  • Affiliations:
  • Universidade Federal de Pernambuco (UFPE), Recife, Pernambuco -- Brazil;Universidade Federal de Pernambuco (UFPE), Recife, Pernambuco -- Brazil;Universidade Federal de Pernambuco (UFPE), Recife, Pernambuco -- Brazil;Universidade Federal de Pernambuco (UFPE), Recife, Pernambuco -- Brazil;Universidade Federal de Alagoas (UFAL), Maceió, Alagoas -- Brazil;Universidade Federal de Alagoas (UFAL), Maceió, Alagoas -- Brazil;Universidade Federal de Alagoas (UFAL), Maceió, Alagoas -- Brazil;Universidade Federal de Alagoas (UFAL), Maceió, Alagoas -- Brazil;Universidade Federal de Alagoas (UFAL), Maceió, Alagoas -- Brazil

  • Venue:
  • Proceedings of the 28th Annual ACM Symposium on Applied Computing
  • Year:
  • 2013

Quantified Score

Hi-index 0.00

Visualization

Abstract

Requirements models can be used to describe what is expected from a software system. On the other hand, architectural models can describe the structure of a system in terms of its components and connectors. However, these models do not capture the rationale of the decisions made during architectural design. This knowledge is important throughout the maintenance and evolution of the system, as it allows a better understanding of the system as well as the impact of changes on it. In this paper, we consider existing proposals for architectural decisions documentation to define a template for recording the rationale of architectural design decisions. This template is based on a metamodel, which borrows concepts from the NFR Framework to express such rationale. Documenting decisions enables the evaluation of architectural design alternatives when requirements evolve or when new alternatives are devised. Moreover, the metamodel provides a relationship between requirements and architectural design fragments, facilitating the maintenance of traceability between the problem and the solution. We illustrate and discuss the use of this metamodel in the context of Acme architectural models and i* requirements models.