The Nature of Questions that Arise During Software Architecture Design

被引:0
作者
Harrison, Neil B. [1 ]
Aguiar, Ademar [2 ]
机构
[1] Utah Valley Univ, Orem, UT 84058 USA
[2] Univ Porto, Fac Engn, INESC TEC, Porto, Portugal
来源
SOFTWARE ARCHITECTURE, ECSA 2024 | 2024年 / 14889卷
关键词
Software Architecture; Requirements; Quality Attributes; REQUIREMENTS;
D O I
10.1007/978-3-031-70797-1_3
中图分类号
TP3 [计算技术、计算机技术];
学科分类号
0812 ;
摘要
During the process of software architectural design, numerous questions arise which must be answered. These questions may be about requirements on the proposed system (the problem space) or about how the system should be designed and developed (the solution space). As questions arise they may be answered immediately, deferred until later, or provisionally answered with an assumption about the answer. The objective of this work was to explore the nature of questions that arise during architecture. We explored the types of questions, how they are organized, how they are tracked, and how and when they are answered. We started by surveying highly experienced architects about their practices with respect to architectural questions. We also performed a controlled experiment with master students about organizing architectural questions that clarified and substantiated the survey data. We learned that architectural questions include slightly more questions about the problem space than the solution space, as well as a minority of questions related to the managing of the project. We found that architects often use ad hoc methods to organize and track them, although they typically organize them along more than one dimension. We learned also that, about a third of the time, architects make assumptions about the answers to architectural questions in order to make progress on the architecture. This suggests that some projects may have risks of incorrect design or later costly rework due to inadequate tracking or incorrectly answered architectural questions.
引用
收藏
页码:37 / 52
页数:16
相关论文
共 17 条
  • [1] Towards an Approach to Stimulate Architectural Thinking during Requirements Engineering Phase
    Anish, Preethu Rose
    [J]. 2016 IEEE 24TH INTERNATIONAL REQUIREMENTS ENGINEERING CONFERENCE (RE), 2016, : 421 - 426
  • [2] [Anonymous], Software Systems Architecture course, Master in Informatics and Computing Engineering
  • [3] Bastani B., 2007, ACM SIGSOFT Software Engineering Notes, V32, P1, DOI [10.1145/1234741.1234753, DOI 10.1145/1234741.1234753]
  • [4] From software requirements to architectures
    Castro, J
    Kramer, J
    [J]. PROCEEDINGS OF THE 23RD INTERNATIONAL CONFERENCE ON SOFTWARE ENGINEERING, 2001, : 764 - 765
  • [5] Characterizing Architecturally Significant Requirements
    Chen, Lianping
    Babar, Muhammad Ali
    Nuseibeh, Bashar
    [J]. IEEE SOFTWARE, 2013, 30 (02) : 38 - 45
  • [6] Clements P., 2011, Documenting Software Architectures: Views and Beyond, Vsecond
  • [7] Harrison N.B., 2006, EUROPLOP, P691
  • [8] Capturing notable architectural decisions
    Harrison, Neil B.
    Rudolph, George
    Tang, Jingpeng
    Thackeray, Lynn
    Wagstaff, David
    [J]. 2023 IEEE 20TH INTERNATIONAL CONFERENCE ON SOFTWARE ARCHITECTURE COMPANION, ICSA-C, 2023, : 179 - 182
  • [9] Jansen A, 2006, 5TH WORKING IEEE/IFIP CONFERENCE ON SOFTWARE ARCHITECTURE, PROCEEDINGS, P109
  • [10] Kazman R., 1998, P 3 INT WORKSH SOFTW, P85, DOI [10.1145/288408.288430, DOI 10.1145/288408.288430]