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

• Korean Journal of Computational Design and Engineering
• /
• v.13 no.2
• /
• pp.121-130
• /
• 2008

The concept of integrated product information has been universalized so that many manufacturing industries have applied the concept to their production system. The field of PDM (Product Data Management), which is one of the core components of the integrated product information, is not an exception. Therefore, various PLM (Product Lifecycle Management) software providers are in process of suggesting the PDM solutions. As the PDM solution is widely adopted in the manufacturing industries, the successful application of the solution has been gathering more strength in manipulation of the product information. However, the standardized implementation methodology is stuck in the basic level contrast with the enhanced PDM's functionality and capability. Present study refers to the application of UML (Unified Modeling Language), which is an object oriented modeling description, to PDM system development procedure. The advantage of UML is its efficiency and effectiveness in handling complex requirement often found in PDM implementation works. This paper shows the integration of PDM and UML proposes a philosophy for the support of requirement analysis throughout the full implementation of PDM system.

• Proceedings of the Korean Information Science Society Conference
• /
• 2001.10a
• /
• pp.553-555
• /
• 2001

기업형 정보 시스템을 개발하는 데 클라이언트 계층, 어플리케이션 서버 계층, 데이터베이스 계층으로 구성된 3계층 아키텍쳐가 널리 사용되고 있다. 따라서 기업형 컴포넌트의 올바른 행위를 시험하기 위해서는 3계층 아키텍처를 고려한 시험 기법이 요구된다. 하지만 기존의 대부분의 컴포넌트 시험 기법들은 클라이언트 계층과 어플리케이션 서버 계층 사이의 관계만을 대상으로 하고 있어서 기업형 컴포넌트 시험에 부족하다. 논문에서는 기업형 컴포넌트의 시험을 위해 클라이언트 계층과 어플리케이션 서버계층 간의 관계만이 아니라 어플리케이션 서버계층과 데이터베이스 서버계층과의 관계를 포함한 시험 기법을 제안한다. 이를 위해 3계층 아키텍쳐를 반영하는 시험모델을 제안했으며 UML/OCL를 컴포넌트의 명세로 사용하여 시험모델을 추출한 뒤 자동으로 시험을 수행하는 시험 환경을 개안했다. 제안된 시험 환경은 일반적인 시험 단계의 뒷부분으로 테스트 케이스를 분석하여 생성하는 것보다는 생성된 시험 사료를 수행시켜 자동으로 시험 과정을 수행하는데 관심을 두고 있다. 제안된 시험환경은 기존의 연구와 달리 3계층 아키텍처를 반영하고 산업체 표준인 UML/OCL을 이용하므로 기업형 응용프로그램의 생산성을 증가시켜 줄 것으로 보인다.

• Journal of KIISE:Software and Applications
• /
• v.32 no.3
• /
• pp.153-162
• /
• 2005

Component Based Development (CBD) is appealing as a technology to improve the productivity of software development through component reuse. Model Driven Architecture (MDA) is a new development paradigm which automatically generates application by transforming design models incrementally. Since both reusability of CBD and model transformation of MDA increase software productivity. integration of two technologies is desirable. To enable this technology integration, we need to devise a UML profile for specifying component design as a PIM. In this paper, we first define a meta-model for components, and propose a UML profile which is used to specify elements of component design as PIM. Since the proposed profile is based on Meta Object Facility (MOF) from which is MDA is derived, it is consistent and compatible with existing MDA methods and tools.

• The KIPS Transactions:PartD
• /
• v.11D no.1
• /
• pp.123-132
• /
• 2004

Defense software has short of interoperability due to the vertical development method which is dependent heavily on application area and development environments. In order to prevent from lack of reusability and operability in application domain software development technology needs component concept and makes shift to the trend of domestic software component industry. This paper covers the research topics such as domain analysis and component architecture to improve and extend reusability and inter-operability for defense information system by two approaches, i.e. CBW (Command Based Work flow) analysis and UML components identification.

• The KIPS Transactions:PartD
• /
• v.9D no.3
• /
• pp.399-408
• /
• 2002

