How To Use ObjectGeode

 Planning Phase (1 or 2 Lead engineers)

   High Level Requirements Analysis:
   1. Create a System Level Interconnection Diagram (My_World.pr)
       Start with a System Block. Add your highest level block and any other block it will communicate
       with. Connect the blocks with high level channels. Name the channels.
   2. Create a System Level MSC Diagram. 
       Show the actors and signals involved in the primary scenario. 

   High Level Architectual Design:
   1. Declare the signals(without parameters for now) necessary to complete the primary scenario.
   2. Add SignalLists to the channels (signalLists require parenthesis() inside the square brackets).
   3. SDL-88: click on the System in Framework...tools...generate...test process to generate stub FSMs.
   4. Execute on the simulator, debug, and check system behavior against the system level MSC.

Iteration 1 (larger group of engineers)

   Requirements Analysis:
   1. Assign tasks to engineers. Supply each engineer with a copy of the System.pr file.
   2. Each engineer will break their assigned process down into subblocks of Interconnection 
       Diagrams and subchannels for subgroupings of signals from the incoming signalList.
   3. Each engineer will create a detailed MSC Diagram representing their primary scenario.

   Architectural Design:
   1. Each engineer will add signals, parameters, and data types necessary for the primary scenario,
       creating the need to generate new stubs.
   2. The main model may be broken down by copying a block to a new system, selecting the process
       in Framework...tools...generate...test environment. It is then possible to use the process 
       Attributes to write the process to a separate file and load that file into the main model.
   3. Each engineer will execute on the simulator, debug, and check the behavior of their block.
   4. Periodically, each engineer will use the block Attributes to write their assigned block 
       into a separate file (Actor_BLK.pr). Place in PCMS.
   5. Periodically, each engineer will use the DCL Attributes to write their data declarations 
       into a separate file (Actor_DCL.pr). Place in PCMS.
   6. Changes to higher level data declarations, signalLists, and channels should be reviewed by
       all affected engineers and included in the Integration Model.
   7. Periodically, Integ will build an Integration Model (one .pr file built from the files in PCMS), 
       debug, and simulate based on the available MSCs.
   8. Periodically, each engineer will copy the Integ Model file and substitute their local block
       for the one in the Integ Model by setting the block attributes.

   Detailed Design:
   1. Each engineer will add functionality to their local FSMs and create skeleton ADTs.
   2. Changes to higher level data declarations, signalLists, and channels should be reviewed by
       all affected engineers and included in the Integration Model.
   3. Periodically, Integ will build an Integration Model (one .pr file built from the files in PCMS), 
       debug, and simulate based on the available MSCs.
   4. Periodically, each engineer will copy the Integ Model file and substitute their local block
       for the one in the Integ Model by setting the block attributes.
   5. Each engineer will execute on the simulator, debug, and check the behavior of their block.
   6. Periodically, each engineer will use the Process Attributes to write their Process
       into a separate file (Actor_FSM.pr). Place in PCMS.

   Stub Code Generation:
   1. Create an Integ\Cross\.. set of directories as specified in geodeb_win_dir.lst and gce_win.bat. 
       There are Build, Code, Gen, and Win_Bin subdirectories.
   2. Add 'COMMENT #c_extern'  after each ADT operator. SDL C Code Generator..Build..Generate. 
       u_ADTname_ADT.h file is created.  Strip out the #Ifndef #endif stuff, add a
       #include "u_ADTname_ADT.h" and save it as a new u_ADTname_ADT.c file in the code area.

   Sim Build with Stubs:
   1. Modify GEODESM_UBLD.BAT file to add .c files (header files of #c_extern routines are 
       generated automatically during the Sim Build).  GEODESM_UBLD.BAT compiles the code 
       and builds the link file(.lub). It is called during the Sim Build process.

   Debugging Code:
   1. Start up the Simulator Tool.
   2. Start up Visual C++ and select Build..Start Debug..Attach to Process. Select process.
   3. Open the code to be debugged and insert breakpoints. Startup from the simulator.

   Cross Build:
   1. The Build subdir in the Integ\Cross\.. area holds the makefile (.umk).
   2. Add all necessary filenames to the makefile. Keep the same order in each section.
   3. If stub FSM still exists in the model, run add_gt.pl script on the single Integration .pr file to
       fix any unresolved external references caused by the GT_ operators in the stub code.
   4. Clear the Gen, Win_Bin subdirectories, Tools..SDL C Code Generator..Build..Build.
   5. When successful, the Win_Bin subdir will contain target .obj files and an executable.

   Test Generation:
   1. Each engineer will generate detailed MSCs from saved simulation scenarios.
   2. System Test will generate system level MSCs from system-wide simulation scenarios.
   3. Final versions of these MSCs are placed in PCMS.

  Iteration 2:
   Just like Iteration 1. Add processes, connections, and signals to be used in Alternate Scenarios.
   Fix mistakes found late in Iteration 1.

 Iteration 3:
   Just like Iteration 1. Add processes, connections and signals to be used in Exception Scenarios.
   Fix mistakes found late in Iteration 2.