Skip to Main Content
George Mason University InfoGuides

QUALitative Research & Tools

For those conducting Qualitative research, including resources on methodologies and software.

[Computer Aided] Qualitative Data Analysis Software is known as QDAS or CAQDAS ("Kak-das") is software that assists with the analysis done by Qualitative researchers in the social, health, and behavioral sciences. 

See also the companion website with additional help for each software.

Choosing QDAS Software

Primary Full-Feature Software Packages

  • Atlas.ti - Originally designed for Grounded theory analysis, Atlas.ti excels at memos and other tools for theory building. It also has network tools and a companion online version. Recent versions have greatly improved labeling and added features that were standard for it's competators. 
  • MAXQDA - Although newer than others, MAXQDA takes advantage of this with many colors, emoji's, and on-the-fly filtering. The interface tends to be more cluttered and redundant, but an identical interface across platforms, regular improvements, and free course licenses and read-only access to projects make it an attractive option. 
  • NVivo - A streamlined and familiar interface and support for a variety of data types and organizational structures make NVivo a good all-around choice for any project. But, annotations and memos are less integrated than they should be, and the Mac version has both fewer features and a different file type (hindering collaboration). Those, combined with the increasingly restrictive and expensive licensing, has many looking elsewhere. 

Note the date of these sites, as software changes frequently!

Transferring Projects Between Software

Software Independence

All the major Qualitative software packages have implemented an exchange file format allowing you to transfer your project from one software to another. We highly recommend using a software that supports the project exchange format OR that is open-source. 

  • Project Exchange  -  Allows the entire project to be converted from one software to another. Do NOT expect that that complex projects or those using special features of a software will be transferred as desired. You can expect the transferred project to include all documents and any straightforward coding. 
    • Supported by: ATLAS.ti, Dedoose, Leipzig Corpus Miner, MAXQDA, NVivo, QDA Miner, Quirkos, Transana
  • Codebook Exchange - Allows the codebook to be transferred from one software to another.
    • Supported by: the above plus f4analyse, HyerRESEARCH

Software Coding Tips

Coding Tips
  • Avoid too many codes. Each code (at least ultimately) should be used at least 4-6 times. Don't go over 100 codes without talking to someone, 20-50 is better.
  • Code using overlap. Instead of separate codes for "Positive Economy" "Postive Environment" "Negative Economy" and "Negative Economy", use "Negative", "Positive", "Environment", and "Economy". In this example, it isn't fewer codes, but it scales better and will be easier to compare later.
  • Code entire thoughts. Analysis is done through the retrieval phase where you look at the coded references. If you see just a bunch of single words that will not be helpful. Plus, that will not allow for coding overlap.