Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

J. Gonzalez-Sustaeta

dblp:82/3577 · DBLP profile ↗
← Back
1ranked-venue papers
1as first author
0since 2021 · last 1986
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Systems, architecture and hardware · 1 · 1 first-author

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
Database system architecture and tuning · 44% Data models and query languages · 44% Data integration and cleaning · 13%

Topics — the 3 heaviest of 3, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Data models and query languages
conceptual model
0.011986
An automated database design tool using the ELKA conceptual model · DAC 1986
Database system architecture and tuning › database design
database design tools
0.011986
An automated database design tool using the ELKA conceptual model · DAC 1986
Data integration and cleaning › metadata management
data dictionary
0.011986
An automated database design tool using the ELKA conceptual model · DAC 1986

Methods — techniques the papers use, named apart from their topics

schema mapping · 0.0
YearPublicationVenuePosition
1986 An automated database design tool using the ELKA conceptual model
abstract
A large group of database design methodologies relies solely on graphic representations of the conceptual schema. When this conceptual schema is translated manually to the DDL of a target DBMS errors are frequently introduced. The database design tool presented in this paper consists of a conceptual model definition language with its compiler, a data dictionary in which the metamodel of the database is stored and a mapping interface. The tool is based on the ELKA (Entity, Link, Key, Attribute) conceptual model, a model which normally relies on a graphic notation. In this tool ELKA structures are defined by the Database Administrator through the conceptual model definition language from where they are mapped automatically into database structures. The metamodel is accessible to the user through the DBMS's data manipulation language, while the equivalent database structures are accessible both to the user and the application programs. Finally, the modeling power of this tool is explored and necessary extensions are identified that are needed to handle the notion of molecular aggregation.
J. Gonzalez-Sustaeta, Alejandro P. Buchmann
DAC1