asp.net web applcaition design pattern

[mit99mh]

I'm going to start building an asp.net web application using vb.net does anyone know of links to a good design pattern - historically I have used model 2 when developing with servlets/beans/jsp's, or templating using php any pattern similiar to these would be ideal.

Any help appreciated.

 

[jfrost10]

since vb.net is fully OO, you might as well get on with UML and a good UML methodology: Rational Unified Process, Iconix, etc.

Addison Wesley publishers have excellent books on all topics of UML, as well as methodologies. Microsoft has a OOP with VB.NEt and C# book, which is good from a coding perspective, but not so hot when it comes to theory and methodology (mho).

hth

D

 

[flanakin]

While UML architecture and design principles are nice, unless you are going to have a large amount of processing, the process will be fairly fruitless, as they are with most web apps. I am not discouraging it, but make sure you know what you're wanting out of it before you jump into it. The most you will probably get out of it is a database structure and a better overall understanding of the project. I kind of doubt that you will use the it to its full potential, unless you are creating a true n-tier application. ________________________________________
Michael C Flanakin
Indigo Web Systems

http://www.indigows.com

michael.flanakin@indigows.com

 

[jfrost10]

I would disagree with Michael:

If you're building a shed or a house, you want to make sure both are structurally sound. So you would use the same methods, just at different scales.

Thats been my experience with utilizing UML: if you're building a small app or a large app, you're still ensuring that the base design is sound and solid.

Adding a methodology like Iconix or the RUP enhances this, by using techniques to ensure your code will be top notch.

Also, you should think long term about your web application:
right now we're working on a member portal. There's security, the portal itself, and hte business logic of the business using it. They also want a sales system, a purchasing system, and an accounting system inter-twined, some of that being web based, some being desktop based, all using the same database. Architecture is PARAMOUNT in this situation.

mit99: i'm not sure how large your web app is, but from my experience, utilizing UML and a software methodology can benefit you no matter what the scope is. Its more about getting into the mindset of how to develop great software than it is whether you'll "fully benefit" from it. My last company started using it, then stopped, and they still are plagued with horribly buggy code, long hours, and major design flaws that could have been avoided if they would have done full analysis and design first.

just mho


D'Arcy