Behavior Engineering Based Software Change Case Studies



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.1 Initialize SCS (version 3)


Before the SCS can be used, it must be initialized by sending it an IN (initialize SCS) command message.

IN1) The SCS shall receive and execute an IN (initialize SCS) command message from the Ground Control System (GCS). When this message is received, the SCS will be initialized.

Note: This message will be sent either to periodically initialize the SCS or to respond to system errors.

IN2) The SCS shall prepare and send to the GCS, an INA (SCS initialized) acknowledgment message that the system has been initialized.

IN3) When SCS is due to periodic restart, it will wait until all current transmittion are finished until restart.

The corresponding Requirement Behavior Tree is as below: