n-tier Archit.

im new in the n-tier world, but i know quite a lot, im currently designing an n-tier solution for fun.

the problem is>>

The kiosk can capture blood pressure, percent body
fat, and weight. The user can also enter information such as cholesterol
levels. This information is used by the user to monitor their
health and by the user’s medical aid company for reward schemes
and for statistical analysis.
The user can access their history via the kiosk or through the company’s
website. Medical aid administrators get whichever details
they require (and are allowed to get) from the Cape Town based
company. This will only include information on their own members
and then the actual information gathered on each member depends
on the reward scheme. For example one medical aid administrator
may only require the fact that a particular member has used the
kiosk while another may require details for a particular member to
base the rewards on signs of improvements in that member’s health.

>___End of problem___

This will entail detailing what system will run on the kiosks, local servers,
and on the central server. You will have to detail:
• How the central server will update the local servers.
• How the local servers will update the central server.
• How the kiosk retrieves a members details from the local server.
• How the kiosk updates the local server.
• How the member web site will operate.
• How the medical aid administrator website will operate.
You do not need to describe how the kiosk captures the member’s
readings. You will need to assume how it will store that information
at every phase of the data’s life (on the central server, local server,
and the kiosk). Keep in mind to describe the choice of any particular
method or technology (e.g.: web services or .NET Remoting).


>> Give me an example on what i can manage most of the presentation & business logic