• Proceedings of the Korea Information Processing Society Conference
• /
• 2008.11a
• /
• pp.546-549
• /
• 2008

최근 모바일·임베디드 시스템의 품질 향상 노력의 일환으로 하드웨어보다 소프트웨어 개발에 더 관심을 가지며 비중 또한 증가하고 있다. 모바일·임베디드 소프트웨어는 특정 목적을 위해 개발되는 특성으로 인하여 표준화된 개발 프로세스 없이 개발되는 경우가 많다. 또는 기업 자체 개발 방법론으로 개발하거나 알려진 임베디드 소프트웨어 개발방법론으로 개발하기도 한다. 하지만 잦은 요구사항 변경과 시스템의 결함 등 프로젝트의 실패는 줄어들지 않고, 이에 대한 해결책으로 본 논문에서는 모바일·임베디드 개발 프로세스의 개선으로 품질향상이 필요하다고 주장한다. 소프트웨어 프로세스에 있어서 대기업에서는 CMMI 수준 달성을 위한 노력을 꾀하고 있다. 하지만 이 모델은 일반 중소규모 기업에 적용하기에는 부담이 너무 크다는 단점이 있고 비용 또한 만만치 않다. 이에 본 논문에서는 XP의 실천사항을 바탕으로 모바일 임베디드 소프트웨어 개발 프로세스 개선을 위한 프레임워크를 제안한다. 이를 통해 모바일·임베디드 소프트웨어 개발 기업은 제품 품질 향상과 함께 CMMI 수준 달성에 기여·활용하게 된다.

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

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

• Proceedings of the Korea Information Processing Society Conference
• /
• 2008.11a
• /
• pp.814-817
• /
• 2008

최근 임베디드 소프트웨어가 다양한 분야에서의 개발이 증대되면서 요구사항도 변화되고 있다. 즉, 임베디드 시스템이 단순하고 독립적인 소형시스템에 정착되어 운영되었던 과거와는 달리 최근에는 초정밀의 동작제어와 함께 복잡하고 다양한 플랫폼 환경을 요구하거나 다수의 소프트웨어 통합하고 제어하는 시스템 중속적인 요구사항들이 많이 발생하고 있다. 기존의 개발방법들은 하드웨어와의 밀접한 관계, 여러 유사 도메인에 대한 고수준의 재사용성 요구 등 임베디드 소프트웨어가 갖고 있는 특성들을 효과적이로 반영하지 못하고 있다. 본 연구에서는 개발 프로세스 혁신하고 오류를 최소화하기 위해서는 "계획 ⇒ 설계 ⇒ 구현 ⇒ 테스팅" 단계와 같은 임베디드 소프트웨어 개발 프로세스를 정립하고 각 단계에서 필요한 최적의 품질관리 체계를 구축함으로써 경쟁력 있는 임베디드 소프트웨어 제품의 개발을 지원할 수 있는 방법론을 확립하였다.

• Journal of the Korea Society of Computer and Information
• /
• v.13 no.6
• /
• pp.95-105
• /
• 2008

Recently use of embedded software has been increased to different areas. The requirements and demands for the embedded software have also been altered. In the past, the embedded system was used in simple task and small portable devices but now, the usage of the embedded software has expanded to do much more complex and precise actions in a variety platform environment. The embedded software enables multiple softwares to be integrated into one and at the same time, control it. Currently the biggest challenges embedded software is facing during its development process is the improvement in product production and quality assurance. Our research team has developed an embedded software based on the component (technology or methodology) which both improves production capabilities as well as quality. Additionally, we also established and constructed a reliability test system which can effectively test the quality of the developed embedded software to further increase its competiveness.

• Journal of KIISE:Software and Applications
• /
• v.33 no.11
• /
• pp.915-922
• /
• 2006

Recently, the requirements of the embedded software are getting diverse as the diversity of embedded software application fields increases. The systematic development methods are issued to deal with the dependency between hardware and software. However, the existing development methods have not considered the software's close connection to hardware and the high-level reusability for common requirements of several similar domains. In this paper, we propose a design method of development process model of product lines to support an efficient development method for embedded software. For this, we firstly suggest a domain scoping method and an IDEF0(Integration DEFinition)-based business model for extracting the efficient requirements. Next, we present a component deriving method based on the service architecture and an architecture design method after considering the hardware dependency. And we explain the artifacts of MSDFS(Multi Sensor Data Fusion System) at each design step in order to show how the proposed model can be applied to the embedded software development.

• Journal of the Korea Society of Computer and Information
• /
• v.14 no.10
• /
• pp.271-281
• /
• 2009

