As Vadim as said, don't start from patterns usage. Start from creating =
solutions to problems as in this case "designing a payrol". The secret =
to understanding Pattern application and usage is DEJAVU (A sense of =
feeling u've done this before). You must feel this in one of more of the =
problem areas of designing your solution, then you can apply an =
appropriate pattern that solves that problem.
I understand you want to build a windows application and a web =
application. I'll suggest you take a look at Microsoft Software =
Factories of particular not in your situation is Web Client Software =
Factory (WCSF) and Smart Client Software Factory. These has best of =
patterns applied for you. =20
[quoted text, click to view] "Vadim Chekan" <vadim@nowhere.com> wrote in message =
news:K4agj.43320$1C4.14153@newsfe10.phx...
> DS wrote:
>> Hello,
>>=20
>> I am new to design pattern and need help to understand How to achieve =
on a=20
>> conclusion which pattern is best suited for a Given Complex =
application.
>>=20
>> For example, consider a Payroll application in ASP.Net and a =
Inventory=20
>> Management system Windows application.
>>=20
>> Which Pattern is best suited for above two examples and why?
>>=20
>> Please throw some light on this.
>>=20
>=20
> Unfortunately, only experience can help to decide which pattern to =
use.
> First of all, you should not start from pattern and try to use it. You =
> should start from the concrete problems that you are facing or=20
> anticipate to face and try to come up with a solution. If you=20
> experiences some similar problem in the past, and you utilize the=20
> approach, then it becomes a pattern. There are a catalogs of the most=20
> popular patterns and you may want to make yourself familiar with at=20
> least with GoF (google for "gof patterns") or buy a book:
>
http://www.informit.com/store/product.aspx?isbn=3D0201633612&rl=3D1 >=20