HERE are some pages I put together on architecture. Phillipe Kruchten at Rational suggested "four plus one" ways to look at architecture. The Application Architecture page talks about that. (The link to Kruchten's paper has gone stale, darn it.)
See if that gets you far enough into the topic to raise new questions.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
Explain from how a user gets response from a request.
If it is telephonic interview it is difficult to explain the architecture, so try to explain how a request will be processed and response will be shown to the user.
If it is personal interview try to explain what are all the components involved in your project and how they interact.
Ravinder S Edhan
Joined: Dec 15, 2003
Thanks Guys... This will certainly help me.
Regards Ravinder Singh Edhan
Joined: Jan 29, 2003
Sorry that page I sent you to didn't really say much about 4+1. I found a fresh link to Krutchen's paper.
The point I didn't really bring out is that architecture means many different things to different people. Someone who says "architecture" might be interested in
*Whether the app is fat client or web or other *General architectural patterns, eg MVC2 *Detailed class designs: how did you do X? *Technical stack, what products and frameworks are used *High availability: redundancy, load balancing, failover *Geographic distribution *Whether your database is partitioned *Packaging for reuse or partial deployments *Performance, volume and throughput *Network capacity, configuration *So many more ...
If someone just said "Describe the architecture" I'd probably ask what interests them, maybe list Krutchen's four views to explore the focus of the question. Or run to a whiteboard and draw for three or four hours.