Single Responsibility Principle

by nixusg 24. June 2009 23:06

For those who attended the SA Developer.Net talk tonight or anyone else who may be interested the slides and video for the Single Responsibility Principle section of this talk can be found at the bottom of this post.

The Single Responsibility principle deals with application architecture and states "There should never be more than one reason for a class to change"

Some benefits of applying the Single Responsibility Principle include:

  • Code complexity is reduced by being more explicit and straightforward
  • Readability is greatly improved
  • Coupling is generally reduced
  • Your code has a better chance of cleanly evolving

For details on the other topics of this session the OCP (Open-Closed Principle) and LSP (Liskov Substitution Principle) please contact Johan or Daniel. Their blogs are http://dotnet.org.za/johanvw/ and http://dotnet.org.za/danielvanwyk/ respectively.

I hope you all enjoyed the presentation or video.

 

Slides (SADeveloper.Net-SOLID-SingleResponsibilityPrinciple-Slides.zip - 1MB)

Video (SADeveloper.Net-SOLID-SingleResponsibilityPrinciple-Video.zip - 12.4MB)

Be the first to rate this post

  • Currently 0/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5

Tags:

SA Developer.Net | Architecture

Comments are closed

Powered by BlogEngine.NET 1.4.5.0
Theme by Mads Kristensen