Question about the design architecture


Author
Message
Michael Gonzalez
Michael Gonzalez
StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)StrataFrame Novice (52 reputation)
Group: Forum Members
Posts: 20, Visits: 40
Does SF implement proper layered separation of concerns (SoC), such as the presentation (PLL), business (BLL), and data layers (DAL)?



Additionally, does the BLL use a Domain Model pattern with a separate Repository pattern for mapping entities to data access operations?



Also, does the PLL use an SoC pattern, such as MVC, MVP, or PM?



And finally, can I use dependency injection?



Thanks.

Reply
Ivan George Borges
Ivan George Borges
Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)Strategic Support Team Member (4.9K reputation)
Group: StrataFrame MVPs
Posts: 1.9K, Visits: 21K
Michael.

I guess you missed part of Trent's answer, so I am quoting back here so you can give it another try:

Trent L. Taylor (03/10/2010)


Yes. StrataFrame is a true tier separated framework and can operate in a number of different environments. The documentation goes over this in much more detail, so instead of just rehashing the docs let me give a brief summary.

First, many of the acronyms that you are using (i.e. SoC) are called by other names as well (i.e. n-tier or 3-tier). So many of the things that you are asking may be a difference in nomenclature.

Next, StrataFrame is designed as a 3-tier framework which true physical separate of the DAL (Data Access Layer), BL (Business Layer), and PL or UIL (Presentation Layer or User-Interface Layer).

As for design patterns, we use many different patterns. As for the implementation of a Domain Model Pattern, this would pertain more as to how you write your application than how the framework is written. The Domain Model Pattern is basically a pattern that makes it easy for the flow of business rules and logic to change easily. So this is more driven by the design of your application than the framework. The framework ultimately allows you to work in either model (tightly or loosely coupled business rules). As for the repository pattern, this too is more determined by the design of your application, yet StrataFrame has intrinsic tools to aide in this if you choose to map connections to your data, etc. and decouple this from the application.

Cheers!

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...





Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search