Well its unfortunate but in order to educate you in this architecture we would have spend a couples years teaching layer by layer....so when we started building up the N-Tier it wont be so confusing.
But since you want the answer Now, http://lmgtfy.com/?q=n-tier+architecture On Aug 23, 11:31 am, "P.Bixam" <[email protected]> wrote: > Thanks for your advices, > > I would appreciate if anybody replies in a Technical way to elaborate them. > * > *Regards > P. Bixam > > On Tue, Aug 23, 2011 at 6:25 AM, Stephen Russell <[email protected]>wrote: > > > > > On Mon, Aug 22, 2011 at 11:08 AM, P.Bixam <[email protected]> wrote: > > > Hi All, > > > > I need any advice regarding n-tier architecture... > > > As of now I am following the bellow structure, > > > > 1. UI-Layer - aspx, aspx.cs, Javascript, Styles > > > 2. Business Layer - Invoking DAL Objects, Caching, Auditing (Any Adivce > > > here) > > > 3. Business Entity - Classes with Properties > > > 4. Data Access Layer - Database interactions > > > 5. Common Layer - Constants, Singleton class > > -------------- > > > I separate my tiers into actual projects for reuse in other ongoing > > work. The GUI won't be shared but the DAL is the core to a great many > > apps. > > > From your listing I see 2 == 4 > > > My KISS setup is as follows: > > 1. Solution file for GUI. Holds the following > > 2. Project for Data (RDBMS specific) interaction. How to pass a call > > to a SPROC and receive a Table back. > > 3. Project for Managers, contain Data Objects. Used to call to data > > and translate to whatever transportation layer is needed. > > 4. Project for Business Rules. This reads metadata and sets up what > > is seen by user(s) as well as identifying if general data from GUI is > > good enough or does it need more before it can be committed to the > > database. > > > In this setup There are only N projects for #1, each for the RDBMS > > they target. It just gets data or errors and returns them upchain. > > > #3 and #4 tend to be consumed together. HR Rules go with HR Managers. > > They are separate because Rules can change! Where schema for the > > designed data rarely does. > > > I work in team environment with 3-4-5 others interacting in this type > > of code base. > > > -- > > Stephen Russell > > > Unified Health Services > > 60 Germantown Court > > Suite 220 > > Cordova, TN 38018 > > > Telephone: 888.510.2667 > > > 901.246-0159 cell > > > -- > > You received this message because you are subscribed to the Google > > Groups "DotNetDevelopment, VB.NET <http://vb.net/>, C# .NET, > > ADO.NET<http://ado.net/>, > > ASP.NET <http://asp.net/>, XML, XML > > Web Services,.NET Remoting" group. > > To post to this group, send email to [email protected] > > To unsubscribe from this group, send email to > > [email protected] > > For more options, visit this group at > >http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en > > or visit the group website athttp://megasolutions.net- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "DotNetDevelopment, VB.NET, C# .NET, ADO.NET, ASP.NET, XML, XML Web Services,.NET Remoting" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/dotnetdevelopment?hl=en?hl=en or visit the group website at http://megasolutions.net
