122:, computer scientists have been doing DSR without naming it. They have developed new architectures for computers, new programming languages, new compilers, new algorithms, new data and file structures, new data models, new database management systems, and so on. Much of the early research was focused on systems development approaches and methods. The dominant research philosophy in many disciplines has focused on developing cumulative, theory-based research results in order to make prescriptions. It seems that this âtheory-with-practical-implicationsâ research strategy has not delivered on this aim, which led to search for practical research methods such as DSR.
22:(DSR) is a research paradigm focusing on the development and validation of prescriptive knowledge in information science. Herbert Simon distinguished the natural sciences, concerned with explaining how things are, from design sciences which are concerned with how things ought to be, that is, with devising artifacts to attain goals. Design science research methodology (DSRM) refers to the research methodologies associated with this paradigm. It spans the methodologies of several research disciplines, for example
131:
iterated a number of times before the final design artifact is generated. In DSR, the focus is on the so-called field-tested and grounded technological rule as a possible product of Mode 2 research with the potential to improve the relevance of academic research in management. Mode 1 knowledge production is purely academic and mono-disciplinary, while Mode 2 is multidisciplinary and aims at solving complex and relevant field problems.
265:
The rigor cycle provides past knowledge to the research project to ensure its innovation. It is incumbent upon the researchers to thoroughly research and reference the knowledge base in order to guarantee that the designs produced are research contributions and not routine designs based upon the application of well-known processes. The central
109:
that professionals of the discipline in question can use to design solutions for their field problems. Design sciences focus on the process of making choices on what is possible and useful for the creation of possible futures, rather than on what is currently existing. This mission can be compared to
206:
Transparency in DSR is becoming an emerging concern. DSR strives to be practical and relevant. Yet few researchers have examined the extent to which practitioners can meaningfully utilize theoretical knowledge produced by DSR in solving concrete real-world problems. There is a potential gulf between
110:
the one of the âexplanatory sciencesâ, like the natural sciences and sociology, which is to develop knowledge to describe, explain and predict. Hevner states that the main purpose of DSR is achieving knowledge and understanding of a problem domain by building and application of a designed artifact.
264:
DSR can be seen as an embodiment of three closely related cycles of activities. The relevance cycle initiates DSR with an application context that not only provides the requirements for the research as inputs but also defines acceptance criteria for the ultimate evaluation of the research results.
65:
disciplines, though is not restricted to these and can be found in many disciplines and fields. DSR, or constructive research, in contrast to explanatory science research, has academic research objectives generally of a more pragmatic nature. Research in these disciplines can be seen as a quest for
277:
DSR in itself implies an ethical change from describing and explaining of the existing world to shaping it. One can question the values of information system research, i.e., whose values and what values dominate it, emphasizing that research may openly or latently serve the interests of particular
255:
DSR artifacts can broadly include: models, methods, constructs, instantiations and design theories (March & Smith, 1995; Gregor 2002; March & Storey, 2008, Gregor and Hevner 2013), social innovations, new or previously unknown properties of technical/social/informational resources (March,
151:
for the specified problem. In order to form a novel research contribution, the artifact must either solve a problem that has not yet been solved, or provide a more effective solution. Both the construction and evaluation of the artifact must be done rigorously, and the results of the research
130:
The design process is a sequence of expert activities that produces an innovative product. The artifact enables the researcher to get a better grasp of the problem; the re-evaluation of the problem improves the quality of the design process and so on. This build-and-evaluate loop is typically
278:
dominant groups. The interests served may be those of the host organization as perceived by its top management, those of information system users, those of information system professionals or potentially those of other stakeholder groups in society.
247:
Artifacts within DSR are perceived to be knowledge containing. This knowledge ranges from the design logic, construction methods and tool to assumptions about the context in which the artifact is intended to function (Gregor, 2002).
251:
The creation and evaluation of artifacts thus forms an important part in the DSR process which was described by Hevner et al., (2004) and supported by March and Storey (2008) as revolving around âbuild and evaluateâ.
892:
March, S. T., Storey, V. C., (2008). Design
Science in the Information Systems Discipline: An introduction to the special issue on design science research, MIS Quarterly, Vol. 32(4), pp. 725â730.
286:
There are limited references to examples of DSR, but Adams has completed two PhD research topics using
Peffers et al.'s DSRP (both associated with digital forensics but from different perspectives):
418:, Kuechler, W. (2004/21). âDesign Science Research in Information Systemsâ January 20, 2004 (updated in 2017 and 2019 by Vaishnavi, V. and Stacey, P.; last updated November 24, 2021. URL:
850:
184:
Effective design-science research must provide clear and verifiable contributions in the areas of the design artifact, design foundations, and/or design methodologies.
818:
653:
Aparicio, J.T.; Aparicio, M.; Costa, C.J. (2023). "Design
Science in Information Systems and Computing". In Anwar, S.; Ullah, A.; Rocha, Ă.; Sousa, M.J. (eds.).
861:
912:
Opdenakker, Raymond en Carin
Cuijpers (2019),âEffective Virtual Project Teams: A Design Science Approach to Building a Strategic Momentumâ, Springer Verlag.
915:
Van Aken, J. E. (2004). Management
Research Based on the Paradigm of the Design Sciences: The Quest for Field-Tested and Grounded Technological Rules.
889:
March, S. T., Smith, G. F., (1995). Design and natural science research on information technology. Decision
Support Systems, 15(4), pp. 251â266.
93:
Design science is a valid research methodology to develop solutions for practical engineering problems. Design science is particularly suitable for
45:
with the explicit intention of improving the functional performance of the artifact. DSRM is typically applied to categories of artifacts including
508:
Van Aken JE (2005). "Management research as a design science: Articulating the research products of mode 2 knowledge production in management".
196:
The search for an effective artifact requires utilizing available means to reach desired ends while satisfying laws in the problem environment.
794:
487:
256:
Storey, 2008), new explanatory theories, new design and developments models and implementation processes or methods (Ellis & Levy 2010).
922:
Watts S, Shankaranarayanan G., Even A. Data quality assessment in context: A cognitive perspective. Decis
Support Syst. 2009;48(1):202-211.
640:
Hevner, A. R.; March, S. T.; Park, J. & Ram, S. Design
Science in Information Systems Research. MIS Quarterly, 2004, 28, 75-106. URL:
851:
https://www.researchgate.net/publication/258224615_The_Advanced_Data_Acquisition_Model_ADAM_A_process_model_for_digital_forensic_practice
876:
Adams, R., Hobbs, V., Mann, G., (2013). The
Advanced Data Acquisition Model (ADAM): A process model for digital forensic practice. URL:
190:
Design-science research relies upon the application of rigorous methods in both the construction and evaluation of the design artifact.
350:
140:
172:
The objective of design-science research is to develop technology-based solutions to important and relevant business problems.
178:
The utility, quality, and efficacy of a design artifact must be rigorously demonstrated via well-executed evaluation methods.
202:
Design-science research must be presented effectively both to technology-oriented as well as management-oriented audiences.
916:
862:
https://espace.curtin.edu.au/bitstream/handle/20.500.11937/93974/Adams%20RB%202023%20Public.pdf?sequence=1&isAllowed=y
746:"Research Perspectives: Design Theory Indeterminacy: What Is it, How Can it Be Reduced, and Why Did the Polar Bear Drown?"
225:
The engineering cycle is a framework used in Design
Science for Information Systems and Software Engineering, proposed by
166:
Design-science research must produce a viable artifact in the form of a construct, a model, a method, or an instantiation.
238:
744:
HEC Montréal, Canada; Lukyanenko, Roman; Parsons, Jeffrey; Memorial University of Newfoundland, Canada (2020-09-01).
269:
iterates between the core activities of building and evaluating the design artifacts and processes of the research.
292:
2024: The Advanced Framework for Evaluating Remote Agents (AFERA): A Framework for Digital Forensic Practitioners
79:
50:
948:
698:
Watts S; Shankaranarayanan G & Even A (2009). "Data quality assessment in context: A cognitive perspective".
725:
Markus ML; Majchrzak A & Gasser L. "A design theory for systems that support emergent knowledge processes".
87:
641:
311:
23:
877:
144:
75:
67:
812:
765:
603:
564:
452:
395:
301:
289:
2013: The Advanced Data Acquisition Model (ADAM): A process model for digital forensic practice
898:"On the Use of Experiments in Design Science Research: A Proposition of an Evaluation Framework"
800:
790:
556:
483:
387:
346:
242:
220:
757:
707:
658:
595:
548:
517:
475:
444:
419:
379:
119:
62:
435:(2008). "On theory development in design science research: Anatomy of a research project".
432:
415:
321:
306:
535:
Peffers, Ken; Tuunanen, Tuure; Rothenberger, Marcus A.; Chatterjee, Samir (2007-12-01).
679:
Iivari J (2007). "A paradigmatic analysis of information systems as a design science".
655:
Proceedings of the International Conference on Information Technology and Applications
942:
769:
521:
226:
71:
54:
568:
456:
211:. Guidelines for addressing this challenges are provided in Lukyanenko et al. 2020.
207:
theoretical propositions and concrete issues faced in practiceâa challenge known as
143:(IS). DSR requires the creation of an innovative, purposeful artifact for a special
266:
139:
Hevner et al. have presented a set of guidelines for DSR within the discipline of
662:
470:
Dresch, Aline; Lacerda, Daniel Pacheco; Valle, José AntÎnio Jr. Antunes (2015).
58:
552:
745:
711:
479:
316:
153:
31:
27:
897:
804:
657:. Lecture Notes in Networks and Systems. Vol. 614. Springer, Singapore.
560:
536:
391:
106:
46:
35:
786:
Design science methodology for information systems and software engineering
784:
642:
https://citeseerx.ist.psu.edu/pdf/7d02dc5c8c0b316e592244c441796e6ad31d8bff
761:
448:
607:
583:
537:"A Design Science Research Methodology for Information Systems Research"
472:
Design Science Research: A Method for Science and Technology Advancement
399:
367:
148:
878:
http://researchrepository.murdoch.edu.au/id/eprint/14422/2/02Whole.pdf
832:
Hevner AR (2007). "The three cycle view of design science research".
599:
383:
83:
90:âs Organisation and System Design Centre, use the DSR approach.
41:
DSR focuses on the development and performance of (designed)
933:
Design Science Research in Information System and Technology
420:
http://desrist.org/design-research-in-information-systems
147:. The artifact must be evaluated in order to ensure its
57:) and languages. Its application is most notable in the
932:
152:
presented effectively both to technology-oriented and
750:Journal of the Association for Information Systems
584:"Design Science in Information Systems Research"
368:"The Science of Design: Creating the Artificial"
411:
409:
636:
634:
632:
70:. Such renowned research institutions as the
8:
282:Academic Examples of Design Science Research
834:Scandinavian Journal of Information Systems
681:Scandinavian Journal of Information Systems
817:: CS1 maint: location missing publisher (
345:. Thousand Oaks, Calif.: SAGE. p. 2.
215:The engineering cycle and the design cycle
135:Guidelines in information systems research
674:
672:
541:Journal of Management Information Systems
503:
501:
499:
437:European Journal of Information Systems
333:
896:Mettler T, Eurich M, Winter R (2014).
810:
159:Hevner counts 7 guidelines for a DSR:
7:
105:The main goal of DSR is to develop
82:'s Software Engineering Institute,
53:, design methodologies (including
14:
582:Hevner; March; Park; Ram (2004).
343:Encyclopedia of management theory
522:10.1111/j.1467-8551.2005.00437.x
78:'s Center for Design Research,
623:The sciences of the artificial
474:. Cham: Springer. pp. i.
42:
1:
917:Journal of Management Studies
510:British Journal of Management
663:10.1007/978-981-19-9331-2_35
239:Human factors and ergonomics
66:understanding and improving
209:design theory indeterminacy
194:Design as a search process:
965:
553:10.2753/MIS0742-1222240302
366:Simon, Herbert A. (1988).
236:
218:
200:Communication of research:
114:Evolution and applications
80:Carnegie Mellon University
38:within research projects.
902:Communications of the AIS
712:10.1016/j.dss.2009.07.012
480:10.1007/978-3-319-07374-3
51:human/computer interfaces
118:Since the first days of
88:Brunel University London
26:, which offers specific
783:Wieringa, Roel (2014).
312:Participant observation
182:Research contributions:
20:Design science research
164:Design as an artifact:
24:information technology
156:-oriented audiences.
762:10.17705/1jais.00639
621:Simon, H.A. (1969).
449:10.1057/ejis.2008.40
341:Kessler, EH (2013).
16:Research methodology
141:Information Systems
76:Stanford University
700:Decis Support Syst
302:Empirical research
260:A three-cycle view
176:Design evaluation:
170:Problem relevance:
919:, 41(2), 219â246.
871:Research examples
796:978-3-662-43839-8
489:978-3-319-07373-6
243:Human reliability
221:Engineering cycle
68:human performance
956:
949:Research methods
909:
864:
859:
853:
848:
842:
841:
829:
823:
822:
816:
808:
780:
774:
773:
756:(5): 1343â1369.
741:
735:
734:
722:
716:
715:
695:
689:
688:
676:
667:
666:
650:
644:
638:
627:
626:
618:
612:
611:
600:10.2307/25148625
579:
573:
572:
532:
526:
525:
505:
494:
493:
467:
461:
460:
428:
422:
413:
404:
403:
363:
357:
356:
338:
120:computer science
63:Computer Science
964:
963:
959:
958:
957:
955:
954:
953:
939:
938:
929:
895:
886:
884:Further reading
873:
868:
867:
860:
856:
849:
845:
831:
830:
826:
809:
797:
782:
781:
777:
743:
742:
738:
724:
723:
719:
697:
696:
692:
678:
677:
670:
652:
651:
647:
639:
630:
620:
619:
615:
581:
580:
576:
534:
533:
529:
507:
506:
497:
490:
469:
468:
464:
430:
429:
425:
414:
407:
384:10.2307/1511391
378:(1/2): 67â82 .
365:
364:
360:
353:
340:
339:
335:
330:
322:Design thinking
307:Action research
298:
284:
275:
262:
245:
235:
223:
217:
188:Research rigor:
137:
128:
126:Characteristics
116:
103:
17:
12:
11:
5:
962:
960:
952:
951:
941:
940:
937:
936:
928:
927:External links
925:
924:
923:
920:
913:
910:
893:
890:
885:
882:
881:
880:
872:
869:
866:
865:
854:
843:
824:
795:
789:. Heidelberg.
775:
736:
717:
706:(1): 202â211.
690:
668:
645:
628:
613:
574:
527:
495:
488:
462:
443:(5): 489â504.
423:
405:
358:
351:
332:
331:
329:
326:
325:
324:
319:
314:
309:
304:
297:
294:
283:
280:
274:
273:Ethical issues
271:
261:
258:
234:
231:
219:Main article:
216:
213:
204:
203:
197:
191:
185:
179:
173:
167:
145:problem domain
136:
133:
127:
124:
115:
112:
102:
99:
95:wicked problem
55:process models
15:
13:
10:
9:
6:
4:
3:
2:
961:
950:
947:
946:
944:
934:
931:
930:
926:
921:
918:
914:
911:
908:(1): 223â240.
907:
903:
899:
894:
891:
888:
887:
883:
879:
875:
874:
870:
863:
858:
855:
852:
847:
844:
839:
835:
828:
825:
820:
814:
806:
802:
798:
792:
788:
787:
779:
776:
771:
767:
763:
759:
755:
751:
747:
740:
737:
732:
728:
727:MIS Quarterly
721:
718:
713:
709:
705:
701:
694:
691:
686:
682:
675:
673:
669:
664:
660:
656:
649:
646:
643:
637:
635:
633:
629:
624:
617:
614:
609:
605:
601:
597:
593:
589:
588:MIS Quarterly
585:
578:
575:
570:
566:
562:
558:
554:
550:
546:
542:
538:
531:
528:
523:
519:
515:
511:
504:
502:
500:
496:
491:
485:
481:
477:
473:
466:
463:
458:
454:
450:
446:
442:
438:
434:
427:
424:
421:
417:
416:Vaishnavi, V.
412:
410:
406:
401:
397:
393:
389:
385:
381:
377:
373:
372:Design Issues
369:
362:
359:
354:
352:9781412997829
348:
344:
337:
334:
327:
323:
320:
318:
315:
313:
310:
308:
305:
303:
300:
299:
295:
293:
290:
287:
281:
279:
272:
270:
268:
259:
257:
253:
249:
244:
240:
232:
230:
228:
227:Roel Wieringa
222:
214:
212:
210:
201:
198:
195:
192:
189:
186:
183:
180:
177:
174:
171:
168:
165:
162:
161:
160:
157:
155:
150:
146:
142:
134:
132:
125:
123:
121:
113:
111:
108:
100:
98:
96:
91:
89:
86:âs PARC, and
85:
81:
77:
73:
72:MIT Media Lab
69:
64:
60:
56:
52:
48:
44:
39:
37:
33:
29:
25:
21:
905:
901:
857:
846:
837:
833:
827:
785:
778:
753:
749:
739:
730:
726:
720:
703:
699:
693:
684:
680:
654:
648:
625:. MIT Press.
622:
616:
591:
587:
577:
547:(3): 45â77.
544:
540:
530:
516:(1): 19â36.
513:
509:
471:
465:
440:
436:
431:Kuechler B,
426:
375:
371:
361:
342:
336:
291:
288:
285:
276:
267:design cycle
263:
254:
250:
246:
224:
208:
205:
199:
193:
187:
181:
175:
169:
163:
158:
138:
129:
117:
104:
94:
92:
40:
19:
18:
433:Vaishnavi V
59:Engineering
733:: 179â212.
328:References
317:Case study
237:See also:
154:management
101:Objectives
47:algorithms
32:evaluation
28:guidelines
935:community
813:cite book
805:899248827
770:222094969
594:(1): 75.
561:0742-1222
392:0747-9360
233:Artifacts
107:knowledge
43:artifacts
36:iteration
943:Category
840:(2): 87.
687:(2): 39.
608:25148625
569:17511997
457:16297257
296:See also
400:1511391
149:utility
803:
793:
768:
606:
567:
559:
486:
455:
398:
390:
349:
766:S2CID
604:JSTOR
565:S2CID
453:S2CID
396:JSTOR
84:Xerox
819:link
801:OCLC
791:ISBN
731:2002
557:ISSN
484:ISBN
388:ISSN
347:ISBN
241:and
61:and
34:and
30:for
758:doi
708:doi
659:doi
596:doi
549:doi
518:doi
476:doi
445:doi
380:doi
97:s.
945::
906:34
904:.
900:.
838:19
836:.
815:}}
811:{{
799:.
764:.
754:21
752:.
748:.
729:.
704:48
702:.
685:19
683:.
671:^
631:^
602:.
592:28
590:.
586:.
563:.
555:.
545:24
543:.
539:.
514:16
512:.
498:^
482:.
451:.
441:17
439:.
408:^
394:.
386:.
374:.
370:.
229:.
74:,
49:,
821:)
807:.
772:.
760::
714:.
710::
665:.
661::
610:.
598::
571:.
551::
524:.
520::
492:.
478::
459:.
447::
402:.
382::
376:4
355:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.