• Journal of Information Technology Applications and Management
• /
• v.10 no.4
• /
• pp.185-194
• /
• 2003

One method to improve S/W quality before releasing after development is to enhance the its reliability, whose direct methodology is to detect and revise the fault through testing. Once the S/W is released because it meets the target reliability, We operational reliability arises. it is obvious the operational reliability different depending on the condition whether it is universal(package) S/W or dedicated S/W. We propose the methodology to calculate operational software reliability of universal and dedicated S/Ws in this paper.

• Journal of Information Technology Services
• /
• v.4 no.2
• /
• pp.47-59
• /
• 2005

S/W product line is a S/W product or a set of S/W system, which has common functions. We can develop a specific S/W product, which satisfiesrequirements of a particular market segment and a mission in a specific domain by reusing the core asset such as the developed S/W architecture through the S/W product line. S/W development methodology based on the S/W product line can develop a S/W more easily and fast by reusing the developed S/W core asset. An advanced country of S/W technology selects S/W product line as a core field of S/W production technology, and support technology development. In case of USA, CMU/SEI (Carnegie Mellon University / Software Engineering Institute) developed product-line framework 4.0 together with the industry and the Ministry of National Defense. Europe is supporting the development of product line technology through ITEA(IT for European Advancement) program. In this paper, we aim to construct reference architecture of S/W product line for production of the S/W product line.

• Journal of the Korea Institute of Information and Communication Engineering
• /
• v.13 no.3
• /
• pp.445-450
• /
• 2009

One method to improve quality before releasing of S/W after development is to enhance the reliability, whose direct methodology is to detect and revise fault through testing. Once the S/W is released because it meets the target reliability, the operational reliability problem arises. It is obvious the operational reliability different from that of testing stage depending on the condition whether it is universal(package) S/W or dedicated S/W. I propose the methodology to calculate operational software reliability of universal and dedicated S/W in this paper.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2003.11c
• /
• pp.1625-1628
• /
• 2003

컴포넌트 기반 시스템의 개발 생산성과 유지 보수성을 향상시키기 위해 기존에 생성된 소프트웨어 컴포넌트를 재사용할 수 있는 컴포넌트 기반 시스템 개발 방법론을 제시하고 종합적이고 체계적인 형태로 재사용 프로세스를 구성하고 각 단계별로 필요한 작업과 핵심 산출물을 살펴보도록 한다.

• 제어로봇시스템학회:학술대회논문집
• /
• 2003.10a
• /
• pp.706-710
• /
• 2003

In this paper, we will present brief design feature, implementations, and tests for verification of KOMPSAT-2 simulator, which is a subsystem of KOMPSAT-2 MCE. SIM is implemented on PC server to minimize costs and troubles on embedding onboard flight software into SIM, OOA/OOD methodology is employed to maximized S/W reusability, and XML is used for S/C characteristics, TC, TM and Simulation data instead of commercial DB. Consequently, we can reduce costs for the system, efforts embedding flight software, and maximize software reusability. SIM subsystem test was performed successfully.

• Proceedings of the IEEK Conference
• /
• 2000.06b
• /
• pp.153-156
• /
• 2000

This paper presents a SOC design methodology using the newly-emerging SystemC. The suggested methodology firstly uses SystemC to define blocks from the previously-developed system level algorithm with internal behavior and interface being separated and validate such a described blocks' functionality when integrated. Next, the partitioning between software and hardware is considered. With software, the interface to hardware is described cycle-accurate and the other internal behavior in conventional ways. With hardware, I/O transactions are refined gradually in several abstraction levels and internal behavior described on a function basis. Once hardware and software have been completed functionally, system performance analysis is performed on the built model with assumed performance factors and influences such decisions regressively as on optimum algorithm selection, partitioning and etc. The analysis then gives constraint information when hardware description undergoes scheduling and fixed-point trans- formation with the help of automatic translation tools or manually. The methodology enables C/C++ program developers and VHDL/Verilog users to migrate quickly to a co-design & co-verification environment and is suitable for SoC development at a low cost.

• Proceedings of the Korea Information Processing Society Conference
• /
• 2004.11a
• /
• pp.401-404
• /
• 2004

임베디드 시스템의 개발이 시장 적시성과 개발 생산성을 만족시키도록 개발 방법을 향상시키기 위해 제품 계열(Product Line) 기반의 개발 방법을 제시한다. 기존에 생성된 소프트웨어 컴포넌트를 재사용할 수 있는 컴포넌트 기반 시스템 개발 방법론을 제시하고 종합적이고 체계적인 형태의 재사용 프로세스를 구성하며 각 단계별로 필요한 작업과 제품 생산 원칙을 살펴보도록 한다.

• The KIPS Transactions:PartD
• /
• v.12D no.3 s.99
• /
• pp.429-438
• /
• 2005

For the implementation of science and technology based agriculture, one of the domestic rural development strategies, it is essential that we should have an integrated information system for each crop production. This system would be a web-based collaborative system for the local farmer and the advisors who guide the crop production technically, and would be capable of providing the real-time analysis functionalities and expert knowledge. In this thesis, we proposed a component based development methodology called MCPI(Method for Crop Production Information system) which employs and re-organizes Marmi-III, the popular existing component based methodology for the large scale S/W development project. In particular, MCPI is designed to reflect the characteristics of crop production information system and for the small and medium S/W project. To show the applicability in real-world problems, we develop and evaluate a prototype which is based on our proposed methodology for the rice production farmer in mid-Choongnam area.

• The Journal of the Institute of Internet, Broadcasting and Communication
• /
• v.15 no.6
• /
• pp.147-154
• /
• 2015

Recently agile development process became increasing effectiveness, quality, attention to experts in customer satisfaction, as evidenced in this methodology when selecting projects promoting productive efficiency. With regard to contemporary needs and user requirements on the methodology selected to meet this paper is the product based Cross functional team suggested methodology Feature Team model to solve problems of this model, and organizing the Cross functional team, this team but this outcome (product) basis, were examined for the model that points to progress the development across multiple product as a functional unit, value-driven agile project through the Skills-based model and proposed a difference. And it examined the Agile Maturity metrics. PRINCE2 Agile Health-check entries future development direction of Agile techniques is a requirement of the project outset has studied the subject objective evaluation by the assumption that they can be changed at any time, not fixed this way and for the project team through research The proposed.

• Korean Journal of Computational Design and Engineering
• /
• v.9 no.4
• /
• pp.387-396
• /
• 2004

In order to keep and increase a competitive potential, industrial enterprises have to reduce their costs for product development as well as shorten lead time in product development processes. Moreover they have to respond to market factors and conditions such as increasing demands for functionality and individuality of products, short product life cycles, high pressure on prices and time to market. The improved functional requirement in connection with high time and cost pressure lead to high risk in product development. Technological fine improvements in connection with high time and cost pressure lead to high development risk. To cope with these challenges many enterprises have to collaborate globally. The collaborative engineering in product development is aimed to create distributed collaborative corporations and to facilitate the management of design conflicts. This paper provides a methodology for analyzing collaborative design process as well as the tools and the framework to support collaborative product development. The methodology can identify the interdependences among design tasks and teams. The tools and framework are implemented to facilitate the management of product development process.