Current Organizations / Institutes

The organizations/institutes from the scholar's latest article


Tilen Hliš has a total of 10 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    A Workflow for Geospatial–Temporal Numerical Association Rule Mining from Enriched Cycling Activity Data

    by Tilen Hliš, Iztok Fister, Sancho Salcedo-Sanz, Iztok Fister

    Training Center XML (TCX) files store detailed cycling activity data. However, conventional association rule mining methods do not directly capture their geographic context. This study proposes a geospatial–temporal method for numerical association rule mining from enriched TCX-based cycling activity data. The method transforms fused trackpoint-level observations, enriched with OpenStreetMap and Open-Meteo attributes, into a property graph representation of recurring segments, connected paths, and segment runs. Candidate rules are evaluated within graph-derived spatial contexts using a multi-component fitness function that balances rule quality, spatial specificity, path extent, and repeated traversal evidence. The proposed method is implemented in a Julia workflow that supports rule construction, optimization-based search, rule archiving, and map-based interpretation. An evaluation on cycling activities shows that the method generates compact and locally consistent rules linking performance, temporal, infrastructure, and weather attributes. The resulting rule archive preserves both rule quality measures and spatial metadata, enabling the discovered patterns to be inspected in their geographic context.

  • Open Access

    Evaluating the Usability and Functionality of Intelligent Source Code Completion Assistants: A Comprehensive Review

    by Tilen Hliš, Luka Četina, Tina Beranič, Luka Pavlič

    As artificial intelligence advances, source code completion assistants are becoming more advanced and powerful. Existing traditional assistants are no longer up to all the developers’ challenges. Traditional assistants usually present proposals in alphabetically sorted lists, which does not make a developer’s tasks any easier (i.e., they still have to search and filter an appropriate proposal manually). As a possible solution to the presented issue, intelligent assistants that can classify suggestions according to relevance in particular contexts have emerged. Artificial intelligence methods have proven to be successful in solving such problems. Advanced intelligent assistants not only take into account the context of a particular source code but also, more importantly, examine other available projects in detail to extract possible patterns related to particular source code intentions. This is how intelligent assistants try to provide developers with relevant suggestions. By conducting a systematic literature review, we examined the current intelligent assistant landscape. Based on our review, we tested four intelligent assistants and compared them according to their functionality. GitHub Copilot, which stood out, allows suggestions in the form of complete source code sections. One would expect that intelligent assistants, with their outstanding functionalities, would be one of the most popular helpers in a developer’s toolbox. However, through a survey we conducted among practitioners, the results, surprisingly, contradicted this idea. Although intelligent assistants promise high usability, our questionnaires indicate that usability improvements are still needed. However, our research data show that experienced developers value intelligent assistants highly, highlighting their significant utility for the experienced developers group when compared to less experienced individuals. The unexpectedly low net promoter score (NPS) for intelligent code assistants in our study was quite surprising, highlighting a stark contrast between the anticipated impact of these advanced tools and their actual reception among developers.


  • Open Access

    Izzivi in vzorci zasnove mikrostoritev v brezstrežniškem okolju

    by Tilen Hliš, Luka Pavlič, Avtorji Marjan Heričko (Ur.) Univerza v Mariboru, Fakulteta Za Elektrotehniko

    Mikrostoritvena arhitektura je preizkušen, in kot kažejo podatki, tudi vodilen arhitekturni stil informacijskih rešitev zadnjega desetletja. Kot je praksa na vseh inženirskih področjih, tudi pri vpeljavi mikrostoritvene arhitekture uporabljamo preizkušene dobre prakse. Načrtovalski vzorci ne predstavljajo konkretne implementacije, temveč praktično preizkušene ideje, kako rešiti določeno skupino izzivov. Vzorce lahko umestimo v kategorije ali skupine - vsaka izmed njih naslavlja določeno problematiko s katero se soočajo razvojne skupine. Brezstrežniško računalništvo z vedno hitrejšim razvojem oblačnega računalništva vedno bolj pridobiva na pomenu. Arhitekture brez strežnika predvidevajo zasnovo informacijskih rešitev, ki vključuje zaledje kot storitev (angl. Backend as a Service - BaaS) in kodo po meri (angl. Functions as a Service -FaaS), ki se izvaja v upravljanih, kratkotrajnih vsebnikih na izbrani platformi.

  • Open Access

    The Gap between the Admitted and the Measured Technical Debt: An Empirical Study

    by Luka Pavlič, Tilen Hliš, Marjan Heričko, Tina Beranič

    Technical debt is a well understood and used concept in IT development. The metaphor, rooted in the financial world, captures the amount of work that development teams owe to a product. Every time developers take a shortcut within development, the technical debt accumulates. Technical debt identification can be accomplished via manual reporting on the technical debt items, which is called self-admitted technical debt. Several specialised methods and tools have also emerged that promise to measure the technical debt. Based on experience in the community, the impression emerged that the measured technical debt is of a significantly different amount than the self-admitted debt. In this context, we decided to perform empirical research on the possible gap between the two. We investigated 14 production-grade software products while determining the amount of accumulated technical debt via (a) a self-admitting procedure and (b) measuring the debt. The outcomes show clearly the significant difference in the technical debt reported by the two methods. We urge development and quality-assurance teams not to rely on technical debt measurement alone. The tools demonstrated their strength in identifying low-level code technical debt items that violate a set of predefined rules. However, developers should have additional insight into violations, based on the interconnected source code and its relation to the domain and higher-level design decisions.