Академический Документы
Профессиональный Документы
Культура Документы
Open Rubric
1
10/24/2017
From:
http://www.phdcomics.com/comics/archive.php/tellafriend.php?comi
cid=798
2
10/24/2017
Plan
• Part 1: Mechanics
– Scientific reporting: Technical or Creative Writing?
– Perspectives: The audiences & “their” parts of the paper
– The organization and the red thread
• Part 2: The Paper
– The introduction: how to motivate the readers
– The literature review: establishing a gap
– The methodology: real science
– The findings: compelling, not boring
– The discussion: establishing a contribution
– The conclusion: the supported claims
– The abstract
– The appendix
– Avoiding Bugs
Part 1: Mechanics
3
10/24/2017
Full Text
Partial Text
Abstract
Title
Size of Audience
Workload
Your reader (Inversely Proportional) You
Work Done by
the Author
Work Done by
the Reader
4
10/24/2017
Perspectives
• The owner and publisher
• The editor
• The reviewer
• The reader
• The author
5
10/24/2017
The editor
6
10/24/2017
The reviewer
I might learn something new about my topic or
about reviewing. This could help me in writing my
own research. Maybe I can suggest cites to my
work!
14
7
10/24/2017
15
The reader
8
10/24/2017
The author
If my article gets accepted and published, I might get
rewarded, promoted, tenured or have my workload
adjusted.
18
9
10/24/2017
Intro
Lit Rev
Findings
Method
Discussion Conclusion
10
10/24/2017
21
A venerable mistake
22
11
10/24/2017
23
(Qualifier)
Claim
(Rebuttal)
Warrant
(Backing)
Support
(Rebuttal)
24
• Major parts:
– Claim: The point being argued.
– Support: Persuasive reasons: Evidence, proof, data, arguments, or grounds. May consist
of facts, statistics, expert opinion, examples, explanations, and logical reasoning.
– Warrants: Underlying assumptions. Generally accepted beliefs and values, usually
unstated and implied.
• Optional parts
– Qualifiers: Arguments are rarely certain, the claims rarely absolute.
– Rebuttal: Refutation of opposing claims and alternative explanations of supporting
evidence.
– Backing: Evidence to support the warrant
• Five Categories of Claims
– Claims of fact.
– Claims of definition.
– Claims of cause.
– Claims of value.
Adapted from Chas Swadley (2006), Oklahoma University
– Claims of policy. http://students.ou.edu/S/Charles.R.Swadley- 1/argumentation.htm who
draws on Nancy Wood's Perspectives on Argument, 2nd ed. (pp.161-72)
12
10/24/2017
25
13
10/24/2017
27
14
10/24/2017
29
30
15
10/24/2017
31
16
10/24/2017
33
17
10/24/2017
35
http://www.phdcomics.com/comics.php?
f=1887
36
18
10/24/2017
• Still an argument
– Must compel the reader to believe your
results
• Know and rebut the “vogue” complaints
– E.g., Quantitative tests for mediation vs
moderation
• Use of data windows in qualitative studies
to increase authenticity
https://www.youtube.com/watch?v=tDNCkcC47eQ
38
19
10/24/2017
40
From: http://www.phdcomics.com/comics/archive.php?comicid=1144
20
10/24/2017
41
42
21
10/24/2017
44
THE ABSTRACT
22
10/24/2017
45
The abstract
• Using _________ methodology, this study
finds _________. This contribution is
important because __________.
• Not a teaser, it is an elevator pitch.
• Just the facts. Got 5 facts? List
and define all 5.
46
For example
The ubiquity of computing is necessarily disseminating computer
expertise more widely. As a result, organisational IT expertise no
longer resides solely in its information systems divisions. Is the
increase in user IT expertise making them better partners in systems
implementations? In this study we report a questionnaire-based
survey of 79 companies with enterprise systems projects. It is a
sophisticated survey because it matches responses from each
company’s IS department with those of its user departments. The
research finds that IT competence held jointly by developers and users
significantly improves user satisfaction. The results also indicate how
joint leadership in systems development projects is also a positive
effect. This finding is a timely addition to the IS success literature
because many users are increasingly motivated and competent to
serve as full partners in IS development. Developers can no longer
restrict these experts to service merely as a requirements vehicle and
expect to achieve the same levels of success as those who regard them
as partners.
Baskerville, R. (2009) The EJIS editorial organisation and
submissions. European Journal of Information Systems 18(1).
23
10/24/2017
47
THE APPENDIX
48
The Appendix
• Device for managing length
• Increasing use of online appendices
• Sometimes download automatically with
online article access
• Rule: Details unnecessary to compel the
concluding claims
• Paper should stand alone without the
appendices
24
10/24/2017
49
AVOIDING BUGS
Avoiding bugs
• Length Use of tables and figures
• Use of headings and sub-headings
• Citations and references
– Avoid interrupting sentences
• Text Reuse or Self-plagiarism
25
10/24/2017
51
Length
– Find a model and mimic it
– Trading off work between the author and the
reader
– Short, active case, helps you to be clear
– Don’t be afraid of “useful ambiguity” (Peter
Checkland)
– Length can irritate reviewers
26
10/24/2017
27
10/24/2017
References:
• Davis, M. (1971). That's interesting.
Philosophy of Social Science, 1, 309-344.
• Smith, A. J. (1990). The Task of the
Referee. Computer, 23(4), 65-71.
28
10/24/2017
58
29