1 / 12

CiTR’s DECADE Strategy

CiTR’s DECADE Strategy. DECADE vision integrated electronic customer access independent of the UI technology independent of the application domains DECADE Environment Many UI Technologies Isolated Business Logic Many Implementation Technologies. Internet Billing Application.

fran
Download Presentation

CiTR’s DECADE Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. - 1 -

  2. CiTR’s DECADE Strategy • DECADE vision • integrated electronic customer access • independent of the UI technology • independent of the application domains • DECADE Environment • Many UI Technologies • Isolated Business Logic • Many Implementation Technologies - 2 -

  3. Internet Billing Application • Call Preview - First telecommunications internet billing application in Australia • Allow customers to access bill details via a Web Browser • Call Preview developed using DECADE • System must be able to eventually support up to 1000 concurrent users • ECA adds value to basic Call Preview service - 3 -

  4. Computing Architecture Web Browser Firewall (ITP) Call Preview FLEXCAB/MICA R/E - 4 -

  5. Service Architecture • Based on TINA’s Service Architecture • Core Components • User Agent • Login Manager • Combined Service Session Manager • Service Factory - 5 -

  6. Meeting Scalability Requirements (1) • Scalability addressed by Computing Architecture and Service Architecture • 3 tier architecture - 6 -

  7. Meeting Scalability Requirements (2) • Cluster Management • Cluster • Cluster Container • Cluster Factory • Implemented in computing architecture • Limits inter process communication • Minimises resource leaks - 7 -

  8. Meeting Response-time Requirements • Generating HTML pages on-the-fly • Thin clients - no processing done on client box • New functionality and services available immediately • CORBA platform under load - 8 -

  9. Deployment • Interfacing to systems • Web Servers • Firewalls (routers and Security constraints) • Backend Databases • Orbs • System Requirements • network setup • common environment from Test to Production - 9 -

  10. What we Learnt • Requirement for “shakeout” period • Integration “not easy” • Real user testing required, not just automated tools • GUIs with C++ not quick fixes - maybe Java would have been easier?? • CORBA Servers need to be VERY robust in a high use environment • Customers are usually BIG organisations, which affects the turnaround time for problems - 10 -

  11. Future Work • Additional user functionality • CSV export • Enhanced sorting and filtering • Web based reporting for CSRs • how many customers accessing certain • usage of functions • Improve ability to change GUI characteristics quickly • for enhancement • for new clients! - 11 -

  12. Conclusion • Internet application provided within short timeframe • Understanding of the types of architectures required for similar applications • Implementation of DECADE architecture • Experiences learnt interfacing with one of Australia’s largest companies - 12 -

More Related