• Proceedings of the Korean Information Science Society Conference
• /
• 한국정보과학회 2004년도 가을 학술발표논문집 Vol.31 No.2 (2)
• /
• pp.445-447
• /
• 2004

최근의 정보시스템 개발은 컴포넌트 기반 소프트웨어 개발로서 반복적인 소프트웨어 개발 공정을 따른다 반복(Iteration)이란 정보시스템 개발 생명주기(SDLC)의 요구사항, 분석, 설계, 개발, 테스트 과정을 기존의 Waterfall방식으로 개발하지 않고, 각 단계들을 반복적으로 수행하여 시스템을 개발하는 방식이다. 따라서 기존의 단계, 액티비티 그리고 하위의 타스크에 해당하는 산출물 완성유무를 가지고 프로세스 측면의 공정 진척을 적용하게 되면 프로젝트 현 시정의 공정 상태를 명확하게 파악하는 것이 불가능하다. 본 연구에서는 최근의 컴포넌트 기반 소프트웨어 개발에서 요구되어지는 유스케이스 기반의 프로덕트 중심의 공정 진척 관리에 필요한 기법들을 연구하였다. 본 논문에서는 유스케이스가 분석, 설계, 개발, 테스트, 배포되는 과정에 있어서 산출물 기반 진척관리에 대한 기법을 제안함으로서 반복적인 소프트웨어 개발에서의 진척 관리 체계화를 증대할 수 있는 기법을 제시한다.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 한국정보통신학회 2013년도 추계학술대회
• /
• 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.

• The Journal of Society for e-Business Studies
• /
• 제12권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.

• Journal of KIISE:Software and Applications
• /
• 제29권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 Software Assessment and Valuation
• /
• 제16권1호
• /
• pp.27-36
• /
• 2020

The software development cost appraisal is treated as a part of the program completion appraisal, and the software engineering methodology is applied. In particular, software cost estimation techniques have been actively applied. For more information about the software development costs calculation, we can refer to the "SW cost estimation guide". Although successful appraisal of a number of development costs based on the guide has been processed, but a number of cases requiring discussion of appraisal results have been discovered. In this study, we propose a use case-based size estimation method to maintain the accuracy and consistency of size estimation. As a result of performing performance evaluation of the proposed method in an environment similar to the development cost appraisal case, it was proved that the accuracy was improved over the existing function points method.

• Proceedings of the Korea Information Processing Society Conference
• /
• 한국정보처리학회 2012년도 추계학술발표대회
• /
• pp.1519-1522
• /
• 2012

기존의 리스크기반 테스팅은 조직, 프로젝트, 제품에만 초점이 맞추어져 있어 소프트웨어 개발에 관련된 리스크 활동은 잘 고려되지 않는다. 본 논문에서는 소트프웨어 개발에 리스크를 적용하고자 유스케이스 기반 리스크 위험도 측정과 우선순위화를 제안한다. 제안한 리스크 위험도 측정방법은 GoRE의 Goal 중요도 매트릭스를 리스크 결정 매트릭스로 확장하고 이를 이용하여 리스크의 위험도를 우선 순위화에 적용한 것이다. 확장한 리스크 결정 매트릭스는 유스 케이스와 요구사항의 연관관계를 파악한 후 고객 중요도를 계산하여 리스크 위험도를 측정하는 방법이다. 이를 통해 소프트웨어 개발 전 리스크 요구사항 고려로 시스템 구축에 도움이 되고자 한다.

• Journal of Internet Computing and Services
• /
• 제4권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
• /
• 제43권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.

• Proceedings of the Korean Information Science Society Conference
• /
• 한국정보과학회 2005년도 한국컴퓨터종합학술대회 논문집 Vol.32 No.1 (B)
• /
• pp.352-354
• /
• 2005

1990년대 후반에 들어서면서 않은 기업들이 기업의 생산성 향상 및 고객 서비스를 위해 IT투자를 확대해감에 따라 기업 내에서도 다수의 이질적인 시스템 도입을 추진하게 되었다. 그 결과 않은 기업 내에는 호환성이 없는 시스템이 산재해 업무추진에 어려움을 주고 있으며, 이러한 복잡하고 까다로운 분산화된 시스템을 통합하고자 업계에서는 많은 노력을 기울이게 되었다. 그 결과로 등장한 기술이 웹서비스이며 이것은 분산화된 시스템을 통합하는 기존의 통합기술들의 문제점을 해결하고 분산된 애플리케이션을 저비용${\cdot}$고효율로 통합하기 위한 대안이 되었다. 본 논문에서는 웹서비스기반 시스템 개발을 위한 웹서비스 개발 절차를 제시하고 비즈니스 도메인에서 요구사항 분석을 통해 생성된 유스케이스모델을 기반으로 하는 웹 서비스 식별 방법을 제안한다. 유스케이스를 기반으로 서비스를 식별하므로 서비스에 도메인의 비즈니스가 잘 반영되도록 할 수 있으며 적절한 입도(granularity)을 갖는 서비스를 식별할 수 있다.

• Journal of KIISE:Software and Applications
• /
• 제36권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.