How It All Started
MS SQL SERVER 2000
Each transaction or "business message" was implemented as an SQL Server stored procedure. All of our stored procedures were packaged to maintain code modularity. Most "read" and "populate" operations are performed using client-issued SQL that executes directly against database tables. In some cases, we have implemented stored procedures to generate a list-of-values.
The underlying database tables, views, and packages were created in a "secure" database account. Public synonyms were created for those objects that needed to be "readable" to a user of the system. Each user has an individual SQL Server 2000 account, to which object and system privileges are granted via an SQL SERVER 2000 role.

BORLAND DELPHI 7
The challenge to IT professionals today is to efficiently develop and deploy applications for use on both corporate intranets and over the Internet. The Borland Delphi 7 is a revolutionary set of components that streamline the development, deployment, and management of enterprise applications and it is complete in a sense that it is possible to develop a large class of enterprise applications using only Delphi 7. Borland Delphi provides the ability to deploy component-based enterprise applications across multiple tiers in a platform natural manner.
Among multi-tiered system architecture, three-tiered client/server architecture provides an environment, which supports all the benefits of both the one-tiered approach and the two-tiered approach while supporting the goals of a flexible architecture.

Lessons Learned
BabySentry has been a production system since 2000. During the past years we have learned quite a deal about deploying ART applications throughout the clinic.

Tuning and Performance
Before production rollout, we did an extensive load test of the application system. We ran the application on several PCs and were able to simulate 100 concurrent users issuing a fairly standard set of transactions. From this, we gathered performance statistics. Since the initial benchmark of the system, we perform routine monitoring of our application server's resource usage. To date, we have supported 180 concurrent users without significant performance degradation. We plan to continue our rollout to support hundreds of simultaneous web users.

Application Maintenance
Category Description Frequency Impact
Major Release Application re-write 1 time Synchronized re-distribution of Client Application & update to business logic and database.
Minor Release Significant Enhancement of overall functionality (e.g., a new screen or other major new features). Significant user interface change. Once in 3-4 months Synchronized re-distribution of Client Application or database.
Maintenance Release Minor Enhancement of functionality (e.g., new report) Once in 2-3 months Redistribution of Client Application
Patch Bug fixes policy changes, legal requirements Once in 1-2 months Update of centralized database logic

Back to Top