1. Session 34 Feedback on the Strategic Direction of the Finance Systems
Presenter: Marchand Hildebrand
Date: 11 March 2014

2. User Group 2014 Finance Sessions
Nokuthula Mafenuka
Session 32 Integrator 3 Enhancements SD,BL,CT,CB
Neetham Dabideen
Session 33 Integrator 3 Enhancements PM, GL, Web
Marchand Hildebrand
Session 34 Development Roadmap
SD, CB examples Nokuthula Mafenuka
Discussion / feedback
Session 35 Introduction ADF
AR, Space examples Raymond Schoonraad
Session 36 ADF Continued

3. Integrator positioned for success…
Process
New Technology
Road Map
Client Partner Participation
User Group Proposals

4. The Process Followed
System Usage Statistics

5. System Usage Statistics

6. System Usage Statistics User Group Workshops Development Proposals
The Process Followed
System Usage Statistics
User Group Workshops
Development Proposals
Industry Experts – would have like to invite everybody but it is not practical. If you would like to be involved in the future please let me know !

7. Development Register

8. The Process Followed
System Usage Statistics
User Group Workshops
Development Proposals
Client Funded Development
Industry Expert Workshops

9. Our Approach
Client Centered
Appropriate Technology
Best Practice
Knowledge & Experience

10. Technology Path ADF Java/J2EE Web application development framework
Java/J2EE Web application - web-based enterprise applications
Development Framework - environment for developing, building and deploying applications, products and solutions
What is ADF?
A software framework is a universal, reusable software platform to develop applications, products and solutions.
Short for Java 2 Platform Enterprise Edition. J2EE is a platform-independent, Java-centric environment from Sun for developing, building and deploying Web-based enterprise applications online. The J2EE platform consists of a set of services, APIs, and protocols that provide the functionality for developing multitiered
Three-tier organization
In three-tier organization, applications are structured around three physical tiers: client, application, and database.[7][8][9][10] The database is normally an RDBMS. The application contains the business logic, running on a server and communicates with the client using HTTP.[11] The client, on web applications is a web browser that runs HTML generated by the application layer.[12][13] The term should not be confused with MVC, where, unlike in three-tier architecture, it is considered a good practice to keep business logic away from the controller, the "middle layer".[14][15]
Many frameworks follow the MVC architectural pattern to separate the data model with business rules from the user interface. This is generally considered a good practice as it modularizes code, promotes code reuse, and allows multiple interfaces to be applied. In web applications, this permits different views to be presented, such as web pages for humans, and web service interfaces for remote applications.

11. Development Frameworks
Three-tier structure
Client
Application
Database
Three-tier organization
In three-tier organization, applications are structured around three physical tiers: client, application, and database. The database is normally an RDBMS. The application contains the business logic, running on a server and communicates with the client using HTTP.The client, on web applications is a web browser that runs HTML generated by the application layer.
Java Database access technology JDBC – allows java programs to execute SQL

12. Development Frameworks
Model–view–controller (MVC)
Data model
Business Rules
User Interface
MVC
The MVC architectural pattern to separate the data model with business rules from the user interface. This is generally considered a good practice as it modularizes code, promotes code reuse, and allows multiple interfaces to be applied. In web applications, this permits different views to be presented, such as web pages for humans, and web service interfaces for remote applications.

13. Oracle ADF View Controller Model

14. ADF Faces - Example

15. Improve the usability of the system
Our objectives
Improve the usability of the system
Future proof your investment in ITS Integrator
Improve the scalability of the iEnabler products
Enable the use of web-, cloud- and mobile devices
Improve and enrich functionality
Usability is the ease of use and learnability of .
Future-proofing is the process of anticipating the future and developing methods of minimizing the effects of shocks and stresses of future events.
Scalability is the ability of a system, network, or process to handle a growing amount of work in a capable manner or its ability to be enlarged to accommodate that growth
Based on feedback from clients, advice from industry experts and own research

16. Short Term
Integrator 3 is available
Some client funded standard development on the Integrator 3 Platform in process
ITS Integrator 4
ITS Integrator 4 or First priority for Integrator 5
Medium - and Long Term (ITS Integrator 5 and future releases)

17. ITS Integrator 4 or First priority for Integrator 5
Roadmap
Short Term
Integrator 3 is available
Some client funded standard development on the Integrator 3 Platform in process
ITS Integrator 4
Mixture Oracle ADF-Faces & Oracle Forms 11g
ITS Integrator 4 or First priority for Integrator 5
Medium - and Long Term (ITS Integrator 5 and future releases)

