EDBT 2026 Demo / reviewers in the wild / expert
Amr Kamel
dblp:55/2562
· DBLP profile ↗
4ranked-venue papers
0as first author
1since 2021 · last 2024
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 2Artificial intelligence and machine learning · 1Databases, data management, data science and information retrieval · 1 · 1 since 2021Applied, interdisciplinary, general and emerging computing · 1
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.
| Software engineering, system software, and programming languages
1 paper |
Empirical software engineering · 77% Requirements engineering and software design · 23% |
Topics — the 2 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Empirical software engineering
developer studies |
0.0 | 1 | 2000 | Exploring O-O framework usage (poster) · ICSE 2000 |
Requirements engineering and software design
application frameworks |
0.0 | 1 | 2000 | Exploring O-O framework usage (poster) · ICSE 2000 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2024 | GizaML: A Collaborative Meta-learning Based Framework Using LLM For Automated Time-Series Forecasting
Esraa Sayed, Mohamed Maher 0001, Omar Sedeek, Ahmed Eldamaty, Amr Kamel, Radwa El Shawi |
EDBT | 5 |
| 2019 | Investigating the Use of Deep Neural Networks for Software Defect PredictionabstractMany software projects are shipped to customers containing defects. Defective software cost money, time, and lives. To reduce this harm, software companies allocate testing and quality assurance budgets. The enormous sizes of modern software pose challenges to traditional testing approaches due to the need for scalability. Defect prediction models have been used to direct testing efforts to probable causes of defects in the software. Early approaches for software defect prediction relied on statistical approaches to classify software modules and decide whether each module is a defect-prone module or not. Lately, many researchers used machine learning techniques to train a model that can classify software modules to defect-prone modules and not defect-prone modules. Starting from the new millennium, neural networks and deep learning won many competitions in machine learning applications. However, the use of deep learning to build a software defect prediction model was not investigated thoroughly. In this paper, we used a deep neural network to build a software defect prediction model and compared our proposed model with other machine learning algorithms like random forests, decision trees, and naive Bayesian networks. The result shows small improvement over the other learning models in most of the comparisons. These results prove the value of using deep learning for defect prediction and open the door for more experiments. Mohamed Samir, Mohammad El-Ramly, Amr Kamel |
AICCSA | 3 |
| 2013 | Software Effort Estimation using Regularized Radial Basis Function Neural Networks
Khaled Mohamed Shams, Haitham S. Hamza, Amr Kamel |
SEKE | 3 |
| 2000 | Exploring O-O framework usage (poster)abstractObject-oriented application frameworks are becoming an increasingly popular part of software development but there has been little work on studying how they are actually used. An object-oriented application framework comprises a design and an object-oriented implementation of that design meant to apply to a broad range of applications, or subsystems within a single domain, such as graphical user interfaces. FrameScan is an ongoing study with the goal of understanding how developers can effectively and efficiently understand and deploy framework technology to construct and evolve their applications. In order to study how frameworks are used, 34 students of a senior year software engineering course were divided up into six teams of five or six students each. Each team had three months to design and implement a small client-server application of their choosing with the requirement that a framework for client-server computing called CSF (Client-Server Framework) be used as part of the project. The conclusions of the study are presented. Garry Froehlich, Amr Kamel, Paul G. Sorenson |
ICSE | 2 |