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

Ernst Siepmann

dblp:08/2220 · DBLP profile ↗
← Back
3ranked-venue papers
3as first author
0since 2021 · last 1994
—ORCID · none

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

Systems, architecture and hardware · 2 · 2 first-authorSoftware engineering, systems software and programming languages · 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.

Software engineering, system software, and programming languages
1 paper
Software testing · 100%
Computer architecture, parallel and distributed computing, and storage systems
1 paper
Electronic design automation · 100%

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

TopicWeightPapersLastEvidence papers
Software testing
object-oriented testing
0.011994
TOBAC: A Test Case Browser for Testing Object-Oriented Software · ISSTA 1994
Software testing
regression testing
0.011994
TOBAC: A Test Case Browser for Testing Object-Oriented Software · ISSTA 1994
Software testing › test process › test management
test case management
0.011994
TOBAC: A Test Case Browser for Testing Object-Oriented Software · ISSTA 1994
Electronic design automation › design data management
design database
0.011989
An Object-Oriented Datamodel for the VLSI Design System PLAYOUT · DAC 1989
Electronic design automation
design data management
0.011989
An Object-Oriented Datamodel for the VLSI Design System PLAYOUT · DAC 1989
Electronic design automation › design methodology
VLSI design system
0.011989
An Object-Oriented Datamodel for the VLSI Design System PLAYOUT · DAC 1989

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

object-oriented modeling · 0.0
YearPublicationVenuePosition
1994 TOBAC: A Test Case Browser for Testing Object-Oriented Software
abstract
TOBAC1 is part of a test management system for object-oriented software.A test case browser built under the Smalltalk-80 environment to dejire, manage and execute test cases is introduced.The main benejit of TOBA C is support for regression testing of complex objects.TOBAC is selfadaptable to the structure of an arbitrary complex object.
Ernst Siepmann, A. Richard Newton
ISSTA1
1989 An Object-Oriented Datamodel for the VLSI Design System PLAYOUT
abstract
A complete datamodel for an integrated VLSI design system is developed in a stepwise manner. This datamodel introduces a unified view of all design domains and hierarchy levels that result in a considerable simplification of the communication among the design tools. We defined five basic objects: cell, interface, contents, instance and configuration for high level description of all design data. The model also covers views, types, alternatives, versions and the design history. In particular our handling of the configuration demonstrates reasonable response times, due to the strict avoidance of redundant information and the storage of complex objects. This datamodel can be directly used for the implementation of an efficient object-oriented design database.
Ernst Siepmann, Gerhard Zimmermann
DAC1
1989 A data management interface as part of the framework of an integrated VLSI-design system
abstract
The framework of the PLAYOUT design system supports hierarchical decomposition, multiple representations, realization alternatives, versioning, and concurrency. It includes a universal meta data schema, based on an object-oriented data model, a design database, and a design flow manager. The design work is done by toolboxes. A methodology for interfacing the toolboxes and the database system, called the data management interface, is presented. It handles the exchange of the design data as a toolbox transaction. This nonstandard transaction includes the data retrieval and preparation for the toolbox, synchronization with other transactions, and consistency check of the toolbox output data. If the check fails, the transaction in reset and the toolbox data are removed from the database. The toolbox transactions are started by the design flow manager. New toolboxes can be easily adapted to this framework by adding a toolbox description written in an object-oriented retrieval language.>
Ernst Siepmann
ICCAD1