• Journal of the Korea Society of Computer and Information
• /
• v.13 no.5
• /
• pp.163-170
• /
• 2008

As the degree of dependency and application of component increases, the need to strengthen security of component is also increased as well. The component gives an advantage to improve development productivity through its reusable software. Even with this advantage, vulnerability of component security limits its reuse. When the security level of a component is raised in order to improve this problem, the most problematic issue will be that it may extend its limitation on reusability. Therefore, a component model concerning its reusability and security at the same time should be supplied. We suggest a Separation of Concerns Security Model for Extension of Component Reuse which is integrated with a wrapper model and an aspect model and combined with a reuse model in order to extend its security and reusability by supplying information hiding and easy modification, and an appropriate application system to verify the model's compatibility is even constructed. This application model gives the extension of component function and easy modification through the separation of conceits, and it raise its security as doll as extends its reusability.

• Journal of KIISE:Software and Applications
• /
• v.32 no.12
• /
• pp.1205-1216
• /
• 2005

Component-based Development (CBD) is gaining popularity as an effective reuse technology. Especially commercial-off-the-shelf (COTS) components are mainly for inter-organizational reuse, rather than intra-organizational reuse. One of the essential tasks in CBD is to reuse the right components that provide the functionality and interface required by component consumers. If candidate components provide a limited applicability and customizability, a component consumer cannot reuse the components in application development. To resolve this partial matching problem, we need smart connectors that fill the gap between candidate components and the specification of components required. Previous researches about smart connector describe only connector types to resolve mismatch problems. However, previous researches do not address the identification and design method to resolve the problems. In this paper, we suggest taxonomy of various mismatch problems to identify partial match problems between requirements of the application and components. We identify smart connector types and suggest a systematic process for designing smart connectors using the taxonomy. Therefore, components that have the problems can be used to develop applications.

• Journal of KIISE:Software and Applications
• /
• v.33 no.3
• /
• pp.289-300
• /
• 2006

Product line is nowadays well known as a representative method for reuse. In the product line, important assets are components. Although enough concerns were given of the product line, it was not accomplished to structure and specify a product-line component with variability. This paper presents an approach to specify components in the product line. The approach describes the static and dynamic structure of a product-line component and explains the behavior and concurrency of the component. The component information is separately described in the black-box and white-box using the Feature-Oriented Reuse Method(FORM). This research also formalizes the data on a component specification in the form of BNF. The specification is described through careful consideration for many different characteristics of the product-line component, so this paper helps to easily develop the components in the product line and to well comprehend how to apply a method for the product line.

• Journal of Internet Computing and Services
• /
• v.7 no.6
• /
• pp.1-10
• /
• 2006

A software development using components reuse is an useful method to reduce the software development cost. But a retrieval method by the keyword and category classifications is difficult to search an exact matching component due to components complexity in component reuse. Therefore, after different existing methods are examined and analyzed, an effective classification and retrieval method using XML specifications and the system architecture of components integrated management based on it are presented. Many discording elements of DTD which is component meta-expression exist in components retrieval. To compensate it, this retrieval method using estimations of precision and concision is effective one to catch considerable matching preference components. This method makes possible to retrieve suitable components having better priority due to searching similar matching components that are difficult in an existing keyword matching method.

• The KIPS Transactions:PartD
• /
• v.11D no.3
• /
• pp.605-616
• /
• 2004

The purpose of CBSD(Component Based Software Development) if to develop software using a reuse component and components assembly. The reused components have to be adapter for satisfaction of requirement specification. This paper represents a component adaption method which reuse previously developed component or legacy system, using an adaptation component called by TA(Transaction Adaptor). The adaptation using TA transmits XML data that is translated into stream type, from a client to on host system. And we introduce RS(Rule Server) which gets some Information from XML data for application program development. Through the Interaction of TA and RS, we can improve effectiveness of component development and maintenance and we can reuse legacy system.

• Journal of Software Engineering Society
• /
• v.23 no.4
• /
• pp.151-163
• /
• 2010

In the defense software domain where large-scale software products in various application areas need to be built, reusing software is regarded as one of the important practices to build software products efficiently and economically. There have been many efforts to apply various methods to support software reuse in the defense software domain. However, developers in the defense software domain still experience many difficulties and face obstacles in reusing software assets. In this paper, we analyze practical problems of software reuse in the defense software domain, and define core requirements to solve those problems. To meet these requirements, we are currently developing the Component Grid system, a reuse-support system that provides a developer-centric software reuse environment. We have designed an architecture of Component Grid, and defined essential elements of the architecture. We have also developed the core approaches for developing the Component Grid system: a semantic-tagging-based requirement tracing method, a reuse-knowledge representation model, a social-network-based asset search method, a web-based asset management environment, and a wiki-based collaborative and participative knowledge construction and refinement method. We expect that the Component Grid system will contribute to increase the reusability of software assets in the defense software domain by providing the environment that supports transparent and efficient sharing and reuse of software assets.

• The KIPS Transactions:PartD
• /
• v.9D no.5
• /
• pp.837-846
• /
• 2002

When you develop component, you can offer reusability and extension by analyzing commonality and variability about attribute and behavior. Therefore Component that analyzing commonality and variability are use for the purpose of reducing discord of function and adaptedness. I wish to research reusability and extension of component by analysis commonality and variability of component that exist by domain in this paper, extractfunctionofcomponentbybehavioranalysis.

• 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 the Korea Society of Computer and Information
• /
• v.11 no.3
• /
• pp.161-166
• /
• 2006

In this paper, CPLD low power technology mapping using reuse module selection under the time constraint is proposed. Traditional high-level synthesis do not allow reuse of complex, realistic datapath component during the task of scheduling. On the other hand, the proposed algorithm is able to approach a productivity of the design the low power to reuse which given a library of user-defined datapath component and to share of resource sharing on the switching activity in a shared resource Also, we are obtainable the optimal the scheduling result in experimental results of our using chaining and multi-cycling in the scheduling techniques. Low power circuit make using CPLD technology mapping algorithm for selection reuse module by scheduling.

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