• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.398-413
• /
• 2003

Component-based Software Development(CBSD) supported by both component and reusability can reduce development time and cost, and also can achieve high productivity. To support component reusability systematically domain analysis and design in parallel with CBSD-process is needed. And also it is needed to suggest objective analysis process to fine out commonality and variability in domain, which is lacked in current domain analysis and design method. And to abstract domain component from the information which is well reflected in domain model, and to express it in domain architecture is needed. In this paper, we suggest the method to define, analyze and design domain systematically for enhancing reusability effectively in Component-base Software Development. We abstract components which can be reusable in domain, in other word, which have commonality from requirement analysis level. We sustain and refine them. And we reflect them to the products of each level. From these process, we can produce the domain component which have commonality. On this basis, we can design domain architecture. In this paper, to produce reusable software we investigate new systematic approach to domain analysis and design from the view point of software reusability.

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

• Journal of KIISE:Software and Applications
• /
• v.30 no.5_6
• /
• pp.414-429
• /
• 2003

Component-based development(CBD) has been generalized in industry to master the complexity and reduce the development cost and time. However, current CBD practice is developing the component which is dependent on single application[l][2]. Therefore component variability is emphasized to reuse the component in many family members in a domain[8]. However, components are developed for the reason of replaceability rather than the reusability which is the main purpose of the component due to the insufficiency of the study of component variability definition and type[3]. In this paper, we formally specify the component variability reflecting the characteristics of the component to increase the component reusability. We define the logic variability which was recognized as the existing component variability and we propose all types of variability existing in the component by suggesting three more variability types. And we propose the component variability scope which makes us estimate and verify the number of cases of the variability when we customize the component. We propose these component variability types and scope through formal specification. By applying these techniques in developing components, we can develop high quality components reusable in many family members.

• KSCI Review
• /
• v.2 no.2
• /
• pp.7-18
• /
• 1996

In this paper library is proposed to store and retrieve the software components, in addition to that designed and implemented the user interface for management and control of this library. Applying components to this library for version control, component's quantitative testing are processed. In the case of user selection of component's a high quantative rate components can be selected.

• Journal of the Korea Society of Computer and Information
• /
• v.3 no.1
• /
• pp.63-80
• /
• 1998

In object-oriented software development, reuse has been studied for the enhancement of software quality and software developer's productivity. But improper modeling in design phase and uncontrolled change during maintenance activities have a problem to reuse a class. In this paper we analyze a semantic cohesion of classes using C++ Program dependency graph, and slice a class with cohesion, so that this method supports the re-estimate of class quality and the extensibility of class. Therefore this proposed method in this paper increases the easibility of the restructuring in the reusable systems, when the developer selects a requested component for a object-oriented program development.

• The Journal of the Korea Contents Association
• /
• v.6 no.3
• /
• pp.20-27
• /
• 2006

In this paper we constructed semantic net that can efficiently conform retrieval and reuse of object-oriented source code. In order that initial relevance of semantic net was constructed using thesaurus to represent concept of object-oriented inheritance between each node. Also we made up for the weak points in spreading activation method that use to activate node and line of semantic net and to impulse activation value. Therefore we proposed the method to enhance retrieval time and to keep the quality of spreading activation.

• Journal of Korea Society of Digital Industry and Information Management
• /
• v.10 no.1
• /
• pp.7-15
• /
• 2014

The accuracy of global navigation satellite system(GNSS) positioning has been studied during the last decades. Early GPS software was developed as monolithic tool in which all functions packed in the same software. But, these GPS software have the problems of the high cost of constructing system. close system architecture and the reusability. And there is a lack of interoperability between them because most of them have their own unique data format according to their application fields. In this paper, we have introduced requirements for design and specifications based on business process for the GPS system. commonly used to extract components from the requirements of the GPS business-based development process is presented. These components extracted by the process can be used to assemble components only. In particular, applications for developers to add features specific case without affecting the other components that can be modify the component.

• The KIPS Transactions:PartD
• /
• v.14D no.1 s.111
• /
• pp.67-82
• /
• 2007

Due to the classes in object-orientation, which are too detailed and specific, their reusability can be decreased. Components, considered to be more coarse-grained compared to objects, help maintain software complexity effectively and facilitate software reuse. Furthermore, component technology becomes essential by the appearance of the new frameworks, such as MDA, SOA, etc. Consequently, it is necessary to reengineer an existing object-oriented system into a component-based system suitable to those new environments. In this paper, we propose a model-based quantitative reengineering methodology to identify components from object-oriented systems. We expand system model and process, which are defined in our prior work, more formally and precisely. A system model, constructed from object-oriented system, is used to extract and refine components in quantitative ways. We develop a supporting tool and show effectiveness of the methodology through applying it to an existing object-oriented system.

• The Journal of Society for e-Business Studies
• /
• v.11 no.4
• /
• pp.67-86
• /
• 2006

In parallel with emphasizing more transparency and social responsibility of businesses, usage rate of XBRL, a XML-based language specific to business reporting, is rapidly increasing. XBRL takes the same approach with the standardization of B2B electronic documents in that it defines components (concepts and their structures) of business reporting documents using XSD(XML Schema Definition). However, it is fundamentally different from the standardization of B2B electronic documents because it restricts concepts to specific types and it defines diverse relationship types for connecting the concepts to themselves and other additional information. As XBRL applications are getting activated, one hot issue is the necessity for standardization of XBRL documents in the national level and reusing the components systematically This paper proposes an alternative based on the problem analysis in order to make it possible to standardize and reuse XBRL documents systematically by applying the UN/CEFACT Core Component methodology.

• The Journal of Information Systems
• /
• v.12 no.2
• /
• pp.129-149
• /
• 2003

One of the important applications in Enterprise Resource Planning(ERP) systems is the Manufacturing Resource Planning(MRPII) system using Bill of Material(BOM). The manufacturing resource planning determines the quantity and timing of the production or purchase of subassemblies and raw materials needed to support the Master Production Scheduling(MPS). The bill of material is the recipe, a list of the materials needed to make a product. This paper intends to suggest a component-based materials management system using Unified Modeling Language(UML), as an application system for automobile part industry. Applying component based materials management systems designed with UML methodology, we analyzed the workflow and the document on materials management process from production planning to inventory management, and implemented a prototype of efficient materials management system, as a surrogate of existing material requirement planning(MRPI) system. To produce many other assemblies for a automobile part firm, component parts are assembled into subassemblies that are joined to assemble the finished product. Through the system suggested in this study, the level of inventory has cut down and the cost of inventory management has decreased. Also, the development method using UML makes the analysis and design phase to shorten in implementation period of MRPII system. The implementation of materials management system using CBD shows the ease of use in software reuse and the interoperability with corporate Internal information system. The result of applying object-oriented CBD technique is to minimize the risk of life cycle and facilitate the reuse of software as mentioned to limitation of information engineering methodology.