Antipatterns (Software engineering)
Enlarge text Shrink text-
Topic
-
Save successfulThe item can be found in your Personal ZoneשגיאהLog in to your account to save
- Work cat.: 00039235: Brown, William J. AntiPatterns in project management, c2000:CIP galley (Antipatterns are prevalent, recurring software project management roadblocks to successful delivery directly caused by the lack of understanding of the correct way to manage software development. Antipatterns define bad practice in terms of causes, symptoms, and consequences.)
- Brown, W.J. Antipatterns : refactoring software, architectures, and projects in crisis, 1999(antipatterns target common mistakes, errors, and people issues that can cause a software project to fail)
An anti-pattern in software engineering, project management, and business processes is a common response to a recurring problem that is usually ineffective and risks being highly counterproductive. The term, coined in 1995 by computer programmer Andrew Koenig, was inspired by the book Design Patterns (which highlights a number of design patterns in software development that its authors considered to be highly reliable and effective) and first published in his article in the Journal of Object-Oriented Programming. A further paper in 1996 presented by Michael Ackroyd at the Object World West Conference also documented anti-patterns. It was, however, the 1998 book AntiPatterns that both popularized the idea and extended its scope beyond the field of software design to include software architecture and project management. Other authors have extended it further since to encompass environmental, organizational, and cultural anti-patterns.
Read more on Wikipedia >