Paper Session 2 Argumentation & Progress meeting Paul Klint, - - PowerPoint PPT Presentation

paper session 2 argumentation progress meeting
SMART_READER_LITE
LIVE PREVIEW

Paper Session 2 Argumentation & Progress meeting Paul Klint, - - PowerPoint PPT Presentation

Software Analysis And Transformation Paper Session 2 Argumentation & Progress meeting Paul Klint, Jurgen Vinju, Paul Griffioen, Bas van Vlijmen Wednesday, December 5, 12 Today Argumentation Improve your scheme Prepare for


slide-1
SLIDE 1

Software Analysis And Transformation

Paper Session 2 Argumentation & Progress meeting

Paul Klint, Jurgen Vinju, Paul Griffioen, Bas van Vlijmen

Wednesday, December 5, 12

slide-2
SLIDE 2

SWAT - SoftWare Analysis And Transformation

Today

  • Argumentation
  • Improve your scheme
  • Prepare for final paper
  • Progress meeting

Wednesday, December 5, 12

slide-3
SLIDE 3

SWAT - SoftWare Analysis And Transformation

Argumentation

  • When is argumentation good?
  • When is it bad?
  • Different types of reasoning for different goals?

Wednesday, December 5, 12

slide-4
SLIDE 4

SWAT - SoftWare Analysis And Transformation

Reasoning

Wednesday, December 5, 12

slide-5
SLIDE 5

SWAT - SoftWare Analysis And Transformation

Reasoning

  • Finds a plausible explanation to observed facts

(abduction, used for finding hypotheses)

Wednesday, December 5, 12

slide-6
SLIDE 6

SWAT - SoftWare Analysis And Transformation

Reasoning

  • Finds a plausible explanation to observed facts

(abduction, used for finding hypotheses)

  • Logically arrives at a conclusion from earlier

truths (deduction, used for proving)

Wednesday, December 5, 12

slide-7
SLIDE 7

SWAT - SoftWare Analysis And Transformation

Reasoning

  • Finds a plausible explanation to observed facts

(abduction, used for finding hypotheses)

  • Logically arrives at a conclusion from earlier

truths (deduction, used for proving)

  • Arrives at a general conclusion even though not

all instances have been observed (induction, used for making sense of reality)

Wednesday, December 5, 12

slide-8
SLIDE 8

SWAT - SoftWare Analysis And Transformation

Reasoning

  • He held the gun while standing over the body, so

he is the killer.

  • x = 1, and y = 2, so (using basic arithmetic),

x + y = 3.

  • All cows are black and white.

Wednesday, December 5, 12

slide-9
SLIDE 9

SWAT - SoftWare Analysis And Transformation

Language

  • Be aware when you are arguing
  • If, when, then, because, why, consequentially,

therefore, so, and, but, concluding, believe, assume, know, implies, ...

  • Use the words to make explicit, step by step,

what you are thinking

  • Writing an argumentation often makes you

discover that you do not understand yet. That’s great!

Wednesday, December 5, 12

slide-10
SLIDE 10

SWAT - SoftWare Analysis And Transformation

Common sense

  • Do not underestimate yourselves
  • Be your own audience
  • Use your common sense and your curiosity:
  • O really?
  • But I saw the opposite happening yesterday!
  • Why? Why? Why? and … Why?

Wednesday, December 5, 12

slide-11
SLIDE 11

SWAT - SoftWare Analysis And Transformation

Assume

  • Not all questions can be answered
  • Stop where common sense allows you to assume
  • For example: we (sometimes) assume that
  • better tools always lead to more efficiency
  • we have infinite amount of RAM
  • P != NP, etc.
  • Just state your assumptions

Wednesday, December 5, 12

slide-12
SLIDE 12

SWAT - SoftWare Analysis And Transformation

Strong vs. Weak

  • The difference between proof and evidence?
  • How are arguments made stronger?
  • How are arguments made weaker?
  • The weakest link

Wednesday, December 5, 12

slide-13
SLIDE 13

SWAT - SoftWare Analysis And Transformation

Fallacies

  • Know how to recognize logical fallacies
  • accidental fallacies are just errors
  • intentional fallacies are rhetorical tricks
  • Who can give an example?

Wednesday, December 5, 12

slide-14
SLIDE 14

SWAT - SoftWare Analysis And Transformation

Example

Wednesday, December 5, 12

slide-15
SLIDE 15

SWAT - SoftWare Analysis And Transformation

Example

  • It has been clearly shown that the babies of mothers who

drink a lot of coffee often have health problems in early pregnancy

Wednesday, December 5, 12

slide-16
SLIDE 16

SWAT - SoftWare Analysis And Transformation

Example

  • It has been clearly shown that the babies of mothers who

drink a lot of coffee often have health problems in early pregnancy

  • So, mothers should not drink coffee in early pregnancy, to

prevent health issues of their babies.

Wednesday, December 5, 12

slide-17
SLIDE 17

SWAT - SoftWare Analysis And Transformation

Example

  • It has been clearly shown that the babies of mothers who

