|
After a detailed evaluation of the situation, EPS recommended they start from
scratch. The team built a detailed architectural plan of the system and modeled
alternative implementations to ensure workability in the client's environment.
The final recommendation was based on Microsoft® SQL ServerT and Microsoft
Message Queue. Between the "clients" and the data center, EPS built a custom
transfer engine based on compressed XML. That engine provided options for
extensibility to ensure maintainability. To provide the required reliability,
the system implemented a "receipt" sub-system, similar to the system utilized
by BizTalkT Server. The new EPS application was optimized to allow operation
with limited bandwidth.
During development, EPS continued to test both for scalability and quality as
each component was completed. EPS also worked closely with the client to
establish the business rules logic that "plugged in" to the transfer engine to
ensure that corporate needs were met. The system architecture allowed for
changes and additions "on the fly" as needed.
The system was deployed on budget, but not on time: it was up and running
several weeks before the project deadline!
|
