• Proceedings of the Korea Information Processing Society Conference
• /
• 2000.04a
• /
• pp.766-769
• /
• 2000

OMG의 공식 표준으로 자리 잡은 UML은 9 종류의 기본 모델들을 기초로 하여 다양한 관점에서 대상 소프트웨어 시스템을 모델링 하도록 지원해주고 있다. 특히 Use Case의 경우 시스템 사용자와의 대화의 수단으로 시스템이 최종 사용자에게 제공하는 서비스들을 잘 표현하고 있다. 그러나 객체 모델이나 순차도 등의 다른 모델들에 비해 설명이 보다 모호하고, 정형화 되어 있지 않아서, 특히 전사적인 규모의 실무에 Use Case 모델 을 적용할 경우, 여러 가지 어려움들이 있다. 개념 단계와 상세 단계에서의 일관성 유지 문제, 하부 시스템으로 나누어 작업 시, ${\ll}include{\gg}$ 나 ${\ll}extend{\gg}$ 관계의 Use Case에 대한 배치, 전체나 일부에서 공통으로 사용되는 ${\ll}include{\gg}$ Use Case의 표현 문제 등이 그것들이다. 본 논문에서는 실무 적용 시 부딪힐 수 있는 Use Case 모델링의 그러한 문제점들에 대한 실무적인 지침들을 사례 연구와 함께 제안하고자 한다.

• Journal of Information Technology Applications and Management
• /
• v.12 no.1
• /
• pp.21-34
• /
• 2005

Object-oriented paradigm has required the fundamental changes in the developers' practice and orientation. However. the relevant literature has not still provided the solid practical methodology but created some myths regarding Use Case modeling. In this study. we attempt to 'demythologize' some key aspects of Use Case Modeling by describing what we have observed in our research and practice. In order to identify the developers' perceptions. the survey methodology was utilized. By discussing the differences between what must be done and what has been done. this study provides rich insights into the better understanding of the Use Case modeling and the successful development of object-oriented systems.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2001.10a
• /
• pp.347-350
• /
• 2001

이 논문은 기존의 Use Case 방법론을 개선하려는데 초점을 두고 있다. Use Case 방법론의 설계단계 중, 설계 프랙티스(Design practices)단계에 소프트웨어 테스팅 개념을 적용하였다. 이 방법은 먼저 사용자의 요구 사항을 상호작용 다이어그램을 통해 분석하고, 설계 컴포넌트(Design Component Units)라고 불리는 기능적 컴포넌트들로 새롭게 정의하고 추출한다. 추출된 기반을 바탕으로 생성된 설계 컴포넌트들을 설계 스키마(Design schema)에서 계층구조로 분할하는 방법이다. 여기서 개발자들의 목적에 따라 선택한 수 있도록, 다양한 기준에 적용한 수 있는 여러 가지 설계 컴포넌트들을 정의하였다. 개선된 Use Case 방법론을 토대로 변환 알고리즘[11]을 이용해 새로운 Use Case 툴을 개발하고자 한다.

• Asia pacific journal of information systems
• /
• v.3 no.1
• /
• pp.31-53
• /
• 1993

Computer Aided Software Engineering(CASE) tools are suggested as an automated method for the efficient development of softwares. This study are intended to measure the use level of CASE tools and to provide the meaningful information on the whole software development environment supported by CASE tools. Therefore, the results of a survey on CASE environment in Korea are empirically reported and analyzed. The use of CASE tools is measured; purposes purchasing CASE tools and achievement levels are investigated. Implications from the comparative analysis of the utilization of software engineering methodologies between the CASE user group and the non-user group are described. A proposition is suggested to check the request frequency for program change. Further studies on the reverse engineering, program reuse and the use of CASE tools under distributed processing systems such as client-server environments are suggested.

• Research in Community and Public Health Nursing
• /
• v.25 no.3
• /
• pp.159-169
• /
• 2014

Purpose: The purpose of this study was to evaluate the effectiveness of case management for patients with hypertension on their health status and medical service utilization. Methods: This study was a secondary analysis of data collected for a larger study of chronic disease management in 2008 using the National Health Insurance Corporation database. A total of 12,944 patients who received case management for hypertension were included in this analysis. The subjects of case management were classified into subgroups, namely, over-use, under-use, and non-use groups according to the amount of medical service utilization. To compare the medical service utilization, a control group was selected randomly. The data were analyzed through descriptive statistics, McNemar test, and ANOVA. Results: All the subgroups displayed significant differences in blood pressure, self-management, social support, and their characteristics of medical service utilization. The total medical expense of the under-use and non-use groups increased after case management. However, there was no decrease in the medical expense of the over-use group. Conclusion: This finding suggests that there is a need to re-examine why patients overuse medical services and to supplement specific strategies for encouraging appropriate medical service utilization, and enhancing case management efforts for the over-use group.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2003.11c
• /
• pp.1685-1688
• /
• 2003

객체지향 환경에서 복잡한 소프트웨어 시스템을 개발하기 위해서는, 그것의 복잡성과 대규모성 때문에 추상화에 의한 다계층적인 use case model 의 사용이 불가피하다. 이러한 경우 모델의 consistency 유지가 매우 주요하고 어려운 이슈가 된다. 본 논문에서는 각 추상화 단계에 따른 use case model 들 사이에서 자동적으로 형식적인 consistency 를 체킹할 수 있는 방법을 제안한다. 이 접근 방법은 rule 을 기반으로 하여 actor tree, use cose composition diagram를 use case description을 활용한다. 본 접근법을 검증하기 위하여, ITS 아키텍처 (Intelligent Transportation System architecture)의 한 파트를 예로 들어 적용하였다.

