Design Science Research according to Peffers et al: Difference between revisions

From Design Science Research Methods
Jump to navigation Jump to search
(Created page with "== Process description == == Problem identification and motivation == === Description === Define the specific research problem and justify the value of a solution. Since the...")
 
No edit summary
Line 4: Line 4:
== Problem identification and motivation ==
== Problem identification and motivation ==
=== Description ===
=== Description ===
Define the specific research problem and justify the value of a solution. Since the problem definition will be used to develop an effective artifactual solution, it may be useful to atomize the problem conceptually so that the solution can capture the problem’s complexity. Justifying the value of a solution accomplishes two things: it motivates the researcher and the audience of the research to pursue the solution and to accept the results and it helps to understand the reasoning associated with the researcher’s understanding of the problem. Resources required for this activity include knowledge of the state of the problem and the importance of its solution (Peffers et al. 2007).
Define the basic issue of analysis, and explain the importance of a solution. As the problem description will be used to create an effective artifactual solution, conceptual atomization of the problem can be useful so that the solution can capture the central problem.
Justification of the importance of a solution accomplishes two things: it motivates the researcher and the research community to follow the solution and embrace the findings and it helps to consider the logic associated with explaining the problem by the researcher. Resources needed for this activity include knowledge of the state of the problem and the importance of solving it.


=== Examples ===
=== Examples ===
Line 16: Line 17:
== Objectives of a solution ==
== Objectives of a solution ==
=== Description ===
=== Description ===
Infer the objectives of a solution from the problem definition. The objectives can be quantitative, e.g., terms in which a desirable solution would be better than current ones, or qualitative, e.g., where a new artifact is expected to support solutions to problems not hitherto addressed. The objectives should be inferred rationally from the problem specification. Resources required for this include knowledge of the state of problems and current solutions and their efficacy, if any (Peffers et al. 2007).
Infer objectives from problem description of a solution. The aims may be quantitative, e.g., terms in which the desired approach will be better than existing ones, or qualitative, e.g., when a new tool is expected to support solutions to problems not addressed so far. The objectives should be rationally derived from problem specification. Resources required for this include awareness of the state of problems and existing approaches, and their efficacy, if any.  
 
=== Examples ===
=== Examples ===


Line 27: Line 27:
== Design and development ==
== Design and development ==
=== Description ===
=== Description ===
Create the artifactual solution. Such artifacts are potentially, with each defined broadly, constructs, models, methods, or instantiations (Hevner et al. 2004). This activity includes determining the artifact’s desired functionality and its architecture and then creating the actual artifact. Resources required moving from objectives to design and development include knowledge of theory that can be brought to bear as a solution (Peffers et al. 2007).
Create the artifactual solution. Such artifacts are potentially constructs, models, methods, or instantiations. This activity includes determining the artifact’s desired functionality and its architecture and then creating the actual artifact.


=== Examples ===
=== Examples ===
Line 48: Line 48:
== Evaluation ==
== Evaluation ==
=== Description ===
=== Description ===
Observe and measure how well the artifact supports a solution to the problem. This activity involves comparing the objectives of a solution to actual observed results from the use of the artifact in the demonstration. It requires knowledge of relevant metrics and analysis techniques. Depending on the nature of the problem venue and the artifact, evaluation could include such items as a comparison of the rtifact's functionality with the solution objectives from activity 2 above, objective quantitative performance measures, such as budgets or items produced satisfaction surveys, client feedback, or simulations. At the end of this activity, the researchers can decide whether to iterate back to step 3 to try to improve the effectiveness of the artifact or to continue on to communication and leave further improvement to subsequent projects. The nature of the research venue may dictate whether such iteration is feasible or not (Peffers et al. 2007).
Observe and evaluate how well the artifact supports a problem solution. This activity includes matching the objectives of a solution to the actual outcomes obtained from the artifact being used in the demonstration. Knowledge of the correct metrics and techniques for studies is requiered.
 
Depending on the nature of the problem venue and the artifact, evaluation could include:
* comparison of the rtifact's functionality with the solution objectives
* objective quantitative performance measures, such as budgets or items produced satisfaction surveys
* client feedback
* simulations
Researchers need to decide whether to iterate back to try to improve the effectiveness of the artifact or to communicate the results.
Depending on the nature of the research such iteration may be feasible or not.


