An exploratory study of architectural practices and challenges in using agile software development approaches

Babar, Muhammad Ali

doi:10.1109/wicsa.2009.5290794

Cited by 39 publications

(39 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Agile methods such as Scrum, Extreme Programming (XP), and Crystal Clear, which more or less adhere to the values of the Agile Manifesto 1 [9], share common characteristics, such as iterative and incremental development life cycles, focusing on small releases, collocated teams, and a planning strategy based on a release plan or feature backlog [10] where architectural design issues are not very important [11]. For instance, the incremental design practice of XP claims that architecture can emerge in daily design (emergent design) [12], which implies that architecture emerges from the system rather being imposed by some direct structuring force [11].…”

Section: Background and Related Workmentioning

confidence: 99%

“…For instance, the incremental design practice of XP claims that architecture can emerge in daily design (emergent design) [12], which implies that architecture emerges from the system rather being imposed by some direct structuring force [11]. Apart from verbal discussions related to design decisions and overall architecture, also Scrum does not place any emphasis on architecture related practices.…”

Section: Background and Related Workmentioning

confidence: 99%

“…Apart from verbal discussions related to design decisions and overall architecture, also Scrum does not place any emphasis on architecture related practices. In Scrum, the architecture of one-project application can always be re-factored and repackaged for a higher level of reuse [11]. While "refactoring, for its part, has emerged as an important software engineering technique, it is not a replacement for sound upfront design; if an architecture is decent you can improve it, but re-factored junk is still junk" [13].…”

Section: Background and Related Workmentioning

confidence: 99%

See 2 more Smart Citations

Supporting Large-Scale Agile Development with Domain-Driven Design

Uludağ

Hauder

Kleehaus

et al. 2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. An increasing number of large organizations are adopting agile and lean methods at larger scale for building complex software systems. One major critique of agile development and in particular of large-scale agile development is the neglect of proper architecting assistance in such development efforts. On the one hand, emergent architecture design may require excessive redesign efforts in large systems, while on the other hand, big upfront architecture delays the starting point of implementation. Domain-driven Design (DDD) addresses this problem by providing means for evolving the architecture of complex systems in an agile way. We describe how DDD can support large-scale agile development based on a conducted case study in a large insurance company with three agile teams. Furthermore, we present a lightweight framework that can be used by agile teams as guidance for architecting in large-scale agile development programs. The presented framework is largely based on Large-Scale Scrum and incorporates strategic and tactical DDD.

show abstract

Section: Background and Related Workmentioning

confidence: 99%

Section: Background and Related Workmentioning

confidence: 99%

Section: Background and Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Supporting Large-Scale Agile Development with Domain-Driven Design

Uludağ

Hauder

Kleehaus

et al. 2018

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

show abstract

“…up-front architecting is too effort intensive [15]. Specific architecture related challenges in an agile context were identified by [16], such as a lack of consideration for quality requirements and planning for system structures to fulfill quality requirements in the long run. From a practice perspective, such as continuous integration, solutions that enable continuous delivery are beneficial, among them cloud infrastructures.…”

Section: B8mentioning

confidence: 99%

A Context Model for Architectural Decision Support

Carlson

Papatheocharous

Petersen

2016

2016 1st International Workshop on Decision Making in Software ARCHitecture (MARCH)

View full text Add to dashboard Cite

Abstract-Developing efficient and effective decision making support includes identifying means to reduce repeated manual work and providing possibilities to take advantage of the experience gained in previous decision situations. For this to be possible, there is a need to explicitly model the context of a decision case, for example to determine how much the evidence from one decision case can be trusted in another, similar context. In earlier work, context has been recognized as important when transferring and understanding outcomes between cases. The contribution of this paper is threefold. First, we describe different ways of utilizing context in an envisioned decision support system. Thereby, we distinguish between internal and external context usage, possibilities of context representation, and context inheritance. Second, we present a systematically developed context model comprised of five types of context information, namely organization, product, stakeholder, development method & technology, and market & business. Third, we exemplary illustrate the relation of the context information to architectural decision making using existing literature.

show abstract

“…depending on the project context [8]. In [22], the documentation was reduced to component diagrams and design decisions published on a wiki.…”

Section: Literature On Software Architectures and Their Usage In Agilmentioning

confidence: 99%

An Approach to Software Architecting in Agile Software Development Projects in Education

Angelov

Beer

2015

Software Architecture

View full text Add to dashboard Cite

The architecting activities in agile software development methods are weakly defined and even sometimes neglected. While there is sufficient literature on how software architectures and the architecting activities could be approached in agile projects, there is little information on how this topic should be treated in the education of software engineering students. In this paper, we propose an approach to the architecting activities in agile software projects in a bachelor software engineering course. The approach is inspired by theoretical and industry sources and is tailored to fit our educational goals and context. Our first experiences from the application of the approach show improved and deepened treating of software architectures, clarity on the purpose of the executed architecting activities, and improved student motivation.

show abstract

An exploratory study of architectural practices and challenges in using agile software development approaches

Abstract: Abstract

Cited by 39 publications

References 21 publications

Supporting Large-Scale Agile Development with Domain-Driven Design

Supporting Large-Scale Agile Development with Domain-Driven Design

A Context Model for Architectural Decision Support

An Approach to Software Architecting in Agile Software Development Projects in Education

Contact Info

Product

Resources

About