18. Client Funded Std Development on Int 3
Supplier Biographical {FPMM-2}
BBBEE status indicator
Involved persons
Required Documentation,
Validations i.e. Banking Detail
Debt Collection Interface (Vericred) {FSDC}
Ad-hoc EFT payments {FCTO-6}

19. Client Funded Standard Development on Integrator 3
Outstanding Orders {New Option}
Asset iEenabler - enhancement
Inter Departmental Request {GL Journals}
Travel Request integrated Fin Requisition
Additional Payment Methods in the iEnabler (e.g. Vouchers)

20. Integrator 4
Implement new technology while introducing some functional improvements
Focus implementation on system areas used most intensively
Continue partnering with clients to drive system functionality through
Consideration of development requests (ITS Integrator User Group and Other)
Continuously reassess the relevance of system modules (from user group- and other feedback)
Develop adaptors / interfaces to systems that provide functionality outside the core ITS Integrator scope
User Interface Improvements
New Functionality
Mixture of Forms & ADF Applications

21. Mixture of Forms & ADF Applications

22. Integrator 4
Student Debtors (SD)
Student Account Query
Maintain Student Status
Delete Financial Status
Student Statement / Invoice

23. Integrator 4
Cash Books (CB)
Maintain Statement Journals
Query Bank Statements
Ability to Recreate Bank Reconciliation
Distribute Cash Book Journal

24. Integrator 4
Counter System (CT)
Distribute Receipt
Distribute Payment and Cash Book Journal
Internet Payments / EFT’s

25. Integrator 4
Accounts Receivable (AR)
Maintain Invoices (Cancel Invoices)
Debtor Query (No-show’s)
Debtor Biographical

26. Integrator 4
VAT
General Ledger (GL)
Journal Processing
GL Query - Including Fin iEnabler
Requisitions (Finance iEnabler)
Purchase Orders

27. ITS Integrator 4 / First priority for Integrator 5
Continued implementation of ADF
Ability to handle of multiple companies i.e. institutes, trusts, etc
Student Journals
Update of Payment Agreement
Maintain Show Indicators
Student Debt / Income Reporting Enhancements
Receipts / Payments

28. ITS Integrator 4 / First priority for Integrator 5
Asset Surveys
Approvals
Asset iEnabler
Research Administration
Vehicle Tracking

29. Medium & Long Term
Subsidy Distribution
Upload SD Transactions from File
Improved Functionality to Implement Tuition and Other Fee Increases.
Cash Flow - Ability to Exclude Earmarked Funding, Releasing Income Based on Cash Received
Procurement Tenders
Automation of transactions i.e. Re-valuation

30. Short Development Cycles User Feedback
Client Participation
Waterfall vs Agile
Short Development Cycles
User Feedback
Agile software development is a group of software development methods based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It
The waterfall model is a sequential design process, often used in software development processes, in which progress is seen as flowing steadily downwards (like a waterfall) through the phases of Conception, Initiation, Analysis, Design, Construction, Testing, Production/Implementation, and Maintenance.

31. Invitation to participate
Suggestion from Adapt IT
Define Business Objectives
Determine a list of feature set(s) that will allow the client to achieve business objectives
Adapt IT and the client together determine the hours that the client is prepared to commit to.
Start development in Scrum Sprints
The goal of each sprint is communicated
After review, clients test and confirm the sprint goal achieved
Client billed for sprint delivery (billing milestones may include several sprints)
Because of incremental addition of features, client will have working software.
If the pre-determined hours are reached and not all features added, negotiate new development hours
If all features has been developed and there are still hours left, new features can be included.
This must be negotiated with Adapt IT.
How do we plan to do this?
on the INT4 roadmap (that will be discussed in later sessions)
This roadmap has been based on
Adapt IT strategic technology direction
UG Proposals
Strategic meetings with high level client management representatives.
Using a platform such as Webex to communicate and show
Initial client involvement:
once a month
Need more frequent feedback and that can be done at bi-weekly review meetings

32. User Group Proposals
User should continue to propose system enhancement
Client input / requests valuable
User Feedback

33. Questions

34. Disclaimer
The information, comments and material presented in this presentation are provided for information purposes only. The presentation is not addressing all possible technical or business aspects and does not claim to be complete or exhaustive.
Adapt IT reserves the right to change its business or product development plans as circumstances dictate.
This document may not be reproduced or distributed without the written permission of Adapt IT (Pty) Ltd.

35. Thank you