Software Architecture: Organizational Principles and Patterns Software Architecture: Organizational Principles and Patterns Software Architecture: Organizational Principles and Patterns Worldwide Institute of Software ArchitectsWorldwide Institute of Software Architects

Publications

   Home
   Reviews
   Publications
   Presentations
   Errata
   References
   Resources
   Search
Patterns: An Antidote for "Best" Practices Gone Bad
SPC E-ssentials Newsletter, Issue 53, September 25, 2001
by David Kane and David Dikel

Abstract: Although many organizations want to apply "best" practices, the results are not always what they expect. Sometimes "best practices" do more harm than good. What works for one organization may not work for another. Patterns, which are familiar to many software engineers as a way of describing design elements, can be used describe organizational practice and process solutions. By capturing the context in which a particular solution makes sense, and by articulating the consequences and risks associated with implementation, patterns help managers select practices that best fit their situation and avoid selecting practices that waste everyone's time.

Patterns presented:

  • Rotation

Note: A version of this article alse appeared at InformIT. (Registration Required)


Copyright © 2003 David Kane, David Dikel, and Jim Wilson


If you have questions or comments about this site, please send them to info@vraps.com