• Journal of KIISE:Software and Applications
• /
• v.28 no.2
• /
• pp.104-112
• /
• 2001

객체지향 프로그램에서 클래스는 수정한 후 재사용하는 화이트박스 재사용과 수정없이 재사용하는 블랙박스 재사용으로 나눌 수 있다. 컴포넌트 기반 소프트웨어 개발 방법론에서의 컴포넌트는 블랙박스 재사용 형태를 띤다. 클래스와 컴포넌트는 절차적인 특성과 객체지향적인 특성을 모두 가지고 있으므로 이를 고려하여 재사용성을 측정해야 한다. 이 논문에서는 클래스와 컴포넌트의 재사용성 측정 모델과 측정 기준을 제안한다. 제안된 모델을 사용하여 측정된 클래스는 화이트박스 재사용이 유리한지 블랙박스 재사용이 유리한지를 판단할 수 있다. 아울러 총평가점수를 산정하여 비교하므로 어느 클래스가 재사용성이 높은지를 알 수 있다.

• Journal of the Korea Society of Computer and Information
• /
• v.10 no.4 s.36
• /
• pp.103-111
• /
• 2005

The reuse of a programs is classified into white-box reuse to reuse with modification and black-box reuse to reuse without modification. A component in component-based development has the property of black-box reuse. In order to measure resuability of class and component, we must consider all the procedural and object-oriented attribute. In this paper, we propose a new model for measurement of class and component reusability and the measure criteria. A component that is measured by proposed model can know a degree of reuse and we can select which component is high in resuability.

• Journal of KIISE:Software and Applications
• /
• v.29 no.10
• /
• pp.694-702
• /
• 2002

An application in Component-Based Software Development (CBSD) is built by 'composing'two kinds of components; One is a component that is made by current developer himself, and the other is a component that is from other developments. We define the former as a 'White-box component' and the latter as a 'Black-box component.' The error from the composition can be said to be caused by interactions of Black-box components and White-box components. This paper proposes a new testing technique for composition errors, and applies the technique to Enterprise Java Beans component architecture. Our technique selects test cases by injecting a fault only into the specific parts of a White-box component. This specific parts for injecting a fault are selected by analyzing composition patterns, and lead to make our test cases have a good effectiveness. We show the effectiveness of our test cases through an experiment. Moreover, we also mention an automation tool for our technique.

• Proceedings of the Korean Information Science Society Conference
• /
• 1999.10a
• /
• pp.498-500
• /
• 1999

컴포넌트 기반 소프트웨어 공학에서 컴포넌트를 명세하기 위한 명세 언어는 컴포넌트 분류, 검증 및 검색에 가장 기본적인 조건이다. 기존에 이미 많은 명세 언어가 사용되어 왔지만 명세의 복잡성으로 인한 어려움이 있다. 따라서 이 연구에서는 이러한 복잡성과 개발자에게 좀 더 쉬운 명세 방법을 제공하기 위해 XML을 기반으로 하여 새로운 컴포넌트 명세 언어를 제안하였다. 제안한 명세 언어는 컴포넌트의 기능명세부분, 타입 검사에 의한 검색을 위한 부분, 명세 일치 방식을 위한 부분으로 구성된 컴포넌트 기능명세와 소프트웨어 아키텍쳐를 위한 명세로 구성된다. 이 연구에서는 각 부분을 XML 태그에 의해 정의하였다. 또한 소프트웨어 아키텍쳐 명세를 위한 그래픽 표기법과 텍스트 표기법을 제안하였다. 이 연구에서 제안한 명세언어는 화이트박스 재사용과 블랙박스 재사용을 지원하고 오류가능성을 줄일 수 있다.

• Journal of the Korea Society of Computer and Information
• /
• v.25 no.11
• /
• pp.147-155
• /
• 2020

