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.2 Uploading and Downloading Data Packets

Once an uplink/downlink site-SCS connection has been made between two customer satellite data communication sites, the uplink site may upload data packets to the SCS and the SCS may forward the uploaded packets to the downlink site. Without such a connection, packet uploading and downloading is not possible.

An uplink/downlink site-SCS connection has been established when:

(1) the SCS as received a TG (Customer time slot go) from the GCS;

(2) the SCS has forwarded the TG (Customer time slot go) messages to the uplink and downlink sites; and

(3) both the uplink and downlink sites have sent the SCS ready messages, i.e., the uplink site has sent the SCS an UG (uplink good) acknowledgment message and the downlink site has sent the SCS a DG (downlink good) acknowledgment message.

DI1) A DI (data packet) shall contain the following data:

(1) the uplink site ID, i.e., uplink_ID;

(2) the downlink site ID, i.e., downlink_ID;

(3) packet ID, i.e., packet_ID; and

(4) packet data.

DI2) The SCS shall receive each DI (data packet in) received from the uplink site if a connection was successfully established between the uplink and downlink sites and the SCS.

The following conditions describe a successful uplink/downlink site-SCS connection:

(1) the uplink and downlink sites both sent UG and DG acknowledgment messages, respectively, to the SCS;

(2) neither the uplink or downlink site has recently sent a UB or DB message; and

(3) the GCS has not sent a TE (time slot expired) message to the SCS to terminate the current customer data transmission time slot.

DI3) The SCS shall forward each DI (data packet in) received from the uplink site to the downlink site.

DI4) A DI may be received only during a valid "Transmit Data" transaction.

The corresponding Requirement Behavior Tree is as below: