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

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.3
• /
• pp.808-817
• /
• 2000

Component specification languages in consideration of reuse are essential factor in classification, verification and retrieval of components. A number of legacy specification languages have already been used, however, they are complex and include many necessary elements in the specification for implementation. In this paper, we present XML-based component specification and software architecture specification language to solve these problems of legacy specification languages. The presented specification languages consist of component specification, which is composed of signature specification, interface specification and message specification, and software architecture specification providing graphical notations and textural notations. Component specification supports component retrieval with behavioral match and black-box reuse of component. In addition to this, it improves the efficiency of retrieval and document management with XML-based component specification. Software architecture specification supports the structural reuse of architecture, which is white-box reuse, through mesage-based architecture specification.

• ETRI Journal
• /
• v.31 no.3
• /
• pp.304-314
• /
• 2009

Component-based software reuse has been generally regarded as a promising approach to improving software productivity and quality within software development. However, progress in component-based software reuse has been slower than expected. Much of the software reuse literature points to the lack of software components that can maximize users' benefits as the most important source of the slow progress. Considering that the underlying processes behind component-based software reuse are strikingly similar to commercial software marketing, this paper attempts to identify the aspects of software components that consumers value and to establish relationships between the identified aspects and consumer behavior in the software component market. More specifically, this paper focuses on the perceived subjective features of software components. This study was conducted in a web-based artificial market environment called "SofTrade."

• Journal of the Korea Society of Computer and Information
• /
• v.11 no.6 s.44
• /
• pp.27-33
• /
• 2006

In this thesis, we presents the component design and retrieval prototype system which can retrieve the most appropriate component for reuse system. If it used only an abject to reuse unit, it can not understand mutual reaction and can not sustain relationship between objects. Therefore, we porposed clustering component for reuse unit. It makes to understand relationship and reaction between object, so User can retrieve the proper component for reuse system. And porposed retrieval prototype system can select the correct things. it provide 3 facet retrieval environment against ambiguous retrieval definition.

• Journal of Information Processing Systems
• /
• v.8 no.4
• /
• pp.539-554
• /
• 2012

Model-driven and component-oriented development is increasingly being used in the development of embedded systems. When combined, both paradigms provide several advantages, such as higher reuse rates, and improved system quality. Performing model-driven and component-oriented development should be accompanied by a component model and a method that prescribes how the component model is used. This article provides an overview on the MARMOT method, which consists of an abstract component model and a methodology for the development of embedded systems. The paper describes a feasibility study that demonstrates MARMOT's capability to alleviate system design, verification, implementation, and reuse. Results indicate that model-driven and component-based development following the MARMOT method outperforms Agile development for embedded systems, leads to maintainable systems, and higher than normal reuse rates.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1205-1216
• /
• 2005

Component-based Development (CBD) is gaining popularity as an effective reuse technology. Especially commercial-off-the-shelf (COTS) components are mainly for inter-organizational reuse, rather than intra-organizational reuse. One of the essential tasks in CBD is to reuse the right components that provide the functionality and interface required by component consumers. If candidate components provide a limited applicability and customizability, a component consumer cannot reuse the components in application development. To resolve this partial matching problem, we need smart connectors that fill the gap between candidate components and the specification of components required. Previous researches about smart connector describe only connector types to resolve mismatch problems. However, previous researches do not address the identification and design method to resolve the problems. In this paper, we suggest taxonomy of various mismatch problems to identify partial match problems between requirements of the application and components. We identify smart connector types and suggest a systematic process for designing smart connectors using the taxonomy. Therefore, components that have the problems can be used to develop applications.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.5
• /
• pp.1388-1400
• /
• 2000

An important technical issue in recent software development is to make needed software by the composition of components that are assemblable, and configurable, and independently extracted. The main advantage of component-based software development is reducing development time and cost. It is more cost-effective in development time to use components that are already developed than developing from scratch. There are two ways of component-based software development: one is to compose self-developed components, and the other is to by the components developed by third-parties and compose them. In the second case, existing non component programs must can be used for reuse in the component development. In this paper, we approach two methods for increase of reusability of Java program. First, we suggest the technique of extracting the elements suitable for the Beans component model from Java program, and then we show a process and a guideline of converting the extract elements into the Beans component model. Second, we suggest a technique of automatically extracting component information from the Java Beans component, expressing them in XML, its is possible to reuse the efficient component environment.

• The Journal of Society for e-Business Studies
• /
• v.8 no.2
• /
• pp.113-129
• /
• 2003

Component-based software development (CBSD) has been recognized effective reuse techniques for software development by many of researchers and companies. The purpose of CBSD is to produce a high quality software system quickly through using verified software component which is contained fine-grained business logics. This paper suggests the metrics and techniques for to extract component and its interface from legacy object oriented application. For extract component, we apply metrics to measure complexity, cohesion and coupling to the legacy system.

• Journal of Software Engineering Society
• /
• v.23 no.4
• /
• pp.151-163
• /
• 2010

In the defense software domain where large-scale software products in various application areas need to be built, reusing software is regarded as one of the important practices to build software products efficiently and economically. There have been many efforts to apply various methods to support software reuse in the defense software domain. However, developers in the defense software domain still experience many difficulties and face obstacles in reusing software assets. In this paper, we analyze practical problems of software reuse in the defense software domain, and define core requirements to solve those problems. To meet these requirements, we are currently developing the Component Grid system, a reuse-support system that provides a developer-centric software reuse environment. We have designed an architecture of Component Grid, and defined essential elements of the architecture. We have also developed the core approaches for developing the Component Grid system: a semantic-tagging-based requirement tracing method, a reuse-knowledge representation model, a social-network-based asset search method, a web-based asset management environment, and a wiki-based collaborative and participative knowledge construction and refinement method. We expect that the Component Grid system will contribute to increase the reusability of software assets in the defense software domain by providing the environment that supports transparent and efficient sharing and reuse of software assets.

• Journal of Internet Computing and Services
• /
• v.7 no.6
• /
• pp.41-50
• /
• 2006

In order to improve software development productivity and quality, reuse approaches and supporting library systems have been proposed. Library systems have applied various methods to classify, store, retrieve, and comprehend reusable components effectively. As the number of library systems grows, it is difficult to categorize, compare and analyze existing reuse libraries. In this paper, we present classification criteria for reuse library systems. A set of criteria is defined by integrating facet-based and attribute-based classification methods which encode the properties of a reusable component. In order to show the usefulness of the proposed classification criteria, representative library systems based on application domains, as well as component classification methods ore selected and reviewed. We then classify these library systems according to the proposed criteria.