design software: requires understand problem

Property	Similarity
requires understand problem	1.00
causes wrong problem to be solve	0.87
be used to solve problem	0.87
be motivated by solve problem	0.87
causes help solve problem	0.86
requires analyze problem first	0.86
requires fully understand problem domain	0.85
requires prepare and analyze problem	0.84
requires determine need	0.78
requires study problem domain carefully	0.78

0.72

Rule weight: 0.85
Evidence weight: 0.98
Similarity weight: 0.86

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.08

¬ Salient(design software, causes help solve problem)

0.72

Rule weight: 0.85
Evidence weight: 0.97
Similarity weight: 0.87

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.16

¬ Remarkable(design software, be used to solve problem)

0.72

Rule weight: 0.85
Evidence weight: 0.98
Similarity weight: 0.86

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.12

¬ Remarkable(design software, causes help solve problem)

0.72

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.87

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.82

¬ Plausible(design software, be used to solve problem)

0.72

Rule weight: 0.85
Evidence weight: 0.97
Similarity weight: 0.87

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.73

¬ Plausible(design software, be motivated by solve problem)

0.71

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.87

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.20

¬ Remarkable(design software, be motivated by solve problem)

0.71

Rule weight: 0.85
Evidence weight: 0.97
Similarity weight: 0.86

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.73

¬ Plausible(design software, causes help solve problem)

0.71

Rule weight: 0.85
Evidence weight: 0.97
Similarity weight: 0.86

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.70

¬ Plausible(design software, requires analyze problem first)

0.71

Rule weight: 0.85
Evidence weight: 0.95
Similarity weight: 0.87

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.19

¬ Salient(design software, be used to solve problem)

0.71

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.87

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.17

¬ Salient(design software, be motivated by solve problem)

0.70

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.85

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.92

¬ Plausible(design software, requires fully understand problem domain)

0.69

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.84

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.87

¬ Plausible(design software, requires prepare and analyze problem)

0.69

Rule weight: 0.85
Evidence weight: 0.94
Similarity weight: 0.86

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.24

¬ Salient(design software, requires analyze problem first)

0.67

Rule weight: 0.85
Evidence weight: 0.92
Similarity weight: 0.86

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.43

¬ Remarkable(design software, requires analyze problem first)

0.67

Rule weight: 0.85
Evidence weight: 0.94
Similarity weight: 0.84

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.34

¬ Remarkable(design software, requires prepare and analyze problem)

0.65

Rule weight: 0.85
Evidence weight: 0.90
Similarity weight: 0.84

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.38

¬ Salient(design software, requires prepare and analyze problem)

0.65

Rule weight: 0.85
Evidence weight: 0.97
Similarity weight: 0.78

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.61

¬ Plausible(design software, requires study problem domain carefully)

0.64

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.78

Evidence: 0.96

Plausible(design software, requires understand problem) ⋁

Evidence: 0.98

¬ Plausible(design software, requires determine need)

0.64

Rule weight: 0.85
Evidence weight: 0.88
Similarity weight: 0.85

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.64

¬ Remarkable(design software, requires fully understand problem domain)

0.63

Rule weight: 0.85
Evidence weight: 0.96
Similarity weight: 0.78

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.23

¬ Remarkable(design software, requires study problem domain carefully)

0.63

Rule weight: 0.85
Evidence weight: 0.93
Similarity weight: 0.78

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.07

¬ Typical(design software, requires determine need)

0.62

Rule weight: 0.85
Evidence weight: 0.94
Similarity weight: 0.78

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.25

¬ Salient(design software, requires study problem domain carefully)

0.60

Rule weight: 0.85
Evidence weight: 0.82
Similarity weight: 0.85

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.20

¬ Typical(design software, requires fully understand problem domain)

0.59

Rule weight: 0.85
Evidence weight: 0.82
Similarity weight: 0.85

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.72

¬ Salient(design software, requires fully understand problem domain)

0.57

Rule weight: 0.85
Evidence weight: 0.86
Similarity weight: 0.78

Evidence: 0.81

Remarkable(design software, requires understand problem) ⋁

Evidence: 0.76

¬ Remarkable(design software, requires determine need)

0.52

Rule weight: 0.85
Evidence weight: 0.77
Similarity weight: 0.78

Evidence: 0.74

Salient(design software, requires understand problem) ⋁

Evidence: 0.89

¬ Salient(design software, requires determine need)

0.50

Rule weight: 0.85
Evidence weight: 0.70
Similarity weight: 0.84

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.34

¬ Typical(design software, requires prepare and analyze problem)

0.41

Rule weight: 0.85
Evidence weight: 0.55
Similarity weight: 0.87

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.51

¬ Typical(design software, be used to solve problem)

0.36

Rule weight: 0.85
Evidence weight: 0.50
Similarity weight: 0.86

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.57

¬ Typical(design software, requires analyze problem first)

0.32

Rule weight: 0.85
Evidence weight: 0.44
Similarity weight: 0.87

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.64

¬ Typical(design software, be motivated by solve problem)

0.26

Rule weight: 0.85
Evidence weight: 0.36
Similarity weight: 0.86

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.73

¬ Typical(design software, causes help solve problem)

0.22

Rule weight: 0.85
Evidence weight: 0.33
Similarity weight: 0.78

Evidence: 0.12

Typical(design software, requires understand problem) ⋁

Evidence: 0.76

¬ Typical(design software, requires study problem domain carefully)

design software: requires understand problem

Related concepts

Related properties

Priors about this statement

Cues

Evidence

Clauses

Salient implies Plausible

Similarity expansion

Typical and Remarkable implies Salient

Typical implies Plausible

Parents	-
Siblings	-