scispace - formally typeset
Proceedings ArticleDOI

How Much Architecture? Reducing the Up-Front Effort

Reads0
Chats0
TLDR
Early results show that the experience of the architects and predefined or template architectures both help to reduce the architectural effort required without sacrificing the benefits of a full architecture design.
Abstract
A key part of software architecture is the design of the high level structure of a software system -- an exercise in planning ahead. Agile software development methods discourage planning ahead, encapsulated by the Agile Manifesto philosophy "[we value] responding to change over following aplan". Development without architecture planning risks failure. This leads to an apparent paradox: how can you design an architecture while using a methodology that promotes not planning ahead? This paper introduces Grounded Theory research that is exploring the factors that affect how much architecture planning industry practitioners do up-front -- in other words, how much architecture? Early results show that the experience of the architects and predefined or template architectures both help to reduce the architectural effort required without sacrificing the benefits of a full architecture design.

read more

Citations
More filters
Journal ArticleDOI

A systematic mapping study on the combination of software architecture and agile development

TL;DR: The results of this SMS help the software engineering community to reflect on the past thirteen years of research and practice on the architecture-agility combination with a number of implications.
Proceedings ArticleDOI

How much up-front?: a grounded theory of agile architecture

TL;DR: A grounded theory of agile architecture is presented that describes how agile software teams answer the question of how much upfront architecture design effort is enough to help them determine how much effort they should put into up-front design.

Reconciling agility and architecture: a theory of agile architecture

TL;DR: The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility.
Journal ArticleDOI

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

TL;DR: A literature review of the Dynamic System Development Method (DSDM) highlights that, in its current form, the DSDM does not support developing secure software and proposes enhanced D SDM that will cater the security aspects in software development.
Journal ArticleDOI

Agile architecture in the digital era: Trends and practices

TL;DR: 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).
References
More filters
Book

Extreme Programming Explained: Embrace Change

Kent Beck
TL;DR: You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Book

Software Architecture in Practice

TL;DR: This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.
Book

The Rational Unified Process: An Introduction

TL;DR: This chapter discusses the Rational Unified Process, a method for Modeling the Software Development Business using Software Engineering Techniques for Business Modeling, and its applications, from the Business Models to the Systems.
Journal ArticleDOI

Grounded Theory Methodology: The Pressing Need for a Coherent Logic of Justification

TL;DR: In this article, a new logic of justification, termed methodological hermeneutics, derived from Margolis's reconciliation of realism and relativism, has been developed by the author.