Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

States of SUT interface #931

Open
pjljvandelaar opened this issue Aug 27, 2019 · 0 comments
Open

States of SUT interface #931

pjljvandelaar opened this issue Aug 27, 2019 · 0 comments

Comments

@pjljvandelaar
Copy link
Member

Would the following interface of set of possible states of SUT result in a performance gain?

  • inputMenu
    contains only input channels [and hidden channels for internal processes]
  • inputTaken
    move to next set of possible states given that the input is provided to the SUT
    Note this function should only be called when the input is offered and accepted by SUT
    and no output occurred before input was delivered to SUT via mapper / adapter
  • observedOutput :: Maybe Mismatch
    move to next set of possible states given the observed output
    of course, report mismatch when output is no in agreement with model
    of course, observed Output can be Quiescence (no output at all observed)

By restricting the menu to input (and hidden channels) only, TorXakis has less to calculate and outputs are never offered anyway!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant