The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.01 - January/February (2010 vol.27)
pp: 10-11
Frank Buschmann , Siemens Corporate Technology
ABSTRACT
It's the architect's responsibility to ensure that a software system delivers the right functionality with the right operational and developmental qualities. Balancing the two aspects is challenging. When architects have a dominating preference for functional coverage or an excessive bias towards performance tuning and adding variability points, projects rarely have a chance to succeed on time and budget.
INDEX TERMS
performance, flexibility, feature coverage, walking skeletons, architecture quality
CITATION
Frank Buschmann, "Learning from Failure, Part 2: Featuritis, Performitis, and Other Diseases", IEEE Software, vol.27, no. 1, pp. 10-11, January/February 2010, doi:10.1109/MS.2010.14
REFERENCES
1. K. Marquardt, "Performitis," Proc. 8th European Conf. Pattern Languages of Programs, Universitätsverlag Konstanz, 2003, pp. 48–49.
2. F. Buschmann, "Learning from Failure, Part 1: Scoping and Requirements Woes," IEEE Software, Nov./Dec. 2009, pp. 68–69.
3. K. Henney, "Use Uncertainty as a Driver," 97 Things Every Software Architect Should Know, R. Monson-Haefel ed., O'Reilly, 2009, pp. 321–361.
4. K. Pohl, G. Böckle, and F. van der Linden, Software Product Line Engineering: Foundations, Principles, and Techniques, Springer, 2005.
5. D.M. Weiss and C.T.R. Lai, Software Product-Line Engineering: A Family-Based Software Development Process, Addison-Wesley 1999.
6. E. Evans, Domain Driven Design, Addison-Wesley, 2004.
7. K. Czarnecki and U. Eisenecker, Generative Programming, Methods, Tools and Applications, Addison-Wesley, 2000.
8. G. Booch, "On Design," Handbook of Software Architecture, blog, 2 March 2006, www.handbookofsoftwarearchitecture.com/index.jsp?page=Blog&part= 2006.
20 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool