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

• KIEE International Transactions on Power Engineering
• /
• v.2A no.4
• /
• pp.145-152
• /
• 2002

This paper illustrates applications of the Component Object Model (COM) for power system software developments. As an integral part of Microsoft's component services, COM has gained increased popularity for developing enterprise applications. This paper illustrates the concepts of COM and the latest developments as well as the available tools for developing COM components. Possible COM applications for developing power system software, such as sparse matrix manipulation, fault location, genetic algorithm applications, and so on. are presented. Advantages and promises brought about by COM are manifested through these examples.

• The Transactions of the Korea Information Processing Society
• /
• v.3 no.4
• /
• pp.855-865
• /
• 1996

In this paper, we propose a automation of the classification process for reusable software component and construction method of structured software components library. In order to efficient and automatic classification of software component, we decide the facets to represent characteristics of software component by acquiring semantic and syntactic information from software components descriptions in natural language, and compose the software component identifier or automatic extract terms corresponds to each facets. And then, in order to construct the structured software components library, we sore in the near location with software components of similar characteristic according to semantic similarity of the classified software components. As the result of applying proposed method, we can easily identify similar software components, the classification process of software components become simple, and the software components store in the structured software components library.

• Journal of Institute of Control, Robotics and Systems
• /
• v.16 no.6
• /
• pp.608-616
• /
• 2010

Robot software components can be categorized into two types; the pure S/W component and the H/W-related one. Since interface testing of the robot software component is the labour-intensive and complicated work, an effective automated testing tool is necessary. Especially it is difficult to test all types of H/W-related components because it is hard work to prepare all H/W modules related to them. This paper proposes a new simulation-based interface testing automation tool(SITAT) which generates automatically test cases for interface testing of the robot software component and executes the interface test with the generated test cases where the simulator is used for simulation of the activity of a H/W module instead of the real H/W module. This paper verifies the effectiveness of the suggested SITAT with testing of the real H/W-related robot software component.

• The KIPS Transactions:PartD
• /
• v.9D no.3
• /
• pp.399-408
• /
• 2002

Component technology was proposed and applied to software development to overcome software crisis. Software component is a black box like an integrated circuit in hardware but it can not be utilized without good support specially for helping users understand efficiently. This paper shows that data book format for understanding hardware component can be well applied to representing software component. We selected an approach to understand component by matching the contents of data book with UML and API model technique. Besides, we added the architecture part and the interface which are the most important property of software component to the data book for software components. In order to verify effectiveness of components data book we extended batch descriptor in EJB and performed an experiment providing data book to programmers with components.

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

As software industry is rapidly evolving, IT business enterprises have been meeting with cutthroat competition in developing software. As software reusability, time to market, and maintainability are considered as a competitive edge, software component techniques have lately attracted considerable attention. Currently, although there are some supporting tools for developing software components, they do not have tight connections among component developing processes such as component identification, component modeling, detailed design, code generation, deployment, and testing. And it is restrictive for users to construct various scales of components on component platform architecture. In this paper, we provide an implementation and a design of a supporting tool for constructing platform-independent software components, which covers all development lifecycles of components. In the phase of component modeling, platform independent, conceptual components are identified from domain model information in the view of system partitioning. Detailed design and implementation of a component are performed on the J2EE platform architecture. And the changes on the design model and source codes are consistently managed by using round-trip techniques.

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

Many researchers have studied component technologies with concept, methodology and implementation for partial business domain, however there are rarely researches for component classification to manage these systematically. In this paper, we suggest a component classification model, which can make component reusability higher and can derive higher productivity of software development. We take four focuses generalization, abstraction, technology and size. The generalization means which category a component belongs to. The abstraction means how specific a component encapsulates its inside. The technology means which platform for hardware environment a component can be plugged in. The size means the physical component volume.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.3
• /
• pp.808-817
• /
• 2000

Component specification languages in consideration of reuse are essential factor in classification, verification and retrieval of components. A number of legacy specification languages have already been used, however, they are complex and include many necessary elements in the specification for implementation. In this paper, we present XML-based component specification and software architecture specification language to solve these problems of legacy specification languages. The presented specification languages consist of component specification, which is composed of signature specification, interface specification and message specification, and software architecture specification providing graphical notations and textural notations. Component specification supports component retrieval with behavioral match and black-box reuse of component. In addition to this, it improves the efficiency of retrieval and document management with XML-based component specification. Software architecture specification supports the structural reuse of architecture, which is white-box reuse, through mesage-based architecture specification.

• The Journal of the Korea Contents Association
• /
• v.2 no.4
• /
• pp.59-66
• /
• 2002

As for the software development, it is complicated, and size of software is growing larger. And contraction of a software development period is required acutely because it is short a period of software life cycle. Also, it becomes harder development and a maintenance because it is short a life cycle of developed software. According to this an effort is increased in order to reduce a development cost and time as using a component to have been implemented previously in development of software. A current component technology is developing into a very fast speed and is bringing a large change into development of a Web base system in addition to existing software development method. In this paper, we were handling a related technology for Web system development of a CBD base systematically and derived an issue to apply it to development of a Web system and presented an efficient practical use method of a component technology. First of all we looked into a component technology and a CBD methodology systematically and described a component technology in Web. Also, we proposed a method to increase development and efficiency of practical use of a Web system based on a component. The this study result can decrease a development cost of a Web system and a load of maintenance management through the re-use of a code.

• Journal of KIISE:Computing Practices and Letters
• /
• v.9 no.3
• /
• pp.241-253
• /
• 2003

SCA (Software Communication Architecture), which has been adopted as a SDR(Software Defined Radio) Forum standard, provides a framework that successfully exploits common design patterns of embedded systems software. However, the SCA is inadequate as a component framework since it does not explicitly specify (1) a component model that defines how to express a component interface and how to implement it, (2) a package model that defines what and how to package in deployment units, and (3) a deployment model that defines the deployment environment and deployment process. In this paper, we propose a SCA-based component framework for SDR. Specifically, we present (1) a component model that defines a component as a specialized CORBA object that implements object management functionality, (2) a package model exploiting the existing XML descriptors of the SCA, and (3) a deployment model that defines a SCA-based deployment environment, a boot-up process that restores the deployment state, and a deployment process that supports lazy application instantiation and dynamic component replacement.