27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

dataflow and data de pendency relationship betwee n<br />

components are represented with an arrow and a dotted<br />

arrow respectively. Fig. 1 depicts the dataflow between<br />

components for part of the Environment Modeling and<br />

Perception (EMP) in the Unmanned Ground Vehicle (UGV)<br />

application [Roh11]. The L aser Range Finder (LRF ) and<br />

Camera components generate LRF data array and 24 bits raw<br />

RGB respectively. The Car Detection component produc es<br />

other cars trajectory by analysing the data that com es from<br />

the LRF and Camera components. Using the data from the<br />

Car Detection com ponent, the Dangerous Situation<br />

component determines wheather it should generate an alarm<br />

to prevent critical accidents.<br />

Laser Range<br />

Finder (LRF)<br />

LRF data array<br />

have a minor impact from a com ponent failure. The Car<br />

Detection component (Fig. 2) is supported by two Camera<br />

components, each impact level of whic h is de fined as<br />

tolerable. Even though one of two Camera components fails<br />

to capture other cars pictures, the Car Detection component<br />

can make other cars trajectory using the remaining Camera<br />

component.<br />

Laser Range<br />

Finder (LRF)<br />

Camera 1<br />

insignificant<br />

tolerable<br />

Car Detection<br />

serious<br />

Dangerous<br />

Situation<br />

Camera1<br />

Camera2<br />

24 bits raw<br />

RGB<br />

24 bits raw<br />

RGB<br />

Car Detection<br />

List of car trajectory<br />

Dangerous<br />

Situation<br />

Fig. 1 Dataflow between Components for Environment<br />

Modeling and Perception in UGV application<br />

The impact of a component failure to another component<br />

is analyzed using the data dependency relationship between<br />

components. The impact is defined depending on how much<br />

a component is affected from other co mponent failure, and<br />

the impact level is determined by considering the importance<br />

of received data. The impact level of a component failure to<br />

its dependent components is categorized as insignificant,<br />

tolerable, serious, and catastr ophic. An insignificant im pact<br />

level describes a data depe ndency in which a com ponent<br />

uses an extra data from another component to verify or<br />

increase the reliability of co mponent output additionally. A<br />

component can provide its full functionality required without<br />

any problem even though there is no extra data from a fai led<br />

component. The impact is represented with an impact level<br />

on the data dependency relationship between components.<br />

Fig. 2 depicts the data dependency relationships between<br />

components for the Environment Modeling and Perception<br />

(EMP), which are defined based on the dataflow in Fig. 1.<br />

The LRF co mponent is in significant for the Car Detection<br />

component (Fig. 2), which receives data from the LRF and<br />

two Camera components to trace other cars trajectory. Even<br />

though the LRF component fails, the Car Detection<br />

component can still produce other cars trajectory using only<br />

the data generated from the Camera components. The LRF<br />

component is added to the EMP as an extra component so<br />

that the Car Detection com ponent can produce high quality<br />

of other cars trajectory.<br />

Failures of a component, which is t olerable to its<br />

dependency component, do not disrupt the normal function<br />

of its dependent component. The dependent component may<br />

Camera 2<br />

tolerable<br />

Fig. 2 Data Dependency Relationship between Components<br />

for Environment Modeling and Perception in UGV<br />

application<br />

A component failure that makes serious impact to its<br />

dependents component causes the dependent to st op<br />

processing data. This is because the dependent component<br />

cannot generate a reliable output any more without the data<br />

from the failed com ponent. Stopping the de pendent<br />

components could give a ripple effect to the next dependent<br />

components so that it can pa ralyze part of an application.<br />

But, stopping the dependent components does not lead the<br />

application to a total failure. The application can provi de<br />

still partial services using the remaining components, which<br />

may not have critical impact from the stopped com ponents.<br />

The data generated by the Car Detection c omponent is<br />

critical to the Dangerous Sit uation component in Fig. 2, so<br />

the impact of Car Detection component to the Dangerous<br />

Situation component is defi ned as seriou s. When the Car<br />

Detection component fails, the Da ngerous Situation<br />

component should stop processing the data. This is because<br />

the Dangerous Situation c omponent cannot generate the<br />

reliable output without t he data from the Car Detection<br />

component.<br />

Catastrophic impact is used to describe a sit uation where<br />

a component failure needs to stop all components<br />

constituting an application. An application may encounter a<br />

critical accident if all the com ponents do not stop<br />

immediately. Catastrophic i mpact may be associated wi th<br />

safety of robots. The Virtual Robot component in the UGV<br />

application controls real devices such as engine and steering<br />

wheel. A failure of Virtual Robot component may cause the<br />

UGV to encounter an accident, which could lead to l ose<br />

human life.<br />

Some kind of data dependency relationships bet ween<br />

components, which have the same impact level, can have a<br />

cardinality constraint that describes a m inimum number of<br />

685

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!