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

Developing a component-based software requires verified and standardized software components. This paper presents a component quality management (CQM) process. The process was developed and applied to the government-sponsored trial projects that developed software components. The process is composed of four phases：quality specification, quality planning, quality control, and quality evaluation. With this process, we can establish quality goals and focus our efforts on the activities to achieve the goals. A component quality model is also suggested to transform the implicit quality requirements into the measurable quality goals and to be used for the basis when we evaluate the quality of software components against the quality goals.

• The Transactions of the Korea Information Processing Society
• /
• v.4 no.6
• /
• pp.1519-1530
• /
• 1997

Object-oriented software, reusability enables to specialize the software techniques by leading the user friendly thought and meets the user's need only concentrating on convenience of development environment. Reuse effect can be maximized through retrieval system. In this paper, we development the MT-Views(Multiple-Template Views) to realize the reuse effect as integrated reuse system including retrieval, understanding and rebuilding tools based on class library. We used the hybrid retrieval model for easy and efficient retrieval of similar software components. With using these tools, users can retrieve the reusable components and reuse the components for constructing therir own applications. Also, we can acquire many informations about retrieved components, so can rebuild components conforming our original intend.

• Journal of Multimedia Information System
• /
• v.2 no.2
• /
• pp.241-248
• /
• 2015

The safety-critical software in healthcare systems needs more and more perceptive excess among human observation and computer support. It is a challenging conversion that we are fronting in confirming security in healthcare systems. Held in the center are the patients-the most important receivers of care. Patient injuries and fatalities connected to health information technologies commonly show up in the news, contrasted with tales of how health experts are being provided financial motivation to approve the products that may be generating damage. Those events are unbelievable and terrifying, however they emphasize on a crucial issue and understanding that we have to be more careful for the safety and protection of our patients.

• Journal of the Ergonomics Society of Korea
• /
• v.22 no.3
• /
• pp.45-56
• /
• 2003

This study was conducted to develop user interface design guidelines for those who design education software products (web sites or CD-ROM titles). To establish this guideline scheme, international standards, commercial design guidelines, and research papers were surveyed. Especially, ISO 9241 was referred as a basic model of a guideline scheme. First, the research group developed draft guidelines. After that, education software developers, designers, and a user group reviewed the draft and the draft was revised with their commentations. Five components were selected as a primary class of guideline scheme: general principle, dialogue design, user guidance, visual interface, and information presentation. Each component was divided several components as a secondary class. Finally, 45 items were selected as user interface design guidelines for the education software design.

• The Transactions of the Korea Information Processing Society
• /
• v.4 no.1
• /
• pp.97-106
• /
• 1997

Software reuse techniques make reapplication of various well-organized information knowledge to system development so that improve productivity and make it easy to maintain software. This paper describes the design and implementation of CSORUS(C and C++ SOurce ReUse System) which can extract reuse components using reverse engineering, and store, retrieve, merge them written with C of C++ programming language. The construction components using reverse engineering has advantage in quality assurance because they are reliable components already tested in real environments.

• The Transactions of the Korea Information Processing Society
• /
• v.7 no.4
• /
• pp.1092-1102
• /
• 2000

In this paper, we made software components reusable through syntax-analysis method, designed a Viewer for understanding component information, and retrieved similar components by using Enhanced SARM. Because SARM requires a lot of computation time, it was enhanced by reducing unnecessary activation value. Also GUI was designed for component-query relationship and Viewer represents hierarchy diagram of a retrieved component. This system supports facilities which can insert and delete components on diagram. For a component modification, this system supports a editor to rebuild class inheritance relationship. In this paper, SCRS (software components reuse system) is consisted of syntax-analysis method, component-query relationship interface, retrieval (Enhanced SARM), diagram viewer, reuse on diagram, and a editor.

• 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

• Journal of Internet Computing and Services
• /
• v.3 no.4
• /
• pp.83-94
• /
• 2002

Recently for software development productivity a lot of researches in the field of software engineering hove focuses on the component-based software product lines which allows the reuse of forger-granularity software components Its purpose is to develop the specific software application of quality more rapidly by instantiating and assembling the components populated in software product line assets The essential part to build the component-based software product lines is the quality of components, and one of the most important features determining the quality of components is 'reconfigurability' Component reconfigurability means the extent to which the reusers can change the functions and architecture of the component according to their context and environment. This paper proposes the component code generation technique which provides the reconfigurability at the time of code generation using The feature diagram and XML/XSLT technologies The approach of this paper allows the component reusers to get automatically their own component source code by providing only the values of variabilities represented in the feature diagram of the component family. The real world example, the code generation system for o list container family, shows the applicability of the feature model and XML related technologies in the area of the generative programming. Our approach should be basis to build the component based software product lines and extensible to support the larger graularity components.

• Journal of Internet Computing and Services
• /
• v.6 no.4
• /
• pp.21-35
• /
• 2005

Software product-lines is the software development paradigm to attain the rapid development of quality applications by customizing the reconfigurable components and composing them based on predefined software architectures. Recently various methodologies for the component-based product lines are proposed, but these don't provide the specific implementation techniques of the components in terms of variability resolution mechanism. In other hand, the several approaches to implement the component supporting the variabilities resolution are developed, but these don't define the systematic analysis and design method considering the variabilities from the initial phase. This paper proposes the integration of PLUS, the one of product line methodologies extending UML modeling, and component code generation technique in order to increase the efficiency of producing the specific product in the software product lines. In this paper, the component has the hierarchical architecture consisting of the implementation elements, and each implementation elements are implemented as XSLT scripts. The codes of the components are generated from the feature selection. Using the microwave oven product lines as case study, the development process for the reconfigurable components supporting the automatic variability resolution is described.

• The Journal of the Korea Contents Association
• /
• v.10 no.6
• /
• pp.144-155
• /
• 2010

In recent years, there has been a rapid and wide spread of robot system in our lives and with the ever increasing the requirement of user for robot functionality, the software component is increasingly sophisticated and complicated. Accordingly it is inevitable to employ a standardized software platform. The OPRoS is open standard software platform based on component for robot system. When the software components were developed, it has got to validate the conformity of robot software components which comply with the OPRoS standard specification. In this paper, we deal with the design and implementation of the structural conformance test suite to verify and validate the conformance of components to be developed by user. As the results of some experiments, we could verify it from this test suite whether the components satisfied standard requirement or not.