How to Approach the Design of a new Application?

[Guest]

I have been working as a Senir .NET Developer for the past 4 years and worked
with VB6 and Classic ASP for 4 years previous to this.

I have did an interview recently for an Architect Role. They asked how I
approached Design and also what methodologies I used.

Generally the applications I have worked on have been designed on an ad-hoc
basis using no real methodologies.

This is something that I am lacking.

Can someone advise me as to how they approach design and what methodologies
exist?

Any recommendations on a book on the area to get me up to speed would be
appreciated?

Thanks in Advance.

 

[RobinS]

Deborah Kurata has a new book coming out called (I think) "Doing Objects In
VB 2005"
that explains the GUIDS methodology and how to apply it to application
development in
general, and also explains business objects and object orientation.
Unfortunately,
I don't think it's coming out until next year.

You could pick up her "Doing Objects in VB6" book -- it explains the GUIDS
methodology
and how to apply it in more detail than the 2005 book. It might be less
painful than
buying a straight methodology book (zzzzzz). And they have it on amazon.com
for
only 53 cents. How can you go wrong for 53 cents + shipping?

Robin S.

 

[Michael Nemtsev]

Hello C,

C> I have been working as a Senir .NET Developer for the past 4 years
C> and worked with VB6 and Classic ASP for 4 years previous to this.
C> I have did an interview recently for an Architect Role. They asked
C> how I approached Design and also what methodologies I used.
C>
C> Generally the applications I have worked on have been designed on an
C> ad-hoc basis using no real methodologies.
C>
C> This is something that I am lacking.
C>
C> Can someone advise me as to how they approach design

It's too general question to answer by two words.
Firstly, they probably wanted to know what is your understanding of "architecture".
How you can leverage with the components which make "application architecture"
- what approach based on which condition you need to choose to create the
best app with reasonable extensibility in time and in bounds of resourses/budget.

There is no schema of what and where to use, it comes from your experience
and knowledge.

I'd recommed you to grope for the such meanings as "SOA, EDA, MDA, n-tier,
EAI, ESB" words to understand where and which to use, their prons and cons
in application architecturing.

C> what methodologies exist?

It corncerns to the existed Waterfall, RUP, XP, SCRUM, PSP, Agile methodologies.
To understand which is approproate for the your project.

Googling to find the overview of these notions and to be informent what is it


---
WBR,
Michael Nemtsev :: blog: http://spaces.live.com/laflour

"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsche

 

[Guest]

Spending sometime in the "Patterns and Practices" section of the Microsoft
web site will help a lot. There is a ton of information there - too much to
digest in one sitting.