Component technology was proposed and applied to software development to overcome software crisis. Software component is a black box like an integrated circuit in hardware but it can not be utilized without good support specially for helping users understand efficiently. This paper shows that data book format for understanding hardware component can be well applied to representing software component. We selected an approach to understand component by matching the contents of data book with UML and API model technique. Besides, we added the architecture part and the interface which are the most important property of software component to the data book for software components. In order to verify effectiveness of components data book we extended batch descriptor in EJB and performed an experiment providing data book to programmers with components.

• The KIPS Transactions:PartD
• /
• v.14D no.1 s.111
• /
• pp.83-88
• /
• 2007

In this paper, we introduce MDA based Development Method for Embedded Software Component. This method applies MDA approach to solve problems about reusability of the heterogeneous embedded software system. With our proposed method, we produce 'Target Independent Meta Model'(TIM) which is transformed into 'Target Specific Model'(TSM) and generate 'Target Dependent Code' (TDC) via TSM. We would like to reuse a meta-model to develop heterogeneous embedded software systems. To achieve this mechanism, we extend xUML to solve unrepresented elements (such as real things about concurrency, and real time, etc) on dynamic modeling of the particular system. We introduce 'MDA based Embedded S/W Modeling Tool' with extended XUML. With this tool, we would like to do more easily modeling embedded or concurrent/real time s/w systems. It contains two examples of heterogeneous imbedded systems which illustrate the proposed approach.

• Journal of KIISE:Software and Applications
• /
• v.34 no.7
• /
• pp.635-645
• /
• 2007

Component technology has been widely accepted as an effective way for building software systems with reusable components, and Microsoft (MS) .NET is one of the recent representative component technologies. Model Driven Architecture (MDA) is a new development paradigm which generates software by transforming design models automatically and incrementally. Transformation of structural models in MDA has been successfully applied. However, transformation of dynamic models and pervasive services, such as transaction service, security service, synchronization service and object pooling are largely remains as an area for further research. The recent enterprise system has multi tier distributed architecture, and the functionality of early mentioned pervasive services is essential for this architecture. .NET platform can implement Component Object Model+ (COM+) component for supporting pervasive services by specify Attribute code. In this paper, we specify the functionalities of the COM+ component offering pervasive services, and then those functionalities are defined by UML profile. By using the profile, the Platform Specific Model (PSM) for .NET/C# is specified, and .NET components are automatically generated through our tool. The development productivity, extensibility, portability, and maintenance of software can be dramatically improved by using of the proposed methods.

• The KIPS Transactions:PartD
• /
• v.14D no.4 s.114
• /
• pp.389-394
• /
• 2007

This study suggests that it dynamically generates semantic Web services from Java and C++ components in order to supporting semantic Web service by using ontology. And the semantic Web should enable greater access not only to content but also to services on the Web. It needs semantic service discovery for components. So, we add ontology-based framework to Web service generation system from components. Especially, components and ontologies are transformed UML model so that it makes WSDL documents to support a generation of dynamic Web service using object modeling. The main contribution of this study is to generate web service dynamically from components and to support semantic Web environment by using ontology. In other words, this study integrates semantic Web service based on ontology and CBD method.

• Journal of KIISE:Computing Practices and Letters
• /
• v.12 no.2
• /
• pp.129-140
• /
• 2006

The existing CBD development methods deal with the analysis phase in a superficial manner. Applying such a superficial analysis to business applications with a number of subsystems makes analysis models be inconsistent with levels and styles, only depending on experiences of the analysts. This inconsistent analysis might cause more serious problems during the subsequent development phases, resulting in the failure of the projects. In this paper, we propose a rule-based analysis pattern that provides an analysis template for business applications. This pattern analyzes the concepts of business applications by using external events and internal rules that process the events. Employing this pattern, a huge business application can be developed by a couple of co-analysts who work together in a consistent and systematic manner. This paper also describes an efficient way to develop business components with the suggested analysis pattern using banking deposit case study through UML Components development process.