On this page you will learn the difference between scholarly and other types of journals, will learn how to read scholarly articles efficiently, and will have the opportunity to practice a bit.
Contents:
Magazines and journals take distinct forms based on their purpose and audience. In the case of scholarly journals and technical/trade journals, they have the same audience -- a particular profession or group of people working in the same discipline. Scholarly journals and technical/trade journals are also alike in that the articles within both are typically written by professionals in the discipline. However, these two types of journals differ in terms of purpose.
Most reading is now done online, and often the articles are found separately --not in the context of the journal or magazine in which the article was published.
If you would like a more detailed explanation, read on...
To read a scholarly article, you will need a basic understanding of how research articles are structured. However, the structure of the article will be affected by the nature of the research being reported. For example, research papers in science typically follow a standard format that includes sections for introduction, literature review, methods, results, and discussion (see annotated map of this type of paper in "Anatomy of a Scholarly Article"). However, the nature and range of research approaches related to information technology produces articles with more variation in structure. For example, a design science research article, reporting on the development and evaluation of an artifact, will have section labels appropriate to that type of research.
While some articles may label the sections differently, the main sections you will often find within a research article include:
Research articles have a formal structure that allows you to move from section to section easily. The key to effective reading of research articles is to use this formal structure to your advantage.
Tip 1. Do not read the article sequentially from first page to last. This will only get you bogged down in the details, and make it difficult to make overall sense of it.
Tip 2. Do read the following sections in order: abstract, introduction, discussion, and any tables and graphs.
Gives you a quick, easy to understand overview of the research goals and findings.
Skim the background (literature review). Focus on finding the purpose of the research, and any hypotheses being tested.
If different from the abstract, go with the information given in the Introduction.
Explains what was found (or how successful the study was), and any problems encountered by the researchers.
If different from the abstract, go with the information given in the Discussion.
Provides data about the study population and the results (statistics).
Tip 3. Do read the entire article sequentially, AFTER you have scanned the sections above and IF you have decided to include it in your literature review.
Follow the instructions below to practice what you have learned about reading a scholarly article.
NOTE: When off-campus, you will be required to login with your DSU credentials when you link to the articles below.
1. Scan this article and answer the question immediately below it.
Dejaeger, K., Verbeke, W., Martens, D., Baesens, B. (2012). Data mining techniques for software effort estimation: A comparative study. IEEE Transactions on Software Engineering, 38(2), 375-397. DOI: 10.1109/TSE.2011.55
Question (click on question for answer):
2. Scan this article and answer the question immediately below.
Luo, X., Warkentin, M., & Li, H. (2013). Understanding technology adoption trade-offs: A conjoint analysis approach. The Journal of Computer Information Systems, 53(3), 65-74. Retrieved from http://www.ezproxy.dsu.edu:2048/login?url=http://search.proquest.com/docview/1370707436?accountid=27073
Question (click on question for answer):
3. Scan this article and answer the question immediately below.
Baysal, O., Holmes, R., Godfrey, M.W. (2013). Developer dashboards: The need for qualitative analytics. IEEE Software, 30 (4), 46-52. DOI: 10.1109/MS.2013.66.
Question (click on question for answer):
4. Return to this article and answer the question immediately below.
Baysal, O., Holmes, R., Godfrey, M.W. (2013). Developer dashboards: The need for qualitative analytics. IEEE Software, 30 (4), 46-52. DOI: 10.1109/MS.2013.66.
Question (click on question for answer):