Download Next Generation Command and Control Wind Tunnel for Courses of

C2WInteractionRoot must derive from InteractionRoot.
The interaction hierarchy must be rooted – no more than 1 root nodes should be found.
There should not be a cycle in any of the COAs (all COAs should be DAGs).
Make sure that the time specified for a synchronization point is positive.
Make sure that FlowID of any branch doesn’t contain any whitespace characters.
The "branchesFinishedCondition" must include space (or newline) separated flow-IDs of
only those connections that are the SyncPoint node's incoming connections.
COASequencesGroup models must contain at least one reference to a COA.
A COA must be referred in maximum one COASequenceGroup in an experiment model.
Make sure no COA reference in a COASequenceGroup is null.
If deployment scripts are to be generated, a project must have at least one network model
with at least one computer model in it.
H.2.3 Execution time error-handling
Check if mappings have been correctly specified (provided detailed comments in the
generated code so that users can tie compilation errors to invalid mappings in the model).
Check if the expression of OutcomeFilter nodes are valid (provide detailed comments in
the generated code so that users can tie compilation errors to invalid OutcomeFilter
expressions in the model.
Normalize the probabilities on ProbabilisticChoice branches to 1.0.
H.3 ERROR-HANDLING FOR INVALID EXECUTION/EXPERIMENTATION
SETUP
Not-only do these user errors need to be detected, but an appropriate error dialog should be
generated that points the user as close as possible to the actual error location in the model. If the
experiment is run in the batch mode (non-GUI), then an appropriate error message should be
recorded in the federation manager’s log file.
H.3.1 Initialization time error-handling (before simulation is launched)
Test if IP address and credentials are correct before launching.
Test if any federation is already running before launching.
Check if Java3D is installed.
Check if C++ and OMNeT++ federate executable exist.
Check if the required Java classes can be loaded using the classpath set in the shell scripts.
Check if user has generated code ( e.g. whether <federation-name>.fed file exists).
Check if ProcessId project has been built and a shared object has been generated.
Check if Main machine’s IP address is same as in the deployment model.
Make sure no two federates attempt to join the federation simultaneously (problem with
portico).
If the runAll script is used for an experiment, that experiment must specify either an endtime or the terminate-on-coa-finish flag.
Make sure there are no compilation errors in byte-code of the compiled federation and
generic C2WT Java classes.
108