• Journal of Internet Computing and Services
• /
• v.4 no.6
• /
• pp.1-11
• /
• 2003

This paper is introduced about Design driven testing, for real time system, based on use case approaches, We focuses on a part of an extended use case approach for real time software development, which partitions design schema into layered design component architecture of functional components called "design component", We developed a use case action matrix to contain a collection of related scenarios each describing a specific variant of an executable sequence of use case action units, which reflected the behavioral properties of the real time system design, in this paper, we attempt to apply real time system with design driven testing with test plan metrics which is introduced which produces an ordering of this scenario set to enhance productivity and both promote and capitalize on test case reusability of existing scenarios.scenarios.

• Journal of KIISE:Computing Practices and Letters
• /
• v.16 no.5
• /
• pp.566-570
• /
• 2010

Use Case Point(UCP) is a measure of a software project size for software effort estimation based on use case. UCP measures the size of the software project based on the use case model. Because UCP is based on the use case model, it is intuitive and easy to obtain. Also, it does not require extra artifacts. On the other hand, UCP has some problems. UCP assumes every transaction has the same complexity. But, the number of operations and complexity of operations may affect complexity of transaction. In addition, UCP uses simple rating scale of complexity, but it may be inadequate for detailed estimates. To solve these problems, we suggest "Transaction Point(TP)", a size measure based on use case transaction. TP considers actors and operations in transaction. Complexity of transaction is based on the number of operations and complexity of operation, so it can support detailed estimation.

• Journal of Korean society of Dental Hygiene
• /
• v.8 no.2
• /
• pp.53-66
• /
• 2008

There was to purpose of this study improves analyzing cause that prosthesis brings bite engaging that is inaccurate in patient's mouth, when supposed that all conducts that do in operatory and dental laboratory are perfect. Impression did check bite by alginate impression material and polymerization style silicon impression material that use usually in presence at a sickbed Irreversibility, hydrocolloid, alginate impression material washed in flowing water and poured anhydrite after wait about 8 minutes so that region that charge interest after impression check bite may become undoing. And hydrophile property addition polymerization style impression material poured anhydrite after blow 30 considering impression material dwell time and H2 gas occurrence time (5~15 minute) after have washed in flowing water. I got each 7 models, result that manufactures total 28 and measures by third dimension measuring instrument (Meteo, Korea) following sequence curing in tray holder and floor 1, By Alginate impression when is hardened in tray holder and when is hardened in the floor after do check bite, SPH 4, SPH5 all as there is synonymy appeared(P<0.05). By in case do not use average 0.1741 in case use tray holder in 0.0447 SPH5s in case do not use average 0.2838 pastas in case use tray holder in SPH4 0.0309, When did not use both SPH4 and SPH5 tray holder, when used tray holder, 1 appeared more greatly. 2. By amity sex addition polymerization style silicon impression when is hardened in tray holder after do check bite and when is hardened in the floor SPH 4, a11 of the SPH5s very big synonymy be(P>0.05). And in case use tray holder in 0.000657 pasta SPH5s in case do not use average 0.000129 pastas in case use tray holder in SPH4 average 0.000114 pastas, by in case do not use 0.000757, I appeared more greatly when used tray when did not use both SPH4 and SPH5 tray holder, but 1 appeared is not level to keep in mind(Table 8~9). 3 SPH4 was looked very big mindfulness in model that manufacture doing impression check bite by Alginate and model that do impression check bite by amity sex accessory penalty silicon without using tray holder(P< 0.001). I use tray holder and SPH4 did not appear synonymy in model that manufacture doing impression check bite by Alginate and model that do impression check bite by amity sex accessory penalty silicon(P>0.05). Study finding of above when see synthesis Alginate certainly tray holder use must and I could know that hardening method does not exert big influence on volume stability if remove impression sieve of excess because amity sex accessory penalty silicon passes over tray, Also, Alginate impression material previewed can get heading a conspiracy style that volume stability of accessory penalty silicon impression material degree is if use tray holder.

• Proceeding of Spring/Autumn Annual Conference of KHA
• /
• 2006.11a
• /
• pp.86-91
• /
• 2006

This study is aimed to provide a guide for PC use space in apartment. To achieve this, a design about PC use space which was considered adequate location, area, form was suggested. As methods of the study, survey research method and case study. The survey was taken by five hundred-eighty-nine people who used PCs in apartment from May 2005 to July 2005 in Je-Ju province for an analysis of data. The results of the survey were showed PC use space situation and furnitures layout patterns. The case was classified by unit plans of size, and it showed design example of PC use space. In case of the 20s pyeong(about 3.30 square meters) type, PC use space was located in dead-space in the residence with minimum scale, because of 20s pyeong types are smaller than the other types. In case of the 30s pyeong type, PC use space which was divided with a partition panel was located in the livingroom expanding the room space to the balcony. In case of the 40s pyeong type, PC use space was located in the room of sons or daughters which was arranged with other furniture. The adequate area of PC use space is 1.4$^{\sim}$2.2 square meters, and it should take into account furniture size and human active sphere. And PC use space of form should consider traffic line, personal space and privacy. Besides it is required of ergonomic design in chair, table in its scale. And it is necessary development of systematic furniture for PC use space.