Design and Architecture

Thank you for the answer! I did well at my presentation! :)

As their name implies it. A data access layer has the responsibility to access data sources (e.g. a data base). Possible implementations of that layer may contain SQL statements. The business logic layer contains all the logic of the domain you're in. It gets the data needed for its business processes by using the functionalities of the data access layer. It doesn't care about how the data is grabbed from a source. The data access layer in contrast is not able to acccess the businnes layer (which lays "above" it).

I just can tell you about how i have done it (so far at least). Usually i just divide one solution by subfolders for the different layers of the architecture e.g. View, Model, Controller. If for example you look at the ASP.NET MVC approach you'll find this in a similar way. Just by the path of the class file you could tell lets say a View from a Controller. Another benefit is, if you're are consistent in Naming your files you can simply by this convention tell which Control belongs to which View. In my opinion Reuse doesn't come from your project management but the class design itself. Anyway i think it's easier to keep your different layers in one solution. good question btw ;)

Hire someone to sale/market it. This is not a technical question and thus it is not the right forum for such question. This fits in for a discussion and pick Lounge or similar forum for the same. Sandeep Mewara [My last tip/trick]: Browser back button issue after logout

I have 2 major project in my Silverlight apps. WCF with the model and the dal (controller). The models have no relationships, they don't even have adorners yet but that will change. The model does however have all the fields from a view rather than a table. The DAL does all the decision making. All access is via stored procs (this maybe old school for some but it is the way I work) and most selects return a view (this being and extended table and matches the model). The second project is purely UI with view and viewmodel folders (among others). I also have a utilities project that is used across projects and is still in constant flux. I am continually finding that the standard controls all seem to be missing something and therefore we have moved to the Telerik control suite which I highly recommend (expensive and it adds 1mb+ to the silvelight client download). Never underestimate the power of human stupidity RAH

According to http://www.oodesign.com/design-principles.html, http://www.amazon.com/Software-Development-Principles-Patterns-Practices/dp/0135974445 should have some

Hi Kannan, Your inheritance approach seems fine. I have the following things that you can ponder about: 1) Isn't the user's call to a setter a little backwards? Another approach is just to require a getter from the user's concrete class e.g. public abstract class LibSetting { public abstract int MaxCount { get; } } Furthermore, you could supply the user with good default settings e.g. public abstract class LibSetting { /// <summary> /// Default set to 100. /// /// Don't call base when you override this. /// <summary/> public virtual int MaxCount { get { return 100; } } } Hope it makes sense... Regards, Keld Ølykke

Thank you so much for the ideas. Yes, you are right and thats what I am realizing now. At this moment, I am avoiding the extra BLL layer, but I will keep a sharp eye when duplication of code is apparent, and only then, I will add the BLL with only the refactored common methods. So, some of my UI will call DAL and some of my UI will call BLL and over time, depending on BLL will be increased and DAL dependency will decrease.

Try Google, there are lots of ready made packages around. I must get a clever new signature for 2011.

It depends on what is the job of controllers, your architecture is not the only possible, i post a fragment from wikipedia about architectures : Architecture description languages Architecture description languages (ADLs) are used to describe a Software Architecture. Several different ADLs have been developed by different organizations, including AADL (SAE standard), Wright (developed by Carnegie Mellon), Acme (developed by Carnegie Mellon), xADL (developed by UCI), Darwin (developed by Imperial College London), DAOP-ADL (developed by University of Málaga), and ByADL (University of L'Aquila, Italy). Common elements of an ADL are component, connector and configuration. Piccadilly Yum Yum

I agree that it ain't directly connecting to the computer science approach, and sounds more likely to be a marketing approach. But I guess he ask on a development forum in the fact that he doesn't know the software price estimate variables... But as Eddy say's, its a combination of many variables related to a giving project.

gbovee wrote: Is there a better way of doing this other than running a windows service thats polling the database? Since you only get a value when you execute it, there'd be no alternative to polling. You'd have to execute the sproc to see if the value changed. What does the sproc do? Perhaps the logic can be moved elsewhere? I are Troll :suss:

You could make a thing in google stile, in a textbox type a char and only products beginning with that char will be displayed, for example in a combo. Then typing one more or more char and so on, finally select the product by name by id as you like :) Piccadilly Yum Yum

One entry/exit point for your service is better, but then I would dispatch the logic behind it in several classes with each their own logic/domain etc.. So basically a bit of both :)

I've actually opted for a completely different tact. I'm going to leave the database security alone as there simply isn't a one size fits all solution. I'm also going to make use of the Windows Identity Foundation and implement a claim based security model. Keeps it all flexible. Jammer My Blog | Articles | DMon | SampleSort

Thanks for sharing ;)

Here is an extensive list. Personally I know Rational Rhapsody, Rational Rose (which is quite different) and Enterprise Archtect quite well. The first one I like the best as it not only lets you generate State diagrams, but also can run them, so you can see what state a particular state machine is in rigth in your diagrams while the code is being executed. A very visually oriented way of debugging. Unfortunately it's also the most expensive of these tools. It's been a long time I've used Rational Rose, and it seemed inferior to Rhapsody. At that time both products did not belong to IBM yet. I am not quite sure what kind of effect IBM had on the further development of these two direct competitors after obtaining them... :confused: Enterprise Architect is something you can easily afford even for private purposes, and it covers most of the functionality of the more expensive products. It is what I use now, mostly for designing class hierarchies and generating code, but also occasionally for reengeneering some fossile code bases.

MSMQ is still very much in active use. It's just not talked about as much, and is generally hidden behind abstractions such as WCF. I'm not a stalker, I just know things. Oh by the way, you're out of milk. Forgive your enemies - it messes with their heads My blog | My articles | MoXAML PowerToys | Onyx