• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.13 no.2
• /
• pp.243-252
• /
• 2009

This paper presents an implementing of Use Case Description writing tool to support systematically writing and editing Use Case Description. It also supports both 1 column and 2 column formats of use case scenarios and increases convenience for editing scenario steps with automated step numbering function we presented. It results in not only user-friendly and effective description for use case but also contributing to development of integrated use case modeling tool with use case diagram.

• Journal of KIISE
• /
• v.42 no.9
• /
• pp.1117-1123
• /
• 2015

Use The Use Case Points method is a software estimation method that is based on user requirements. When requirement analysts elicit user requirements, they obtain different use cases because different levels of detail are possible for the Use Case, and this affects the Use Case Points. In this paper, we suggest a method to refine the level of detail of the Use Case by using the concept of an elementary function. This refinement method achieves the desired reliability for the Use Case Points because it produces less of a deviation in the Use Case Points for different requirement analysts than other methods that are based on the step, transaction, and narrative of the Use Case.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.379-381
• /
• 2005

비즈니스 시스템 분석을 위한 비즈니스 모델링에서 사용자와 개발자간의 원활한 의사소통은 프로젝트의 성공을 결정할 수 있는 중요한 요소이다. UML 기반의 유스케이스 모델링은 숙련자의 경험에 많이 의존하고 있으며, 모델링의 수준을 결정하기 어렵고, 또한 사용자가 쉽게 이해하기가 어렵다. 따라서 사용자의 업무를 분석하여 직관적으로 표현할 수 있는 속성구조 다이어그램을 이용한 정보구조 모델링은 사용자와 개발자 모두 쉽게 이해할 수 있는 구조로 사용자의 요구사항을 직관적으로 분석하여 요구사항 분석에서부터 발생되는 사용자의 잦은 변경을 줄일 수 있으므로 유스케이스 모델링을 보완할 수 있는 효과적인 방법이 될 수 있다.

• Journal of KIISE:Software and Applications
• /
• v.31 no.7
• /
• pp.869-882
• /
• 2004

This paper proposes an effective method to create logically consistent and structured requirement model by applying consistency control approach of the formal method to the use-case modeling. This method integrates the multi-perspective scattered requirement segments that may overlap and conflict each other into a structured requirement model. The model structure can be analyzed based on context goal and concerned area overlap analysis. The model consistency can be achieved by using specification overlap-based consistency checking method as an integration vehicle. An experimental application to case study shows that the Proposed method can successfully identify requirement overlaps and inconsistency. It can also transfer multi-viewpoint requirement segments into a consistently integrated use-case model to clarify software behaviors and functionality This method helps users to enhance capability to identify specification inconsistency in the use-case modeling at the early stage of software engineering development. The proposed approach can also facilitate communication between users and developers to ensure customer satisfaction.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2013.10a
• /
• pp.805-808
• /
• 2013

As the development type of domestic technology on information & communications have changed from following development to leading devalopment, developing new technology and creating new market through securing basic technology and IPR has been more essential than ever before. At the same time, it is required to increase the possibility of commercialization on developed technology. Therefore, it is necessary to formulate the consensus on the value and function of project at project planning phase for creative & innovative idea to be adopted into project and to be performed successfully. Accordingly, this paper proposes use case developing methodology adopted to creative & innovative project by analysing use case developing method in software engineering. Also, new methodology is appled to LASA display developing project to prove the reliability. Since the demands on new technology is henceforth expected to increase gradually, it is necessary to continue to study on the methodology of being more formal and logically related between phases as well as on that of analysing relationship among use cases and proving logical reliability of use case.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.07b
• /
• pp.370-372
• /
• 2005

아키텍처는 요구사항을 기반으로 생성되어야 한다. 특히 비기능적 요구사항은 아키텍처의 생성에 않은 영향을 미치는 요인이다. 본 논문은 아키텍처를 생성하기 위한 요구사항 분석 기법과 전략을 제안한다. 제안하는 방법은 유스케이스를 이용하여 기능 요구사항을 추출하고, AHP(Analytic Hierarchy Process)를 이용하여 비기능 요구사항의 중요도를 정량적으로 분석한다.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2008.10a
• /
• pp.507-510
• /
• 2008

In this paper, we present a method of editing use case scenario for use case description. It presents interaction between scenario steps for automating the step numbering in editing scenarios and identify elements of scenario steps, extension and data structure and maintaining relationship of success scenario and ex tension.

• The KIPS Transactions:PartD
• /
• v.12D no.7 s.103
• /
• pp.1071-1078
• /
• 2005

Use case modeling is a widely used technique for functional requirements analysis of business system but it is difficult to identify a use cases at the right level and use case specifications are too long and confusing. It is also hard to determine a functional decomposition Phases·s of use cases. Therefore customer doesn't understand the use cases. This paper is defining concept of the Information Structure Modeling(ISM) and analyzing business system for the customer's perspective. ISM is an efficient mechanism for analyzing user requirements and for Identifying objects in a business system using Attribute Structure Diagram which is a major tool of the ISM that describes user event. This paper is also to show how the classes are classified and derived as event-asset-transaction type in ISM. It provides a user-friendly approach to visually representing business model.

• Journal of KIISE:Software and Applications
• /
• v.29 no.4
• /
• pp.211-224
• /
• 2002

As system become larger and more complex, it is important to correctly analyze and specify user's requirements. Use case modeling is widely used in Object-Oriented Analysis and Design(OOAD) and Component-Based Development(CBD). It is useful to mitigate the complexity of the requirements analysis. However, use cases are difficult to be structured, to explicitly represent non-functional requirements, and to analyze what is affected by changes of use cases. To alleviate these problems, we propose scenario-based goal-oriented approach for use case modeling. The approach is to apply goal-oriented analysis method to use case model. Since goal-oriented analysis method is not systematic and heuristics is considerably involved, we adopted scenarios as the basis for the goal extraction. The proposed method is applied to City Bus Information Subsystem(CBIS) in Intelligent Transport Systems(ITS) domain. The proposed approach helps software engineer to analyze what is affected by use case's changes and represent non-functional requirements.

• Journal of KIISE
• /
• v.43 no.10
• /
• pp.1104-1114
• /
• 2016

Software is continuously changing during development and after development. When a change is required, it is difficult to precisely grasp the scope of impact intuitively. A systematic method is needed to accomplish the required change. The purpose of impact analysis on software change is to avoid missing any information by recognizing the ripple effect that the change might cause. This paper proposes a dynamic method that can easily identify the scope of change request by using the association between use-case scenarios and artifacts of UML modeling in object-oriented development environment. By using this approach, the scope of impact that the change might have on other components such as class diagram and sequence diagram in use-case scenarios can be identified by forward tracing. In addition, analysis of influence of possible further changes due to changes in other components can be identified iteratively through backward tracing. The results of this paper are not limited to impact analysis on artifacts and change type. They can also be used as basic guidelines during impact analysis for various change requests.