1. Session 13 Feedback on the Strategic Direction of the Student Systems
Presenter: Phlip Pretorius
Date: 17 March 2015

2. Positioned for success…
Recap 2014 Strategic Direction
Strategy
Road Map
Progress
In this session I will
Recap of 2014 FSDF – I will refreshing our memories on what we presented in this session at the previous UG
Strategy - Then what is our strategic goals and how we intend to achieve these goals.
Roadmap – Going into a more detail level what is on the roadmap for the student systems
Progress – lastly the development progress that we have made.

3. Recap 2014 Strategic Direction
Roadmap Inputs
User Group
Workshops
Strategic Discussions
Internal With Senior Management from clients
Technical Strategy
Marketing
New Technology
Road Map
Client Partner Participation
Recap 2014 Strategic Direction
System Usage Statistics
User Group Workshops
Development Proposals
Client Funded Development
Industry Expert Workshops
New Technology
Three-tier structure
Client – web browser
Application – in the application server
through the ADF framework.
It is no longer Java Applets
HTML page that gets rendered
Database - Oracle
Model–view–controller (MVC)
Data model
Business Rules
User Interface
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

4. Future proof your investment in ITS Integrator
Objective
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
Improve the usability of the system
Scalability is 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.
Usability is the ease of use and learnability of a human-made object
1. If you attend sessions 14 and 15 you will see how we achieved this objective.

5. Targeting High Usage Areas for Conversion Dedicated Development Team
Strategy
Technology
Oracle 11g database & Weblogic Server 11c
Mixture - Oracle ADF-Faces & Oracle Forms 11g
Targeting High Usage Areas for Conversion
Dedicated Development Team
Utilise Industry Experts
Retraining & Reskilling Staff
Adopted the Agile Development Methodology
Continuous User Feedback
Reporting Strategy to be Decided
Agile software development is a group of software development methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.
Work broken down in sprint
Planning meeting
Back log refinement meetings
Daily stand-up
Sprint Review
Sprint Retrospective
Local software requests
UG Specialist Working Groups
User feedback

6. Short Term - ITS Integrator 3
Road Map
Short Term - ITS Integrator 3
Client Funded Standard Development
Statutory changes
ITS Integrator 4
Post Integrator 4

7. Short Term: ITS Integrator 3
Several smaller items delivered that will be reported on in Sessions 14 and 15 e.g.
Custom Header with Logo
Duplicate ID overwrite
Future date for Enrolment Cancellation
Full Period Mark validity period added
More – please attend the sessions
Custom Header with Logo
A new Stylesheet, TXT2PDLL.xsl
Ground Rules
Report must be designed to print on letter head.
"*ccc.pc" and "prg.sql" programs only
Header/footer dimensions:
Height - 4 cm
Width cm
Some reports already have custom stylesheet to print header/footer.
Duplicate ID overwrite
System will not allow anymore
Supervisor can now override
Data restriction SDID
Re-registration of failed subject: Controlled by
SOD 'P1'
Apply Re-Registration of Passed Subject Rules
SOD 'P2'
Result Code - Absence for Exam with Valid Reason
SOD 'P3'
Re-Registration of Failed Subject Allowed
SOD 'P4'
Re-Registration Exam Type
Future date for Enrolment Cancellation
Auto create Mark Type and Assessment Records
SOD 'AF' / SR Change Mark Type criteria when Primary Lecturer code changes
SOD 'AG' / SR Create Mark Type criteria when new Primary Lecturer created
Action code ‘BW’ added on the Student iEnabler - Registration Restrictions
Full Period Mark validity period added
Number of months
Specified on:
Qualifiction Type
Qualification
Subject
Hierarchy of testing
Registration program in {SREGAR-1} changed to apply Full Period Mark validity rule
Supervisor can overwrite
Data Access restriction 'AFPO' in {SMNT-5}
Bulk registration for additional exams in {SSTUR4-21} changed to apply Full Period Mark validity rule
Send the iComms Letter with Attachment Loaded in the DSR
In final testing phase
Subject Summary Report
{SSTUDRN-4}
Added
ID Number
Specific Mark Type identified in SOD 'MT' / SR
ISAT Mark Type Code
Created a new stylesheet
Can be set to Default in {USERS-1}
Exam Admission Permits per Campus in {SEXAM6-2}
Print per campus
Class Attendance
Print Attendance Register per student in {SSTURL-6}
New report to print summary of attendance in {SSTUR2-11}
New Cohort objects to identify attendance in {SSTUD9-1}
New Cohort "Chain" relationship code in {SSTUD9-10}
New report to print attendance "patterns" using the chain Cohort in {SSTUR2-12}
New SOD 'MC' / SR to allow the calculation of marks for cancelled students.
Management Information in iEnabler
Changes to headcount - can count per block code.
Assessment Results statistics
Student iEnabler View Results
Created an event Code = PQ {STWEBM-7} to differentiate between showing only Primary qualifications or all qualifications.
Student will see links for every Block Code/Year enrolled for
Choose a year will see all results for all block codes.

8. Short Term: ITS Integrator 3
In process
An Appeals Functionality
Promotion and Graduation
Please attend session 17
Download and upload of assessment marks
In final testing phase.

9. Letters, Lists and Labels will be discontinued
Integrator 4
Letters, Lists and Labels will be discontinued
Only Programs that generate documents
Not set-up and log file
Concrete and measurable
Know the programs
Know what to be done
Can estimate

10. Concrete and measurable
Integrator 4
Concrete and measurable
Phase 1 Items
New system cycle for of Full period marks
Done
Do not allow mixture of compulsory and non-compulsory for the same subject in same qualification
Will be Done (by end of UG)
PNAM Local Software for approval of marks
Not started yet
Re-do Lecturer iEnabler for marks capturing

11. Integrator 4 Vague and unknown Do not know which programs
Do not know exactly what to be done
Cannot estimate

12. Integrator 4 Vague and unknown Phase 1 Items
Provide workflow functionality
Provide more immediacy
Upgrade the user experience in the iEnabler products
Workflow functionality
Please help us by providing a typical sequence of programs used in a Business Process
Describe the process
Link each step in the process to program
What is the data manipulation that is done?
More immediacy
Warn when within 10% of quota at application
Where else can this be added to the system?

13. Integrator 4 Vague and unknown Phase 1 Items
Conversion of high volume usage programs to ADF
System Cycle
Academic Structure Converted
Several programs in {SREGB} converted
Most Code structures
Busy with:
Student Biographical
Academic Applications
About 380 programs converted

14. Integrator 4 Vague and unknown
Phase 2 items
Extend mobile technology to operational aspects e.g. registration
Further refine "Interested in Studying here"
Further develop mechanisms to include our clients in the Agile Philosophy.

15. Multi-level organizational structure
Post Integrator 4
Multi-level organizational structure
Extend Text customization in iEnabler
New validation in exam paper definition for attend only
Copy of Assessment Criteria
Add a subminimum to Mark Type
Enhance export capabilities
Additional parameters for {STWEBM-3}
Prevent illegal evaluation methods in Main-Modules
Multi-level organizational structure:
Currently only have Faculty and Department on Academic Structure
Need to extend to the structure that can be created in e.g. {GCS-10}
{STWEBM-3}
Student Registration Validation Control.

16. Post Integrator 4
Change final commit of iEnabler registration program to use one standard package

17. 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.

18. Any Questions?

19. Thank you.