• IE interfaces
• /
• v.12 no.4
• /
• pp.635-642
• /
• 1999

Recently, business application vendors have responded to customer demand with several technological and organizational changes for reflecting network-oriented process flow with electronic communication and expanding their market. In organizational changes. Vendors are adding new functionality to their core offerings through mergers and acquisitions, or by partnering with front-office operation and SCM vendors. And technological changes are embracing the development of component-based application and middleware technology to be possible with integration of their function modules. We will present the design and development process of component-based SCM system to be integrated with heterogeneous ERP under implementation. Especially, we survey and analyze the technology related with CBD(Component-Based Development) to be adapted this research - component's design and methodology, the interface for component integration, middleware's development methodology of Enterprise Middleware vendo to bundle various types of middleware into a single package product with easy-to-use interface.

• 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 Korea Multimedia Society
• /
• v.5 no.4
• /
• pp.468-476
• /
• 2002

Nowadays for reliable software and cost reduction there are many research works on software development based on component. One of the challenge in designing a component-based system is determining which components are required and where they fit in the overall system architecture. In this paper, we developed a EJB component for transforming RDB instances to XML documents. Accordly users can build XML applications based on relational database just by assembling this component. Consequently they can reduce time and cost for developing their XML applications.

• IE interfaces
• /
• v.16 no.spc
• /
• pp.127-131
• /
• 2003

Component-based development approach is used in modern software system development projects that are very complex and large-scale. Technical components are more effective rather than business components in software development. However, on the Microsoft .net environment, the technical component-based development issues are not adopted. Moreover, software architecture on the .net environment is not studied yet because the development platform is recently used in the development of enterprise-level system. This paper proposes a technical component-based software architecture on .net environment. Seven technical components - configuration, data access, exception, file I/O, log, message, and paging - are contained in the architecture. The proposed architecture enables developers to reduce development time and to concentrate business logic rather than architectural issues. To verify the proposed architecture and the components, a partner management system is developed based on the architecture.

• The KIPS Transactions:PartD
• /
• v.10D no.5
• /
• pp.745-752
• /
• 2003

The component-based development methodology becomes famous as the reuse technology for independence and productivity of software development It is necessary component metrics for component-based systems, because It should be measurable to improve the quality of the software. Hence, in this paper, we propose component cohesion and coupling metrics which is reflected in characteristics of component. The operation use value is calculated by the information of classes interface commonly uses to offer the component's service. And, the operation similarity value is calculated by the operations use value. Component cohesion and coupling is calculated by the operation similarity and based of the information which is extracted in the analysis phase. And, we examine the necessity of component metrics in comparison with object-oriented metrics.

• 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 KIISE:Software and Applications
• /
• v.27 no.2
• /
• pp.180-192
• /
• 2000

Recently, the component technology has played a main role in software reuse. It has changed the code-based reuse into the binary code-based reuse, because components can be easily combined into the developing software only through component interfaces. Since components and component users have increased rapidly, it is necessary that the users of components search for the most proper components for HTML among the enormous number of components on the Internet. It is desirable to use web-document-typed specifications for component specifications on the Internet. This paper proposes to use XML component specifications instead of HTML specifications, because it is impossible to represent the semantics of contexts using HTML. We also propose the XML context-search method based on XML component specifications. Component users use the contexts for the component properties and the terms for the values of component properties in their queries for searching components. The index structure for the context-based search method is the inverted file indexing structure of term-context-component specification. Not only an XML context-based search method but also a variety of search methods based on context-based search, such as keyword, search, faceted search, and browsing search method, are provided for the convenience of users. We use the 3-layer architecture, with an interface layer, a query expansion layer, and an XML search engine layer, of the search engine for the efficient index scheme. In this paper, an XML DTD(Document Type Definition) for component specification is defined and the experimental results of comparing search performance of XML with HTML are discussed.

• KSII Transactions on Internet and Information Systems (TIIS)
• /
• v.9 no.3
• /
• pp.1014-1034
• /
• 2015

Location information of sensor nodes plays a critical role in many wireless sensor network (WSN) applications and protocols. Although many localization algorithms have been proposed in recent years, they usually target at dense networks and perform poorly in sparse networks. In this paper, we propose two component-based localization algorithms that can localize many more nodes in sparse networks than the state-of-the-art solution. We first develop the Basic Common nodes-based Localization Algorithm, namely BCLA, which uses both common nodes and measured distances between adjacent components to merge components. BCLA outperforms CALL, the state-of-the-art component-based localization algorithm that uses only distance measurements to merge components. In order to further improve the performance of BCLA, we further exploit the angular information among nodes to merge components, and propose the Component-based Localization with Angle and Distance information algorithm, namely CLAD. We prove the merging conditions for BCLA and CLAD, and evaluate their performance through extensive simulations. Simulations results show that, CLAD can locate more than 90 percent of nodes in a sparse network with average node degree 7.5, while CALL can locate only 78 percent of nodes in the same scenario.

• The Journal of Society for e-Business Studies
• /
• v.8 no.4
• /
• pp.239-252
• /
• 2003

High quality software is the one that has an excellent performance with a low price, consumer's request satisfaction and less bug. In addition, it should have structure easily maintainable. CBD(Component Based Development)technology is getting more popular as a method for software development which can satisfy all above conditions. Although there are a lot of test methods about component for composition, function, compatibility and reliability, it's not enough to ensure that the component has reliability, maintainability, and reusability, so an integated method are necessary. In this paper, we are going to propose the solution model for integrating components, which are based on UML (Unified Modeling Language) technologies. This model can extract existing faults in the component interfaces by referencing sequence diagram and collaboration diagram.

• The KIPS Transactions:PartD
• /
• v.9D no.1
• /
• pp.91-102
• /
• 2002

We need a component-based system to reflect software changes in user's requirements, to implement a system at a rapid speed as well as to efficiently manage the system in a maintenance phase and to easily change software. Moreover, the component-based system has a merit in development cost. However, existing component development methodology for implement of component-based system is inefficient in object identification for component identification. Moreover, the existing component development methodology also fails to provide any method to identify system component. It merely provides procedures and methods to identify business component focused on a whole system domain. In addition, it has another problem that it considerably relies on developer's experiences and intuitions for component identification. Therefore, according to this paper, RUP (Rational Unified Process) is applied from a requirement analysis phase to an object identification phase in order to improve the inefficiency of object identification. In addition, this paper procedures and methods for system component identification, and identifies business components based on the identified system component, rather than on the whole system domain. This paper also provides and applies cohesion metric and coupling metric so as to overcome the problem that component identification depends on developer's intuitions and experiences. Accordingly, the component identification method proposed in this paper, may identify components more effectively based on facility of object identification, functional reusability of components, traceability, and independence of components.