• Journal of the Korean Operations Research and Management Science Society
• /
• v.28 no.2
• /
• pp.91-103
• /
• 2003

Use case modeling on UML (Unified Modeling Language) is getting widely used in OOAD and CBD and it is considered a useful technique in dealing with the complexity of the requirements analysis. However, some of the problems with use case modeling are that it is not structured, difficult to handle non-functional requirements, and to analyze impacts among use cases. To alleviate these problems, we propose a scenario-based goal-oriented approach for use case modeling. The proposed approach is to apply a goal-oriented analysis method to use case modeling. Since goal-oriented analysis method is not systematic and many heuristics are involved, we have adopted scenarios as the basis for goal extraction. The proposed method is applied to CBIS (City Bus Information Subsystem) in ITS (Intelligent Transportation System) domain. The proposed approach helps software engineers to analyze the impact among use cases and represent non-functional requirements.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.12
• /
• pp.3668-3674
• /
• 2009

Use case diagram is used for defining inter-action between users and systems in object-oriented modeling. It is very important to defining users' requirements for efficient software development. In this paper, we propose a object-oriented modeling process using hierarchical use case analysis for designing class model. First, We define many use case diagrams by several hierarchical modeling level. And next, we can also design class model using the use case diagrams. Our proposed modeling process provides interaction between use case model and class model. That can make us to check the modeling process during the software development. Using the proposed object-oriented modeling we can develop software based on users' requirements. It is very useful for class modeling.

• KIPS Transactions on Software and Data Engineering
• /
• v.3 no.7
• /
• pp.255-262
• /
• 2014

Our previous research[1] suggested object extraction and modeling method based on Fillmore's case grammar. This approach had not considered of use case extraction and method. To solve this problem, we adopt Fillmore's semantic method as linguistic approach into requirement engineering, which refine fillmore's case grammar for extracting and modeling use cases from customer requirements. This Refined mechanism includes the definition of a structured procedure and the representation of visual notations for 'case' modeling. This paper also proposes the use case decision matrix to identify use case size from extracted use cases based on goal oriented requirement engineering(GoRE), which related with the complexity of use case, and also prioritizes the use cases with this matrix. It demonstrates our proposal with the bank ATM system.

• 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.

• Journal of KIISE:Software and Applications
• /
• v.28 no.8
• /
• pp.537-549
• /
• 2001

소프트웨어의 생산성과 유지보수 비용을 줄여줄 수 있는 기법으로 다양한 컴포넌트 기반의 개발 방법론이 제안되고 있다. 그러나 컴포넌트 기반의 시스템에서 재사용성과 독립성이 높은 컴포넌트의 식별은 가장 중요한 성공 요소 중의 하나임에도 불구하고, 대부분의 컴포넌트 기반 방법론들에서는 직관적이고 분석자의 경험에 의존적인 컴포넌트 식별 방법만을 제공하고 있을 따름이다. 본 논문에서는 분석 단계의 산출물인 시스템의 기능 모델 Use Case 모델과 자료 모델인 클래스 모델에 기반 하여 체계적인 컴포넌트 식별 기법과 지침들을 제안한다. 먼저 클래스에 대한 Use Case의 자료 접근값을 정의하고, 정의된 접근값을 기반으로 Use Case별로 접근되는 클래스의 가중치와 클래스별 동일 접근값을 가지는 Use Case들의 가중치를 계산하다. 두 가중치를 곱하여 최종적인 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.

• Journal of KIISE:Software and Applications
• /
• v.28 no.3
• /
• pp.211-223
• /
• 2001

