Hyo Taeg Jung

Managing security and privacy in ubiquitous eHealth information interchange

Ubiquitous computing has the potential to significantly improve the quality of healthcare delivery by making relevant patient health history and vital signs readily available on-demand to caregivers. However, this promise of the ability to track electronic health information signals from distributed ubiquitous devices, conflicts with the security and privacy concerns that most people have regarding their personal information and medical history. While security and privacy concerns have been dealt with extensively in mainstream computing, there is need for new techniques and tools that can enable ubiquitous system designers in healthcare domains to build in appropriate levels of protection. Such techniques can help ensure that patient information is minimally but sufficiently available to different stakeholders in the care giving chain, and are useful in ubiquitous environments where traditional security mechanisms may be either impractical or insufficient. This paper presents a goal-centric and policy-driven framework for deriving security and privacy risk mitigation strategies in ubiquitous health information interchange. Specifically, we use scenario analysis and goal-oriented techniques to model security and privacy objectives, threats, and mitigation strategies in the form of safeguards or countermeasures. We demonstrate that traditional solutions are insufficient, while introducing the notion of purpose-driven security policies based on sensitivity meta-tags. We also show how administrative safeguards (such as those required by HIPAA rules) can be refined into intermediate specifications that can be analyzed more systematically. To validate the utility of our approach, we illustrate our major concepts using examples from ubiquitous emergency response scenarios.

Transformation of an activity model into a Colored Petri Net model

As the Unified Modeling Language (UML) becomes an industrial standard for object-oriented software development, many system models have been specified in UML notation. A system can be described in terms of the functional view through the use case model, the static view through the class model, and the dynamic view through activity or sequence model. In particular, activity model has more to do with the subject of the modeling and the experience of the modeler; for business modeling, for modeling the logic captured by a single use case or for modeling the detailed logic of a business rule. In this paper we propose mapping rules and a transformation algorithm to translate a UML activity diagram into a Colored Petri Nets (CPNs).

A systematic software development process for non-functional requirements

As the importance of non-functional requirements has increased, many researchers have become interested in software development process for non-functional requirements including the notation, modeling, and assessment of non-functional requirements. However, the characteristics of non-functional requirements are so sophisticated that there have been many topics that should be defined more clearly. In order to address one of the challenging topics, we propose a systematic software development process to support the management of nonfunctional requirements. The process consists of six steps, each of which is composed of detailed activities. Using the proposed process, the non-functional requirements can be more effectively and systematically managed and modeled.

Development of an object-oriented framework for intranet-based groupware systems

In the past decade, the research of reuse technology has been studied in software engineering including class library, design pattern, framework, and component. We have focused on the object-oriented framework because it provides the large-scale reuse. The object-oriented framework is defined as reusable designs of all or part of a software system described by set of abstract classes and the way instances of those classes collaborate. It is intended to capture the functionality common to several similar applications. It has the reused business logic and defines the customized modules by framework users. They build some applications not from scratch but based on the framework. In paper, we present an application framework of an intranet-based groupware system. Our framework consists of main and subframework. The subframework includes user authentication, BBS, EDA, organization management, and e-mail framework.

A design and implementation of object-oriented framework-based RAD tool (INTRAD)

A framework is defined as a set of reusable designs of all or part of a software system described by set of abstract classes and the way in which instances of those classes collaborate. It is intended to capture the functionality that is common to several similar applications. By developing and reusing frameworks, the reuse also encompasses design and analysis. When programmers develop applications in a specific domain using a RAD (rapid application development) tool with which frameworks are provided, they can focus their attention on their particular problem domain and do not have to start from scratch each time they write applications. In this paper, we design and implement a framework diagram and a framework-based RAD tool, called INTRAD (INTranet RAD). Also, we implement an e-mail framework for the INTRAD system, which supports the development of intranet applications.