Very easy one-page integration to Microsoft's Reporting Services
Introduction
The Amlin Reinsurance Project application was designed and written for Amlin plc, a UK Insurance company. The application provides reinsurance experts a way of storing, processing, and handling cover notes, claims, and premiums for reinsurance purposes.
Multiple currencies are handled for both claims and premiums
Users enter data manually for any given year, and then roll forward or backward in time, automatically migrating the data and saving hours in entering similar information. In addition, rates of exchange, currencies, and rating can be imported as CSV (comma separated value) files with full validation and reporting.
The application stores information on multiple reinsurers and their S & P and Amlin ratings
A new dynamic security model was used, giving users the ability to dynamically add users to roles and assign security settings to roles individually or in a batch. Access to all controls on a page and the page itself can be dynamically set at runtime.
Microsoft SQL Reporting Services was used to handle the reporting requirements.
Application Size and Scope
One Microsoft SQL Server database comprises over 150 tables and views, the largest currently holding 125,000 records. This table grows as audit entries are added for each insert/edit and delete of the other tables, approximately 20,000 per year. The application is split into two Intranet websites, one for the main application and one for the administrative functions, totaling of over 300 web pages and 1900 stored procedures. The administrative site allows privileged users to administer data and configurations without the IT team or DBA.
The administrative functionality is integrated into the main application seamlessly even though they are two different applications
The Project
The project took 4 months to implement with one person, a senior developer with 27 years experience, doing the database design, web design, and implementation. After the initial application becomes established, a second phase is planned and will take another 4 months or so.
Code Extensions and Customizations
Infragistics web controls were used where extra functionality was required such as tree view and drop down menus
Code customizations have been used extensively to handle menus, breadcrumb trails, and tree views. User Controls are used where possible to keep the changes separate from the Iron Speed Designer generated code. The application architecture generated by Iron Speed Designer made this a very easy task and worked consistently well. Shared customizations were made to the BaseApplicationPage class, and individual changes made to the code-behind to handle menu events and pre-processing of data.
Layout Customizations
Using the master page template, a new layout was designed with menus, treeview, breadcrumb, and help screens
A new design theme based on an existing theme was created before work started. Custom panels were also used to aid reusability across the project.
Metrics for Success
Coding proved to be a lot easier with Iron Speed Designer, because the majority of the application "plumbing" is generated for you, saving time and money. It works time after time, and builds confidence in the system reliability. Without Iron Speed Designer, another developer or two would have been needed to complete the project on time.
The application in action, treeview navigation on the left and the main view on the right
Iron Speed Designer Impact
Building the application by hand would have been feasible, but would have taken a lot longer to produce the same results. Employees testing the application have commented on just how robust and reliable the code is - it just works consistently day-after-day. They also really appreciate the uniformity, robustness, and responsiveness that the Iron Speed framework has provided.
Next Steps
Phase two will commence as soon as this the initial application becomes established in the organization. Many of the code customizations will be reused in the next phase.
