2002
DOI: 10.1109/52.976942
|View full text |Cite
|
Sign up to set email alerts
|

Is this a pattern?

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
22
1

Year Published

2005
2005
2012
2012

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 32 publications
(23 citation statements)
references
References 8 publications
0
22
1
Order By: Relevance
“…Winn and Calder (2002) suggest nine essential characteristics of pattern, some of which reflect attributes also identified by previous researchers. Below we summarise the characteristics that Winn and Calder identify.…”
Section: Characteristics Of Pattern a Number Of Researchers Have Discmentioning
confidence: 90%
See 2 more Smart Citations
“…Winn and Calder (2002) suggest nine essential characteristics of pattern, some of which reflect attributes also identified by previous researchers. Below we summarise the characteristics that Winn and Calder identify.…”
Section: Characteristics Of Pattern a Number Of Researchers Have Discmentioning
confidence: 90%
“…However, it is not enough simply to capture good HCI practice: pattern mining requires capture of practice that is both good and significant (Fincher & Utting, 2002). Patterns are not intended to state obvious solutions to trivial problems or to cover every possible design decision, but to capture "big ideas" (Winn & Calder, 2002). A pattern should capture insights about the design that can inform even an experienced designer; explaining not only how a problem can be solved but also why a design choice is appropriate to a particular context.…”
Section: Identifying Patternsmentioning
confidence: 99%
See 1 more Smart Citation
“…Design patterns provide a possible way to deal with non-functional requirements since they provide solutions to satisfy functional requirements as well as better solutions to meet nonfunctional requirements [34]. In other words, besides providing a basic, functional solution to a problem, a design pattern offers a qualified, non-functional improvement to that solution.…”
Section: 2mentioning
confidence: 99%
“…Moreover, each team could record some software patterns [28], [29] (or anti-patterns [30]) that take the hardware characteristics into consideration and encapsulate knowledge gained from software analysis and design that successfully increased efficiency (or that failed to increase ef-ficiency). By explicitly stating which patterns are to be applied to the model, judging the efficiency of the model would become easier, and this should result in the generation of final software that is more efficient.…”
Section: 4mentioning
confidence: 99%