Just Enough Anticipation: Architect Your Time Dimension

Poort, Eltjo; Pautasso, Cesare; Zimmermann, Olaf

doi:10.1109/ms.2016.134

Cited by 10 publications

(13 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This challenge is growing in modern complex development and production environment, where systems of systems or software ecosystems are formed, with a multitude of interdependencies between commercial and dedicated software, hardware platforms and organizational entities, each of which has its own evolutionary cycle (Poort, 2016).…”

Section: Interdependence Of Componentsmentioning

confidence: 99%

“…For some extremely complex systems, it is not far from the truth that "everything affects everything", and especially the interdependence between functional and non-functional requirements (Mirakhorli & Cleland-Huang, 2013). Poort (2016) considers the interdependence of demands in light of architecturally significant events, adding a time dimension.…”

Section: Interdependence Of Requirementsmentioning

confidence: 99%

“…The traditional role of an architect is changing, which implied deep domain knowledge, a high level of abstraction in defining the structure, and an implicit or explicit right to make a decision in the field of interest (Poort, 2016). The architect focuses on delivering architecture as a service (Blair et al, 2010;Faber, 2010), coding according to needs, transferring technical knowledge (Babar, 2009), assisting the team in "violation of rules", providing communication on minimum documentation, with a division of responsibilities on the quality attributes (architect) and functionality (team) (Faber, 2010).…”

Section: Understanding the Role Responsibilities And Competencies Ofmentioning

confidence: 99%

“…In the digital era, SOA and microservices, i.e. services of different granularity (macro & micro), reduce dependency with the help of vertical decomposition, allowing their independent development, testing and delivery (Villamizar et al, 2015;Poort, 2016;Zimmermann, 2016b;Holmes & Nicolaescu, 2017;Taibi et al, 2017), where the decomposition approach is chosen based on the context, vision, requirements and criteria of dependency, where DDD is one, but not the only one (Pautasso et al, 2017a).…”

Section: Decomposition and Granularitymentioning

confidence: 99%

“…Evolution of components (Woods, 2015) and services (Zimmermann, 2016b) implies the application of the principle of backward compatibility, so that the changes affect users less. Evolution and change should get the lead, with timely anticipation of future architecturally significant events and their evolution point of view (Poort, 2016). It seems that the next phase, the so-called dynamic evolution, be even more radical, with intelligent dynamic compositions, cloud platforms, and linking IoT (Woods, 2016).…”

Section: An Evolutionary Approachmentioning

confidence: 99%

See 4 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

Section: Interdependence Of Componentsmentioning

confidence: 99%

Section: Interdependence Of Requirementsmentioning

confidence: 99%