2010
DOI: 10.1007/978-1-4419-5653-8_2
|View full text |Cite
|
Sign up to set email alerts
|

Design Science Research in Information Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

11
2,814
1
145

Year Published

2010
2010
2021
2021

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 1,775 publications
(2,971 citation statements)
references
References 17 publications
11
2,814
1
145
Order By: Relevance
“…To conduct this research we have followed design science principles as suggested by Hevner et al (2004) and, in particular, we have applied the design science research methodology (DSRM) (Peffers et al 2007) as follows: Problem identification and motivation phase : In this phase, we reviewed both research proposals related to our research question, i.e., responsibility management applied to executable business processes, and how this is currently applied in industry. Table 3 collects those that take into consideration more than one type of responsibility.…”
Section: Motivation and Research Methodsmentioning
confidence: 99%
“…To conduct this research we have followed design science principles as suggested by Hevner et al (2004) and, in particular, we have applied the design science research methodology (DSRM) (Peffers et al 2007) as follows: Problem identification and motivation phase : In this phase, we reviewed both research proposals related to our research question, i.e., responsibility management applied to executable business processes, and how this is currently applied in industry. Table 3 collects those that take into consideration more than one type of responsibility.…”
Section: Motivation and Research Methodsmentioning
confidence: 99%
“…In order to develop the proposed EABV assessment approach, we employ an adapted Design Science Research (DSR) methodology proposed for example in [12]. Our DSR artifact build cycle is based on [13,14].…”
Section: Design Science Research and Evaluationmentioning
confidence: 99%
“…Before evaluating our approach, we need to choose the appropriate criteria, e.g. functionality, completeness, consistency, accuracy, performance, reliability, usability, fit with organization, and others more [12]. Generally, these criteria are derived from the artifact objectives [13].…”
Section: Artifact Evaluationmentioning
confidence: 99%
“…The focus on mutual adaptation suggests, however, the mTAC is particularly well suited to approaches that address the emergent nature of requirements, such as prototyping and agile systems development (Hall 2001;Surendra 2008). The tendency for people to adapt technologies to suit their needs also suggests that technologies should be designed for appropriation by making them more tailorable, malleable and flexible in order to better support technology adaptation (Carroll 2004;Hevner et al 2004;MacLean et al 1990). Furthermore, the insights gained from reflecting on the process of appropriation for a particular user cohort and use context can potentially guide changes to contextual influences, leading to appropriation behaviours that are more productive and persistent.…”
Section: The Technology Appropriation Cyclementioning
confidence: 99%
“…There appears to have been a shift, however, towards giving greater attention to the social and organisational context-including history, work practices, infrastructure, organisational norms and values, information flows and stakeholder perspectives-in recognition that IS projects are an organisational intervention, not just a technical intervention (Farbey et al 1993;Hallikainen and Chen 2006;Huang 2003;Symons 1991). There is also recognition that the process of evaluation plays an important role in supporting the design and development of systems (Hevner et al 2004;Symons 1991).…”
Section: Introductionmentioning
confidence: 99%