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

• ETRI Journal
• /
• v.32 no.5
• /
• pp.646-656
• /
• 2010

A component is a reusable and replaceable software module accessed through its interface. Component-based development is expected to shorten the development period, reduce maintenance costs, and improve program reusability and the interoperability of components. This paper proposes a new robot software component platform in order to support the entire process of robot software development. It consists of specifications of a component model, component authoring tool, component composer, and component execution engine. To show its feasibility, this paper presents the analysis results of the component's communication overhead, a comparison with other robotic software platforms, and applications in commercial robots.

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.515-528
• /
• 2003

Component Based Software Development has been recognized as a new software development paradigm, and received much attention among researchers. However, it requires software architecture based development to assure component reusability and efficient software development. This paper proposes the Component Based 4+1 View Model of software architecture to support component based software development. It is redefined on the basis of the existing 4+1 view model of software architecture developed by Kruchten. Also, we describe the elements of the view model in detail with UML. This architecture constructs the foundation of component based software such as increasing the understanding of software and providing the information about how the components interact with each other. It can be done by exposing the context for the use of software components to each views.

• Proceedings of the KSRS Conference
• /
• 1999.11a
• /
• pp.188-193
• /
• 1999

Technology of GIS evolved as a means of assembling and analyzing diverse spatial data. Many systems have been developed, and almost of systems are proprietary. There is a lots of lack of interoperability and reusability between them. This paper describes the development of Open GIS component software. The developing system have an end in view of GIS tool software which is interoperable and reusable. To increase the interoperability and reusability, the system is based on the OGC(Open GIS Consortium)'s Open GIS Simple Features Specification for OLE/COM. The OGC's specification is announced to increasing the full interoperability of various geospatial data and geoprocessing resources. With the Open specification, component based software ensures the reusability. We implement three kinds of component: Geometry component, Spatial Reference System Component, and MapBase Component. The first two components are compatible to the OGC's specification and the third one is designed to GIS tool software for variant GIS applications. The Open GIS component software system is developed on object-oriented computing environment, ATL/COM and Visual C++. As we made application programs using Visual Basic, the advantages of component based Open GIS software was proved.

• Computers and Concrete
• /
• v.1 no.3
• /
• pp.303-324
• /
• 2004

The Component-Based Software Development (CBSD) has established itself as a sound paradigm in the software engineering discipline and has gained wide spread acceptance in the industry. The CBSD relies on the availability of standard software components for encapsulation of specific functionality. This paper presents the framework for the development of a software component for the design of general member cross-sections. The proposed component can be used in component-based structural engineering software or as a stand-alone program developed around the component. This paper describes the use-case scenarios for the component, its design patterns, object models, class hierarchy, the integrated and unified handling of cross-section behavior and implementation issue. It is expected that a component developed using the proposed patterns and model can be used in analysis, design and detailing packages to handle reinforced concrete, partially prestressed concrete, steel-concrete composite and steel sections. The component can provide the entire response parameters of the cross section including determination of geometric properties, elastic stresses, flexural capacity, moment-curvature, and ductility ratios. The component can also be used as the main computational engine for stand-alone section design software. The component can be further extended to handle the retrofitting and strengthening of cross-sections, shear and torsional response, determination of fire-damage parameters, etc.

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.175-178
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• Proceedings of the KSRS Conference
• /
• 2007.10a
• /
• pp.460-463
• /
• 2007

COMS (Communication Ocean Meteorological Satellite) is the geostationary satellite being developed by Korea Aerospace Research Institute for multi-mission: experimental communication, ocean monitoring and meteorological observations. The COMS operation is controlled by the on-board software running on the spacecraft central computer. The software is written in ADA language and developed under the software life cycle: Requirement analysis, Design, Implementation, Component test and Integration test. Most functional requirements are tested at component level on a software component testing tool, ATTOL. ATTOL provides a simple way to define the test cases and automates the test program generation, test execution and test analysis. When two or more verified components are put together, the integration test starts to check the non-functional requirements: real-time aspect, performance, the HW/SW compatibility and etc. This paper introduces the COMS on-board software and explains what to test and how to test the on-board software at component level using ATTOL.

• Proceedings of the Korean Society of Precision Engineering Conference
• /
• 2001.04a
• /
• pp.703-706
• /
• 2001

This paper presents a component-based integration framework and its software component architecture for supporting the rapid integration of legacy design supporting systems in the distributed environment. Also, using standard interface, this software component architecture provides flexibility, extensibility and compatibility which ensure software components to be independent of the integration middleware and systems to be integrated.

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

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