Design Smells

Question 1

What is meant by the term Design Smells?

Answer 1

Design smells are certain structures in the design that indicate
violation of fundamental design principles and negatively impact design quality

Question 2

What are the different classification of design smells?

Answer 2

• Abstraction
• Encapsulation
• Modularization
• Hierarchy

Question 3

Define the Principle of Abstraction

Answer 3

advocates the simplification of entities
through reduction and generalization: reduction is by elimination of
unnecessary details and generalization is by identification and
specification of common and important characteristics.

Question 4

Techniques for applying the principle of Abstraction

Answer 4

• Map Domain Entities
• Ensure coherence and completeness
• Avoid duplication
• Provide a crisp conceptual boundary and a unique identity
• Assign Single and Meaningful Responsibility

Question 5

List the types of Abstraction Smells

Answer 5

Missing Abstraction (clumps of data, absence of classes)
Abstraction Imperative (method turned into class)
Incomplete Abstraction (does not support complementary/interrelated methods completely)
Multifaceted Abstraction (has more than one responsibility )
Unnecessary Abstraction ( unnecessary Abstraction gets introduced)
Unutilized Abstraction (Abstraction not used)
Duplicate Abstraction (identical name or implementation of abstraction)

Question 6

Explain the principle of Encapsulation

Answer 6

The principle of encapsulation advocates separation of concerns and
information hiding. Hiding implementation details and hiding
variations are two techniques that enable the effective application of
the principle of encapsulation.

Question 7

How do you enable techniques for applying the principle of encapsulation

Answer 7

• Hide implementation details

- Hide variations

Question 8

Types of Encapsulation Smells

Answer 8

• Deficient Encapsulation : Accessibility of abstraction is more permissive than needed
• Leaky Encapsulation : Abstraction exposes implementation details( public)
• Missing Encapsulation : no implementation
• Unexploited Encapsulation :

Question 9

What is technical Debt?

Answer 9

• Technical debt is the debt that accrues when you knowingly or
unknowingly make wrong or non-optimal design decisions.

Question 10

Describe the types of technical debts

Answer 10

• Code debt: Static analysis tool violations and inconsistent coding
style.
• Design debt: Design smells and violations of design rules.
• Test debt: Lack of tests, inadequate test coverage, and improper test
design.
• Documentation debt: No documentation for important concerns,
poor documentation, and outdated documentation.

Question 11

How do you manage technical debt?

Answer 11

• Knowledge and awareness of the concept of technical debt
• Detection of technical debt
• Repayment of technical debt
• Preventing accumulation of technical debt - by tracking monitoring and
continuous payment