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 [2013/09/30 11:51] tcalders [Pattern Mining for Object Tracking] |
teaching:mfe:is [2014/02/14 15:15] svsummer |
||
|---|---|---|---|
| Line 109: | Line 109: | ||
| * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimanyi]] | * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimanyi]] | ||
| + | |||
| + | ===== Efficient computation of simulation for structural indexing ===== | ||
| + | |||
| + | Simulation and bisimulation are fundamental notions in computer science. They underlie many formal verification algorithms, and have recently been applied to the construction of indexing data structures for relational databases and the semantic web. | ||
| + | |||
| + | Essentially, a simulation or bisimulation is a relation on the nodes | ||
| + | of a graph. Unfortunately, however, while efficient main-memory | ||
| + | algorithms for computing whether two nodes are simulating or bisimulating exist, these algorithms fail when no the input graphs are too large to fit in main memory. | ||
| + | |||
| + | The goal of this thesis is to study, compare, and implement various | ||
| + | approaches to computing simulation in an external memory setting, for | ||
| + | the explicit purpose of using the implementation to efficiently construct | ||
| + | simulation-based indexes for large relational databases and the | ||
| + | semantic web. | ||
| + | |||
| + | * Contact : [[stijn.vansummeren@ulb.ac.be|Stijn Vansummeren]] | ||
| ===== Aspects of Text Analytics and Information Extraction ===== | ===== Aspects of Text Analytics and Information Extraction ===== | ||
| Line 250: | Line 266: | ||
| * Contacts : | * Contacts : | ||
| - | * [[avaisman@ulb.ac.be|Alejandro Vaisman]] (CoDE) | ||
| * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | ||
| Line 265: | Line 280: | ||
| * Contacts : | * Contacts : | ||
| - | * [[avaisman@ulb.ac.be|Alejandro Vaisman]] (CoDE) | ||
| * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | ||
| Line 277: | Line 291: | ||
| * Contacts : | * Contacts : | ||
| - | * [[avaisman@ulb.ac.be|Alejandro Vaisman]] (CoDE) | ||
| * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] (CoDE) | ||
| - | |||
| - | ===OLD Subjects 2011-2012==== | ||
| - | |||
| - | ===== From Relational Databases to Linked Open Data ===== | ||
| - | |||
| - | |||
| - | [[http://www.w3c.org/|RDF]] is the [[http://www.w3c.org/|W3C]] proposed framework for representing information | ||
| - | in the Web. Basically, information in RDF is represented as a set of triples of the form (subject,predicate,object). RDF syntax is based on directed labeled graphs, where URIs are used as node labels and edge labels. In spite of the constant growth in the amount of RDF data available on the Web, and the growing number of applications for these data, most companies still store their data in relational databases. Nevertheless, many of these companies are interested in publishing (part of) their data on the Web in RDF format. Further, the [[http://linkeddata.org/|Linked Open Data]] (LOD) initiative is aimed at extending the Web by means of publishing various open datasets as RDF, setting RDF links between data items from different data sources. This suggests that the problem at hand will be, in the near future, to transform relational to Linked Open Data. | ||
| - | |||
| - | The increasing interest in publishing relational data as RDF resulted in the creation of the W3C RDB2RDF Working Group, which is elaborating a recommendation for mapping relational to RDF data. This mapping poses challenges not only from a theoretical point of view, but also from a practical one as well. Just to mention a few ones: generating IRIs to represent RDF resources is not trivial, as it is not the representation of keys (e.g., primary and foreign) in the RDF world. | ||
| - | |||
| - | We propose to develop a Relational to RDF translation framework, using the principles stated in the [[http://www.w3c.org/TR/201/WD-rdb-direct-mapping-20110324/|W3C RDB2RDF]] working group document. This framework will be tested using real-world datasets provided by interested partners. Further, our goal is to transform the resulting RDF graph using the LOD principles, which will allow to leverage the value of each partner's dataset. | ||
| - | |||
| - | * Contacts : | ||
| - | * [[avaisman@ulb.ac.be|Alejandro Vaisman]] (CoDE) | ||
| - | * [[svsummer@ulb.ac.be|Stijn Vansummeren]] (CoDE) | ||
| - | |||
| - | |||
| - | ===== Projects and issues management tools for public safety software development ===== | ||
| - | |||
| - | Intergraph S.A. (SG&I Division) is the leading provider of software solutions to the Belgian Emergency Services (100, 101 &112 call centers). Intergraph’s responsibility is to deliver high quality software and provide maintenance servicesto the users of these services (police, medical and fire brigades). | ||
| - | |||
| - | Intergraph uses several tools (Project Plan, Redmine, SharePoint,…) to plan new projects and to report and track issues. Each tool has its strengths and its target audience. For example, Redmine is used as a defect tracking tool by the development team. It enables to control the bug fixing workflow from reporting to solution verification by the quality team. Project Plan and SharePoint are used by managers to communicate higher level information like cost, milestones and progress. | ||
| - | |||
| - | Intergraph Development Team has the objective to reach CMMI Level 2 (Capability Maturity Model Integration). This level of maturity requests to develop software with processes that are planned and measured. Planning is based on agile Sprint methodology. Measures are for examples effort, tasks burn down, cost, reaction time…We want to integrate these processes – planning and key measures - in our Redmine environment. We want to be able to report automatically project delays to the executive management and costs to the accounting department using the data reported in Redmine. | ||
| - | |||
| - | |||
| - | The goal of this thesis is: | ||
| - | - To understand the CMMI Level 2 and make proposals to reach that level. | ||
| - | - To study the feasibility of enhancing the Redmine application with tools that will help us to implement better planning and reporting. | ||
| - | - To design, develop and test these tools. | ||
| - | Intergraph S.A. is looking for profiles able to handle such tasks. This thesis can be seen as a main entrance gate to the Company for a permanent position. | ||
| - | |||
| - | * References : | ||
| - | * [[http://www.intergraph.com/]] | ||
| - | * [[http://www.intergraph.com/global/be/]] | ||
| - | * [[http://www.sei.cmu.edu/reports/10tr033.pdf]] | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | ===== Automatic Support for Spatio-Temporal Integrity Constraints ===== | ||
| - | |||
| - | The Object Constraint Language (OCL), part of the UML standard, is a formal language for defining constraints on UML models. The [[http://dresden-ocl.sourceforge.net/|Dresden OCL toolkit]] is an open source software platform for OCL tool support. One of the tools comprising the OCL toolkit is OCL2SQL, an SQL code generator that generates an SQL check constraint, assertion or trigger for an OCL invariant. OCL2SQL can be used and adapted for different relational database systems and different object-to-table mappings. | ||
| - | |||
| - | The objective of the project is to extend the toolkit for taking into account spatial, temporal and multi-representation constraints, as those proposed by the MADS model. | ||
| - | |||
| - | * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimányi]] | ||
| - | |||
| - | |||
| - | ===== A database infrastructure for storing and manipulating trajectories ===== | ||
| - | |||
| - | Thanks to current sensors and GPS technologies, large-scale capture of the evolving position of individual mobile objects has become technically and economically feasible. | ||
| - | |||
| - | Typical examples of moving objects include cars, persons and planes equipped with a GPS device, animals bearing a transmitter whose signals are captured by satellites, and parcels tagged with RFIDs. | ||
| - | |||
| - | Analysis of trajectory data is the key to a growing number of | ||
| - | applications aiming at global understanding and management of complex phenomena that involve moving objects (e.g. worldwide courier distribution, city traffic management, bird migration monitoring). | ||
| - | |||
| - | This project consists of studying and extending the limited capabilities of commercial data management systems for storing and manipulating the position of moving objects all along their lifespan. | ||
| - | |||
| - | |||
| - | * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimányi]] | ||
| - | |||
| - | |||
| - | ===== Extending PostGIS for the support of continuous fields ===== | ||
| - | |||
| - | PostGIS is an popular open-source database system supporting spatial application applications. | ||
| - | |||
| - | Continuous fields are phenomena that are perceived as having a value at each point in space and/or time. Examples of such phenomena include | ||
| - | temperature, altitude, or land use. In [[http://code.ulb.ac.be/dbfiles/VaiZim2009aincollection.pdf|this paper]] we defined a data type that encapsulates the different operations needed | ||
| - | for manipulating continuous fields. The objective of the project is to implement such a data type in the PostGISsystem. | ||
| - | |||
| - | * Contacts : | ||
| - | * [[ezimanyi@ulb.ac.be|Esteban Zimányi]] | ||