This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
teaching:mfe:is [2014/03/25 12:51] svsummer [Foundations of Data Description Languages] |
teaching:mfe:is [2014/03/25 13:10] svsummer [Structural compression of relational and semantic web databases] |
||
|---|---|---|---|
| Line 109: | Line 109: | ||
| * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimanyi]] | * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimanyi]] | ||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | |||
| + | ===== Design and Implementation of a Curriculum Revision Tool ====== | ||
| + | |||
| + | Stijn Vansummeren (WIT), Frédéric Robert (BEAMS) | ||
| + | |||
| + | This MFE concers the analysis, design, and implementation of a | ||
| + | software system that can assist in the revision of teaching curricula | ||
| + | (also known as teaching programs). | ||
| + | |||
| + | The primary targetted functionalities of the software system are as | ||
| + | follows: | ||
| + | * It should allow to make different versions of the teaching programs, much in the same way as version control systems like GIT and subversion offer the possibility to make different "development branches" of a program's source code. | ||
| + | * It should allow an extensible means to check the modified program for inconsistentcies. (For example, if course X has course Y as prerequisite, then course Y should not be scheduled in 2nd semester and X in 1st semester. Moreover, the total number of ECTS of all courses should be at most 60 ECTS. ) | ||
| + | * It should allow to analyze the modifications proposed in the teaching programs, and summarize the impact that these changes could have on other programs. (For example, if a course is removed from the computer science curriculum, it should be flagged that it should also be removed from all curricula that included the course.) | ||
| + | * It should load data from (and preferably, save data to) the ULB central administration database. | ||
| + | * It should give suggestions concerning the impact of the modifications on the course schedules. | ||
| + | |||
| + | A proof-of-concept implementation of a revision tool that supports the first two requirements above is currently being developed in the context of a PROJH402 project. The MFE student that selects this topic is expected to: | ||
| + | |||
| + | * Develop this prototype to a production-ready implementation. | ||
| + | * Implement the communication with the central ULB database. | ||
| + | * Implement the impact analysis concerning the course schedules. | ||
| + | * Interact with the administration of the Ecole Polytechnique to fine-tune the above requirements; test the implementation; and integrate remarks after testing | ||
| + | |||
| + | Contact : Stijn Vansummeren <stijn.vansummeren@ulb.ac.be>, Frédéric Robert <frrobert@ulb.ac.be> | ||
| ===== Structural compression of relational and semantic web databases ===== | ===== Structural compression of relational and semantic web databases ===== | ||
| + | |||
| + | Stijn Vansummeren (WIT) | ||
| Recent research in database management systems at ULB has shown how to | Recent research in database management systems at ULB has shown how to | ||