A Preliminary Study on Software Architecture Evolution in Agile Development Process

Abstract:

Software architecture always exists in the target system although agile methodology (AM) weakens the design documents of the software architecture, and it will be improved continually as iteration process. The changes of business process and customer requirements should be dealt with in time. Therefore, it is essential that the stages of architecture evolution are explored in each release plan. The main hierarchy of architecture evolution is shown, the relationship between user stories and components is presented, and a method to support architecture evolution is given.

• Periodical: Applied Mechanics and Materials (Volumes 241-244)
• Pages: 2701-2708
• DOI: https://doi.org/10.4028/www.scientific.net/AMM.241-244.2701
• Online since: December 2012
• Authors: Xiao Hua Wang, Xu Zeng
• Keywords: Agile Methodology, Evolution Design, Incremental Development, Software Architecture

References

[1] Robert L. Glass，Extreme Programming：The Good，the Bad，and the Bottom Line[J]IEEE Software，2001，11: 234-237

[2] Xiaohua Zhang, Yi Zeng, Zhengguang Tu. Architecture SCM Model. Chinese Computer Engeering and Design,2006, 24(4): 704-707.

[3] Richard M., Eva K¨uhn, Alexander S.. Towards an Architectural Framework for Agile Software Development.17th IEEE International Conference and Workshops on Engineering of Computer-Based Systems (2010). IEEE COMPUTER SOCIETY, pp.276-280.

DOI: 10.1109/ecbs.2010.38

[4] Gerard Meszaros, Janice Aston. Adding usability testing to an agile project. Proceedings of AGILE 2006 Conference (AGILE'06), IEEE COPUTER SOCIETY。

DOI: 10.1109/agile.2006.5

[5] Mohammad Alshayeb, Wei Li. An Empirical study of system instability metric and design evolution in an agile software process. The Journal of system and software. 74(2005),p.269~274.

DOI: 10.1016/j.jss.2004.02.002

[6] Robert C.Martin. Agile Software Development: Principles, Patterns, and Practices. Pearson Education, 2003.

[7] Jim Shore. Continuous Design. IEEE Software, Jan./Feb., 2004, p.20~22.

[8] Xiaohua Wang, Ming Zhao. Using user stories to estimate the iteration periods and effort in extreme programming. Proceedings of international workshop on computer science and engineering (WCSE2008), May 2008, Moscow, Russia. pp.52-56.

[9] Kent Beck，Extreme Programming Explained : Embrace Change，2000，First Edition。

[10] Mingshu Li, Meng Huang, Fengdi Shu etc.. A Risk-Driven Method for eXtreme Programming Release Planning. ICSE'06, May 20-28, 2006, Shanghai, China, pp.423-430.

[11] Scott W. Ambler, Agile Model Driven Development(AMDD). XOOTIC Magazine, Feb. 2007, p.13~21.

[12] Kent Beck. Embracing Change with Extreme Programing. IEEE Computer,Oc t. 1999. pp.70-77.

[13] Robert L. Nord, James E. Tomayko, Rob Wojcik. Integrating Software-Architecture-Centric Methods into Extreme Programming (XP). Carnegie Mellon University, 2004.

DOI: 10.21236/ada431084

[14] William J. B., Raphael C. M., Hays W. M. etc. AntiPatterns: Refactoring Software, Architecture, and Projects in Crisis. Post & Telecom Press(Chinese Edition), 2008, pp.148-166.

[15] Wang YH，Zhang SK，Liu Y etc., Ripple-Effect analysis of software architecture evolution based on reachablility matrix. Journal of Software, 2004, 15(8): 1107~1115.

[16] Lei Ding, Nenad M.. Focus: A Light-Weight, Incremental Approach to Software Architecture Recovery and Evolution. Working IEEE/IFIP Conference on Software Architecture (WICSA'01), 2001, p.1~9.

DOI: 10.1109/wicsa.2001.948429