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.

Quality

  • Editor Reviews
  • User Rating
  • Comments  (2) Comments
  • Learning Exercises
  • Bookmark Collections
  • Course ePortfolios
  • Accessibility Info

More about this material

Comments

Log in to participate in the discussions or sign up if you are not already a MERLOT member.
James Goggin
James Goggin (Student)
10 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)
15 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.
hidden