• ETRI Journal
• /
• v.25 no.6
• /
• pp.464-474
• /
• 2003

Component-based development leverages software reusability and reduces development costs. Enterprise JavaBeans (EJB) is a component model developed to reduce the complexity of software development and to facilitate reuse of components. However, EJB does not support component assembly by a plug-and-play technique due to the hard-wired composition at the code level. To cope with this problem, an architecture for EJB component assembly is defined at the abstract level and the inconsistency between the system architecture and its implementation must be eliminated at the implementation level. We propose a component-based application development tool named the COBALT assembler that supports the design and implementation of EJB component assembly by a plug-and-play technique based on the architecture style. The system architecture is first defined by the Architecture Description Language (ADL). The wrapper code and glue code are then generated for the assembly. After the consistency between the architecture and its implementation is checked, the assembled EJB components are deployed in an application server as a new composite component. We use the COBALT assembler for a shopping mall system and demonstrate that it can promote component reuse and leverage the system maintainability.

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

• Journal of the Korea Society for Simulation
• /
• v.25 no.1
• /
• pp.11-20
• /
• 2016

Recently in the field of defense Modeling and Simulation (M&S), Component-Based Development technology is widely applying to save the cost and increase the reusability of weapon system development. Related with this, researches for rapid reconfiguration and simulation of the component-standardized weapon system is actively carrying out. To rapidly reconfigure the new weapon system, complex and various functions of component information has to be effectively searched. So, it requires differentiated search technique unlike existing Keyword-based Search method. Semantic Search System provides semantically related information among the extensive information. In this research, metadata of weapon system components and their representative functional words are built as an ontology. And it provides an ontology-based semantic search system.

• Computational Structural Engineering : An International Journal
• /
• v.1 no.1
• /
• pp.71-80
• /
• 2001

A reliability approach to evaluate structural performance has gained increased acceptability and usage over the past two decades. Most reliability analyses are based on the reliability of an individual component without examining the entire structural system. These analyses often result in either unnecessary repairs or unsafe structures. This study uses examples of series, parallel, and series-parallel models of structural systems to illustrate how the component reliabilities affect the reliability of the entire system. The component-system reliability interaction can be used to develop optimum lifetime inspection and repair strategies for structural systems. These examples demonstrate that such strategies must be based on the reliability of the entire structural system. They also demonstrate that the location of an individual component in the system has a profound effect on the acceptable reliability of that component. Furthermore, when a structure is deteriorating over time, the reliability importance of various components is a1so changing with time. For this reason, the most critical component in the early life of the structure may not tie the most critical later.

• Proceedings of the Korea Society for Simulation Conference
• /
• 2001.10a
• /
• pp.484-484
• /
• 2001

The sophistication of current software applications results in the increasing cost fur software development time. The component-based software development framework is proposed to overcome the difficulty and time-consuming requirements by modularity and reusability. As is the general software case, a component-based simulation framework encourages the reusability of the real system model based on the modularity of the applied simulation methodology. This paper presents a component-based simulation environment that is based on the DEVS/COM run-time infrastructure. The DEVS (Discrete Event System Specification) formalism provides a formal modeling and simulation framework for the generic dynamic systems [1] and Microsoft's COM (Component Object Model) is one of the strongest competitor fur the component standard. The reusability by the DEVS/COM simulation environment saves model development time remarkably and component technology make simulator itself to be a subparts of real application.

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

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

• The Journal of Information Systems
• /
• v.12 no.1
• /
• pp.87-116
• /
• 2003

One of the important applications for business-to-business electronic commerce is in procurement and inventory management using electronic data interchange(EDI). Using online catalogs and approved supplier lists, firms can easily create requisitions and purchasing documents. The emerging trend in EDI technology is changed from VAN(Value Added Network) based EDI to XML based EDI. This paper intends to suggest a component-based XML/EDI system using Unified Modeling Language(UML), as an application system for automobile part industry. Applying component based XML/EDI systems designed with UML methodology, we analyzed the workflow and the document on procurement process between trading partners and implemented a prototype of efficient XML/EDI system, as a surrogate of existing VAN/EDI. The result of applying object-oriented CBD(Component Based Development) technique is to minimize the risk of life cycle and facilitate the reuse of software as mentioned to limitation of information engineering methodology. It enables the interoperability with corporate legacy systems such as ERP(Enterprise Resource Planning), SCM(Supply Chain Management). This system proposes a solution to apply analysis phase and design phase in implementation of XML/EDI system. The implementation of XML/EDI system using CBD shows the ease of use in software reuse and the interoperability with corporate internal information system. The purchasing department with XML/EDI system can electronically communicate purchase orders, delivery schedules to external suppliers and interoperate with other application systems.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.5S
• /
• pp.1629-1637
• /
• 2000

With wide spending the Internet and Web techniques, we have recognized the necessary and commercial-value of electronic commerce system. Electronic commerce(EC) means the whole economical activities based on electronic medium. Both scalability and flexibility are fundamental attributes of EC system and interoperability among heterogeneous systems must be supported. So, for successful a developing of EC system, it is necessary to apply the CBD (Component Based Development) based on component assembling and customization. In this paper, we propose the method for identifying and specifying the components to construct the component based electronic commerce system. To do, we define the component/system architecture specified on EC domain, identified and classified the EC components with hierarchy relationship. Also, we suggested the specification notation and some examples.

• Journal of the Korea Computer Industry Society
• /
• v.7 no.5
• /
• pp.495-502
• /
• 2006

This paper describes how to implement reporting system for web-based information system. Reporting system is the S/W module that user is able to produce output of data in formal format. In Client/Server system, remote user can make formal output with client-side reporting component module. This client reporting component is usually system dependent. With web based information system, intranet, evolving, this client/server system need to he migrated to web-based reporting system. Reporting system component support multi-processing and real-time text/graphic output of server data. Ant Client can save or pint web page of client module. Especially, for real test its function and user interface, this reporting component is adopted in real network management system. The result shows that this reporting system component is very smart and excellent for real time web based monitoring system.