XI Workshop de Testes e TolerÃ¢ncia a Falhas (WTF) - SBRC 2010

More documents

Recommendations

Info

126 Anais invalid inputs caused by hardware faults. However, hardware faults are not addressed by the PUS standard. As a consequence, only classes (i) to (iii) could be modeled. In the case of the telecommand verification service, each class is modeled by one finite state machine. The first model represents the normal behavior of this service and it is shown in Fig. 5. Four states represent the current stage of the service depending on the event associated to the transition. The events “TC_Arrival” and “TC_OK” are events from the embedded software, and thus, the person who is applying the test cases cannot observe their occurrences. The responses of the system are within the telemetry packets. They contain the reports mentioned in section 4.2. The responses “RepSucAcc” (Success Report of Telecommand Acception) and “RepSucCompExec” (Success Report of Telecommand Completion of Execution) are only sent if their respective bits, „3‟ and „0‟ in the telecommand “Ack” field, are set to „1‟. Otherwise, they are not sent. The “Ack” field of the telecommand is represented by the four bits “0123” inside the brackets in the events “Acc_OK[0123]” and “CompExec[0123]”. Telecommand Verification Service – Normal Behavior Model Without TC TC_Arrival / - Checking TC CompExec_OK[0---] / - TC_OK / Send_TC_to_Process CompExec_OK[1---] / RepSucCompExec Waiting for Acceptance Acc_OK [---0] / - Acc_OK [---1] / RepSucAcc Waiting for TC Execution Conclusion Figure 5. Telecommand Verification Normal Behavior model.
XI Workshop de Testes e Tolerância a Falhas 127 As a second example, the model developed for the Specified Exceptions Behavior is presented in Fig. 6. This class encompasses the events that the standard has defined for specified types of failure or abnormal functioning of the system. In this case, the PUS defines six failures that may occur in the acceptance stage and their respective codes. For other stages, the errors are mission-specific. The codes “X1” and “X2” in Fig.6 show that these errors are not in the standard. Also, it is important to note that the “Ack” bits are represented by this configuration “[----]”. It means that the corresponding failure report must be sent regardless the value of these bits. Telecommand Verification Service – Specified Exceptions Behavior Model Without TC CompExec_NOK[----] / RepFalCompExec(Code=X2) Acc_NOK [----] / RepFalAcc(Code=X1) APID_NOK[----] / RepFalAcc(Code=0) TC_Arrival / - Checking TC TC_OK / Send_TC_to_Process Length_NOK[----] / RepFalAcc(Code=1) CkSum_NOK[----] / RepFalAcc(Code=2) Tipo_NOK[----] / RepFalAcc(Code=3) Subtipo_NOK[----] / RepFalAcc(Code=4) DApp_NOK[----] / RepFalAcc(Code=5) Waiting for Acceptance Acc_OK [---0] / - Waiting for TC Execution Conclusion Figure 6. Telecommand Verification Specified Exceptions Behavior model.
Page 1 and 2:
XXVIII Simpósio Brasileiro de Rede
Page 3 and 4:
XI Workshop de Testes e Tolerância
Page 5 and 6:
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13:
Page 16 and 17:
4 Anais tais problemas. Portanto, h
Page 18 and 19:
6 Anais consenso para o modelo ass
Page 20 and 21:
8 Anais em andamento (por exemplo,
Page 22 and 23:
10 Anais cada partição síncrona,
Page 24 and 25:
12 Anais A tarefa T 4 é executada
Page 26 and 27:
14 Anais • Assumimos que o proces
Page 28 and 29:
16 Anais Veríssimo, P. and Casimir
Page 30 and 31:
18 Anais Entretanto, em caso de fal
Page 32 and 33:
20 Anais à aplicação: SafeSendT
Page 34 and 35:
22 Anais Na fase de inicialização
Page 36 and 37:
24 Anais acesso a C e nem a C d . E
Page 38 and 39:
26 Anais Prova. 1. Se t + 1 /∈ C
Page 40 and 41:
28 Anais algoritmo de término. Vá
Page 42 and 43:
30 Anais instantânea. Além disso,
Page 44 and 45:
32 Anais [Chandra and Toueg 1996].
Page 46 and 47:
34 Anais Every JXTA-FD instance exe
Page 48 and 49:
36 Anais 3.4. GossipTask A rotina G
Page 50 and 51:
38 Anais mecanismo foi adotado para
Page 52 and 53:
40 Anais Tempo de Detecção e Recu
Page 54 and 55:
42 Anais nout em relação à exati
Page 56 and 57:
44 Anais Fischer, M. J., Lynch, N.
Page 58 and 59:
46 Anais 1. Introdução Sistemas d
Page 60 and 61:
48 Anais canais de comunicação co
Page 62 and 63:
50 Anais Figura 1. Interface do QoS
Page 64 and 65:
52 Anais onde as aplicações solic
Page 66 and 67:
54 Anais • QOSP _REGIST ER: Esta
Page 68 and 69:
56 Anais O DSCP utilizado para o Se
Page 70 and 71:
58 Anais seu destino, enquanto que
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88: XI Workshop de Testes e Tolerância
Page 101: XI Workshop de Testes e Tolerância
Page 104 and 105: 92 Anais geralmente baseados nos gr
Page 106 and 107: 94 Anais Os parâmetros podem repre
Page 108 and 109: 96 Anais Um exemplo de configuraç
Page 110 and 111: 98 Anais E. Evolução O Módulo Ev
Page 112 and 113: 100 Anais Tabela 1: Cobertura obtid
Page 114 and 115: 102 Anais ineditismo, o que parece
Page 116 and 117: 104 Anais Evaluation of Novel Appro
Page 118 and 119: 106 Anais protocolo; (2) verificaç
Page 120 and 121: 108 Anais Uma MEF pode ser represen
Page 122 and 123: 110 Anais se dá em uma seqüência
Page 124 and 125: 112 Anais 1 2 3 4 5 Data: MEF M e C
Page 126 and 127: 114 Anais (a) Variação do número
Page 128 and 129: 116 Anais Fujiwara, S., Bochman, G.
Page 189:
show all

XI Workshop de Testes e TolerÃ¢ncia a Falhas (WTF) - SBRC 2010

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

Delete template?

Save as template?