oo with interface
•
0 likes•590 views
The document discusses object-oriented principles and design, including interfaces, SOLID principles, and clean coding best practices. It explains key concepts like interfaces being used to define shared boundaries for exchanging information between components. The five SOLID principles - single responsibility, open/closed, Liskov substitution, interface segregation, and dependency inversion - are covered through examples. Additional best practices like KISS, YAGNI, and DRY are also mentioned. Peer review concepts such as contrived complexity, cyclomatic complexity, and downcasting are highlighted.
Recommended
More Related Content
Viewers also liked
Viewers also liked (19)
Recently uploaded
Recently uploaded (20)
oo with interface
- 1. STAC THINK IN OO WAYS WITH INTERFACE AND COL-POP 1
- 9. “SHARED BOUNDARY ACROSS WHICH TWO SEPARATE COMPONENTS OF A COMPUTER SYSTEM EXCHANGE INFORMATION” Wikipedia/interface WHAT IS INTERFACE 9
- 10. WHAT IS INTERFACE KEY POINT ▸ Exchange information ▸ Shared boundary 10
- 11. WHAT IS INTERFACE KEY POINT ▸ Exchange information ▸ Shared boundary 11
- 12. WHAT IS INTERFACE EXCHANGE INFORMATION Procedural vs Object 12
- 13. WHAT IS INTERFACE EXCHANGE INFORMATION Procedural vs Object 13
- 14. WHAT IS INTERFACE EXCHANGE INFORMATION Procedural vs Object 14
- 15. WHAT IS INTERFACE KEY POINT ▸ Exchange information ▸ Shared boundary 15
- 16. WHAT IS INTERFACE KEY POINT ▸ Exchange information ▸ Shared boundary 16
- 17. WHAT IS INTERFACE SHARED BOUNDARY interface C A implements C B implements C A.FOO(1, 2) B.FOO(1, 2) C —— FOO:INT, INT->INT 17
- 19. WHAT IS COLPOP COLPOP implements Eatable, Drinkable http://www.java67.com/2015/12/top-30-oops- concept-interview-questions-answers- java.html#What is the 5 objects oriented design principle from SOLID? 19
- 23. COLLOP & INTERFACE SOLID ▸ Single responsibility ▸ Open / Close ▸ Liskov substitution ▸ Interface segregation ▸ Dependency inversion 23
- 31. COLLOP & INTERFACE SOLID ▸ Single responsibility ▸ Open / Close ▸ Liskov substitution ▸ Interface segregation ▸ Dependency inversion 31
- 32. OPEN / CLOSE Open Close 32
- 33. OPEN / CLOSE Open Close OPEN 33
- 34. OPEN / CLOSE Open Close OPEN 34
- 35. OPEN / CLOSE Open Close OPEN CLOSE 35
- 36. OPEN / CLOSE Open Close OPEN CLOSE 36
- 37. COLLOP & INTERFACE SOLID ▸ Single responsibility ▸ Open / Close ▸ Liskov substitution ▸ Interface segregation ▸ Dependency inversion 37
- 38. LISKOV SUBSTITUTION Let q(T) is avail 38
- 39. LISKOV SUBSTITUTION Let q(T) is avail If S ⊂ T then q(S) is also avail 39
- 40. LISKOV SUBSTITUTION Let q(T) is avail If S ⊂ T then q(S) is also avail 40
- 41. LISKOV SUBSTITUTION Let q(T) is avail If S ⊂ T then q(S) is also avail T 41
- 42. LISKOV SUBSTITUTION Let q(T) is avail If S ⊂ T then q(S) is also avail T S T 42
- 43. LISKOV SUBSTITUTION Let q(T) is avail If S ⊂ T then q(S) is also avail T S T S 43
- 44. COLLOP & INTERFACE SOLID ▸ Single responsibility ▸ Open / Close ▸ Liskov substitution ▸ Interface segregation ▸ Dependency inversion 44
- 49. COLLOP & INTERFACE SOLID ▸ Single responsibility ▸ Open / Close ▸ Liskov substitution ▸ Interface segregation ▸ Dependency inversion 49
- 56. DEPENDENCY INVERSION Cup Cup Use Layering! Lamp example from The Dependency Inversion Principle[1] 56 [1] [Martin96] Robert C. Martin, Engineering
- 57. LET’S MAKE LAMP WITH BUTTON 57 button lamp on off
- 58. THE DEPENDENCY INVERSION PRINCIPLE class Lamp { void turn(boolean isOn); } class Button { Lamp lamp; void detect() { lamp.turn(getPhysicalState()); } boolean getPhysicalState() { // … some code to get button physical state } }
- 59. THE DEPENDENCY INVERSION PRINCIPLE interface ButtonClient { void turn(boolean isOn); } interface Button { boolean getState(); } class ButtonOnOffLamp implements ButtonClient { } class ClickButton implements Button { }
- 60. THE DEPENDENCY INVERSION PRINCIPLE interface ButtonClient { void turn(boolean isOn); } interface Button { boolean getState(); } class ButtonOnOffLamp implements ButtonClient { } class ClickButton implements Button { }
- 61. THE DEPENDENCY INVERSION PRINCIPLE interface ButtonClient { void turn(boolean isOn); } interface Button { boolean getState(); } class ButtonOnOffLamp implements ButtonClient { } class ClickButton implements Button { }
- 62. COLLOP & INTERFACE EXTRA RULE ▸ KISS 62
- 63. COLLOP & INTERFACE EXTRA RULE ▸ KISS ▸ Keep it Simple and Stupid 63
- 64. COLLOP & INTERFACE EXTRA RULE ▸ KISS ▸ Keep it Simple and Stupid ▸ YAGNI 64
- 65. COLLOP & INTERFACE EXTRA RULE ▸ KISS ▸ Keep it Simple and Stupid ▸ YAGNI ▸ You ain’t gonna need it 65
- 66. COLLOP & INTERFACE EXTRA RULE ▸ KISS ▸ Keep it Simple and Stupid ▸ YAGNI ▸ You ain’t gonna need it ▸ Dry 66
- 67. COLLOP & INTERFACE EXTRA RULE ▸ KISS ▸ Keep it Simple and Stupid ▸ YAGNI ▸ You ain’t gonna need it ▸ Dry ▸ Do not Repeat Yourself 67
- 69. 10 MIN
- 70. 5 MIN
- 71. STOP
- 72. PEER REVIEW
- 73. TEXT PEER REVIEW ▸ Contrived complexity
- 74. TEXT PEER REVIEW ▸ Contrived complexity ▸ Cyclomatic complexity
- 75. TEXT PEER REVIEW ▸ Contrived complexity ▸ Cyclomatic complexity ▸ Down casting
- 76. TEXT PEER REVIEW ▸ Contrived complexity ▸ Cyclomatic complexity ▸ Down casting ▸ Too many parameters
- 77. TEXT PEER REVIEW ▸ Contrived complexity ▸ Cyclomatic complexity ▸ Down casting ▸ Too many parameters ▸ Composition over Inheritance
- 78. TEXT MUST READ ▸ http://www.slideshare.net/gyumee/ss-55817747 ▸ http://www.slideshare.net/gyumee/ss-55616001
- 79. CLEAN CODE
- 80. EFFECTIVE JAVA
- 81. CLEAN CODER