본 논문에서 제안하는 시나리오기반 검증기법의 목적은 UML로 작성된 객체지향 분석모델의 완전성 및 일관성을 진단하는 것이다. 검증기법의 전체 절차는 요구분석을 위한 Use Case 모델링 과정에서 생성되는 Use Case 시나리오와 UML 분석모델로부터 역공학적 방법으로 도출된 객체행위 시나리오와의 상호참조과정 및 시나리오 정보트리 추적과정을 이용하여 단계적으로 수행된다. 본 검증절차를 위하여 우선, UML로 작성된 객체지향 분석모델들은 우선 정형명세언어를 사용하여 Use Case 정형명세로 변환하다. 그 다음에, Use Case 정형명세로부터 해당 Use Case 내의 객체의 정적구조를 표현하는 시나리오 정보트리를 구축하고, Use Case 정형명세 내에 포함되어 있는 객체 동적행위 정보인 메시지 순차에 따라 개별 시나리오흐름을 시나리오 정보트리에 표현한다. 마지막으로 시나리오 정보트리 추적과 시나리오 정보 테이블 참조과정을 중심으로 완전성 및 일관성 검증작업을 수행한다. 즉, 검증하고자 하는 해당 Use Case의 시나리오 정보트리를 이용한 시나리오 추적과정을 통해 생성되는 객체행위 시나리오와 요구분석 과정에서 도출되는 Use Case 시나리오와의 일치여부를 조사하여 분석모델과 사용자 요구사양과의 완전성을 검사한다. 그리고, 시나리오 추적과정을 통해 수집되는 시나리오 관련종보들을 가지고 시나리오 정보 테이블을 작성한 후, 분석과정에서 작성된 클래스 관련정보들의 시나리오 포함 여부를 확인하여 분석모델의 일관성을 검사한다. 한편, 본 논문에서 제안하는 검증기법의 효용성을 증명하기 위해 대학의 수강등록시스템 개발을 위해 UML을 이용해 작성된 분석모델을 특정한 사례로써 적용하여 보았다. 프로세싱 오버헤드 및 메모리와 대역폭 요구량 측면에서 MARS 모델보다 유리함을 알 수 있었다.과는 본 논문에서 제안된 프리페칭 기법이 효율적으로 peak bandwidth를 줄일 수 있다는 것을 나타낸다.ore complicate such a prediction. Although these overestimation sources have been attacked in many existing analysis techniques, we cannot find in the literature any description about questions like which one is most important. Thus, in this paper, we quantitatively analyze the impacts of overestimation sources on the accuracy of the worst case timing analysis. Using the results, we can identify dominant overestimation sources that should be analyzed more accurately to get tighter WCET estimations. To make our method independent of any existing analysis techniques, we use simulation based methodology. We have implemented a MIPS R3000 simulator equipped with several switches, each of which determines the accuracy level of the

• Journal of Information Technology Services
• /
• v.21 no.2
• /
• pp.61-84
• /
• 2022

With the recent application of deep learning to Natural Language Processing (NLP), the performance of NLP has improved significantly and NLP is emerging as a core competency of organizations. However, when encountering NLP use cases that are sporadically reported through various online and offline channels, it is often difficult to come up with a big picture of how to understand and interpret them or how to connect them to business. This study presents a framework for systematically analyzing NLP use cases, considering the characteristics of NLP techniques applicable to almost all industries and business functions, environmental changes in the era of the Fourth Industrial Revolution, and the effectiveness of adopting NLP reflecting all business functional areas. Through solving research questions based on the framework, the usefulness of it is validated. First, by accumulating NLP use cases and pivoting them around the business function dimension, we derive how NLP techniques are used in each business functional area. Next, by synthesizing related surveys and reports to the accumulated use cases, we draw implications for each business function and major NLP techniques. This work promotes the creation of innovative business scenarios and provides multilateral implications for the adoption of NLP by systematically viewing NLP techniques, industries, and business functional areas. The use case analysis framework proposed in this study presents a new perspective for research on new technology use cases. It also helps explore strategies that can dramatically improve organizational performance through a holistic approach that encompasses all business functional areas.

• Journal of KIISE:Software and Applications
• /
• v.30 no.3_4
• /
• pp.293-307
• /
• 2003

Object-oriented development has been generalized, but object-oriented project planning and scheduling techniques have not been studied enough. Furthermore, it is difficult to apply the conventional software management techniques to object-oriented projects. Especially, the large scaled projects are increasing, but the project planing techniques for these large scaled projects have not been proposed enough. In this paper, we propose systematic techniques for OO based project scheduling. We suggest a 7 step-process for deriving the OO project schedule from the use-case diagram which is describing the functional requirements of the system. The proposed process includes identifying use-cases, drawing preliminary chart through interdependency analysis, identifying characteristics of each use case, determining the number of iteration, assigning use-cases to iteration, considering available resource and constraints, drawing revised PERT chart. Each step has the explanation of the input, output, and the guidelines needed to perform the step. The project scheduling technique proposed in this paper ran be used effectively in the planning phase which the purpose is to plan a development schedule to yield the high quality software in minimum time.

• The KIPS Transactions:PartD
• /
• v.9D no.4
• /
• pp.639-650
• /
• 2002

We have to carry out systematic, definite requirements analysis for the successful development of software. The UML gives the ways to grasp user or customer requirements and decide the boundary of business systems from the use case modeling. This paper presents how to extract use case diagram from the requirements specification systematically by applying the standardized rules as a part of the study for use case modeling. We modify requirements specification by applying $R_{RS}$ (Rules for Requirements Specification) and extract actor, use case, relationship by applying $R_{A}$(Rules for Actors), $R_{U}$(Rules for Use Cases) and $R_{R}$(Rules for Relationships) to the modified requirements specification separately and then become to make out use case diagram in the end. By applying the rules presented in this paper to the requirements specification for personnel management, we can reduce the existing difficulties of extracting use case diagram based on the narrative descriptions without any standardized rules.rules.