• The Journal of the Korea institute of electronic communication sciences
• /
• v.14 no.3
• /
• pp.513-518
• /
• 2019

The non-destructive testing equipment using an eddy current was developed to check for defect in the vehicle transmission component. A defect master sample was made to test all types of defects that occur in the component and also an eddy current detector was manufactured and used to test and detect all kinds of defects. In addition, testing was held against the actual defective items to investigate the cause and type of defects, and a comparative study was conducted based on results from the examination. The software system of the eddy current detector was developed so that even a non-specialist can make assessment of detect in the component from the test results displayed on the monitor.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.16 no.1
• /
• pp.155-162
• /
• 2016

In recent years, hoping the interaction of individuals and rather than software development process and tools, and customers want software that works first, rather than a comprehensive document, in cooperation with the customer, rather than the developer negotiate a contract, to each other stick to the plan I think even more so than the value that corresponds to the change. In view of this, software development is given the autonomy and motivation to project team rather than process-oriented and have a passion and vision and human relations oriented management approach is required. In recent years, increasing the productivity benefits of agile development processes, improved quality, efficiency and customer satisfaction as is demonstrated in the methodology selected to promote the project, attention was given to the experts. Contemporary demands with regard to the methodology chosen to meet your needs, in this paper in the organization, and to solve the problems of product-based Cross functional team proposed methodology Feature Team model, this model is an organizational Cross functional team and the team is not the outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-plan through the driven agile technique-based model and proposed a difference. And the domain analysis, required extraction by conventional JAD (joint application development) meeting the targets for the object-oriented modeling, in modeling and organize, review, aware in advance and the UML Structure and Behavior Diagrams and proposed to proceed with the project.

• Journal of Satellite, Information and Communications
• /
• v.8 no.1
• /
• pp.54-60
• /
• 2013

The need for high performance of on-board computer (OBC) is essential due to the growing requirements and diversified missions, and so OBC has been developed on the basis of the standard design and reconfigurable modularization in order to improve the utilization of OBC for different missions. The processor in OBC of next generation satellite which is currently developed by KARI is adopted the LEON2-FT/AT697F processor based SPARC v8 as main processor and controls various devices such as SpaceWire, MIL-STD-1553B and CAN through PCI on the standardized communication chips. This paper presents the architecture and design of system software for LEON2-FT processor based on PCI, and development of PCI software component. Also it describes the porting of VxWorks 6.5 for LEON2-FT and the test under the simulation environment for LEON2-FT and PCI with communication chips.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2000.04a
• /
• pp.797-802
• /
• 2000

컴포넌트 지향 소프트웨어 개발은 독립적이고 확장성 있는 재사용 부품을 만들어 표준화되고 신뢰성 있는 소프트웨어 모듈 조립에 의한 것이며, 개발비용과 시간을 줄이고 유지보수를 용이하게 한다. 이러한 컴포넌트는 여러 가지 도메인 상에서 제공될 수 있도록 기존의 컴포넌트 생성을 위한 방법론이 제시되어져 왔다. 본 논문에서는 비즈니스 도메인을 기반으로 요구사항에서부터 분석 및 설계, 구현, 그리고 실행에 이르는 분산형 비즈니스 컴포넌트를 생성하는 개발 프로세스를 제시하여, 확장된 형태의 4가지 비즈니스 컴포넌트(attribute, operation, facility, package)를 얻어낼 수 있도록 하며, 분산형 컴포넌트는 웹을 기반으로 세분화한 시스템 관리를 단순하게 하고, 비즈니스 컴포넌트의 재사용성을 높이고 유지보수를 줄이며, 컴포넌트간의 통합을 쉽게 한다. 또한, 사용자가 원하는 실세계의 비즈니스 개념을 올바르게 적용할 수 있으며, 단일 개념의 단순한 형태로 사용자가 원하는 내용을 쉽게 변화시킬 수 있도록 하여 미숙한 재사용자들이 빠르고 효과적으로 활용할 수 있도록 한다.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2000.10a
• /
• pp.583-586
• /
• 2000

대부분의 응용 시스템들이 인터넷과 웹 기술을 기반으로 개발, 운영됨에 따라 상호운영성을 허용하고 동적 변화에 민첩하게 대응할 수 있는 소프트웨어 개발을 위한 방법론 및 툴 지원이 요구된다. 이에 따라 컴포넌트 기반의 소프트웨어 개발(CBD : Component Based Development)은 소프트웨어 시스템 구축을 위한 가장 이상적 전략으로 인식되고 있다. CBD 개발을 지원하기 위한 컴포넌트 저장소는 컴포넌트의 개발과 유통, 활용을 위한 컴포넌트 및 관련 모든 프로덕트 정보들의 통합적인 관리 중심체이다. 그러므로 효과적인 CBD의 전개를 위해서는 정규화된 컴포넌트 참조 아키텍쳐에 기반한 저장소 구축은 필수적이다. 본 논문에서는 CBD 방법론에 의한 컴포넌트 저장소 구축을 목적으로 저장 아키텍쳐를 제시하고 이를 기반한 저장소 프로토타이핑을 개발한다. 이를 위해 컴포넌트 기능성 영역의 수직적 관점과 라이프사이클 관점의 수평적 관점이 혼합된 아키텍쳐를 정의하고 이에 식별, 정의되어진 컴포넌트를 적용한다.

