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

• Journal of KIISE:Software and Applications
• /
• v.28 no.12
• /
• pp.896-909
• /
• 2001

Recently, above 50 percentages of software are being developed based on distributed application platforms. And recent technologies such as EJB(Enterprise Java Beans)[1]COM(Component Object Model)[2] CORBA(Common Object Request Broker Architecture)[3] have been advanced for distributed component-based software development . Therefore a systematic development process is necessary to develop component based applications using distributed application platforms. However, most of component-base software development processes do not define concrete flows between tasks and relationships among artifacts of each task Also, distribution issues are not considered explicitly in most of component-based software development In this paper, we present an approach to analyze and design software based on distributed components. In this approach, we propose systematic guidelines for developing a software based on Unified process and the relationships among artifacts which are produced, Also we explicitly consider the distribution issues such as performance, fault tolerance, security, distributed transaction of CORBA environments.

• International Journal of Computer Science & Network Security
• /
• v.23 no.12
• /
• pp.187-193
• /
• 2023

Large software systems are being produced with a noticeably higher level of quality with component-based software engineering (CBSE), which places a strong emphasis on breaking down engineered systems into logical or functional components with clearly defined interfaces for inter-component communication. The component-based software engineering is applicable for the commercial products of open-source software. Software metrics play a major role in application development which improves the quantitative measurement of analyzing, scheduling, and reiterating the software module. This methodology will provide an improved result in the process, of better quality and higher usage of software development. The major concern is about the software complexity which is focused on the development and deployment of software. Software metrics will provide an accurate result of software quality, risk, reliability, functionality, and reusability of the component. The proposed metrics are used to assess many aspects of the process, including efficiency, reusability, product interaction, and process complexity. The details description of the various software quality metrics that may be found in the literature on software engineering. In this study, it is explored the advantages and disadvantages of the various software metrics. The topic of component-based software engineering is discussed in this paper along with metrics for software quality, object-oriented metrics, and improved performance.

• Journal of KIISE:Software and Applications
• /
• v.31 no.6
• /
• pp.741-749
• /
• 2004

Component users must customize components they obtain from providers, in order to fit them to their own purposes. Normally, a component consists of black-box parts and white-box parts. Component users customize a component by modifying white-box parts of a component, and the customization faults appear through the interaction between black-box parts and white-box parts. Customization testing could be an integration testing of these two parts of a component. Also, customization testing in CBSD should select effective test data to reduce the testing cost, since CBSD aims to reduce the development cost. Therefore, this paper proposes a customization testing technique based on COM architecture through analyzing many COM components, and the technique selects effective test data. This paper evaluates the effectiveness of the test data selected by the proposed technique through an empirical study. It applies the techlique to a large-scale component-based system, Chamois, and it shows that the technique enables us to test customized COM components that run in a real component-based system

• Journal of the Korean Operations Research and Management Science Society
• /
• v.39 no.3
• /
• pp.93-115
• /
• 2014

In collaborative product development with multiple suppliers, buyers must manage the suppliers' activities. This empirical research investigates the performance impacts of three strategies that buyers use to manage suppliers who design interdependent components. These strategies are: Instructionism (giving clear instructions to suppliers), Teaming (forming an interactive development team with suppliers), and Delegation (transferring component development responsibilities to suppliers). Data were collected through a cross-industry web-based survey of buying firms in manufacturing industries whose products require multiple, interdependent components. A path analysis utilizing 318 survey responses indicates that Instructionism has a positive effect on design quality, and Teaming has a positive effect on design quality and component innovation. The use of Delegation is not related to any of the performance indicators. The practical implication of this research for product development managers is that both Instructionism and Teaming can be effective strategies. For the purpose of assuring design quality, a buyer should give clear instructions in detailed specifications or work closely with suppliers in development teams. If competitive priority is product innovativeness, however, the buyer should work closely with its suppliers during component development processes using a Teaming strategy.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.5
• /
• pp.171-177
• /
• 2008

