Thread with BA and call sequence

[jjhugues]

For the moment, the following is valid

    thread implementation Mission.impl
        calls
            C: {
                S: subprogram Mission_Compute;
            };
        properties
            Dispatch_Protocol => Periodic;
            Period => 500ms;

    annex behavior_specification {** 
    states 
        flip: initial complete state;
        flop: complete final state;
    transitions
        flip -[on dispatch]-> flop { Mission_Compute! };
        flop -[on dispatch]-> flip { Mission_Compute! };    

    **};

Should we have provisions that states that if a component like a thread has call sequences, compute_entryoint property set, then it cannot have a BA annex clause? How to phrase such limits?

[smithdtyler]

I would prefer a warning to a restriction. In the past I have been bitten by the addition of new restrictions that invalidate previously-valid models. Presumably AADLv3 will simply some of the behavior specifications - I would rather make more aggressive corrections there and not risk breaking existing models.

[jjhugues]

Proposed resolution

• [ ] Document this as a source of potential ambiguity in the model, have the tool report this as an INFO message