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.

Tapio Tallgren

dblp:26/1071 · DBLP profile ↗
← Back
2ranked-venue papers
0as first author
0since 2021 · last 1997
—ORCID · none

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

Software engineering, systems software and programming languages · 2

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%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › software design
design reuse
0.011997
Configuring Designs for Reuse · ICSE 1997
Requirements engineering and software design
software product lines
0.011997
Configuring Designs for Reuse · ICSE 1997
YearPublicationVenuePosition
1997 An Architectural Style Decoupling Coordination, Computation and Data
abstract
In distributed applications, several processes are involved in serving a request. The state of the request is encoded in the states of their processes. This can lead to unnecessary complexity and hard-to-detect errors. This paper presents an architectural style, token architectures, that decouples data, control and synchronization. Tokens encapsulate the state of a computation. Service points manipulate the tokens and perform services for them. The tokens use maps to move between service stations. We show in an example how this style simplifies the design of a telecommunications application and what difficulties traditional designs must solve.
Anssi Karhinen, Juha Kuusela, Tapio Tallgren
ICECCS3
1997 Configuring Designs for Reuse
abstract
The main problem in developing software product families is how to share effort and reuse parts of design and implementation while providing variation of features and capabilities in the products.We discuss the mechanisms that are commonly used to achieve reuse and sharing in product families, and the kind of variance each is best suited for.Our analysis motivates a need for a new mechanism to deal with ad hoc variation of features found in different members of a family.We argue that higher level abstraction and parametrization techniques are not well suited for this task.We propose an alternative approach that enables sufficiently detailed designs for every variant and at the same time achieves a level of design reuse without making designs unnecessarily complex or implementations inefficient.
Anssi Karhinen, Alexander Ran, Tapio Tallgren
ICSE3