Skip to content

User study design #17

Description

@mechtaev

Tentative question formulation:

Question 1:

Are these requirements ambiguous, i.e. leave room for multiple reasonable interpretations or contain contradictions, when considering the intended functionality? In your evaluation, consider how the program is expected to handle edge cases like extreme values. Exclude considerations related to handling invalid inputs or addressing aspects unrelated to functionality, such as performance.

{TEXT}

{TYPED FUNCTION SIGNATURE}

Possible answers:

  1. Yes, they are ambiguous
  2. No, they are not ambiguous
  3. Cannot judge

Question 2 (if the answer is affirmative):

Are these examples fully clarify the ambiguity?

{IO EXAMPLES}

Activity

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

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions