You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generate a report/test procedure for the user to fill out that checks that key assumptions and conventions are properly implemented. Relevant from a systems engineering standpoint for software verification.
Relevant areas to check:
Event Spawning
Initialization
Documentation
Timer Periods
Example Process concerning event spawning:
Generate Code
Spawn event requires pragma to say whether it has been checked or not
Compilation creates report of all areas that have no been checked
Report contains task list and steps for code verification
Example task list for event spawning:
When should this event be spawned while in this state?
Do the current conditionals for event spawning in this state properly meet the intended criterion for event spawning?
Are there any child states that will change how this event is spawned or handled?
If so, will this event still be spawned and handled properly?
The text was updated successfully, but these errors were encountered:
Should generate matrix of all states and all events showing which events are not handled in which states. Should include form for signing off that this is indeed correct behavior.
Perhaps we can do this from within the modeling environment as a separate viz and store the signoff in the model?
Generate a report/test procedure for the user to fill out that checks that key assumptions and conventions are properly implemented. Relevant from a systems engineering standpoint for software verification.
Relevant areas to check:
Example Process concerning event spawning:
Example task list for event spawning:
The text was updated successfully, but these errors were encountered: