VLDB 2026 Research / reviewers in the wild / expert
Marino Rocca
dblp:41/3364
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 1994
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 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 |
Requirements engineering and software design · 100% | |
| Interdisciplinary, comprehensive, and emerging computing
1 paper |
Computational science and engineering · 100% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Requirements engineering and software design › software architecture › component-based software engineering
component integration |
0.0 | 1 | 1994 | MI - An Object Oriented Environment for Integration of Scientific Applications · OOPSLA 1994 |
Requirements engineering and software design
software architecture |
0.0 | 1 | 1994 | MI - An Object Oriented Environment for Integration of Scientific Applications · OOPSLA 1994 |
Computational science and engineering
scientific software |
0.0 | 1 | 1994 | MI - An Object Oriented Environment for Integration of Scientific Applications · OOPSLA 1994 |
| Year | Publication | Venue | Position |
|---|---|---|---|
| 1994 | MI - An Object Oriented Environment for Integration of Scientific ApplicationsabstractScientific and engineering software is often produced by integration of existing software components of the size of a whole program. However, on the average, scientific software was not developed for reusability and is quite distant from the user model of the application problem; integration and retrofitting is as such a costly process. An architecture, methodology and several C++ class libraries for supporting integration are introduced. The architecture separates a software component layer, and an integration layer. The latter in based on the concept of software model, that is an abstraction of components and a representation of the system differing from its actual physical structure. The methodology is based on matching needs with existing models. The C++ class libraries are explained in some detail. The application to two major systems is analysed and the ideas behind seven other systems are briefly outlined. Some lessons learned are summarised in the conclusions. Andrea Spinelli, Paolo Salvaneschi, Mauro Cadei, Marino Rocca |
OOPSLA | 4 |