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

Tae-Hyung Kim 0002

dblp:20/6030-2 · also Tae-hyung Kim 0002 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 2010
—ORCID · unresolved

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

Software engineering, systems software and programming languages · 2 · 2 first-authorApplied, interdisciplinary, general and emerging computing · 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%

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

TopicWeightPapersLastEvidence papers
Requirements engineering and software design › distributed system design
service-oriented design
0.112010
Design of Service-Oriented Systems Using SODA · IEEE Trans. Serv. Comput. 2010

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

petri nets · 0.1aspect weaving · 0.1
YearPublicationVenuePosition
2010 Design of Service-Oriented Systems Using SODA
abstract
We propose a design methodology, Service-Oriented Design with Aspects (SODA), for service-oriented systems to address the need to continually upgrade and evolve services while maintaining various versions. Our approach treats aspects as first-class design elements and consistently applies the concept of aspect to all phases of design and evaluation. At the early design stages, crosscutting concerns are first separated out as aspects, and then, services are composed by weaving the different design elements together. The behavior of aspects and services is represented as basic Petri Nets and we present rules for weaving together Petri Nets so as to obtain behavior of the integrated system (with aspects crosscutting services). Even at the evaluation stages, performance and resource data are separated out as aspects to be woven in to the design so as to enable advanced analysis using Petri Net tools. A small order service example is used to illustrate our approach.
Tae-Hyung Kim 0002, Carl K. Chang, Simanta Mitra
IEEE Trans. Serv. Comput.1
2006 An Aspect-Oriented Approach to Resource Composition in Petri net-based Software Architectural Models
abstract
Petri net has been widely used for modeling software systems due to its mathematical soundness and support of various tools. In many cases, performance-related analyses of Petri net for a software system need to consider the resource limitations caused by a specific platform. In terms of aspect-oriented approach, the interference of various resources scattered across a software system can be regarded as a specific concern that is only necessary during its performance-related analysis process. To capture the interactions of resources within the Petri net-based software architectural model, we propose an aspect-oriented resource composition model and the XML-based representation language called the resource extension markup language (ReML) for its description. In our approach, one or more resource composition models can be developed and described in ReML separately from the development of base software architectural models. Through the weaving process, a resource composition model can be applied to extend several Petri net-based software architectural models. The resource weaver generates an augmented Petri net used for analyzing performance characteristics of the extended software architectural model with resource interactions. Our aspect-oriented approach facilitates selecting an optimal or superior resource composition model for a software architectural model, and vice versa, which is illustrated using two exemplary server models
Tae-Hyung Kim 0002, Carl K. Chang
COMPSAC (1)1