http://msmvps.com/blogs/peterritchie/archive/2008/05/08/fundamentals-of-ood-part-2-encapsulation-scope.aspxLet&#39;s look at the ubiquitous Person concept. It might seem logical that an application that deals with people should have a Person interface for classes to implement. For example: public interface IPerson { String GivenName { get; set; } String SurNameenCommunityServer 2008.5 SP2 (Build: 40407.4157)http://msmvps.com/blogs/peterritchie/archive/2008/05/08/fundamentals-of-ood-part-2-encapsulation-scope.aspx#1628573Thu, 29 May 2008 04:53:16 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1628573Navaneeth<p>Hi,</p> <p>Nice one. This series will be really helpful. Thanks for that and looking forward to read the upcoming parts.</p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1628573" width="1" height="1">http://msmvps.com/blogs/peterritchie/archive/2008/05/08/fundamentals-of-ood-part-2-encapsulation-scope.aspx#1621346Mon, 12 May 2008 23:02:00 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1621346Amir<p>Good stuff, but remember about Object Persistency as an another Technique. I think, in real world it’s completely depend on your requirements and the way you are looking on the objects. </p> <div style="clear:both;"></div><img src="http://msmvps.com/aggbug.aspx?PostID=1621346" width="1" height="1">http://msmvps.com/blogs/peterritchie/archive/2008/05/08/fundamentals-of-ood-part-2-encapsulation-scope.aspx#1617701Thu, 08 May 2008 20:08:34 GMTd67277c4-116b-43f1-b688-e9ef184ea916:1617701DotNetKicks.com<p>You&#39;ve been kicked (a good thing) - Trackback from DotNetKicks.com</p> <img src="http://msmvps.com/aggbug.aspx?PostID=1617701" width="1" height="1">