System support software is one of the software that makes up ship combat management system and has the characteristics of being mounted in the combat management systems of all ships but with little functional change. However, despite these characteristics, software modifications due to equipment, etc. are inevitable in the application of new ships. Modification of software causes software reliability testing which is a key factor in increasing development costs. In this paper, the structure of the existing system support software was analyzed to identify and supplement the code change factors, and the system support standardization architecture was designed. The feature model elicited common and variable elements of system support software, and applied white-box reuse to improve software design. In addition, the results of comparing existing system support software with the new architecture in terms of development elements and time to perform reliability test were presented to verify the effectiveness of the new one.

• The KIPS Transactions:PartD
• /
• v.8D no.6
• /
• pp.681-690
• /
• 2001

In this paper, we propose a steering concept that considers overall aspects in the CBSD (Component-Based Software Development) environments. While many researches which are concentrated on using components, market promotion and component development itself seem to be insufficient. To overcome this problem, we introduce a brokerage concept called“Value-Added Brokerage Concept”that provides the following three services：1) domain architecture-based component promotion, 2) intelligent component search, and 3) white-box service. Domain architecture-based component promotion facilitates balancing component production and promoting architecture-level large scale reuse. Intelligent component search enables to overcome the long time search and selection problem. Finally, white-box service is for solving maintenance problems, which is one of the most critical problem in the CBSD environments. Especially, we expect this proposed concept would be well adapted to our national environments.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.289-300
• /
• 2006

Product line is nowadays well known as a representative method for reuse. In the product line, important assets are components. Although enough concerns were given of the product line, it was not accomplished to structure and specify a product-line component with variability. This paper presents an approach to specify components in the product line. The approach describes the static and dynamic structure of a product-line component and explains the behavior and concurrency of the component. The component information is separately described in the black-box and white-box using the Feature-Oriented Reuse Method(FORM). This research also formalizes the data on a component specification in the form of BNF. The specification is described through careful consideration for many different characteristics of the product-line component, so this paper helps to easily develop the components in the product line and to well comprehend how to apply a method for the product line.

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

The business component for satisfying a variety of domain requirements should be developed to provide a variety. But, although components are developed by analyzing the variety of requirements when they are developed, developing components that satisfy all requirements is not easy since unexpected requirements occur as it is used components. For this reason, components are not provided as black boxes but as white boxes, and there by components are not modified in the interface only but the source codes are directly modified. Accordingly, a Time-To-Market by the use of components is not easy and a reusability of the components also decreases. This study proposes a customization technique that can be satisfied requirements of many different kinds of domains by analyzing variable spots of components. The initial variability of components is designed in the component development phase. and a customization technique is used to apply the variability. The variability can be redesigned during the development of application by using the components to which the variability is applied. Through this process, a variability of components evolves and a generality of the components can be improved. The proposing customization technique in this study can change the component to extend without changing the existing component when it is redesigned.

• Journal of KIISE:Software and Applications
• /
• v.36 no.9
• /
• pp.706-717
• /
• 2009

A web application is implemented by reusing the library provided by framework and has hierarchical architecture. Also, to deal with the user request from a screen, the web application has an execution flow, called 'Business Logic', which starts with a screen, executes its composed component and comes back to the screen via database. To test web application effectively, it should reflect the characteristics of web application. In this paper we propose to test web applications via user screens with the black-box testing approach and verify its source codes with the web interface white-box test coverage that covers all the business logics of the test target and their corresponding interfaces. We analyze the proposing testing method through its tool: Testopiacov.

• Journal of KIISE:Software and Applications
• /
• v.33 no.1
• /
• pp.32-43
• /
• 2006

Enterprise JavaBeans (EJB) has been accepted for supporting Component-Based Development (CBD). A component is a large-grained reuse unit consisting of several objects; however, an enterprise bean in EJB is a unit of atomic object and so multiple enterprise beans should be composed to support larger-grained reuse. Therefore, we need practical methods for designing and implementing components with EJB. In this paper, we propose instructions and techniques for designing CBD elements with EJB constructs. That is, we define methods for designing and implementing single and composite components, white- and black-box components, multiple interfaces, and variability mechanism in EJB platform. We evaluate the proposed method by performing a case study and comparing the characteristics of CBD components with the method. Consequently, the method is supposed to improve reusability, applicability, portability of components in EJB platform.