Design Science Method By Temtim Assefa.

Slides:



Advertisements
Similar presentations
Lecture # 2 : Process Models
Advertisements

SECOND MIDTERM REVIEW CS 580 Human Computer Interaction.
Soft Systems Methodology
Introduction to Soft Systems Methodology
Introduction to Soft Systems Methodology. The Vision SSM Models Use Cases Activity Models Dynamic Models Object Models Programs Databases Business Computing.
© 2005 Prentice Hall6-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
 delivers evidence that a solution developed achieves the purpose for which it was designed.  The purpose of evaluation is to demonstrate the utility,
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
OASIS Reference Model for Service Oriented Architecture 1.0
Software Testing and Quality Assurance
Algorithms and Problem Solving-1 Algorithms and Problem Solving.
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Software Processes: Traditional CSCI102 - Systems ITCS905 - Systems MCS Systems.
Four Dark Corners of Requirements Engineering
PPA 502 – Program Evaluation
The Process of Interaction Design. What is Interaction Design? It is a process: — a goal-directed problem solving activity informed by intended use, target.
Design and Evaluation of Iterative Systems n For most interactive systems, the ‘design it right first’ approach is not useful. n The 3 basic steps in the.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Overview of Software Requirements
4. Interaction Design Overview 4.1. Ergonomics 4.2. Designing complex interactive systems Situated design Collaborative design: a multidisciplinary.
SE 555 – Software Requirements & Specifications Introduction
© 2006 Pearson Addison-Wesley. All rights reserved2-1 Chapter 2 Principles of Programming & Software Engineering.
CSC230 Software Design (Engineering)
INTRODUCTION. Concepts HCI, CHI Usability User-centered Design (UCD) An approach to design (software, Web, other) that involves the user Interaction Design.
[ §4 : 1 ] 4. Requirements Processes II Overview 4.1Fundamentals 4.2Elicitation 4.3Specification 4.4Verification 4.5Validation Software Requirements Specification.
Computational Thinking Related Efforts. CS Principles – Big Ideas  Computing is a creative human activity that engenders innovation and promotes exploration.
Architectural Design.
SYSTEM ANALYSIS AND DESIGN
Desired Quality Characteristics in Cloud Application Development Leah Riungu-Kalliosaari.
1. Human – the end-user of a program – the others in the organization Computer – the machine the program runs on – often split between clients & servers.
Software Development Process
Overview of the Database Development Process
Unit 2: Engineering Design Process
What is Software Engineering? the application of a systematic, disciplined, quantifiable approach to the development, operation, and maintenance of software”
Ciarán O’Leary Wednesday, 23 rd September Ciarán O’Leary School of Computing, Dublin Institute of Technology, Kevin St Research Interests Distributed.
Requirements Analysis
RUP Implementation and Testing
© 2007 Pearson Education, Inc. Publishing as Pearson Addison-Wesley 1 A Discipline of Software Design.
المحاضرة الثالثة. Software Requirements Topics covered Functional and non-functional requirements User requirements System requirements Interface specification.
Business Analysis and Essential Competencies
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
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.
1-1 System Development Process System development process – a set of activities, methods, best practices, deliverables, and automated tools that stakeholders.
The roots of innovation Future and Emerging Technologies (FET) Future and Emerging Technologies (FET) The roots of innovation Proactive initiative on:
Lecture 7: Requirements Engineering
1 Introduction to Software Engineering Lecture 1.
Design Science Research Design Science In Information Systems Research - Hevner et al. (2004) 2015/08/17 Positioning And Presenting Design Science Research.
Knowledge Representation of Statistic Domain For CBR Application Supervisor : Dr. Aslina Saad Dr. Mashitoh Hashim PM Dr. Nor Hasbiah Ubaidullah.
Software Engineering Prof. Ing. Ivo Vondrak, CSc. Dept. of Computer Science Technical University of Ostrava
By Temtim Assefa November 2013 DESIGN SCIENCE METHOD.
Systems Analysis and Design in a Changing World, Fourth Edition
Object-Oriented Software Engineering using Java, Patterns &UML. Presented by: E.S. Mbokane Department of System Development Faculty of ICT Tshwane University.
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
1-1 Software Development Objectives: Discuss the goals of software development Identify various aspects of software quality Examine two development life.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
© 2006 Pearson Addison-Wesley. All rights reserved 2-1 Chapter 2 Principles of Programming & Software Engineering.
L&I SCI 110: Information science and information theory Instructor: Xiangming(Simon) Mu Sept. 9, 2004.
Lecture 14 22/10/15. The Object-Oriented Analysis and Design  Process of progressively developing representation of a system component (or object) through.
Introduction to HCI Lecture #1.
to become a critical consumer of information.
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?
Design Evaluation Overview Introduction Model for Interface Design Evaluation Types of Evaluation –Conceptual Design –Usability –Learning Outcome.
Software Design and Development Development Methodoligies Computing Science.
Design Science Method By Temtim Assefa November 2014.
Algorithms and Problem Solving
Object-Oriented Software Engineering Using UML, Patterns, and Java,
Object oriented system development life cycle
Lecture Software Process Definition and Management Chapter 3: Descriptive Process Models Dr. Jürgen Münch Fall
HCI – DESIGN RATIONALE 20 November 2018.
Presentation transcript:

Design Science Method By Temtim Assefa

Design Science Paradigm It is problem-solving paradigm Deals with the ‘design’ of artificial artifacts (i.e., IT artifacts) and creating something new that does not yet exist. design is both a process (set of activities) of ‘creating something new’ and a product (i.e., the artifact that results out of this process) It is one type of research Methdology

Design Science focuses on the development and performance of (designed) artifacts with the explicit intention of improving the functional performance of the artifact. Applied to categories of artifacts including (but not limited to) algorithms, human/computer interfaces, design methodologies (including process models) and languages. Commonly applied in the Engineering and Computer Science disciplines, Natural sciences and social sciences try to understand reality Also applied in many disciplines and fields

Design Science Methodology Include three elements: conceptual principles to define what is meant by design science research, Practice rules, and a process for carrying out and presenting the research.

Conceptual Principles “Design science…creates and evaluates IT artifacts intended to solve identified organizational problems It involves a rigorous process to design artifacts to solve observed problems, to make research contributions, to evaluate the designs, and to communicate the results to appropriate audiences Artifacts may include constructs, models, methods, and instantiations might also include social innovations or new properties of technical, social, and/or informational resources

Practice Rules Hevner et al. [20] provided seven guidelines (practice rules) that describe characteristics of well carried out design science research. research must produce an “artifact created to address a problem the artifact should be relevant to the solution of unsolved business problem Its “utility, quality, and efficacy ” must be rigorously evaluated Provide a verifiable contribution and

Practice … rigor must be applied in both the development of the artifact and its evaluation The development of the artifact should be a search process that draws from existing theories and knowledge to come up with a solution to a defined problem the research must be effectively communicated to appropriate audiences

Procedures Refer to the standard steps design researcher should follow to develop an artifact that can solve the stated problem at the beginning.

Design research process How to Knowledge Process Iterations Theory Inference Identify Problem & Motivate Define Problem Show Importance Define Objectives of a Solution What would a Better Artifact Accomplish? Design & Development Artifact Disciplinary Knowledge Metrics, Analysis Demonstration Find Suitable context Use Artifact to Solve problem Evaluation Observe How Effective, efficient Iterate Back to design Communica-tion Scholarly Publications Professional Publications

Design Science Research outputs Constructs conceptual vocabulary of a problem/solution domain Methods algorithms and practices to perform a specific task Algorithm is step-by-step procedure for calculations. Algorithms are used for calculation, data processing, information retrieval and automated reasoning