In this paper, we propose the enhanced Assessment Model of the Embedded Software Process(MND-ESPAM) which is suitable for the development work of weapons in Korea. In 2008. We developed the MND-ESPAM which is the assessment criteria of software process, but this model is inefficient to apply to Korean military area. Therefore, we elicit and analyze the problems of MND-ESPAM through tow methods. One is to research on the actual condition of the domestic defense industry about software process management. And the other is to apply MND-ESPAM to the defense companies acquiring CMMI level. In order to overcome these problems elicited above, we provide solutions to make MND-ESPAM linked with Software Development Process Guide of Defense Acquisition Program Administration(DAPA) and to systematically strengthen testing activities and to reduce the number of process areas. The proposed model was proved by two objective methods such as checking the coverage with CMMI and whether it is satisfied or not by modified requirements ISO/IEC 14598-3. At last, experts in the field of software process confirmed the effect of MND-ESPAM through applying MND-ESPAM to the defense industry company.

• Journal of Internet Computing and Services
• /
• v.9 no.5
• /
• pp.59-72
• /
• 2008

Computing systems in the modern era are expanding rapidly to include mobile-based businesses that make us of the various convergence distributed business process. This has lead to growing interest in the field of mobile embedded software development methodology, which has in turn lead to the proliferation of the embedded mobility. The use of CBD (Component Based Development) provides reusability, maintainability and portability, all of which are very important and focus issues to the business process. It also comes with the inherent productivity, quality and reliability of CBD. To make efficient use of CBD, though, clarified interface definitions for component integration are necessary. These definitions should be made up of collaborative hierarchical and horizontal architecture layers. Successful definitions should apply an effective framework made up of the architecture and process. In this paper, we describe an interface specification for small grained mobile embedded components(MEC) for the mobile embedded domain to meet maximum user requirements. We build and deploy the reconfigurable design patterns and components (in business domain categories) to make a component hierarchy and business logics for mobile embedded software. Proposed components specification plays a major role in development of the software for handling inconsistency in existing specification. It also includes plenty of specification information, using semantics and modeling based mechanisms to support business processes. We propose a development model of mobile embedded software using CBD for very complex and dynamic mobile business. We can apply it in a plug and play manner to develop the software. We verify that our framework supports very good productivity, quality and maintainability to meet the user's requirements in mobile business.

• The Korean Journal of Applied Statistics
• /
• v.28 no.6
• /
• pp.1257-1273
• /
• 2015

The development process of Embedded Software (SW) is gathering interest due to the increased importance of SW in mobile products. According to tough competition and the growing size of the Embedded SW, there is a demand for a new effective way to improve the SW development process, based on customer and market quality aspects, rather than focusing on defect removals in individual SW modules. We review 103 SW improvement projects from the area of mobile phones in order to check the effectiveness of Six Sigma which is the standard for the process improvement statistical tools and methods.

• Journal of Convergence Society for SMB
• /
• v.1 no.1
• /
• pp.55-65
• /
• 2011

Due to the rapid advance of IT technologies such as mobile communication, sensor network, wearable computer, and so on, the needs of embedded software has increased. In those domain areas, the development of low-power embedded software is one of critical issues to enhance servicability of the system because almost embedded system depends on battery-based power supply system. Therefore this paper identifies the factors that can reduce the power consumption in embedded software operation, and proposes the method that how to handle the factors in software development process. Even though the existing and general studies about power reduction has been performed with code-based analysis, this analysis approach can lead reworks when the requirement for power consumption was not met. Our proposed techniques will support the power reduction in embedded software development process whenever the code was not developed. Our proposed process for lop-power embedded software development can gives the high quality in power-related serviceability.

• Journal of the military operations research society of Korea
• /
• v.33 no.2
• /
• pp.49-60
• /
• 2007

Recently, the application area of an embedded software become larger and larger rapidly due to the development of the wire and wireless communication, the expansion of the digital information device and the convergence of the digital devices and emphasize the effort of the development of more complete software. As a consequence, the importance of the software test process was raised to discover the defects of the software early and improve the quality of an embedded software. However there was no test process model for applying the embedded software which is required the highly precision and the real-time process. In this paper, therefore, we propose the design procedure and case study for the test maturity model of an embedded software(Emb-TMM) which reflects the characteristics of the embedded software and test process. for this, we suggest the three category of the proposed procedure which consists of the selection of the reference model and the derivation of the area, the categorization of the area level, and design model. Then we suggest the case study how the proposed procedure can be applied to the development of an embedded software actually.