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

• The Journal of Society for e-Business Studies
• /
• v.7 no.3
• /
• pp.49-60
• /
• 2002

Many researchers have studied component technologies with concept, methodology and implementation for partial business domain, however there are rarely researches for component classification to manage these systematically. In this paper, we suggest a component classification model, which can make component reusability higher and can derive higher productivity of software development. We take four focuses generalization, abstraction, technology and size. The generalization means which category a component belongs to. The abstraction means how specific a component encapsulates its inside. The technology means which platform for hardware environment a component can be plugged in. The size means the physical component volume.

• ETRI Journal
• /
• v.25 no.2
• /
• pp.121-132
• /
• 2003

To enhance the productivity of software development and accelerate time to market, software developers have recently paid more attention to a component-based development (CBD) approach due to the benefits of component reuse. Among CBD processes, the identification of reusable components is a key but difficult process. Currently, component identification depends mainly on the intuition and experience of domain experts. In addition, there are few systematic methods or tools for component identification that enable domain experts to identify reusable components. This paper presents a systematic method and its tool called a component identifier that identifies software components by using object-oriented domain information, namely, use case models, domain object models, and sequence diagrams. To illustrate our method, we use the component identifier to identify candidates of reusable components from the object-oriented domain models of a banking system. The component identifier enables domain experts to easily identify reusable components by assisting and automating identification processes in an earlier development phase.

• Journal of Korean Society of Industrial and Systems Engineering
• /
• v.31 no.4
• /
• pp.100-105
• /
• 2008

Cost reduction, time to market, and quality improvement of software product are critical issues to the software companies which try to survive in recent competitive market environments. Software Product Line Engineering (SPLE) is one of the approaches to address these issues. The goal of software product line is to maximize the software reuse and achieve the best productivity with the minimum cost. In software product line, software components are classified into the common and variable modules for composition work. In this paper, we proposed a dynamic composition process based on aspect-oriented programming methodology in which software requirements are classified into the core-concerns and cross-cutting concerns, and then assembled into the final software product. It enables developers to concentrate on the core logics of given problem, not the side-issues of software product such as transactions and logging. We also proposed useful composition patterns based on aspect oriented programming paradigm. Finally, we implemented a prototype of the proposed process using Java and Aspect to show the proposed approach's feasibility. The scenario of the prototype is based on the embedded analysis software of telecommunication devices.

• Journal of Internet Computing and Services
• /
• v.6 no.2
• /
• pp.13-24
• /
• 2005

Software development by component integration is the mainstream for time-to-market and is the solution for overcoming the short lifecycle of software. Therefore, the effective techniques for component integration have been working. However, the systematic and practical technique has not been proposed. One of main issues for component integration is how to specify integration and the component architecture for operating the specification, in this paper, we propose a workflow variability design technique for component integration, This technique focuses on designing to a connection contract based on the component architecture. The connection contract is designed to use the provided interface of component and the architecture can assemble and customize components by the connection contract dynamically.

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

As software industry is rapidly evolving, IT business enterprises have been meeting with cutthroat competition in developing software. As software reusability, time to market, and maintainability are considered as a competitive edge, software component techniques have lately attracted considerable attention. Currently, although there are some supporting tools for developing software components, they do not have tight connections among component developing processes such as component identification, component modeling, detailed design, code generation, deployment, and testing. And it is restrictive for users to construct various scales of components on component platform architecture. In this paper, we provide an implementation and a design of a supporting tool for constructing platform-independent software components, which covers all development lifecycles of components. In the phase of component modeling, platform independent, conceptual components are identified from domain model information in the view of system partitioning. Detailed design and implementation of a component are performed on the J2EE platform architecture. And the changes on the design model and source codes are consistently managed by using round-trip techniques.

• Journal of Internet Computing and Services
• /
• v.3 no.4
• /
• pp.71-82
• /
• 2002

Recently. component-based software development is getting accepted in industry as a new effective software development paradigm, Since an introduction of component-based software engineering(CBSE) at later 90's, the CBSD research has focused largely on component modeling, methodology, architecture and platform, However. as the number of components available on the market increases, it becomes more important to make metrics to measure the various characteristics of components. In this paper. we propose metrics for measuring the complexity, customizability, and resuability of software components, Complexity of metrics can be used to evaluate the complexity of components Customizability is used to measure how efficiently and widely the components can be customized for specific requirements organization, Resuability can be used to measure the degree of features that is reused in building applications.

• Journal of the Korea Academia-Industrial cooperation Society
• /
• v.10 no.12
• /
• pp.3715-3724
• /
• 2009

Recently, component-based software development is getting accepted in industry as a new effective software development paradigm. Since the introduction of component-based software engineering (CBSE) in later 90's, the CBSD research has focused largely on component modeling, methodology, architecture and component platform. However, as the number of components available on the market increases, it becomes more important to devise metrics to quantify the various characteristics of components. In this Paper, we propose metrics for measuring the complexity, customizability, and reusability of software components. Complexity metric can be used to evaluate the complexity of components. Customizability is used to measure how efficiently and widely the components can be customized for organization specific requirement. Reusability can be used to measure the degree of features that are reused in building applications. We expect that these metrics can be effectively used to quantify the characteristics of components.

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

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.233-240
• /
• 2003

To develop high-quality software systems satisfying the customer's needs, user-centered design (UCD) process has been emphasized in the area of human-computer interaction. And component-based development (CBD) has been extensively studied to realize a systematic software reuse, thereby reducing the time-to-market and the development cost. Balanced integration of user-centered design process and CBD process will be a promising way for successful software construction, which effectively achieves three goals: the quality of software, the cost of software development, and the time-to-market. However, traditional CBD methodology seems to lack the concept of user-centered design process and the relevant methods. This paper proposes a way of incorporating user-centered design process into a CBD methodology. Firstly, this paper gives the brief introduction of UCD. Secondly, we explain typical UCD activities and methods along the phase of systems development lifecycle and propose the use of usability maturity model (UMM) for integrating UCD activities and methods with those of CBD methodology. Finally, as a case study, we describe the results of comparing the UCD activities to the activities of MaRMI-III, which has been developed as a CBD methodology at ETRI.