Outputs … Models a set of propositions or statements expressing relationships among constructs abstractions and representations Instantiations constitute the realization of constructs, models and methods in a working system implemented and prototype systems Algorithmic codes with target language software Better theories - artifact construction

Design research outputs constructs Better theories models emergent theory about embedded phenomena models methods constructs better theories abstraction abstraction knowledge as operational principles abstraction artifact as situated implementation instatiations methods constructs [Purao , 2002]

1. Problem identification Define the specific research problem and justify the value of a solution Help to develop an effective artifact and atomize the problem Help to capture problem complexity Justification of the solution motivates the researcher as well as audiences to accept the result Resources Required Knowledge of the state of the problem and the importance of its solution

Example 1: Problem identification Distance learning puts learners in Isolation, lack of observation by teachers and more freedom to learners Researchers in distance learning are interested to develop collaborative tools that supports student interactions This is not sufficient, collaboration among tutors is also necessary for effective distance learning No system so far that supports tutors

Example 2 – Amharic Due to the advent of the Internet, many Amharic documents are now available online. Additionally, the popular search engine Google, has provided an Amharic interface. However, to date, no tolerant-retrieval mechanism based on spelling correction has been employed for Amharic; and even there is no published prior work regarding spelling correction for the Amharic language.

2. Define the objectives for a solution Infer the objectives of a solution from the problem definition and knowledge of what is possible and feasible Objectives can be measurable e.g., terms in which a desirable solution would be better than current ones, qualitative, e.g., a description of how a new artifact is expected to support solutions to problems not hitherto addressed Generally good to have Specific, Measurable, Achievable, Reliable and Time bound (SMART) objectives Inputs ----- knowledge of the state of problems and current solutions, if any, and their efficacy.

Objectives Example 1 - collaborative tools To develop a collaborative tools supports tutors in distance education Example 2 – Amharic to develop an Amharic spelling corrector to assist in the development of tolerant-retrieval Amharic search systems

3. Design and development Create the artifact, such as constructs, models, methods, or instantiations or “new properties of technical, social, and/or informational resources” This activity includes determining the artifact’s desired functionality and its architecture and then creating the actual artifact Resources required Knowledge of theory that can be brought to bear in a solution

Example 1 – Computer Supported Collaborative tutoring tool (CSCTT)

CSCTT Architecture

Solution Description This system consists of a manager of collaboration requests that manages the requests issued by the tutor. when the tutor receives an assistance request from a learner, this tutor has the opportunity to work in group and collaborate with another member of his group who has the specified role or tutor (according to the type of assistance request).

Example - Demonstration

Example 2 – Construction of Amharic Dictionary

Compute Amharic Metaphone code, W_Code Get Word Compute Amharic Metaphone code, W_Code If no similar W_code Yes No Add W_code as a key and Word value Add W_code as Next Value If dictionary has another word Yes

Example 2…. As a further refinement, the algorithm tries to suggest replacements for a misspelled word by splitting it into two parts, and then checks whether the pair of words are valid Amharic words. If so, they are offered as a suggestion. The assumption behind this step is that users may have failed to type a blank space between words.

4. Demonstration and Evaluation Demonstration is a single act to prove that the idea works to solve one or all aspects of the problem This could involve its use in experimentation, simulation, case study, proof, or other appropriate activity Resource required Knowledge of how to use the artifact to solve the problem

Evaualtion …. Evaluation refers to the observation and measurement of how well the artifact supports a solution to the problem This activity involves comparing the objectives of a solution to actual observed results from use of the artifact in the demonstration It requires knowledge of relevant metrics and analysis techniques

Evaluation … Evaluation could take many forms. It involves comparison of the artifact’s functionality with the solution objectives For example quantitative performance measures system performance, error reduction, budget saving, customer satisfaction, client feedback, or simulations. At end of evaluation iterate back to step three to try to improve the effectiveness of the artifact or to continue on to communication and leave further improvement to subsequent projects