How Much Architecture? Reducing the Up-Front Effort

Waterman, Michael; Noble, James; Allan, George

doi:10.1109/agileindia.2012.11

Cited by 14 publications

(11 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…refactoring (Nord, Ozkaya & Sangwan, 2012). Waterman, Noble and Allan (2012) explores the design of a minimal upfront architecture, while Fontdevila and Salías (2013) ask the question how to use agile approach and software architecture to increase quality, direct the development process and continuously flow the value for users. Ozkaya, Gagliardi and Nord (2013) emphasizes importance of integrating agile and architectural principles in order to improve the visibility of project status and to improve risk management tactics when scaling volume, team and/or time.…”

Section: The Challenges Of Agile Architecture In the Digital Eramentioning

confidence: 99%

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: The Challenges Of Agile Architecture In the Digital Eramentioning

confidence: 99%

Agile architecture in the digital era: Trends and practices

Dragičević¹,

Bošnjak²

2019

Strategic Management

View full text Add to dashboard Cite

show abstract

“…Friedrichsen [32] points out that an estimate of adequate extent of up front analysis and design depends on software architects' experience, skills, knowledge, as well as effective communication with stakeholders, while Waterman, Noble, and Allan [42] added two more factorsunderstanding of the selected architectural solution and use of a predefined architecture (in terms of existing patterns, architecture recommended by vendors or tools used to automatize the process). Brown et al [36] also advocate that architecture planning must not be too extensive, but rather "sufficient".…”

Section: Theoretical Backgroundmentioning

confidence: 99%

“…An overview of key categories of architectural issues and authors that investigated them is given in Table 2. [32-33, 36, 38-41] Balance between up front and emergent architecture [8,32,[36][37][38][40][41][42][43][44][45][46][47][48]…”

Section: Theoretical Backgroundmentioning

confidence: 99%

Traditionalisation of agile processes: Architectural aspects

Matkovic¹,

Maric²,

Tumbas³

et al. 2018

COMSIS J

View full text Add to dashboard Cite

Mechanisms of agile processes, suited for cost reduction and timely reaction to dynamic market changes, have also been recognized as useful in the development of complex software solutions. Recent studies focused on expansion of agile processes point to a viable possibility for coexistence and integration of complementary elements of agile and traditional development. Within the scope of this paper, this phenomenon is referred to as traditionalisation of agile processes. Software architecture modeling is one of the most sensitive issues associated with incorporation of elements of traditional development into agile processes. The goal of this paper was to determine how suitable particular explicit architectural practices are for incorporation into agile development processes. A mixed method research was carried out for this purpose. Qualitative component of the research resulted in identification of explicit architectural practices suitable for application in agile development processes. Their significances were determined by means of the quantitative component, realized in the form of an empirical research. The research confirmed that emergent architecture in agile processes is not sufficient for the development of complex software solutions, and that agile processes need to incorporate certain explicit architecture practices. Research results revealed that the agile community has an affirmative attitude towards the idea of incorporating explicit architectural practices into agile development processes, with overall agreement on the significances of particular explicit architectural practices for the development of architecture of complex software systems.

show abstract

“…Agile practitioners has found that developers use five broad strategies to determine their level of up-front architecture .However, the remaining four vary in their levels of upfront architecture [29].…”

Section: Mentioned Pabrahamsson Et Al 2010mentioning

confidence: 99%

A Review on Software Development Security Engineering using Dynamic System Method (DSDM)

Sani¹,

Firdaus²,

Jeong³

et al. 2013

IJCA

View full text Add to dashboard Cite

Agile methodology such as Scrum, Extreme Programming (XP), Feature Driven Development (FDD) and the Dynamic System Development Method (DSDM) have gained enough recognition as efficient development process by delivering software fast even under the time constrains. However, like other agile methods DSDM has been criticized because of unavailability of security element in its four phases. In order to have a deeper look into the matter and discover more about the reality, we conducted a literature review. Our findings highlight that, in its current form, the DSDM does not support developing secure software. Although, there are a few researches on this topic about Scrum, XP and FDD but, based on our findings, there is no research on developing secure software using DSDM. Thus, in our future work we intend to propose enhanced DSDM that will cater the security aspects in software development. Keywords AgileDevelopment; Software Security; Software Engineering; Dynamic System Development Method; DSDM INTRODUCTIONThe DSDM software development approach that provides a framework for building and maintaining systems, meets tight time schedule through the use of incremental and iterative prototyping in a controlled project environment [1]. On the other hand, According to the computer Emergency Response Team (CERT) statistics [3].There had been a considerable increase in security related software vulnerabilities reported over the last few years. However, like other agile methods, the existing DSDM does not provide any phase or sub-phase to address security issue in software development. In general, one of the most important reasons why the agile methods ignore security issue of software may come from the misconception that security delays development process [2].Despite this misconception, security remains one of the most important non-functional requirements of a software system. Though, recently, a few efforts have made in order to address the security in software development, such efforts using agile models like Scrum, XP. Some of such efforts have been published However, based on the literature review, we found that there is a small amount of research conducted on developing secure software using DSDM. In order to have a deeper look into the fact, this paper presents the concepts of DSDM, its principles, techniques, practices, general security principles, limitations of DSDM in terms of addressing security, and the analysis of literature review. Thus, it is appropriate to commence with the concept of DSDM. DSDM AND PRINCIPLESThe basic concept of DSDM is that the time and resource are adjusted, so that the agility feature of DSDM is satisfied. Basically, DSDM has four main phases (Figure 1). The four main phases are feasibility, functional model iteration, design and build iteration and implementation. Then each phase has several sub-phases as mentioned below.

show abstract

How Much Architecture? Reducing the Up-Front Effort

Cited by 14 publications

References 8 publications

Agile architecture in the digital era: Trends and practices

Agile architecture in the digital era: Trends and practices

Traditionalisation of agile processes: Architectural aspects

A Review on Software Development Security Engineering using Dynamic System Method (DSDM)

Contact Info

Product

Resources

About