From the course: Dart Clean Code: Writing High-Efficiency, Maintainable Dart Programs
Unlock the full course today
Join today to access over 24,700 courses taught by industry experts.
Interface segregation principle - Dart Tutorial
From the course: Dart Clean Code: Writing High-Efficiency, Maintainable Dart Programs
Interface segregation principle
- [Instructor] A FinTEch startup created payment software that allows people to send money to friends and family. After a few months of operation, some software developers began requesting SDKs to access payment service. Unfortunately, the startup failed to consider abstraction when the software was being developed. Because of their current implementation, software developers will be forced to implement services that they may never use. Making modifications to the code base may be challenging for the startup because the service is already in production. In reality, software should be created with abstraction in mind. The heart of object-oriented design is abstraction. It frees the client from having to worry about implementation details of functionality. Abstraction is achieved in many OOP languages through abstract classes, and interfaces. The interface segregation principle provides guidelines for implementing…
Contents
-
-
-
-
Single responsibility principle3m 29s
-
(Locked)
Open-closed principle3m 10s
-
(Locked)
Liskov substitution principle3m 15s
-
(Locked)
Interface segregation principle3m 27s
-
(Locked)
Dependency inversion principle3m 11s
-
(Locked)
Challenge: Create an area calculator29s
-
(Locked)
Solution: Create an area calculator1m 33s
-
-
-
-