index > Visual Studio Team System - Architects > Designing n-tier application in Architect Edition

Designing n-tier application in Architect Edition

Hello,

I am planning to design a n-tier application .. which will have a UI layer, Business logic layer and DB access layer and a DB.

I am planning to design the same in Architect edition... But not very sure how can it help me.. as architect edition is more biased towards designing service oriented applications.

My question is whether architect edition is useful for designing such type of applications.? beacuse all my layers will be on a single m/c .. and i can have the dB on seperate one..

kindly reply.

Rakesh

Rakesh_24

Maybe you can using just for design, not validating connections and so on, hmm well maybe only with database, and use "Generic applications", but I think you will be using only a few capabilities of architect edition, as you say, it's more oriented to use it with SOA applications, and validation of their connetions, with the logical datacenter diagram and systems.

Luis Fraile - MCSD.NET - http://luisfraile.spaces.live.com/

Luis Fraile

Thanks Luis..

But i am not sure how can far this logical datacenter diagram can be useful as i m going to have my applicayion on a single app server and DB on the other..

Is it that the designers in architect edition is useful of desigining SOA and not for desigining the traditonal n- tier application.

kindly revert on this.

Rakesh

Rakesh_24

Aha, that's it, I think it won't be as useful as in SOA design, so just decide if you want to use it just for document the system, with other diagrams also like class diagrams and so on

Luis Fraile - MCSD.NET - http://luisfraile.spaces.live.com/

Luis Fraile

Hello
It is correct that we targeted the designers toward an SOA design. However you can still use them to document a more traditional n-tier design. Remember the logical data center is just that logical. It does not care if everything is on one physical box or not. You can use endpoints to show that client talks to a second application and that it talks to a database. This allows you to document how your system works. Hope this helps.

You may want to take a look at some of the Architecture tech notes.
http://msdn.microsoft.com/vstudio/teamsystem/reference/technotes/default.aspx

Thanks
Brian [MSFT]
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.

Brian Combs MSFT

reply 5