drink a lot of coffee often have health problems in early pregnancy

  • So, mothers should not drink coffee in early pregnancy, to

prevent health issues of their babies.

  • What is wrong with this argument?

Wednesday, December 5, 12

slide-18
SLIDE 18

SWAT - SoftWare Analysis And Transformation

Example

  • It has been clearly shown that the babies of mothers who

drink a lot of coffee often have health problems in early pregnancy

  • So, mothers should not drink coffee in early pregnancy, to

prevent health issues of their babies.

  • What is wrong with this argument?
  • What is an alternative explanation?

Wednesday, December 5, 12

slide-19
SLIDE 19

SWAT - SoftWare Analysis And Transformation

Example

  • It has been clearly shown that the babies of mothers who

drink a lot of coffee often have health problems in early pregnancy

  • So, mothers should not drink coffee in early pregnancy, to

prevent health issues of their babies.

  • What is wrong with this argument?
  • What is an alternative explanation?
  • When pregnancy hormone levels are low, the mother is not

feeling sick and so she is able to drink coffee without feeling

  • nausea. The low hormone levels are also indicative of health

issues for the baby.

Wednesday, December 5, 12

slide-20
SLIDE 20

SWAT - SoftWare Analysis And Transformation

Example

Wednesday, December 5, 12

slide-21
SLIDE 21

SWAT - SoftWare Analysis And Transformation

Example

  • “Code clones are parts of source code that when

represented as an AST are equal to each other. We made a tool that can detect ASTs that are equal. Our tool detects all of these ASTs and no more, so it has maximum recall and precision”

Wednesday, December 5, 12

slide-22
SLIDE 22

SWAT - SoftWare Analysis And Transformation

Example

  • “Code clones are parts of source code that when

represented as an AST are equal to each other. We made a tool that can detect ASTs that are equal. Our tool detects all of these ASTs and no more, so it has maximum recall and precision”

  • What is wrong with this argument?

Wednesday, December 5, 12

slide-23
SLIDE 23

SWAT - SoftWare Analysis And Transformation

Example

  • “Code clones are parts of source code that when

represented as an AST are equal to each other. We made a tool that can detect ASTs that are equal. Our tool detects all of these ASTs and no more, so it has maximum recall and precision”

  • What is wrong with this argument?
  • This argument is true because the definition was

made to fit the quality aspect. Trivially true and definitely uninteresting: circular.

Wednesday, December 5, 12

slide-24
SLIDE 24

SWAT - SoftWare Analysis And Transformation

Example

  • “Code clones are parts of source code that when

represented as an AST are equal to each other. We made a tool that can detect ASTs that are equal. Our tool detects all of these ASTs and no more, so it has maximum recall and precision”

  • What is wrong with this argument?
  • This argument is true because the definition was

made to fit the quality aspect. Trivially true and definitely uninteresting: circular.

  • What do the authors want/need to change here?

Wednesday, December 5, 12

slide-25
SLIDE 25

SWAT - SoftWare Analysis And Transformation

Example

Wednesday, December 5, 12

slide-26
SLIDE 26

SWAT - SoftWare Analysis And Transformation

Example

  • “I have unit-tested every component to the bone.

Let’s assume therefore that there are no more bugs in the components, so the system is bug- free.”

Wednesday, December 5, 12

slide-27
SLIDE 27

SWAT - SoftWare Analysis And Transformation

Example

  • “I have unit-tested every component to the bone.

Let’s assume therefore that there are no more bugs in the components, so the system is bug- free.”

  • What’s wrong here?

Wednesday, December 5, 12

slide-28
SLIDE 28

SWAT - SoftWare Analysis And Transformation

Example

  • “I have unit-tested every component to the bone.

Let’s assume therefore that there are no more bugs in the components, so the system is bug- free.”

  • What’s wrong here?
  • “My atoms are invisible. I am composed of

atoms, so I am invisible.”

Wednesday, December 5, 12

slide-29
SLIDE 29

SWAT - SoftWare Analysis And Transformation

  • Coordinative

(conjunctive, &&)

  • Subordinative

(implication, =>)

  • Single argument

(fact/assumption)

  • Watch out for hidden

assumptions

Wednesday, December 5, 12

slide-30
SLIDE 30

SWAT - SoftWare Analysis And Transformation

Exercise

  • Take somebody’s argumentation scheme
  • detect logical fallacies
  • ask why? why? why?
  • help to improve
  • exceptions
  • hidden assumptions
  • additional arguments

Wednesday, December 5, 12

slide-31
SLIDE 31

SWAT - SoftWare Analysis And Transformation

Discussion

  • Clones
  • Metrics
  • Design
  • What is confusing?
  • What is problematic?
  • What must be assumed?

Wednesday, December 5, 12

slide-32
SLIDE 32

SWAT - SoftWare Analysis And Transformation

Next session

  • Rewrite your argumentation as text
  • include motivation (improve it too!)
  • then put your argumentation
  • finish with a one-paragraph conclusion
  • max 3 pages. more will not be read.
  • We improve it next session
  • Then you submit for a grade, a.s.a.p.

Wednesday, December 5, 12