2

I dont understand this section in research papers. What is the purpose of this section. Now i am working on a paper. I see some potential limitations and some doubts that my method may or may not work good on some other platforms. Should I put this in my threat to validity section?

  • The following book has a detailed description and systematic guidelines: "Claes Wohlin, Per Runeson, Martin Höst, Magnus C. Ohlsson, Björn Regnell: Experimentation in Software Engineering. Springer 2012" – lighthouse keeper May 23 at 11:53
  • 3
    Please specify the field. E.g. I've never seen such a section. – Massimo Ortolano May 23 at 13:40
  • 1
    Out of curiosity, what is the broad classification? Humanities/ Natural Sciences or equiv. qualitative/ quantitative? I often see validity discussions or "extensions and limitations" paragraphs in my area, but not an explicit "threat to validity" section. – Titus May 23 at 13:51
  • The my field is software engineering. @lighthousekeeper how is is only applicable to CS and SE? – Muhammad Ashfaq May 23 at 18:14
  • 1
    @MuhammadAshfaq The book is written for SE researchers. Many SE papers actually include a reference to the book (and its chapter on Threats to Validity) in the "threats to validity" section. – lighthouse keeper May 23 at 19:39
4

As usual, the true (but not very useful) answer is: it depends. I typically come across that section when the article describes an experiment. Experiments typically involve quite an abstraction from the real world, which is why they can keep so much under control. However, this also means that one could question whether what one found in the abstract environment in the lab also applies to the real world. This is called external validity. This is what is discussed in such a section.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.