• The Transactions of the Korea Information Processing Society
• /
• v.7 no.7
• /
• pp.2135-2148
• /
• 2000

Developing network software in embedded systems, such as digital set-top boxes, requires coding under limited computing resources. This paper presents the porting of Point-to-point Protocol (PPP) software, PPPD, to an embedded system. The PPP is the most popular link layer protocol for the information appliance, to an embedded system. In order to achieve this, problems to be solved for the porting were identified and methods to solve the problems were described. First, PPP source codes were divided into modules. Next, functions of each module were analyzed and interfaces between the modules were delineated. With the analysis results, porting to the embedded system was described. The normal operation of the ported software was verified with the help of a network packet analyzer. Finally, experiences during the porting were presented. The method developed in th paper can be applied to the porting of software to an embedded system as well as the porting of network software.

• 한국IT서비스학회:학술대회논문집
• /
• 2006.11a
• /
• pp.190-193
• /
• 2006

Ther are many stages of the development for the embedded systems' hardware and software as well, which results in many test stages of it with respect to corresponding development stages. The software validation of embedded systems is taken into consideration for the testers to make sure that the systems work correctly after the deployment. Among test stages, especially control logic level testing and system validation testing are considered as the most important test, because the robustness of embedded systems' software can be validated by those two level of tests. in this paper, we would like to introduce the idea of how software test system for embedded systems can be established and of what necessary components are needed

• IEMEK Journal of Embedded Systems and Applications
• /
• v.5 no.1
• /
• pp.29-38
• /
• 2010

It is highly requested that the more complicated embedded software is used for high performance and multiple functions of the systems. This is inevitably increasing the errors. Therefore the embedded software testing is getting important recently. There are not general testing methods which are able to be applied for any embedded systems, but via this research, we introduce a testing method which is based on TTCN-3, a testing standard, for embedded systems. A testing environment for network-based embedded software is implemented with considering the features of TTCN-3 testing which is based on message exchange. The testing environment has two additional parts with TTCN-3 test system, the network analyzer to access the network-based systems and the communication interface which is suggested for embedded systems in previous work, and we have implemented the whole testing environment with interacting these two parts. In addition to the normal testing domain, called single node testing as a unit testing of V-model, we suggest another concept to test multiple nodes in network. It could be achieved by adding keywords such as supervisor and object which are describing the feature of TTCN-3 testing component and generating the TTCN-3 Executable code which contains new keywords. The testing has done for embedded software which is based on CAN network and the demonstration of the testing environment has been shown in this paper.

• Journal of Information Processing Systems
• /
• v.2 no.3 s.4
• /
• pp.137-142
• /
• 2006

A large portion of the embedded system development process involves the integration of hardware and software. Unfortunately, communication across the hardware/software boundary is tedious and error-prone to create. This paper presents an automatic hardware/software interface generation system. As the front-end of hardware/software co-design frameworks, a system designer defines XML specifications for hardware functions. Our system generates hardware/software interfaces including Device Driver, Driver API, and Device Controller from these specifications. Embedded software designers can easily use hardware just like system libraries. Our system reduces the mistakes and errors that can be occurred when a software programmer directly connects software to hardware, and supports balancing labors between hardware developers and software programmers. Moreover, this system can be used as the back-end for a hardware/software co-design framework.

• 한국IT서비스학회:학술대회논문집
• /
• 2003.11a
• /
• pp.713-721
• /
• 2003

The time to market and productivity of embedded system needs a quality measurement process management of embedded software. But, defect management without preemptive analysis or prediction is not useful for quality measurement process management. This subject is focused on the defect that is one of the most important attributes of software measure in the process. Defining of defect attribute and quality measurement process management is according to understanding of embedded sw characteristics and defect data. So, this study contributes to propose the good method of the quantitative based on defect management in the test phase of sw lifecycle.

• Journal of KIISE:Software and Applications
• /
• v.37 no.4
• /
• pp.252-263
• /
• 2010

The needs of low-power embedded software are being increased. Along with the needs, the studies to predict the power consumption of embedded software are also being increased. Although existing studies for power analysis have been performed in source code-based, these code-based analysis have some shortages of long analysis time and much feedback efforts. Recently some studies of power analysis based on software models are prompted. This paper describes on the model-based approach using UML diagrams in embedded software development process. Specially we focus on the extension of OMG's MARTE Profile to support model-based analysis. The MARTE extension gives the possibility of power analysis using just UML diagrams without any other analysis model in embedded software development.

• Transactions of the Korean Society of Automotive Engineers
• /
• v.19 no.4
• /
• pp.1-7
• /
• 2011

Various convenient systems which are telecommunication and navigation system and safety system which include Antilock Braking System, Electronic Stability Control, Adaptive Cruise Control have been developed and applied to meet customer needs and each standards since vehicles are used. The complexity of new electronics become significant reason of breakdown especially embedded software failures. Hardware reliability is almost stabilized with long history but software reliability needs more improvements through reliability researches. This new challenge will improve software reliability to clear its overall failures in vehicles. This paper introduces some software reliability models and evaluates embedded software reliability using failure data which occurred during operating.

• 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 KIISE:Software and Applications
• /
• v.36 no.8
• /
• pp.607-615
• /
• 2009

There has recently been a trend that IT industry is united with traditional industries such as military, aviation, automobile, and medical industry. Therefore, embedded software which controls hardware of the system should guarantee the high reliability, availability, and maintainability. To guarantee these properties, there are many attempts to develop the embedded software based on COTS (Commercial Off The Shelf) hardware components. However, it can cause additional faults due to software/hardware interactions beside general software faults in this methodology. We called the faults, Linkage Fault. These faults have high severity that makes overall system shutdown although their occurrence frequency is extremely low. In this paper, we propose a new software reliability model which considers those linkage faults in embedded software development with COTS hardware components. We use the Bayesian Analysis and Markov Chain Monte-Cairo method to validate the model. In addition, we analyze real linkage fault data to support the results of the theoretical model.

• Journal of the Korea Society of Computer and Information
• /
• v.16 no.12
• /
• pp.1-10
• /
• 2011

As requirements of embedded system get complicated, the tool for analyzing the reliability of embedded software is being needed. A probabilistic modeling is used as the way of analyzing the reliability of a software and to apply it to embedded software controlling multiple devices. So, it is necessary to specialize that to embedded software. Also, existing reliability analyzers should measure the transition probability of each condition in different ways and doesn't consider reusing the model once used. In this paper, we suggest a reliability analyzer for embedded software using embedded software Markov chin model and a unit testing tool. Embedded software Markov chain model is model specializing Markov chain model which is used for analyzing reliability to an embedded software. And a unit testing tool has host-target structure which is appropriate to development environment of embedded software. This tool can analyze the reliability more easily than existing tool by automatically measuring the transition probability between units for analyzing reliability from the result of unit testing. It can also directly apply the test result updated by unit testing tool by representing software model as a XML oriented document and has the advantage that many developers can access easily using the web oriented interface and SVN store. In this paper, we show reliability analyzing of a example by so doing show usefulness of reliability analyzer.