Juha Heinänen

dblp:23/2012 · DBLP profile ↗
← Back
5ranked-venue papers
5as first author
0since 2021 · last 1998
—ORCID · none

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

Computer networks · 4 · 4 first-authorDatabases, data management, data science and information retrieval · 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
Requirements engineering and software design · 100%
Databases, data mining, and information retrieval
1 paper
Query processing and optimization · 100%
Human-computer interaction and pervasive computing
1 paper
User interface design and tools · 100%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › formal specification
operational specification
0.011986
A Language for Specifying Functionality of Data Intensive Applications · ICDE 1986
Query processing and optimization › query execution
relational operators
0.011986
A Language for Specifying Functionality of Data Intensive Applications · ICDE 1986

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

pattern-driven input/output actions · 0.0
YearPublicationVenuePosition
1998 A fair buffer allocation scheme
Juha Heinänen, Kalevi Kilkki
Comput. Commun.1
1994 Rolling-Out ATM Based Network Services
Juha Heinänen
Comput. Networks ISDN Syst.1
1992 Frame Relay as a Multiprotocol Backbone Interface
Juha Heinänen
Comput. Networks ISDN Syst.1
1991 Review of Backbone Technologies
Juha Heinänen
Comput. Networks ISDN Syst.1
1986 A Language for Specifying Functionality of Data Intensive Applications
abstract
We are building an application generation environment to provide user friendly means for rapid development of interactive information systems. The environment consists of two closely integrated subsystems: one for specifying the functionality of an application and the other for defining its user interfaces. This paper concentrates on the former and introduces an operational specification language that combines pattern driven input/output actions with simple relational operations. The description of the main concepts of the language is embedded in a running example that illustrates the usefulness of the approach.
Juha Heinänen
ICDE1