|
| |
| Author |
Message |
Isabella
Joined: 15 Jun 2006 Posts: 100
|
Posted: Tue Jul 18, 2006 5:50 am Post subject: .NET Architecture and Design |
|
|
I am working as software engineer and using C# with ASP in web applications. As, I'm in learning phase of .net architecture and design patterns.
I have started a new project (Performance Management System) for which requirement analysis phase's completed and UML Diagrams are just completed too.
Technology is already decided (.Net Application using ASP .net (C#).
For this project i want to choose a proper design pattern for overall application and UI.
I have following questions for same.
1. What factors i should consider to chosse a particular design pattern.
2. What factors should be included to explain architecture of my application.
3. I hav confusion about two words "Layered Architecture (UI, Business Layer, Data Access Layer)" and "Design Patterns" are they synonyms or totally different.
Waiting eagerly for answers
|
|
| Back to top |
|
 |
Xprt Guest
|
Posted: Fri Aug 18, 2006 4:39 am Post subject: |
|
|
Design Pattern:
A pattern describes a proven solution to a recurring design problem, placing particular emphasis on the context and forces surrounding the problem, and the consequences and impact of the solution.
Architecture:
The manner in which the components of a computer or computer system are organized and integrated.
Layered architure is an architectural design pattern that structures applications so they can be decomposed into groups of subtasks such that each group of subtasks is at a particular level of abstraction. Example of layered architecture is 3-Tier client server model.
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|