=== Examples ===
=== Examples ===
Line 60: Line 69:
== Communication ==
== Communication ==
=== Description ===
=== Description ===
Communicate the problem and its importance, the artifact, its utility and novelty, the rigor of its design, and its effectiveness to researchers and other relevant audiences, such as practicing professionals, when appropriate. In scholarly research publications, researchers might use the structure of this process to structure the paper, just as the nominal structure of an empirical research process (problem definition, literature review, hypothesis development, data collection, analysis, results, discussion, and conclusion) is a common structure for empirical research papers. Communication requires knowledge of the disciplinary culture (Peffers et al. 2007).
Communicate the following items to researchers and other relevant audiences:
 
* problem and its importance
* the artifact
* its utility and novelty
* the rigor of its design
* its effectiveness
=== Examples ===
=== Examples ===
 
Example of a common structure for empirical research papers:
# problem definition
# literature review
# hypothesis development
# data collection
# analysis
# results
# discussion, and conclusion


=== Further Readings ===
=== Further Readings ===

Revision as of 10:34, 29 March 2020

Process description

Problem identification and motivation

Description

Define the basic issue of analysis, and explain the importance of a solution. As the problem description will be used to create an effective artifactual solution, conceptual atomization of the problem can be useful so that the solution can capture the central problem. Justification of the importance of a solution accomplishes two things: it motivates the researcher and the research community to follow the solution and embrace the findings and it helps to consider the logic associated with explaining the problem by the researcher. Resources needed for this activity include knowledge of the state of the problem and the importance of solving it.

Examples

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).


Objectives of a solution

Description

Infer objectives from problem description of a solution. The aims may be quantitative, e.g., terms in which the desired approach will be better than existing ones, or qualitative, e.g., when a new tool is expected to support solutions to problems not addressed so far. The objectives should be rationally derived from problem specification. Resources required for this include awareness of the state of problems and existing approaches, and their efficacy, if any.

Examples

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).


Design and development

Description

Create the artifactual solution. Such artifacts are potentially constructs, models, methods, or instantiations. This activity includes determining the artifact’s desired functionality and its architecture and then creating the actual artifact.

Examples

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).


Demonstration

Description

Demonstrate the efficacy of the artifact to solve the problem. This could involve its use in experimentation, simulation, a case study, proof, or other appropriate activity. Resources required for the demonstration include effective knowledge of how to use the artifact to solve the problem (Peffers et al. 2007).

Examples

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).


Evaluation

Description

Observe and evaluate how well the artifact supports a problem solution. This activity includes matching the objectives of a solution to the actual outcomes obtained from the artifact being used in the demonstration. Knowledge of the correct metrics and techniques for studies is requiered.

Depending on the nature of the problem venue and the artifact, evaluation could include:

  • comparison of the rtifact's functionality with the solution objectives
  • objective quantitative performance measures, such as budgets or items produced satisfaction surveys
  • client feedback
  • simulations

Researchers need to decide whether to iterate back to try to improve the effectiveness of the artifact or to communicate the results. Depending on the nature of the research such iteration may be feasible or not.

Examples

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).


Communication

Description

Communicate the following items to researchers and other relevant audiences:

  • problem and its importance
  • the artifact
  • its utility and novelty
  • the rigor of its design
  • its effectiveness

Examples

Example of a common structure for empirical research papers:

  1. problem definition
  2. literature review
  3. hypothesis development
  4. data collection
  5. analysis
  6. results
  7. discussion, and conclusion

Further Readings

Peffers, K., Tuunanen, T., Rothenberger, M. A., and Chatterjee, S. 2007. “A Design Science Research Methodology for Information Systems Research,” Journal of Management Information Systems (24:3), Taylor & Francis Ltd, pp. 45–77. (https://doi.org/10.2753/MIS0742-1222240302).

Retrieved from "https://wiki.mydesignprocess.com/index.php?title=Design_Science_Research_according_to_Peffers_et_al&oldid=226"