Design patterns: TheSingle-Responsibility      Principle  Grzegorz Wilczyński   11th november 2012
SOLIDThe principles when appliedtogether intend to make it morelikely that a programmer willcreate a system that is easy t...
SOLIDSingle responsibilityOpen-closedLiskov substitutionInterface segregationDependency inversionhttp://en.wikipedia.org/w...
BIBLEhttp://www.amazon.com/Agile-Principles-Patterns-Practices-C/dp/0131857258
Rule #1A class should have only onereason to change."Agile Principles, Patterns, and Practices in C#" Robert C. Martin
Rule #2A class should have only onereason to change."Agile Principles, Patterns, and Practices in C#" Robert C. Martin
So please dont...http://3.bp.blogspot.com/-FQZ4VT_gbRY/T8RvXLTPWMI/AAAAAAAABP0/JCckSpENM88/s640/SingleResponsibilityPrinci...
Step 1http://www.remondo.net/wp-content/uploads/2012/03/SingleResponsibilityPrincipleRadio.png
Step 2http://www.remondo.net/wp-content/uploads/2012/03/SingleResponsibilityPrincipleRadioManagers.png
Homework$ git branch gw-solid-1end time: 16.11.2012
Upcoming SlideShare
Loading in …5
×

Single responsibility principle

35,315 views

Published on

Single responsibility principle

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
35,315
On SlideShare
0
From Embeds
0
Number of Embeds
8
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Single responsibility principle

  1. 1. Design patterns: TheSingle-Responsibility Principle Grzegorz Wilczyński 11th november 2012
  2. 2. SOLIDThe principles when appliedtogether intend to make it morelikely that a programmer willcreate a system that is easy tomaintain and extend over time.http://en.wikipedia.org/wiki/Solid_(object-oriented_design)
  3. 3. SOLIDSingle responsibilityOpen-closedLiskov substitutionInterface segregationDependency inversionhttp://en.wikipedia.org/wiki/Solid_(object-oriented_design)
  4. 4. BIBLEhttp://www.amazon.com/Agile-Principles-Patterns-Practices-C/dp/0131857258
  5. 5. Rule #1A class should have only onereason to change."Agile Principles, Patterns, and Practices in C#" Robert C. Martin
  6. 6. Rule #2A class should have only onereason to change."Agile Principles, Patterns, and Practices in C#" Robert C. Martin
  7. 7. So please dont...http://3.bp.blogspot.com/-FQZ4VT_gbRY/T8RvXLTPWMI/AAAAAAAABP0/JCckSpENM88/s640/SingleResponsibilityPrinciple.jpg
  8. 8. Step 1http://www.remondo.net/wp-content/uploads/2012/03/SingleResponsibilityPrincipleRadio.png
  9. 9. Step 2http://www.remondo.net/wp-content/uploads/2012/03/SingleResponsibilityPrincipleRadioManagers.png
  10. 10. Homework$ git branch gw-solid-1end time: 16.11.2012

×