We continue to look back at some of the outcomes of Kuali Days VIII. There were several notable outcomes from the Student Board meeting, while there is also an update on Milestones 1 and 2, project manager Rajiv Kaushik provides a nice overview of the Data Orchestration Framework and its challenges. Note: Links may require login to KS Confluence and appropriate permissions.
Project news
Board Updates
Following its meeting at the Kuali Days VIII, Student Board came away with several key issues to be addressed:
• Development of a formal signoff for functional requirements in Milestone 5 (M5) before each functional release.
• An Intellectual Property (IP) audit is planned for M5
• A security audit is planned for M5
• Functional Council decisions will be entered in the JIRA decision log after each meeting, recording opinions/votes of each institution.
• A schedule will be provided for all functional and non-functional requirements that will be included in each 1.x release for January 11 board meeting
Please take moment to review the Board meeting minutes.
Kuali Student Joins PESC
PESC Mission: “Through open and transparent community participation, PESC enables cost-effective connectivity between data systems to accelerate performance and service, to simplify data access and research, and to improve data quality along the higher education lifecycle.”
M2 and M3 Progress
Just before Kuali Days VIII, code for Milestone 2 (M2) was frozen and as of yesterday that code was released to Quality Assurance (QA). The M2 code will be released to implementers on December 23. M2 includes several key pieces, including search for three components, person academic time period, and organization.
In the meantime, progress of M3 steams ahead and code will be frozen on Dec. 18. M3 will be sent to QA on Jan. 1 and available to implementers. M3 will include a solution to the challenges the project has faced in the development of the data orchestration layer.
Project manager Rajiv Kaushik provided an overview of this progress and covered other items during a recent all-hands meeting last week. Take a listen if you missed it. (Thank to Tim H. for the recording)
Understanding the Data Orchestration Framework
Data orchestration layer or framework is one of the terms that have become part of almost every discussion regarding Release 1. However, many on and around the project team are unclear on what is meant by Data orchestration.
To put it simply: Data Orchestration Layer (DOL) serves as a "data broker" between back-end Services and the front-end UI. It is responsible for translating information between the UI and Services.
For a more detailed description of it, please review Rajiv’s description on the wiki. It includes a very helpful graphic.
No comments:
Post a Comment