Microsoft’s SQL Server provides a stable and efficient platform for creating and maintaining production databases. These files could as easily be migrated to any other ODBC compliant SQL based server platform (e.g., Oracle, DB2, etc.)

Since relatively few individuals perform administrative tasks it appeared expedient to use C++ to develop an Application Management Interface across the network infrastructure. Deployment and maintenance issues are minimized as a result of the limited user base. This architecture further resolves a broad range of security issues since administration is authenticated initially at the network level, and also against the database server's security policies.

The Middle Tier Object provides for data validation, user authentication and the implementation of business rules. System security is ensured because the user, through the Web Application Server, has access only to that functionality explicitly provided for by the middle tier interface. It was necessary to reconcile the efficiency of an in-process middle tier module against the stability and scalability of an application that is executed outside of the server’s process. The compromise became a C++ authored Active X dynamic link library component that is loaded as part of the web application and provides an acceptable level of isolation from the server process in contrast to server API extensions.

Browser based clients provide a universal access mechanism across a broad range of platforms while minimizing compatibility issues. These clients are provided in DHTML/XML, ActiveX, and Java Applet varieties and are delivered subject to the user’s browser capabilities. Cascading Style Sheet technology is used to maintain a consistent appearance throughout the application. User authentication information is stored on the client machine in the form of a cookie if that capability is enabled, if not the user is required to be authenticated to the system at the time of connection. Since the middle tier permits users only the capability to post transactions, and not modify existing information, the risk of project data corruption by unauthorized or malicious users is minimized.

Manager and user accounts are configured through the Application Management Interface and administrators are able to specify those tasks and expenses that will be available for project managers within their respective projects. Restrictions governing how instances are managed when a user attempts to record activity for which sufficient resources have not been allocated, or those allocated resources have been exhausted, can be configured through this interface.

Managers allocate resources based on the project specifications, while users consume these resources by entering time spent, travel information, and other relevant expenses incurred. Concerned individuals are able to review the current status of projects to facilitate project management. Accumulated time and expense data can be transmitted to the accounting department for payroll and invoicing purposes, also actuarial data reflecting project activity can be compiled for job costing purposes.

A Contact Information Manager is provided to allow users a convenient mechanism to access and input information relating to individuals involved in projects into a central repository. This tool is available to all users that have been authorized to access the system and allows an audited mechanism to edit contact information.