Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updated Link for Interface Segregation Principle #1

Merged
merged 1 commit into from
Feb 25, 2017
Merged

Updated Link for Interface Segregation Principle #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ an overview over good priciples that should be applied to software design.
- **Moral of the story: model your classes based on behaviours not on properties; model your data based on properties and not on behaviours. If it behaves like a duck, it's certainly a bird.**
- **This strongly suggests that inheritance should never be used when the sub-class restricts the freedom implicit in the base class, but should only be used when the sub-class adds extra detail to the concept represented by the base class as in 'Monkey' is-an 'Animal'.**
- `I`: Interface Segregation Principle
- [link](http://www.oodesign.com/dependency-inversion-principle.html)
- [link](http://www.oodesign.com/interface-segregation-principle.html)
- [Wiki](https://en.wikipedia.org/wiki/Interface_segregation_principle)
- `D`: Dependency Inversion Principle
- [link](http://www.oodesign.com/dependency-inversion-principle.html)
Expand Down