Design science methodology for a PhD project Roel Wieringa 1IS Seminar 31st August.

Slides:



Advertisements
Similar presentations
Designing an Architecture 1.Design Strategy Decomposition Designing to Architecturally Significant Requirements Generate and Test This generate-and test.
Advertisements

CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Constructing Hypotheses
1 The Database Application Development Process The Database Application Development Process.
9/6/2001Database Management – Fall 2000 – R. Larson Information Systems Planning and the Database Design Process University of California, Berkeley School.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Chapter 1 Software Development. Copyright © 2005 Pearson Addison-Wesley. All rights reserved. 1-2 Chapter Objectives Discuss the goals of software development.
Analysis Concepts and Principles
Requirement Engineering – A Roadmap
Computers: Tools for an Information Age
Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department Software Systems.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
System Engineering Instructor: Dr. Jerry Gao. System Engineering Jerry Gao, Ph.D. Jan System Engineering Hierarchy - System Modeling - Information.
The Inquiry Method for Social Science Research
Requirements Engineering Process – 1
6 Systems Analysis and Design in a Changing World, Fourth Edition.
Chapter 6: The Traditional Approach to Requirements
System Analysis Overview Document functional requirements by creating models Two concepts help identify functional requirements in the traditional approach.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Introduction to Systems Analysis and Design Trisha Cummings.
Systems Analysis and Design: The Big Picture
The Software Development Life Cycle: An Overview
Chapter 4 Requirements Engineering
SCHOOL OF INFORMATION UNIVERSITY OF MICHIGAN si.umich.edu The Literature Review for a Thesis or Dissertation Victor Rosenberg Winter 2005.
Types of evaluation examine different aspects of performance Resources (Inputs) ActivitiesOutputs Short-Term Outcomes Intermediate Outcomes (through customers)
Chapter 4 – Requirements Engineering
BSBPMG502A Manage Project Scope Manage Project Scope Project Scope Processes Part 1 Diploma of Project Management Qualification Code BSB51507 Unit.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Business Analysis and Essential Competencies
Feasibility Study.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
IT Requirements Management Balancing Needs and Expectations.
1 CS 426 Senior Projects Chapter 3: The Requirements Workflow [Arlow & Neustadt, 2005] January 31, 2012.
GSSR Research Methodology and Methods of Social Inquiry socialinquiry.wordpress.com January 17, 2012 I. Mixed Methods Research II. Evaluation Research.
Goal and Requirement Change Management in Enterprise Architecture Abelneh Teka 13, June 2012.
1 Advanced Software Architecture Muhammad Bilal Bashir PhD Scholar (Computer Science) Mohammad Ali Jinnah University.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Develop Project Charter
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Begin at the Beginning introduction to evaluation Begin at the Beginning introduction to evaluation.
1.  Interpretation refers to the task of drawing inferences from the collected facts after an analytical and/or experimental study.  The task of interpretation.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Research Tools and Techniques The Research Process: Step 3 & 4 Lecture 8.
Lecture 4: Requirements Engineering COSI 120b, Principles of Software Engineering.
Requirements Analysis
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 Click to edit Master title style What is Business Analysis Body of Knowledge?
PBL Instructional Design. PBL Instructional Design Name: Name of PBL: Grade Level: Content Area:
6 Systems Analysis and Design in a Changing World, Fourth Edition.
INFOMGP Student names and numbers Papers’ references Title.
Chapter 3: The Requirements Workflow [Arlow and Neustadt, 2005] CS 426 Senior Projects in Computer Science University of Nevada, Reno Department of Computer.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
Lecture №4 METHODS OF RESEARCH. Method (Greek. methodos) - way of knowledge, the study of natural phenomena and social life. It is also a set of methods.
Requirements in the product life cycle Chapter 7.
Case Study Research Case Study Research Manufacturing and Technology Management Research Methodology Workshop 2011 Dr Erik Stam University of Cambridge.
Daniel Amyot, University of Ottawa Based on slides by Gunter Mussbacher (2009) and Stéphane Somé (2008) with material from these standards: IEEE ,
Michael J. Novak ASQ Section 0511 Meeting, February 8, 2017
TJTS505: Master's Thesis Seminar
Workshop to develop theories of change
<Name of Product>Pilot Closeout Meeting <Customer Name>
Please highlight one choice only
The Design Process.
Nature of Science Understandings for HS
Please highlight one choice only
Project Title: (Your project title here)
Requirements Engineering Process – 1
Requirements Management - I
Presentation transcript:

Design science methodology for a PhD project Roel Wieringa 1IS Seminar 31st August

Goal Discuss one of our research projects 1.Subject 2.Methodological structure Relate this to your project 2IS Seminar 31st August

1. Subject Project goal: – Extending enterprise architecture design with goal-oriented requirements engineering Partners: – BizzDesign (Wilco Engelsman) – Novay (Dick Quartel) – UT (Roel Wieringa) 3IS Seminar 31st August

