Click on the image below to view it full size in an image viewer !
The Web Tier

Whoooaaaa, 'Web Tier' ? Where did that come from ?? We were only recently told that:

Typically, multi-tiered applications have a client tier, a middle tier, and a data tier (often called the enterprise information systems tier).

The client tier consists of a client program that makes requests to the middle tier (nested Property version)

Java EE application development concentrates on the middle tier to make enterprise application management easier, more robust, and more secure.

So how does 'The Web Tier' fit in with the idea of a 'middle tier' ? And what about the 'business tier', which deeper source text «wrapper» Components now refer to; how is that related to what we were already told ?

The middle tier's business functions handle client requests and process application data, storing it in a permanent datastore in the data tier: NESTED PROPERTY FORM

Are these new tiers parts of the 'middle tier', i.e., are they sub-tiers ? Let's now use UML™ Parsing Analysis to sort it out.

However first please note in advance:

The source text of some of the deeper «wrapper» Components shown here already suggest "designed" Java EE Classes that may be reverse engineered and bound through UML™ Parsing Analysis, so that these «wrapper» Components may eventually be "executed" as demonstrations from within a UML tool !

Under UML™ Parsing Analysis it is important, however, to till include the analysis step, rather than just jumping straight to the design (or "already designed") layer, because the analysis classes will provide an important organisational bridge.