1. Orientation Workshop on Product Development & Management Functions Workshop 2: IBEX Application Architecture – Part I April 5, 2007 The DSA Project is implemented by Harvard University and funded by Development Cooperation Ireland (DCI), the Netherlands Minister of Cooperation, and the United States Agency for International Development (USAID)

2. 2 Agenda I.Design Methodology II.General Application Architecture Principles III.High Level IBEX Architecture Overview IV.Application Layer 1 - User Interface

3. 3 Design Methodology Designing before Development (Rule of 1/3 rds ) Designing from Procedures/Requirements Design Stages –Specification and Business Design (Requirements gathering) –Requirements Documentation –High-Level Design –Detailed Design Design Iterations / Requirements Management

4. 4 Design Methodology Application Design Tools - Modeling (UML) –Use case diagramming –Class/Static Structure diagrams –Sequence diagrams –Component/Deployment diagrams –Others… Database Design –Should be based on (not lead) application design –Entity Relationship (ER) Diagrams –Proper database normalization

5. 5 Agenda I.Design Methodology II.General Application Architecture Principles III.High Level IBEX Architecture Overview IV.Application Layer 1 - User Interface

6. 6 General Application Architecture Principles Modularity –Ability to use, add or exchange specific components independently (with minimal systematic effect) Extensibility –Ability to easily develop additional functionality Scalability –Ability to grow to meet increased demand (users, locations, processing etc.) Appropriateness –Consideration of the context of use and implementation throughout. Segregation of duties (development consideration) Elegance before Performance

7. 7 Agenda I.Design Methodology II.General Application Architecture Principles III.High Level IBEX Architecture Overview IV.Application Layer 1 - User Interface

8. 8 High Level IBEX Architecture Overview IBEX: Integrated Budget and Expenditure System Technical Implementation A custom solution using industry standard frameworks –I. Technical platform for automation of Public Financial Management (PFM) functions. –II.Implemented functional PFM modules (core & non-core) –III.Migration tools: coexistence with standalone (IBEX and BIS/BDA)

9. 9 Revenue High Level IBEX Architecture Overview Security & User Directory Budget Data Warehouse User Interface Reporting Web Distribution Internationalization Technical Platform Auditing Functional Modules AccountsDisbursements DebtHRPayroll Migration Tools Standalone IBEX or BIS/BDA IBEX CORE MODULES NON-CORE MODULES

10. 10 High Level IBEX Architecture Overview Current modules (core IFMIS functions +) –Budget Preparation –Budget Adjustment –Budget Control –Accounts Transaction Register General Ledger Financial Statements Management Reports –Nationwide Consolidation –Disbursements –Administration Future modules and 3 rd party systems integration… (non-core IFMIS functions) –Payroll, Asset Management, Human Resources, Revenue, Debt Management, Banking Systems ??? FUNCTIONAL MODULES

11. 11 High Level IBEX Architecture Overview Integrated –Functional integration Single ‘data warehouse’ Data entered once, available ‘everywhere’ Single user interface and user security system –Transactional integration Distributed (Web-Enabled) Real-time Transactionality Limited only by available communication infrastructure (WeredaNet) –Procedural integration Integration with existing automated and manual processes TECHNICAL PLATFORM

12. 12 High Level IBEX Architecture Overview Security (prevents unauthorized access to all systems and data) –Industry leading web-application security framework (Netegrity SiteMinder OTS system) –User based/role based security Completely granular security on  Application data  Application ‘resources’ (ex. Reports, user screens, buttons etc.) –Network Security Separate Security Server 2 Hardware Firewalls 128 bit HTTPS Encryption on all network traffic Scalable (grows easily to serve additional users and locations) –Few installations. Easy to support and upgrade. Meets Govt. requirements for devolution to Weredas –Platform flexibility – Grows as telecommunication infrastructure grows –Robust architecture and components Can support many more users and increased use TECHNICAL PLATFORM

13. 13 High Level IBEX Architecture Overview Extensible (easy to develop additional functionality) –Modular design of PFM functions. Easy to develop and ‘plug-in’ future non-core functions. –Easy integration with external systems / 3 rd party applications. –Abstract architecture to allow for alternate/multiple 3 rd party systems (ex. database, security etc.) Internationalized (supports multiple languages and cultural locales) –Can operate in any language. Currently operates in four languages (Amharic, English, Tigrigna and Oromiffa) and additional language support can be added very easily. –Supports multiple calendars, currency types, numbers, times etc… Performance –Upgraded computing infrastructure Data-Loss Prevention (Backup systems and policy) TECHNICAL PLATFORM

14. 14 High Level IBEX Architecture Overview Integrated tools to link BIS/BDA or Standalone IBEX to IBEX –Provide seamless data integration between IBEX and existing BIS/BDA systems. –Support automation of reform in the absence of a comprehensive communications infrastructure –Will probably be necessary for some time to come. As long as standalone automation versions are in use. Migration Tools

15. 15 High Level IBEX Architecture Overview

16. 16 High Level IBEX Architecture Overview High-Level Logical View (3-Tier Architecture ) –User Interface (UI) Layer –Application (Business) Layer –Data Layer Component Model (Logical Separation) –J2EE Component Model –Common Services (Common library) –Functional Modules Deployment Model (Physical Separation) –Web Server –Application Server –Security/Policy Server –Data Warehouse

17. 17 High Level IBEX Architecture Overview UI Layer Application Layer Data Layer Model View Controller Data Services Validation Database Data Layer Implementations Business Objects Business Object Services Internationalization Reporting XML Properties ETL Security High-Level Logical View Auditing

18. 18 High Level IBEX Architecture Overview Deployment Model Security Agent Data Server Application Server Security/Policy Server Web Server User Directory Store Application Data Warehouse Security Services Common Services Functional Modules

19. 19 High Level IBEX Architecture Overview Modularity –Ability to use, add or exchange specific components independently (with minimal systematic effect) Service layer abstraction (data layer, security layer, validation, logging etc.) Extensibility –Ability to easily develop additional functionality Pluggable modules. One way service dependency (shared functionality without mutual dependency) J2EE web-application modules Scalability –Ability to grow to meet increased demand (users, locations, processing etc.) Web distribution Hardware architecture + component separation Robust database + data layer abstraction Appropriateness –Consideration of the context of use and implementation throughout. Open Source Web distribution Standalone + Distributed Environment Software selection Migration tools Segregation of duties (development consideration) –Layered architecture with uni-directional dependence General Application Architecture Principles

20. 20 Agenda I.Design Methodology II.General Application Architecture Principles III.High Level IBEX Architecture Overview IV.Application Layer 1 - User Interface

21. 21 Application Layer 1 - User Interface Web Application Interface Design –Largely determines user interface choices –Discreet requests –Browser limitations –Potential Communication limitations (bandwidth, service failures) Model/View/Controller (MVC) Architecture –Model Contains the application state (to be rendered in the view) –View Renders the application state (contained in models) –Controller Handles the user interaction, manages the models and the views and user interaction logic

22. 22 Application Layer 1 - User Interface Static Web Site Dynamic Web Application

23. 23 Application Layer 1 - User Interface Logical Model

24. 24 Application Layer 1 - User Interface MVC – General Sequence Diagram

25. 25 Application Layer 1 - User Interface Model and Controllers - Apache Struts Framework Views – JSP (using JSTL and Tag libraries) View Layout Management – Specialized (handling HTML frames) IBEX MVC Choices

26. 26 Application Layer 1 - User Interface Struts MVC

27. 27 Application Layer 1 - User Interface Struts MVC Other Framework benefits –Validation –Internationalization –Logging –Exception Handling Declarative Configuration (Using XML) –Front Controller –Actions –Forms

28. Thank you Next Session – IBEX Application Architecture II - (Data Layer & Reporting)