Software Engineering

ISSN Online: 2376-8037 ISSN Print: 2376-8029

Archive Home / Archive

Volume 2, Issue 1, September 2014

  • Authors: G. H. El-Khawaga, Galal Hassan Galal-Edeen, A. M. Riad

    Abstract: The need for having a clear roadmap for a software product developed using an agile method is a reasonable implication of the agilists’ tendency of establishing a planning-driven process rather than a plan-driven one, and chasing and welcoming change rather than limiting it. Building an initial architecture for a product will serve as the railway for a planning process that can enable managing change accommodation rather than unmanaged change accommodation. Change accommodation –while not considering the proposed changes’ effects- may serve its purpose of flexibility on the short term, but on the long term will uncover a complex, unmanageable set of relations between software components within an eroded architecture. In this paper, a framework for embedding architectural practices into an agile software development process –while avoiding problems of current agile architecting, and keeping agile development values- is presented.

    Received: Sep. 12, 2014 Accepted: Sep. 25, 2014 Published: Sep. 30, 2014

    DOI: 10.11648/ View: Downloads: