Chapter 2.2 - Anti-patterns in Software engineering Flashcards
What is an anti-pattern?
A commonly occurring solution to a problem that generates negative consequences.
What are some common root causes for anti-patterns?
Insufficient communication, unfulfilled requirements, insufficient testing, cost overruns, and schedule slips.
What is the impact of “Haste” in software development?
Leads to hasty decisions, compromising software quality.
The “7 Deadly Sins” in Software Practice
Haste, Apathy, Narrow-Mindness, Ignorance, Pride, Avarice (Excessive Complexity), Sloth
How does “Apathy” contribute to anti-patterns?
Developers do not care about problems and refuse to attempt solutions.
What is “Narrow-Mindedness” in software engineering?
Refusal to use widely known solutions, sticking to familiar technologies.
What does “Sloth” mean in software development?
Making poor decisions based on easy answers, leading to costly mistakes later.
What is “Avarice (Excessive Complexity)”?
Over-modeling and addiction to complexity, ignoring simplicity.
How does “Ignorance” affect software projects?
Failure to seek understanding, leading to bad architectural choices.
What does “Pride (Hubris)” lead to in software engineering?
Refusing external solutions and overconfidence in one’s own work.
What is the “Blob” anti-pattern?
A single class monopolizes processing, while other classes only store data.
What are the typical causes of the “Blob” anti-pattern?
Lack of object-oriented architecture, inadequate architectural review, and incremental development without proper class separation.
How can the “Blob” anti-pattern be fixed?
Move behavior away from the Blob and distribute responsibilities across multiple classes.
What is the “Functional Decomposition” anti-pattern?
Implementing an object-oriented system using procedural-style coding.
How can the “Functional Decomposition” anti-pattern be avoided?
Define an analysis model, enforce proper class hierarchies, and ensure developers understand OOP principles.
What is the “Auto-generated Stovepipe” anti-pattern?
Occurs when legacy software is migrated to a distributed system without proper redesign.
What are the key remedies for “Auto-generated Stovepipe”?
Redesign interfaces for distributed systems and use larger-grained data models.
What is the “Golden Hammer” anti-pattern?
Overuse of a familiar tool or technology for every problem, even when it’s not appropriate.
What causes the “Golden Hammer” anti-pattern?
Prior success with a particular tool, lack of exposure to alternatives, and reliance on proprietary features.
How can organizations avoid the “Golden Hammer” anti-pattern?
Invest in professional development, explore new technologies, and commit to open systems.
What is the “Design by Committee” anti-pattern?
A design created by too many stakeholders, leading to excessive complexity and inefficiency.
What are some causes of “Design by Committee”?
No designated architect, ineffective meetings, gold plating, and trying to satisfy everyone.
How can “Design by Committee” be prevented?
Use structured meeting facilitation, assign clear roles, and limit design groups to small teams.
