• Journal of KIISE:Software and Applications
• /
• v.31 no.10
• /
• pp.1286-1303
• /
• 2004

Component-based Development is gaining a wide acceptance as an economical software development paradigm to develop applications by utilizing reusable software components. Well-defined interface manages coupling and cohesion between components, minimizes the effect on the user in case of component evolvement, and enhances reusability, extendibility and maintainability. Therefore, study on systematic development process and design guidelines for component interface has been required since the component has been introduced. In this paper, we propose three types of interfaces based on software architecture layers and functionality types； Provided Interface which provides functionality of a component, Required Interface which specifies required functionality that is provided by other components, and Customize Interface which tailors the component to customer's requirement. In addition, we suggest design criteria for well-designed interface, and systematic process and instructions for designing interface. We firstly cluster operations extracted from use case model and class model to identify Provided interfaces, and design Customize interfaces based on artifacts for variability. We also specify Required interfaces by identifying dependency among interfaces. Proposed interface design method provides traceability, throughout the component interface design. And furthermore, proposed guidelines support practical design for high quality component based on a case study.

• Journal of KIISE:Software and Applications
• /
• v.34 no.4
• /
• pp.303-316
• /
• 2007

Even though many approaches for reuse have been introduced, software engineers are still hesitating to reuse existing software components. Among various reasons for the phenomena, the most significant one is that existing approaches failed to give substantial benefit for the reduction of developers' effort in reusing software assets. To solve this problem, we introduce a custom reuse model utilizing diverse aspects of components specified by RAS and services oriented architecture. We also carried out a case study to demonstrate its feasibility and evaluated it by comparing it to an existing code-based software reuse process. The proposed reuse model helps in the reduction of effort in reusing existing components by decreasing the time for searching and understanding them. Compared to other approaches such as product line engineering, our approach for software reuse using MPC does not require much initial work for implementing the reuse model in different projects. It is of interest to software engineers who are worried about heavy investment, which can cause the delay in their usual development work. Furthermore, the proposed reuse model is not mutually exclusive with other approaches for software reuse such as CBSD or product line engineering. It can accelerate the benefits gained from them.

• The KIPS Transactions:PartD
• /
• v.10D no.1
• /
• pp.67-76
• /
• 2003

The reuse of software is to use the components of software to be made beforehand to improve the productivity of it. The development of electronic commerce requires it which can be shown from changing the change of business models Reuse is the necessary solution to cope with a rapid change in the electronic commercial transaction. These reuse business models have the defects that they are not offered from version management. This paper has the purpose that by doing the supplementation of defects not to be offered from the version management and by introducing the quick change management about reuse business models, reusing the components and saving a development and reducing a development af period. The reuse of components by the new reuse business models has the advantages to minimize the danger elements from the design to the finish. We use the version management and try to present the method to make the efficiency of reuse by introducing components and managing the elements about components to the version in the technique to accomplish the reuse of software.

• Journal of Korea Multimedia Society
• /
• v.5 no.1
• /
• pp.77-93
• /
• 2002

Now we are following component-based software development as a solution to improve the reusability, reliability, and extensibility of the software. To support these, the developed components must be reused through component repository at software development. However, traditional centralized repositories couldn't activate component markets since not only the number of users were restricted but also most of the provided components were those on clients like user interface and so on. Recently, a lot of server-side components, reused in a specific domain, have appeared thanks to the development of both Internet technology and component technology such as EJB, DCOM, etc. Therefore, component repositories, based on domain information, classify and provide components and must offer web-based service for many users to use it stably. This study introduces the implementation of a component repository based on J2EE application model. It provides application developers with the service to search and extract appropriate components, and supplies them reliable services in web environment.

• Proceedings of the Korean Institute of Information and Commucation Sciences Conference
• /
• 2014.10a
• /
• pp.71-74
• /
• 2014

Mobile apps have been developed actively using open source software recently. Tend to be used much more than the component of the functional role on the ground that the reuse of components for the User Interface is an open source implementation of the mobile component is easy. The problem is to apply as an open source mobile components selected for this reason all of the existing two studies. It is an open source software selection process and selection procedures shelf components. We revise to conform to existing mobile components selected for the study on open source software selection process in this paper. Can help increase the productivity of the mobile app development by the open source components to meet the functional requirements when developing mobile apps that can be easily retrieved and presented the selection process of this study is effective.

• Korean Management Science Review
• /
• v.15 no.2
• /
• pp.59-70
• /
• 1998

According to the Gartner Group, the market for ERP software in Korea is growing rapidly. However, the number of successful ERP implementations is quite few. Standard(unmodified) ERP's are built based on best practices. Improvements expected from successful implementation are based on best practices built into the software. Many improvements are lost through modification to "standard" software. Even minor changes in software can significantly reduce benefits. Both implementation time and risk factors are increased with modifications. We introduce a methodology, called package Enable Re-engineering (PER) and the main components of change management program by Ernst & Young. "To-Be" model could be developed through the software capabilities. And change management processes such as continuous education and self-developments are required. The philosophy of the change management processes is to let the software package drive the re-engineering practices and avoid moving the software toward the "As-IS" process. Extensive top management involvement, major focus on speed, extensive communication program, and "clear" picture of the future are essential components of change management. We are sure that the complied experiences and model have implications for practice and for academicians for their endeavors in their fields.

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

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

• The Journal of Korean Association of Computer Education
• /
• v.3 no.2
• /
• pp.87-94
• /
• 2000

Software productivity doesn't satisfy the need of service of software users and software quality isn't improved. Moreover, we still have difficulty in software maintenance. As a plan to counteract solving this crisis, the technology that is called CBSE or Componentware is introduced. Componet Based Software Architecture, one of the technologies associated with CBSE, as a structural description of system, describes both the components composed system of and interaction among these components. Software Architecture provides the technology and the methodology of composition among components in the field of CBSE. is accepted one of core technologies. In this thesis, we analyse information necessary for component specification and then proposed that component specificaton activities using formal specification language Z which is verified with the ability of analysis and logicality. The proposed activities are composed of 9 tasks. By presenting specific 11 products, it is also proposed that component specification activities which is the base of CBSD(ComponentBased Software Development) for reusing.

• The Journal of the Korea Contents Association
• /
• v.12 no.1
• /
• pp.59-67
• /
• 2012

Software change management is focused on the change of a entity like the change of contents of a system or a document. In change management, interactive relationship among requirements and complex decision making is needed to obtain optimized status. In this paper we design a management model of software change management in distributed environment which mange the change among components by time and situation. In addition, each components are defined and use ANP technique for best decision-making by using the subordinate relationship and feedback considering the mutual dependency referring the change of components in distributed environment. Thus, we analyze the dependency among each components and show 3 types of change relationship. Also through analysis of dependency, we verified the effectiveness of such approach.