Abstract
Systems are becoming increasingly reliant on software due to needs for rapid fielding of “70% capabilities,” interoperability, net-centricity, and rapid adaptation to change. The latter need has led to increased interest in agile methods of software development, in which teams rely on shared tacit interpersonal knowledge rather than explicit documented knowledge. However, such systems often need to be scaled up to higher level of performance and assurance, requiring stronger architectural support. Several organizations have recently transformed themselves by developing successful combinations of agility and architecture that can scale to projects of up to 100 personnel. This chapter identifies a set of key principles for such architected agile solutions for software-reliant systems, provides guidance for how much architecting is enough, and illustrates the key principles with several case studies.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
References
Beck, K. (1999); Extreme Programming Explained. Reading, MA: Addison-Wesley.
Boehm, B. (2007); “Agility and quality”. IBM Agile Conference, May 15, 2007; ICSE Workshop on Software Quality, May 21, 2007.
Boehm, B. and Turner, R. (2004); Balancing agility and discipline: a guide for the perplexed.
Addison-Wesley, Boston. Boehm, B. and Lane, J. (2008); Incremental Commitment Model Guide, version 0.5, Center for Systems and Software Engineering Technical Report, December 31, 2008, http://csse.usc.edu/csse/TECHRPTS/2009/usc-csse-2009-500/usc-csse-2009-500.pdf.
Boehm, B., Valerdi, R., and Honour, E. (2008); “The ROI of Systems Engineering: Some Quantitative Results for Software-Intensive Systems”, Systems Engineering, Vol. 11, No.3, Fall 2008, pp. 221-234.
Carlile, P. (2002); “A pragmatic view of knowledge and boundaries: boundary objects in new product development”. Organization Science Vol. 13: 442-455.
Elssamadisy, A. and Schalliol, G. (2002); “Recognizing and Responding to ‘Bad Smells’ in Extreme Programming,” Proceedings, ICSE 2002, pp. 617-622.
Highsmith, J. (2002); Agile Software Development Ecosystems. Boston: Addison-Wesley.
Lane, J. and Zubrow, D. (1996); “Metrics focus brings about improvement in health care software development. Proceedings, SEI Software Engineering Process Group Conference, March 1996.
E-Health Designs, LLC, Legacy System Saviors, http://www.ehealthdesigns.com/?page_id=246, accessed on 12/8/2009. Office of the Under Secretary of Defense for Acquisition, Technology and Logistics (OUSD AT&L), (2008); Systems engineering for systems of systems, Version 1.0. Washington, DC: Pentagon.
Pew, R. and Mavor, A. (2007); Human-system integration in the system development process: a new look. National Academy Press, 2007.
Poppendieck, M and Poppendieck, T. (2003); Lean software development, an agile toolkit. Addison Wesley.
Van Tilborg, A., Acting DUSD(S&T), (2006); “Advancing Software-Intensive Systems Producibility: Charge to NRC Committee,” September 27, 2006 (citing Defense Acquisition University as source).
Principles behind the agile manifesto, http://agilemanifesto.org/principles.html. accessed on 8/4/2009.
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2010 Springer-Verlag Berlin Heidelberg
About this chapter
Cite this chapter
Boehm, B., Lane, J.A., Koolmanojwong, S., Turner, R. (2010). Architected Agile Solutions for Software-Reliant Systems. In: Dingsøyr, T., Dybå, T., Moe, N. (eds) Agile Software Development. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-12575-1_8
Download citation
DOI: https://doi.org/10.1007/978-3-642-12575-1_8
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-12574-4
Online ISBN: 978-3-642-12575-1
eBook Packages: Computer ScienceComputer Science (R0)