What Do Software Architects Think They (Should) Do?

Sherman, Sofia; Unkelos-Shpigel, Naomi

doi:10.1007/978-3-319-07869-4_20

Cited by 4 publications

(2 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This study is a part of broader research that aims to define the role of the architect based on two examinations: (1) the definition of this role in the literature (what an architect is expected to do), and (2) the definition of this role as perceived by professional architects, based on what they actually do in practice as well as what they believe they should do. Our preliminary results [6] suggest that there are several gaps between literature and practice, and that architects, besides their role as technical experts, perform additional practices related to soft aspects. This study may help practitioners in better understanding the soft aspects of the role of the architect, as well as help educators, who teach software architecture, to emphasis the soft aspects of this role.…”

Section: Introductionmentioning

confidence: 89%

See 1 more Smart Citation

Toward Defining the Role of the Software Architect

Sherman

Hadar

2015

2015 IEEE/ACM 8th International Workshop on Cooperative and Human Aspects of Software Engineering

Self Cite

View full text Add to dashboard Cite

Software architecture is integral part of the software development; however, its integration in the development process has become more challenging with the transition from traditional to agile development methods, and with the architects becoming much more than technological experts responsible for high-level design. Some attention has been paid in recent years to the role of the architect, seeking a contemporary and comprehensive definition of this role. This paper reports on the results of an online survey, with the participation of 104 software architects, aimed at defining the soft aspects of the software architect's role. The results reveal that architects perform a variety of human-centered activities such as mentoring, leadership, reviewing and management,. Moreover, in the contexts of mentoring and leadership, software architects strive to do more than they currently do.

show abstract

Section: Introductionmentioning

confidence: 89%

“…Based on literature review as well as results from our previous study [6], we developed an online survey 1 that consisted of 43 questions organized in eight main areas (see Table 2). These questions included 35 closed-ended and eight open-ended questions (one open question at the end of the question set per area).…”

Section: A Data Elicitationmentioning

confidence: 99%

Toward Defining the Role of the Software Architect

Sherman

Hadar

2015

2015 IEEE/ACM 8th International Workshop on Cooperative and Human Aspects of Software Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

Leveraging Usage Data of Software Architecture Artefacts

Grundy

Hosking

et al. 2019

2019 IEEE/ACM 2nd International Workshop on Establishing the Community-Wide Infrastructure for Architecture-Based Software Engi

View full text Add to dashboard Cite

Aligning Software Architecture Training with Software Industry Requirements

Y.¹,

Ariel²,

Kiwelekar³

2023

Int. J. Soft. Eng. Knowl. Eng.

View full text Add to dashboard Cite

The activities of software design, documenting, and evaluating the structure of software systems, referred to as Software Architecture, have been increasingly getting significant attention in industries. This situation is because of the explicit and prominent role assigned to quality attributes while developing software systems. By considering the high relevance of Software Architecture to industry, many academic institutes have introduced a course on Software Architecture as a part of undergraduate programs in Software Engineering. However, teachers offering this course face numerous challenges. Some of these challenges stem from how software architecture is practised in industries and others from teaching them in an academic setting. This paper describes an experience of designing a software architecture course that aligns the competencies expected from professional software architects with teaching practices imparting those competencies. Such an alignment is necessary to improve the employability of graduate students, make their progression from academic institutes to industries an effortless one, and for better learning outcomes. In the absence of such alignment, fresh graduates need to re-train, leading to training costs and delayed recruitment of fresh graduates by their prospective employers. The experience reports recurring challenges observed by earlier researchers, strategies to address them and our experience in implementing those strategies. The teaching strategies suggested are potentially helpful and practical, especially to less-experienced instructors teaching a course on Software Architecture.

show abstract

What Do Software Architects Think They (Should) Do?

Cited by 4 publications

References 7 publications

Toward Defining the Role of the Software Architect

Toward Defining the Role of the Software Architect

Leveraging Usage Data of Software Architecture Artefacts

Aligning Software Architecture Training with Software Industry Requirements

Contact Info

Product

Resources

About