Background

. Behavior Engineering

. Software Change

. Software Tools

. Microwave Oven Case Study

. Satellite Control System

Mircowave Oven Case Study

Version 1

. Requirements and RBT

. The DBT

. Other Design Diagrams

Version 2 and 3

. Version 2

. Version 3

Evolutionary Diagrams

. EVDBT for version 1,2 and 3

. Other Evolutionary Diagrams

Satellite Control System

Requirements and RBTs

. Requirement 2.1

. Requirement 2.2

. Requirement 2.2.1

. Requirement 2.2.2

. Requirement 2.2.3

. Requirement 2.3

. Requirement 2.3.1

. Requirement 2.3.2

. Requirement 2.3.3

. Requirement 2.3.4

. Requirement 2.3.5

. Design Behavior Tree

Other Versions

. Version 2 Requirement 2.2.3

. DBT for Version 2

. Version 3 Requirement 2.1

. DBT for Version 3

. Version 4 Requirement 2.2.2

. DBT for Version 4

. Version 5 Requirement 2.3.4

. DBT for Version 5

. The Evolutionary DBT

2.3.4 Completing a "Transmit Data" Transaction

After an uplink/downlink site-SCS connection has been established, after all planned data packets have been uploaded to the SCS and forwarded, and after all bad packets sent have been replaced, the uplink site may end the "Transmit Data" transaction by sending the SCS a TC (transmission completed) acknowledgment message.

TC1) After the uplink site has completed its data transmission, the SCS shall receive a TC (transmission completed) acknowledgment message from the uplink site.

TC2) Upon receipt of a TC command message, the SCS shall forward it to the GCS.

TC3) A TC command message may be received only during a valid "Transmit Data" transaction.

TC4) Before a TC command has been sent from SCS, SCS will remove the uplink ID from its B/L table

If each PB message uploaded to the SCS was not canceled by a replacement data packet, the SCS shall ignore the TC command message received from the uplink site because one or more bad packets must still be replaced.

The corresponding Requirement Behavior Tree is as below: