EDBT 2026 Demo / reviewers in the wild / expert
Mohamed Dahchour
dblp:83/1372
· DBLP profile ↗
7ranked-venue papers
5as first author
1since 2021 · last 2021
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Databases, data management, data science and information retrieval · 5 · 5 first-authorSoftware engineering, systems software and programming languages · 3 · 2 first-authorArtificial intelligence and machine learning · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 since 2021
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Databases, data mining, and information retrieval
1 paper |
Data models and query languages · 67% Query processing and optimization · 33% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Data models and query languages
conceptual modeling |
0.0 | 1 | 2002 | Materialization and Its Metaclass Implementation · IEEE Trans. Knowl. Data Eng. 2002 |
Query processing and optimization
materialization |
0.0 | 1 | 2002 | Materialization and Its Metaclass Implementation · IEEE Trans. Knowl. Data Eng. 2002 |
Data models and query languages
object-oriented data model |
0.0 | 1 | 2002 | Materialization and Its Metaclass Implementation · IEEE Trans. Knowl. Data Eng. 2002 |
Methods — techniques the papers use, named apart from their topics
metaclass implementation · 0.0dynamic schema evolution · 0.0
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2021 | Following Domain Driven Design principles for Microservices decomposition: is it enough?abstractBuilding software using a microservice architecture is a means that gives more options to scale up applications, deploy them independently and limit their "blast radius" of failure. Microservices tend to solve the complexity and the increasing development problems by applying the functional decomposition principle. This main feature can become a point of weakness in the absence of a fully credible splitting mechanism. One of the main adopted approaches to design services and deal with the boundary identification concern is the Domain Driven Design (DDD). In this paper, we aim to study the efficiency of this approach. We intend to give software architects a full understanding of its capabilities and main limits to be aware of the potential resulting anti-patterns. To this end, we use graph theory to experiment and analyze a reference example, implementing many microservices good practices and patterns. The obtained results show whether if we can rely only on the DDD principles to decompose microservices, or not. Hassan Farsi, Driss Allaki, Abdeslam En-Nouaary, Mohamed Dahchour |
AICCSA | 4 |
| 2018 | Handling Tenant-Specific Non-Functional Requirements through a Generic SLA
Khadija Aouzal, Hatim Hafiddi, Mohamed Dahchour |
ENASE | 3 |
| 2004 | A role model and its metaclass implementation
Mohamed Dahchour, Alain Pirotte 0001, Esteban Zimányi |
Inf. Syst. | 1 |
| 2002 | A Generic Role Model for Dynamic Objects
Mohamed Dahchour, Alain Pirotte 0001, Esteban Zimányi |
CAiSE | 1 |
| 2002 | Materialization and Its Metaclass ImplementationabstractMaterialization is a powerful and ubiquitous abstraction pattern for conceptual modeling that relates a class of categories (e.g., models of cars) and a class of more concrete objects (e.g., individual cars). This paper presents materialization as a generic relationship between two classes of objects and describes an abstract implementation of it. The presentation is abstract in that it is not targeted at a specific object system. The target system is supposed to provide: 1) basic object-modeling facilities, supplemented with an explicit metaclass concept and 2) operations for dynamic schema evolution like creation or deletion of a subclass of a given class and modification of the type of an attribute of a class. The presentation is generic in that the semantics of materialization is implemented in a metaclass, which is a template to be instantiated in applications. Application classes are created as instances of the metaclass and they are thereby endowed with structure and behavior consistent with the generic semantics of materialization. Mohamed Dahchour, Alain Pirotte 0001, Esteban Zimányi |
IEEE Trans. Knowl. Data Eng. | 1 |
| 2001 | Definition and Application of Metaclasses
Mohamed Dahchour |
DEXA | 1 |
| 1998 | Formalizing Materialization Using a Metaclass Approach
Mohamed Dahchour |
CAiSE | 1 |