Work done so far KAOS and i* and Tropos and causal loop diagrams and.... ARMOR Light Armor Fusion: reasons to add elements Reduction: reasons to delete elements 4IS Seminar 31st August

Result (roughly) StakeholderDesire Goal RequirementSystem property 5 Goal is desire for which budget is made available If the goal is a system property, it is called a requirement Requirements must be satisfied by observed system property influence decomposition conflict IS Seminar 31st August Phenomenon Whatever is observable to stakeholders Desire is phenomenon ideal for a stakeholder Is-a

Status Concepts are stable for now... Fixed point in improvement iterations – Still to look at action goals and state goals – Measure of preferences? Relationships require a lot more work – Influence: state→state, action →state, action →action. Use + and – of causal loop diagram for state → state? – Decomposition: analytic and synthetic – Conflict: logically impossible, physically impossible, technically impossible, violation of standards, socially impossible, humanly impossible, too expensive... We will do some empirical work before we return to this 6IS Seminar 31st August

2. Methodological structure Engineering cycle (a.k.a. regulative cycle): Problem investigation Treatment design Treatment validation Implementation (transfer to Bizzdesign) Implementation evaluation 7IS Seminar 31st August “Solution” Artefact Technique Method....

Methodological structure of PhD thesis Problem investigation Treatment design Treatment validation Implementation (transfer to Bizzdesign) Implementation evaluation 8IS Seminar 31st August

What did we do so far Problem investigation: TBD Treatment design: light Armor Treatment validation: TBD Implementation (transfer to Bizzdesign) Implementation evaluation 9IS Seminar 31st August

Methodological options Problem investigation – What we know now: Mging large # of reqs, tracing EA to reqs, determining impact of req change or EA change are all problematic – To do: survey Among BizzDesign consultants? BizzDesign customers? In-depth interviews? Questionnaire Treatment design: light Armor Treatment validation: TBD 10IS Seminar 31st August

11 Initial treatment design Initial problem understanding Improved treatment design Improved problem understanding Treatment validation

Methodological options Problem investigation: Some survey Treatment design: light Armor Treatment validation: TBD 12IS Seminar 31st August

Methodological options Problem investigation: Some survey Treatment design: light Armor Treatment validation questions – Internal validity: LArmor in BizzDesign consultancy mitigates identified problems? – Trade-offs: All of LArmor? – Sensitivity: All of BizzDesign concultancy? Only Bizzdesign consultancy? 13IS Seminar 31st August

Methodological options Problem investigation Treatment design: light Armor Treatment validation methods – Simulation: Wilco uses LArmor with toy example – Simulation: Wilco uses LArmor with past project data – Action research: Wilco uses Larmor in a project – Opinion research: Wilco elicits opinion of Bizzdesign consultants about Larmor concepts & method – Experiment: Wilco studies BizzDesign consultants using Larmor on an artificial problem, compares to control group using current BizzDesign method – Case study: Wilco studies BizzDesign consultants using Larmor in a project 14IS Seminar 31st August

Methodological issues Generalization – Applicable to similar GORE methods? – Applicable to similar companies/projects? Theory – A theory is a dictionary plus a statement with scope of application; mechanism counterfactually supported Preferably, statement indicates mechanism Scope = generalization; always uncertain, possibly limited Mechanism Counterfactual – Theories applied? – Theory that will explain case study observations? 15IS Seminar 31st August

Organizational design science (Van Aken) – Elaborate problem investigation (diagnosis) – Like a physician Artefact design science (Wieringa) – Elaborate treatment design and validation – Like a medicine manufacturer 16IS Seminar 31st August

Discussion What about your project? Written presentation structure? – Problem – treatment – validation, with varying emphases Oral presentation structure? – Table of contents of two items – Context: the stage – Goals: what are you going to do – Why interesting for audience – What is new wrt related work – Substance 1: the version that everyone can understand – Substance 2: brief indication of some technical detail – Please keep your slides readable: minimum point size is 18 17IS Seminar 31st August

Discussion What about your project? Written presentation structure? – Problem – treatment – validation, with varying emphases Oral presentation structure? – Table of contents of two items – Context: the stage – Goals: what are you going to do – Why interesting for audience – What is new wrt related work – Substance 1: the version that everyone can understand – Substance 2: brief indication of some technical detail – Please keep your slides readable: minimum point size is 18 18IS Seminar 31st August

Discussion What about your project? Written presentation structure? – Problem – treatment – validation, with varying emphases Oral presentation structure? – Table of contents of two items – Context: the stage – Goals: what are you going to do – Why interesting for audience – What is new wrt related work – Substance 1: the version that everyone can understand – Substance 2: brief indication of some technical detail – Please keep your slides readable: minimum point size is 18 19IS Seminar 31st August