Introduction to design science methodology Roel Wieringa Slides - PowerPoint PPT Presentation

Introduction to design science methodology Roel Wieringa Slides based on Wieringa, R.J. (2014) Design science methodology for information systems and software engineering. Springer Verlag 30th May 2019 RCIS Brussels 1

Outline • Design problems and knowledge questions • The design cycle • The empirical cycle 30th May 2019 RCIS Brussels 2

Design science • Design science is the design and investigation of artifacts in context • Examples – Design and investigation of a method for user interface design for genomic databases – Design and investigation of an ontology‐based extension of OO‐method – Design and investigation of deep learning system to classify pathologies in X‐rays of the lower back – …. 30th May 2019 RCIS Brussels 3

DESIGN PROBLEMS AND KNOWLEDGE QUESTIONS 30th May 2019 RCIS Brussels 4

Your examples 30th May 2019 RCIS Brussels 5

Two kinds of research problems in design science DESIGN INVESTIGATION Problems & Artifacts To answer knowledge To design an artifact to investigate questions about the artifact in to improve a context problem context Knowledge, New design problems • Design software to estimate Direction Is the DoA estimation accurate of Arrival of plane waves, to be used enough in this context? • in satelite TV receivers in cars Is it fast enough? • Is this routing algorithm deadlock‐ Design a Multi‐Agent Route Planning system to be used for aircraft taxi free on airports? • How much delay does it produce? route planning • Is the method usable and useful for Design a data location regulation auditing method consultants? Change the real world Change your knowledge 30th May 2019 RCIS Brussels 6

Heuristics Knowledge questions Design problems √ To change your knowledge √ To change the world √ Answer is a proposition √ Solution is design √ One answer √ Many solutions √ Evaluated by truth √ Evaluated by usefulness √ What is true depends on the real √ What is useful depends on world stakeholder goals √ Degrees of certainty √ Degrees of utility Doing Thinking 30th May 2019 RCIS Brussels 7

Nesting of problems • To solve a design problem: – Study the problem – Test the proposed solution • To answer a knowledge question: – Design your research 30th May 2019 RCIS Brussels 8

Your examples revisited 30th May 2019 RCIS Brussels 9

Framework for design science Stakeholders may not know they are stakeholders • • Source of relevance. Social context: • Relevance, and money, comes and goes Location of stakeholders: E.g. project sponsors, manufacturers, customers, users, maintenance, interfacing systems, negative stakeholders, attackers, government, labor, ... Goals, budgets Designs Design science Improvement design Answering knowledge questions • Source and destination of theories Knowledge context: • Theories are forever Mathematics, social science, natural science, design science, design specifications, useful facts, practical knowledge, common sense, other beliefs 30th May 2019 RCIS Brussels 10

Stakeholders • A stakeholder of a problem is a biological or legal person affected by treating a problem. – People, organizations, job roles, contractual roles, etc. • Stakeholders may not know that they are stakeholders – They may accept the problem as normal – There may not be a problem at all … but you think/hope that there is an improvement opportunity 30th May 2019 RCIS Brussels 11

Checklist by role (Ian Alexander http://www.scenarioplus.org.uk/papers/papers.htm > A taxonomy of stakeholders) • System under Development Negative stakeholder (who is/perceives to be hurt by the • Normal operator (end user) product) • Operational support • Threat agent (who wants to hurt • Maintenance operator the product) Immediate context • Regulator • Functional beneficiary (client) Involved in development • Roles responsible for interfacing • Champion/Sponsor systems • Developer Wider context • Consultant • Political beneficiary (who gains • Purchaser (customer) status) • Suppliers of components • Financial beneficiary These are just examples 30th May 2019 RCIS Brussels 12

Examples • Design and investigation of a method for user interface design for genomic databases – Stakeholders: ……. • Design and investigation of an ontology‐based extension of OO‐method – Stakeholders: ….. • Design and investigation of deep learning system to classify pathologies in X‐rays of the lower back – Stakeholders: ….. 30th May 2019 RCIS Brussels 13

More examples 30th May 2019 RCIS Brussels 14

THE DESIGN CYCLE 30th May 2019 RCIS Brussels 15

The engineering cycle Stakeholders, goals, • Problem investigation phenomena, evaluation, • Treatment design diagnosis • Design validation • Treatment implementation • Implementation evaluation 30th May 2019 RCIS Brussels 16

The engineering cycle • Problem investigation Treatment = • Treatment design interaction between artifact and context • Design validation • Treatment implementation • Implementation evaluation • Interaction between pill and patient • Interaction between Software and its Context • Interaction between method and its context of use • You design the artifact in order to create a treatment 30th May 2019 RCIS Brussels 17

The engineering cycle Artifact & Context → Effects? • Problem investigation Effects satisfy Criteria? • Treatment design Trade-off: Changes in artifact • Design validation Sensitivity: Changes in context • Treatment implementation • Implementation evaluation 30th May 2019 RCIS Brussels 18

The engineering cycle • Problem investigation • Treatment design • Design validation Transfer to practice! • Treatment implementation Commercialization, sale • Implementation evaluation 30th May 2019 RCIS Brussels 19

The engineering cycle • Problem investigation • Treatment design • Design validation • Treatment implementation • Implementation evaluation Phenomena: Artifact & Context → Effects? Evaluation: Effects satisfy Criteria? 30th May 2019 RCIS Brussels 20

Legend: ? Knowledge questions Where are we ! Tasks Implementation evaluation = Treatment Problem investigation Implementation (transfer to the real • Stakeholders? Goals? world) • Phenomena? Causes? Effects? • Effects contribute to Goals? Engineering cycle Treatment design Treatment validation • Context & Artifact → Effects? • Specify requirements! • Effects satisfy Requirements? • Contribution to goals? • Trade‐offs for different artifacts? • Available treatments? • Sensitivity for different Contexts? • Design new ones! 30th May 2019 RCIS Brussels 21

Legend: ? Knowledge questions Where are we ! Tasks Implementation evaluation = Treatment Problem investigation Implementation (transfer to the real • Stakeholders? Goals? world) • Phenomena? Causes? Effects? • Effects contribute to Goals? Design cycle Treatment design Treatment validation • Context & Artifact → Effects? • Specify requirements! • Effects satisfy Requirements? • Contribution to goals? • Trade‐offs for different artifacts? • Available treatments? • Sensitivity for different Contexts? • Design new ones! 30th May 2019 RCIS Brussels 22

Knowledge questions that need empirical study Treatment Implementation Implementation evaluation = (transfer to the real Problem investigation world) • Stakeholders? Goals? Design • Phenomena? Causes? Effects? • Effects contribute to Goals? cycle Treatment validation Treatment design • Context & Artifact → Effects? • Specify requirements! • Effects satisfy Requirements? • Contribution to goals? • Trade‐offs for different artifacts? • Available treatments? • Sensitivity for different Contexts? • Design new ones! 30th May 2019 RCIS Brussels 23

Outline of a thesis Implementation evaluation = Problem investigation • Stakeholders? Goals? Design • Phenomena? Causes? Effects? • Effects contribute to Goals? cycle Treatment validation Treatment design • Context & Artifact → Effects? • Specify requirements! • Effects satisfy Requirements? • Contribution to goals? • Trade‐offs for different artifacts? • Available treatments? • Sensitivity for different Contexts? • Design new ones! 30th May 2019 RCIS Brussels 24