• Proceedings of the Korea Information Processing Society Conference
• /
• 2009.04a
• /
• pp.459-461
• /
• 2009

시스템 개발을 위해서는 시스템이 제공하는 기능을 명료하게 기술함은 물론 목표 시스템이 참조하는 외부 시스템의 기능을 명확하게 식별하여야 한다. 이는 목표 시스템의 범위를 명확하게 한정하기 위해 매우 중요하다. 그러나 현재의 유스케이스 모델링 기법에서는 외부 시스템은 액터로만 표현된다. 이는 외부 레거시 시스템을 간결하게 표현할 수 있다는 장점이 있으나, 외부 시스템의 기능 중 목표 시스템이 참조하는 유스케이스만을 식별하기 어렵게 만드는 단점도 갖는다. 이러한 불명확성은 유스케이스 명세 시 모델 작성을 어렵게 하여 유스케이스 모델의 이해도를 저하시키는 원인이 된다. 본 논문에서는 외부 유스케이스를 이용한 확장 모델링 기법을 제시한다. 확장 모델링은 레거시 시스템에 존재하는 외부 유스케이스를 표현하고, 내부 유스케이스와 관계성을 가질 수 있도록 확장 메커니즘을 지원한다. 확장을 위해서는 UML 확장 메커니즘 중 하나인 스테레오타입(Stereotype)을 활용하며, 따라서 기존 유스케이스 모델과의 호환성을 그대로 유지함으로써, 기존 모델링 기법과 일관되게 적용 가능하다.

• Journal of Internet Computing and Services
• /
• v.10 no.5
• /
• pp.153-163
• /
• 2009

It is necessary to identify the use cases of the supplier systems in order to define new service using their functions. Current use case modeling techniques, however, do not represent the external use cases clearly, because the external system is represented only by an actor. This ambiguity of the modeling technique declines the comprehensiveness of the model, and does not limit the scope of the target system explicitly. In this paper, we propose the extended use case modeling technique for service-oriented computing. This modeling technique enables the definition of external use cases and components. They are used to limit the boundary of the target system, and the relationship between them are modeled by the realization of external use cases. The proposed technique uses UML stereotype extension mechanism. so the compatibility with current use case modeling technique is preserved.

• The Journal of Society for e-Business Studies
• /
• v.12 no.4
• /
• pp.145-163
• /
• 2007

Service-Oriented Architecture is a style of information systems that enables the creation of applications that are built by combining loosely coupled and interoperable services. A service is an implementation of business functionality with proper granularity and invoked with well-defined interface. In service modeling, when the granularity of a service is finer, the reusability and flexibility of the service is lower. For solving this problem concerns with the service granularity, it is critical to identify and define coarse-grained services from the domain analysis model. In this paper, we define the process to identify services from the Use Case model elicited from domain analysis. A task tree is derived from Use Cases and their descriptions, and Use Cases are reconstructed by the composition and decomposition of the task tree. Reconstructed Use Cases are defined and specified as services. Because our method is based on the widely used UML Use Case models, it can be helpful to minimize time and cost for developing services in various platforms and domains.

• The KIPS Transactions:PartD
• /
• v.12D no.1 s.97
• /
• pp.103-110
• /
• 2005

Software Development is converting from structural to object oriented method. The later software development prefers the iterative process applications, not aterfall process and based on use case model, the requirements are expressed and based on this, analysis, design and coding are accomplished. Therefore, size of the software to be developed is estimated basing on use case and it is only possible to maintain the project success by estimating development effort, cost and development period. Even though development effort estimation models related current use case point. there is no appropriate development effort estimating. This paper shows, as a result of applying the development effort estimating model about UCP to the growth curve, a superior performance improvement to current statistical models. Therefore, estimation of development effort by applying this model, project development maintenance can be appropriately carried out.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2019.10a
• /
• pp.701-703
• /
• 2019

현재의 소프트웨어는 매우 크고 복잡하다. 고품질 소프트웨어는 요구사항 단계부터 정확하게 분석해야 한다. 그러나 자연어 요구사항은 부정확하기 때문에 유스케이스 식별이 어렵다. 게다가, 기존 요구 사항 분석 방법은 객체와 용어 식별에 대한 정확한 기준이 없다. 따라서 분석 결과는 분석가마다 다르다. 본 논문에서는 자연어 요구사항으로부터 유스케이스 추출 및 소프트웨어 공수 산정 방법을 제안한다. 제안한 방법에서는 Goal Modeling과 Fillmore의 Case 메커니즘을 개선했다. 이 방법은 자연어 요구 사항을 단계별로 분석하여 유스케이스를 모델링한다. 또한 유스케이스 점수(Use Case Point)를 이용하여 소프트웨어의 공수를 산정(Effort Estimation)한다. 제안한 방법은 고품질 소프트웨어 개발을 위해 자연어 요구사항의 변경 없이 유스케이스 추출이 가능하다. 또한 추출된 유스케이스를 통해 UCP 기반의 공수 산정을 평가할 수 있다. 본 논문에서는 우체국 시스템의 사례에 적용하였다.

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

• Journal of KIISE:Software and Applications
• /
• v.36 no.5
• /
• pp.361-375
• /
• 2009

The major concern of component users who develop applications using the existing components is to confirm whether a component is collaborating with the different components in accordance with the requirements. Therefore, interoperability testing whose role is to check whether components collaborate with each other within the new operating environment not within the component development content of each component is considered as an importance research topic. In this paper, we propose a test case generation technique for interoperability test of component based software. The proposed technique defines a test model for generating test cases. The proposed technique generates test models from the use case specification and thereafter from these models, test cases for Interoperability testing are derived. In addition, we describe a tool which Implements the procedures for generating test sequences from test models.

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