Line 31: |
Line 31: |
| | | |
| == Concise description of theory == | | == Concise description of theory == |
− |
| |
− | Design theory involves examining and evaluating design as a concept. A number of
| |
− | scholars in information systems research have examined the concept of
| |
− | design. “What is design?” remains elusive
| |
− | to ideate. The focus of design in information systems is on design of IT
| |
− | artifacts. There are differing opinions about what constitutes design
| |
− | theories for information technology artifacts. Walls et al.
| |
− | (1992) specify two major components of IT design theories:
| |
− | a product component and a development process component.
| |
− | Each draws upon kernel theories (usually taken from the
| |
− | natural or social sciences) in specifying prescriptive hypotheses
| |
− | that enable designers to evaluate whether the product and
| |
− | its development process satisfy the design theory. Goldkuhl
| |
− | (2004) specifies a need for multiple grounding of design
| |
− | theories in external theories, reference theories, value
| |
− | theories, etc. Markus et al. (2002) take a more practical view
| |
− | of design theories, using these theories to explain the means–
| |
− | ends relationship as a practical, prescriptively causal mechanism
| |
− | to justify design components.
| |
| | | |
| | | |