• Journal of Korea Multimedia Society
• /
• v.2 no.2
• /
• pp.217-229
• /
• 1999

Framework is the set of interrelated classes, constructing reusable design in specific domain or set of abstracted classes, and defines common architecture among applications included in domain. Developers can reuse not only class code but also wide range of knowledge on domain by reusing framework. In this papers, we present COM(Component-Oriented Methodology) for the reuse of framework, and develop construction environment for framework and domain development. That is, domain is analyzed by input of domain knowledge on real world to create software based on component, and hotspot is identified through analyzed information, and redesigned(refactoring) by putting additional information on users and developers. After that, I will create domain framework and application framework depending on domain. In this Component-oriented methodology, information is searched, understood and extracted or composite through component-pattern library storage internally. Then this information is classified into the information on component and pattern respectively, and used as additional information in redesigning. With this, developer can obtain reusability, easiness and portability by constructing infrastructure environment that allow to register, update and delete component through Component Pattern Management System(CPMS) under the development environment which can be easily applied to his own application using multimedia component, in this thesis, CORBA(Common Object Request Broker Architecture) environment.

• Journal of Internet Computing and Services
• /
• v.20 no.6
• /
• pp.37-46
• /
• 2019

A test plan is a high level document detailing objectives, processes, schedules and so on for verifying a developed software. And a test strategy, a component of a test plan, is about how to test software products to guarantee its quality and find bugs in the software in advance. Therefore, establishing effective and suitable test strategies is important for elaborating test processes. However, these tasks are difficult for project managers who write a test plan if they were not trained well in software test processes. And mis-designed test strategies will also mislead entire testing behaviors that testers would do. As a result, there would be a low quality software product in the end. To solve this problem, we propose a new test strategy reuse technique in this paper. By utilizing test plans of already completed software development projects, we lead test planer to reuse suitable and effective test strategies which were used in previous projects. To do so, we evaluate existing test strategies by utilizing ISO/IEC 25010 quality model for evaluating the suitability of test strategies and also use effectiveness metrics for test strategies. And from these evaluations, we predict completeness of new test plan that is written by reused test strategies. It can help the project manager to write an appropriate test plan for the quality characteristics which are selected as objectives for testing and software product. We show the possibility of our approach by implementing a prototype into the existing framework in a case study.

• International journal of advanced smart convergence
• /
• v.10 no.3
• /
• pp.257-278
• /
• 2021

As the definition of the vendor-oriented implementation method, which was utilized in adopting an ERP system, has been centered around the project construction business, it was difficult for the EPR adopting organization to systematically prepare ERP projects and have enough deliberative opportunities to change-related policies. Furthermore, this method does not have a fully standardized construction process. Accordingly, by defining an organization that wants to adopt an ERP system as a customer, this paper develops the customer-based ERP construction process framework that assists both customers and developers who construct the system. For this purpose, this paper reviews the previous research and collects the construction processes of the commercial ERP SW vendor and ERP construction cases while proposing the three-layer process framework to construct ERP through the KJ method. The ERP process framework consists of 7 processes, 32 activities, 141 tasks while providing definitions for concepts of each component. Furthermore, the proposed processes and phases were set in order of the recommended execution, while the activities were suggested as an open-ended type so that the application and usability can be increased and polished by reflecting experts' opinions. The contribution of this study is to standardize the ERP project process by transforming the previous supplier-based ERP construction method into the customer-based one while providing important procedure and activity frameworks that apply to diverse ERP solutions per vendor. At the same time, this study provides an theoretical foundation to develop the construction process for the customer -based Cloud ERP. In practice, At the beginning of the ERP system construction project, it provides communication or process tailoring tools for the stakeholder.

• IE interfaces
• /
• v.15 no.2
• /
• pp.172-181
• /
• 2002

Customer satisfaction is undoubtedly one of the top strategic issues in the new decade. Today, many organizations are rushing to become more customer focused. A key component of many initiatives is the implementation of customer satisfaction software. In this paper, we provide a case study for customer satisfaction management in a city gas company. The three issues include the plan for giving premiums and the development of a happycall system and a web-based measurement system for customer satisfaction.

• Proceedings of the Korean Information Science Society Conference
• /
• 2005.11b
• /
• pp.334-336
• /
• 2005

유비쿼터스 시대에 진입하면서 임베디드 소프트웨어의 개발에 대한 관심이 높아지고 있다. 국방 분야에서는 국방무기 및 비무기 내장형 소프트웨어 관리지침과 공군에서 운영되는 항공무기 소프트웨어 개발 프로세스 등이 운용되고 있으며, 국방 CBD 방법론은 주로 응용체계 개발을 위한 컴포넌트 기반의 구체적인 방법론이다. 이러한 국방 CBD 방법론을 임베디드 소프트웨어 개발에 적용가능 여부는 발표되지 않았다. 따라서 본 논문에서는 임베디드 소프트웨어개발을 위한 국방 CBD 프로세스 테일러링 방안을 고찰하고자 한다. 이를 위하여 국방 무기 및 비무기 내장형 소프트웨어 관리지침에 근거한 조정, 임베디드 소프트웨어 개발 방식에 따른 조정 컴포넌트 및 객체 지향기술, 그리고 UML 기술 적용으로 구분하여 테일러링 방안을 제시한다. 그 결과 국방 CBD 방법론의 적용 범위의 확대 및 개발 프로세스의 표준화에 기여할 것으로 기대된다.