| Census :: Architecture
The Census architecture follows a three-tier
model, where Census is split into a user interface tier, an
application tier, and a data services tier.
| User Interface Tier |
| On a client machine,
a browser provides the Census user interface. |
| Application Tier |
| On a Web server, Census Web provides
the application logic for bug and defect tracking, and handles
all requests for data by communicating via ADO with the
data services tier. Census Web is an ASP application.
|
| Census Web supports the definition of
multiple Web views for each Census project.
Each Web view is a set of ASP pages generated (using the
Census Web View Editor) from template ASP pages. |
| Data Services Tier |
| Census Server provides access
to Census project data, which is stored in Microsoft Access
or Microsoft SQL Server backend databases. |
| Advantages of the three-tier
model: |
- Application logic is centrally maintained on a Web
server, and can be easily updated
- All presentation/user interface services are handled
by a browser, so the system requirements for the client
machine are low.
- Clients do not communicate directly with the database,
but through the application tier. This reduces the
number of database connections, and therefore the
load on the database server
|
|
