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

Gyusang Shin

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

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

Software engineering, systems software and programming languages · 2Computer networks · 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.

Computer networks
1 paper
Internet of things and sensor networks · 77% Routing and switching · 23%
Software engineering, system software, and programming languages
1 paper
Software maintenance and evolution · 50% Requirements engineering and software design · 50%

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

TopicWeightPapersLastEvidence papers
Internet of things and sensor networks › low-power wireless
low-power and lossy networks
0.112011
Click based IP border router for low-power and lossy networks · SenSys 2011
Routing and switching
routing
0.012011
Click based IP border router for low-power and lossy networks · SenSys 2011
Requirements engineering and software design
software architecture
0.011998
Restructuring OODesigner: A CASE Tool for OMT · ICSE 1998
Software maintenance and evolution
software reengineering
0.011998
Restructuring OODesigner: A CASE Tool for OMT · ICSE 1998

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

click modular router · 0.1c++ · 0.0OMT · 0.0
YearPublicationVenuePosition
2011 Click based IP border router for low-power and lossy networks
abstract
The IETF's new protocols for Low-power and Lossy Networks are delegating their several functions to an IP border router that has more resources than other constrained nodes in the network. It makes the complexity of the IP border router higher than other conventional routers. For this reason, a well-designed platform for routers is important for fast development and easy debugging. In this paper, we check the feasibility of Click Modular Router platform to develop the IP border router for LLNs. Then, we present a design and an implementation of the IP border router on top of Click.
Jongsoo Jeong, Haeyong Kim, Gyusang Shin, Seontae Kim
SenSys3
1999 Experience with Porting a Unix Version CASE Tool to the Corresponding Java Version
abstract
The paper presents similarity in the design and the implementation of a computer aided software engineering (CASE) tool developed on two platforms. OODesigner is a tool that was initially developed to support the Object Modeling Technique (OMT). An initial Unix version was developed in 1994. In 1997, after the completion of the Unix version, we began developing a Java version to support Unified Modeling Language (UML). The development of a CASE tool is a typical application of the Model-View-Controller (MVC) paradigm. Thus, we observed a common design pattern among the versions in the MVC points of view. This design similarity can be used to develop several kinds of CASE tools with the corresponding design notations. We present the process we followed to develop the two versions and we discuss the similarity found between them. We also outline a generic architecture for the design and implementation of CASE tools.
Gyusang Shin, Euyseok Hong
APSEC2
1998 Restructuring OODesigner: A CASE Tool for OMT
abstract
This report describes our experience acquired when we restructured OODesigner, a computer aided software engineering (CASE) tool for object modeling techniques (OMT). We had developed the version 1.x of OODesigner during 3 years since 1994. Although we had developed this version using OMT and C++, we recognized the potential maintenance problem that originated from the ill-designed class architecture. Thus we totally restructured the old version of OODesigner during 12 months, and obtained a new version that is much easier to maintain than the old one.
Gyusang Shin
ICSE2