A Week in the Life of an Architect

Buschmann, Frank

doi:10.1109/ms.2012.55

Cited by 7 publications

(16 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…They neither match with my own practice in handling NFRs, 4 nor with what I knew from other architects. Software quality, such as security, safety, or usability, is often explicitly marketed; it can even create a unique selling proposition.…”

Section: Discussionmentioning

confidence: 82%

Architecture Quality Revisited

et al. 2012

Self Cite

View full text Add to dashboard Cite

A recent study suggests that nonfunctional quality is of little relevance to users and customers but mainly a concern for architects. Nontechnical constraints appear to be driving design as prominently as quality requirements. The PragmaTic archiTecTA recent study, "Non-Functional Requirements in Software Architecture Practice," investigates how architects deal with nonfunctional requirements (NFRs) in their daily practices. 1 The results appear contradictory to the common belief that nonfunctional quality is fundamentally important for architecture sustainability and project success. 2,3 In a nutshell, the study suggests that nonfunctional quality is of little relevance for users and customers, and is instead primarily a concern for software architects. It's thus tempting to conclude that practitioners consider nonfunctional qualities as an afterthought, rather than as a prime driver of architecture design. The study raises several thoughtprovoking questions: Does the research community actually overestimate the relevance of nonfunctional qualities? Is practitioners' understanding about the real importance of architecture quality amiss? What do these results imply? the studyThe study focused on 13 software architects working in Spanish organizations covering a spectrum of application domains. It used exploratory qualitative research with semistructured interviews centered on a single project. The projects themselves varied in functionality, size, and project staff involvement.In this column, we focus on questions and results from the study that we believe have the biggest impact on actual architecture design:

show abstract

Section: Discussionmentioning

confidence: 82%

Architecture Quality Revisited

et al. 2012

Self Cite

View full text Add to dashboard Cite

show abstract

“…(Buschmann & Henney, 2013) and to remove any obstacle that blocks the team's agility and frustrates the stakeholders (Mirakhorli & Cleland-Huang, 2013). He must have a clear architectural vision (Buschmann, 2012), to think beyond structure and technology by dealing with the structure of organization and production infrastructure (Nord et al, 2014), spending the most time with people living with his decisions (Buschmann, 2012).…”

Section: Understanding the Role Responsibilities And Competencies Ofmentioning

confidence: 99%

“…Although decisions can be made by the team, the architect takes care that the decisions are consistent throughout the system, even when multiple teams work simultaneously, thus protecting the conceptual integrity of architecture and design. The architect has leadership qualities (Buschmann, 2012), technical knowledge and experience in design (Buschmann & Henney, 2013).…”

Section: Understanding the Role Responsibilities And Competencies Ofmentioning

confidence: 99%

“…The combination of agile and lean practices, and the application of a lean concept for flow management, enables visualization, monitoring of technical debt and errors, balancing the allocation of critical architectural tasks and improving process flows, contributing to the reduction of total delay and number of errors/corrections (Buschmann, 2012). The application of lean approach has the potential to unify architecturally important tasks with functionalities, as opposed to agile methods that mainly create artificial boundaries, so defining tasks becomes a major problem (Nord et al, 2012).…”

Section: Application Of Lean Principles and Practicesmentioning

confidence: 99%

“…Undefined quality attributes are the causes of design, documentation and code problems (Prause & Durdik, 2012). In order to support a continuous flow of values, prioritization needs to consider the dependence between functional stories and non-functional requirements (quality attributes), and consequently, the dependent functional requirements earlier in development should be withdrawn (Buschmann, 2012;Nord et al, 2012;Fontdevila & Salias, 2013).…”

Section: Quality Attributes -Continuous Focus and Prioritizationmentioning

confidence: 99%

See 2 more Smart Citations

Agile architecture in the digital era: Trends and practices

Dragičević¹,

Bošnjak²

2019

Strategic Management

View full text Add to dashboard Cite

The speed of response to change and fluidity are key preconditions for the next generation of IT solutions in the digital world. We are witnessing a rather unimaginable expansion of the use of technology in everyday life, on the one hand, and a continuous increase in the speed of software delivery, on the other, which significantly increased expectations and contributed to the adoption of agile methods and practices, shifting the pendulum of software architecture from traditional to agile methods and practices. Agile architecture, as a result of the transformation of a traditional and agile approach to software development, is a new approach that uses agile techniques to deliver a flexible architecture, adaptable to changing demands, tolerant to changes, which is the result of the iterative-incremental design of the agile process of software development. In recent years, there has been a shift in focus, in practice and research, from people and processes to integration technologies and application's hosting, which has led to the emergence of microservices and increased interest in software architecture and design. One consequence of this is the emergence and development of new approaches in the process of building Agile architecture, such as Continuous Architecting, Lean Architecting or Evolutionary Architecting, which essentially share the same goals. In this connection, in order to understand better the concept and the new role of Agile architecture in the digital era, it is necessary to study the genesis of Agile architecture, as a special approach in software development, to identify current trends and practices that are adapted to the contemporary digital environment (scalability, distribution, complexity). The results of conducted systematic literature review will help researchers and practitioners in better understanding of what Agile architecture is and its role, the current trends and directions of future development, and practices that are particularly useful in the development of complex software, with the aim of broadening the application and improvement of the agile software development process.

show abstract