1. Home
  2. Material Detail: Application Architecture: an N-Tier approach

Material Detail

Application Architecture: an N-Tier approach

Application Architecture: an N-Tier approach

Article describing the complexities involved in designing a complete system. Good material for programmers to read and help see the big picture.
Disciplines:
Go to Material 
Bookmark / Add to Course ePortfolio
Create a Learning Exercise
Add Accessibility Information
Rate
Add a Comment

Quality

More about this material

Material Type:
Presentation
Date Added to MERLOT:
October 28, 2002
Date Modified in MERLOT:
March 14, 2020
Author:
Submitter:
Lampman
Primary Audience:
College General Ed
Mobile Compatibility:
Not specified at this time
Language:
English
Cost Involved:
No
Source Code Available:
No
Accessibility Information Available:
Unknown
Creative Commons:
No

Browse...

Disciplines with similar materials as Application Architecture: an N-Tier approach
People who viewed this also viewed
Other materials like Application Architecture: an N-Tier approach

Comments

Log in to participate in the discussions or sign up if you are not already a MERLOT member.
James Goggin
James Goggin (Student)
14 years ago
Skimmed the data, had a hard time finding a way to relate the data to my frame of work. I am a programmer and analyst, when working on projects and development, I work only one roll. The project manager spends more time at this level; I have not interest in Project management. This issue I have no Project Managers seem to have a interest at this level. I been working the same job for 7 years so I have a isolated experienced outside of my current environment.

Technical Remarks:

The writer does know what he is talking about, I think the audience is limited due to depth.
Used in course? Yes
Time spent reviewing site: 25 minutes.
Sandy Houston
Sandy Houston (Student)
19 years ago
I spent about 20 minutes reading this article. I really enjoyed learining more
about the n-tier approach to application architecture. The article is a
detailed explaination of an approach to developing architecture that has two or
more isolated layers. The typical model that is shown in the article separates
the architecture into the Presentation GUI, Presentation Logic , Business, Data
Access and Data. The benefits of this separation are explained in the article.
I was particularly interested in learning more about this approach because I
have seen it in the workplace, but did not completly understand it until now.