• 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 Computer Industry Society
• /
• v.4 no.4
• /
• pp.479-490
• /
• 2003

CBD is a software development approach based on reusable component and supports easy modification and evolution of software. For the success of this approach, a component must be developed with high cohesion and low coupling. In this paper, we propose the two types of clustering analysis technique based on affinity between use-cases and classes and propose component identification method applying to this technique. We also propose component reference model and CBD methodology framework and perform a ease study to demonstrate how the affinity-based clustering technique is used in component identification method. Component identification method contains three tasks such as component extraction, component specification and component architecting. This method uses object-oriented concept for identifying component, which improves traceability from analysis to implementation and can automatically extract component. This method reflects the low coupling-high cohesion principle for good modularization about reusable component.

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

• International Journal of Computer Science & Network Security
• /
• v.22 no.9
• /
• pp.143-148
• /
• 2022

Component-based software development (CBD) is a methodology that has been embraced by the software industry to accelerate development, save costs and timelines, minimize testing requirements, and boost quality and output. Compared to the conventional software development approach, this led to the system's development being completed more quickly. By choosing components, identifying systems, and evaluating those systems, CBSE contributes significantly to the software development process. The objective of CBSE is to codify and standardize all disciplines that support CBD-related operations. Analysis of the comparison between component-based and scripting technologies reveals that, in terms of qualitative performance, component-based technologies scale more effectively. Further study and application of CBSE are directly related to the CBD approach's success. This paper explores the introductory concepts and comparative analysis related to component-based software engineering which have been around for a while, but proper adaption of CBSE are still lacking issues are also focused.

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

• The KIPS Transactions:PartD
• /
• v.12D no.5 s.101
• /
• pp.745-754
• /
• 2005

Defence Information System has surely required the guarantee of interoperability between systems as performing task oriented functions. To improve interoperability between them and use the benefits of component based development, defense officers are planning to develop COE like a kind of component bank concept. Defense component development methodology(ADDMe) within COE is a new approach of component based methodology for Defense environment after comparing, analyzing, and synthesizing with traditional CBDs. In this paper we introduce advanced defense component development methodology(ADDMe) and present checklist for improving interoperability between Defence component based systems which are developed with ADDMe. With our proposed interoperability's checklist, we can improve interoperability of defense component based systems through applying per each phase of ADDMe.

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

The various software engineering techniques have been appeared in order to cope with the software crisis since 1980's. Currently, the research against the techniques likes the Design pattern, Component which improve the software's re-use are spread out. Also S/W Development Process are interested intensively which attempts the quality and a increasing productivity of software development with the basic policy. The design pattern is the solution against the problem which occurs repeat in a specific area. Many design pattern are developed and researched, but the method which accommodates the developed design pattern efficiently in the phase of analysis and design software development process is not good enough, so it is the actual applying technique is difficult. In this paper we suggest and the “UML components+” which is a efficient component development process from customizing EJB based the J2EE using the “UML Components” which is a component development methodology. Applying J2EE pattern efficiently with UML components+, there is a possibility of efficiency in the component development based pattern.

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.9
• /
• pp.812-820
• /
• 2003

Component-Based Development(CBD) leverages software reusability and diminishes development costs. Various works about component models, such as EJB, COM, and CCM are in progress to support CBD. However, current component models hardly support flexible assembly of pre-built components. To cope with this problem, architecture for component assembly must be defined in the abstract level and the gap between system architecture and its implementation should be diminished in the implementation level. This paper proposes a method for architecture-based design and implementation of component assembly. Architecture is described by the ADL, and the tool, COBALT Assembler, is introduced to support the proposed design and implementation phase of component assembly.

• Journal of the Korea Safety Management & Science
• /
• v.6 no.3
• /
• pp.211-235
• /
• 2004

Component based design is perceived as a key technology for developing advanced real-time systems in a both cost- and time effective manner. Already today, component based design is seen to increase software productivity, by reducing the amount of effort needed to update and maintain systems, by packaging solutions for re-use, and easing distribution. Nowdays, a thousand and one companies in If(Information Technology) industry such as Sl(System Integration) and software development companies, regardless of scale of their projects, has spent their time and endeavor on developing reusable business logic. The component software is the outcome of software developers effort on overcoming this problem; the component software is the way propositioned for quick and easy implementation of software. In addition, there has been lots of investment on researching and developing the software development methodology and leading If companies has released new standard technologies to help with component development. For instance, COM(Component Object Model) and DCOM(Distribute COM) technology of Microsoft and EJB(Enterprise Java Beans) technology of Sun Microsystems has turned up. Component-Based Development (CBD) has not redeemed its promises of reuse and flexibility. Reuse is inhibited due to problems such as component retrieval, architectural mismatch, and application specificness. Component-based systems are flexible in the sense that components can be replaced and fine-tuned, but only under the assumption that the software architecture remains stable during the system's lifetime. In this paper, It suggest that systems composed of components should be generated from functional and nonfunctional requirements rather than being composed out of existing or newly developed components. about implements and accomplishes the modeling for the Product Control component development by applying CCD(Contract-Collaboration Diagram), one of component development methodology, to MRP(Material Requirement Planning) System