SPL migration tensions: an industry experience
Proceedings of the 2010 Workshop on Knowledge-Oriented Product Line Engineering
Towards architectural information in implementation (NIER track)
Proceedings of the 33rd International Conference on Software Engineering
Towards a process for architectural modelling in agile software development
Proceedings of the joint ACM SIGSOFT conference -- QoSA and ACM SIGSOFT symposium -- ISARCS on Quality of software architectures -- QoSA and architecting critical systems -- ISARCS
Proceedings of the 4th international workshop on Social software engineering
RCDA: Architecting as a risk- and cost management discipline
Journal of Systems and Software
Aligning architecture knowledge management with Scrum
Proceedings of the WICSA/ECSA 2012 Companion Volume
A persona-based approach for exploring architecturally significant requirements in agile projects
REFSQ'13 Proceedings of the 19th international conference on Requirements Engineering: Foundation for Software Quality
Scaling agile methods to regulated environments: an industry case study
Proceedings of the 2013 International Conference on Software Engineering
MockAPI: an agile approach supporting API-first web application development
ICWE'13 Proceedings of the 13th international conference on Web Engineering
Towards optimal software engineering: learning from agile practice
Innovations in Systems and Software Engineering
| Hi-index | 0.00 |
Software architecture is getting a bad rap with many agile proponents due to such aspects as big design up front, massive documentation, and the smell of waterfall. It's pictured as a nonagile practice, something we don't want to even consider, although everybody wants to be called an architect. However, certain classes of systems that ignore architectural issues for too long hit a wall and collapse due to a lack of an architectural focus. So, is agile architecture a paradox, an oxymoron, or two totally incompatible approaches? Software developers have equally important roles in successfully letting agile and architectural approaches coexist. Agile approaches rely more on bottom-up efforts in which developers collaborate closely with stakeholders in general and product owners in particular. This article reviews the real issues at stake, past the rhetoric and posturing, and suggests that the two cultures can coexist and support each other, where appropriate.