CBD(Component-based Development), which refers to the method of treating software as parts of a larger whole and developing new information systems through the assembly and synthesis of existing software, has been popular among many methods for developing software. However, CBD has limitations in the mobile environment which requires frequent requirements change and flexible process. To overcome those limitations, we propose an improved mobile development process based on the UML(Unified Modeling Language) components. Our Proposal is the simple development process implemented as three phase of component diagrams for the mobile system having quickly evolving technology and small-size project. Through the implementation of a mobile banking service with the proposed development process, we show that our proposal works efficiently for the requirements change and flexible development.

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

Component-based development methods are regarded as one of the most important tools for us to cope with ever-increasing software complexity and, at the same time, to improve productivity in software development. This paper presents how to generate test-cases for integrated software from those of member components and how to validate composition of components, by the analysis of domain relations of components. This paper shows the applicability of the proposed technique by the real experiment. This study is based on the dataflow systems architecture and process components, and the technique developed here is an application of domain testing technique.

• ETRI Journal
• /
• v.18 no.1
• /
• pp.15-27
• /
• 1996

The effects of $Nd_2O_3$ and $TiO_2$ addition on the microstructures and microwave dielectic properties of $BaO-Nd_2O_3-TiO_2$ system were investigated. $BaNd_2Ti_4O_{12}$ or $BaNd_2Ti_{5}O_{14}$ phases were observed for compositions based on BaO/$Nd_2O_3$ = 1 ratio. The compositions deviated from $BaO/Nd_2O_3=1$ ratio were composed of major phases of $BaNd_2Ti_4O_{12}$ or $BaNd_2Ti_5O_{14}$, and the compound of $Nd_2O_3$ and $TiO_2(Nd_2Ti_2O_7)$ or that of BaO and $TiO_2(BaTi_4O_9)$. The microstructure of ceramic with $BaO{\cdot}Nd_2O_3{\cdot}4TiO_2$ composition varied from spherical grains to needlelike grains with increasing sintering temperature. With increasing $Nd_2O_3$, the optimum sintering temperature with maximum density increased, and the dielectric constant(${\varepsilon}_r$) and quality factor(Q) decreased due to the formation of secondary phases. With increasing $TiO_2$, the optimum sintering temperature and the dielectric constant decreased with increased Q value. And the temperature coefficient of resonant frequency, ${\tau}_f$ shifted toward positive direction. The dielectric ceramics with $BaO/Nd_2O_3=1$ showed Q values of above 2000 and dielectric constants of above 80 at 3GHz.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.7
• /
• pp.127-138
• /
• 2008

Configuration and data management system for weapon system research and development processes should assist concurrent engineering and collaboration activities for various documents, drawings, part informations and product structure informations. In this thesis we defined the system architecture using the CBD methodology and implemented the component based system development process. Most of the configuration and data management systems consist of three layered system architecture which use the general MVC models. In this thesis we defined four layered system architecture based on EJB structure under J2EE environments. Through the four layered system architecture, we break down the general model layer into two detailed business layers and the ordinary control layer into two system dependent layers. With these four layers, we proposed the methodology that detailed the characteristics of the components. Through the CBD approach and the component based development process, we can get the representation model and implement the actual system of the configuration and data management system for weapon system R&D.

• Journal of Internet Computing and Services
• /
• v.6 no.4
• /
• pp.21-35
• /
• 2005

Software product-lines is the software development paradigm to attain the rapid development of quality applications by customizing the reconfigurable components and composing them based on predefined software architectures. Recently various methodologies for the component-based product lines are proposed, but these don't provide the specific implementation techniques of the components in terms of variability resolution mechanism. In other hand, the several approaches to implement the component supporting the variabilities resolution are developed, but these don't define the systematic analysis and design method considering the variabilities from the initial phase. This paper proposes the integration of PLUS, the one of product line methodologies extending UML modeling, and component code generation technique in order to increase the efficiency of producing the specific product in the software product lines. In this paper, the component has the hierarchical architecture consisting of the implementation elements, and each implementation elements are implemented as XSLT scripts. The codes of the components are generated from the feature selection. Using the microwave oven product lines as case study, the development process for the reconfigurable components supporting the automatic variability resolution is described.