WEUSE I: Paradigms and Techniques Margaret Burnett Oregon State University Project Director, EUSES Consortium.

Slides:

Advertisements

Similar presentations

Debugging in End- User Software Engineering summarized by Andrew Ko Toward Sharing Reasoning to Improve Fault Localization in Spreadsheets Joey Lawrance,

Advertisements

END USER SOFTWARE ENGINEERING Presented By Dinesh Amarneni Vipin Deshmukh.

© Chinese University, CSE Dept. Software Engineering / Software Engineering Topic 1: Software Engineering: A Preview Your Name: ____________________.

4.1 Blended approaches: Information Engineering IMS Information Systems Development Practices.

RSS Part Two ACE 2004 June 21, Versions of RSS

MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )

McGraw-Hill/Irwin Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Chapter 14 Programming and Languages.

Cambridge Spreadsheet Quality Foundations of Spreadsheet Workshop 2004 Margaret Burnett Oregon State University and the EUSES Consortium.

1 st WEUSE Lessons Learned Sebastian Elbaum. Motivation End-user programmers create large amounts of software in the form of spreadsheets, web authoring.

Recall The Team Skills 1. Analyzing the Problem 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 5. Refining the System.

Oregon State University School of Electrical Engineering and Computer Science End-User Programming of Intelligent Learning Agents Prasad Tadepalli, Ron.

13.1 © 2007 by Prentice Hall 13 Chapter Building Systems.

Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.

Software Design by Dr. Eitan Hadar Web:

An Introduction to Software Visualization Dr. Jonathan I. Maletic Software DevelopMent Laboratory Department of Computer Science Kent State University.

The End-User Software Engineering Vision Margaret Burnett Professor, Oregon State University Project Director, EUSES Consortium

Programming and Languages Chapter Competencies (Page 1 of 2) Describe the six steps of programming Discuss design tools including top-down design,

Some Introductory Programming 1. Structured Query Language - used for queries. - a standard database product. 2. Visual Basic for Applications - use of.

Why does the spreadsheet work … … and how can we improve it? A user interface perspective on the foundations of spreadsheets. Alan Blackwell Computer Laboratory.

Business Rules INFS 770 – KM for E-Business Professor L. Kerschberg Spring 2004.

Process-oriented System Automation Executable Process Modeling & Process Automation.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 System and Software Engineering.

Succeeding as a Systems Analyst, Roles Class 2. First, some definitions Systems Development Specifying in detail how the many components of the information.

©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 19Slide 1 Verification and Validation l Assuring that a software system meets a user's.

CW-V1 SDD 0201 Principals of Software Design and Development Introduction to Programming Languages.

DIVERSE Ben Trott Max Woollard 26 th October 2011.

CS 4310: Software Engineering Lecture 3 Requirements and Design.

Verification and Validation Yonsei University 2 nd Semester, 2014 Sanghyun Park.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 22 Slide 1 Verification and Validation.

1. Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2.

Chapter 2 The process Process, Methods, and Tools

Appendix D McGraw-Hill/Irwin Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.

Introduction to SDLC: System Development Life Cycle Dr. Dania Bilal IS 582 Spring 2009.

Ed Hardick Director of Marketing/ Product Support.

ASG - Towards the Adaptive Semantic Services Enterprise Harald Meyer WWW Service Composition with Semantic Web Services

 CS 5380 Software Engineering Chapter 8 Testing.

Steve Dower Software Engineer Python Tools for Visual Studio.

Chapter 1: Overview of Workflow Management Dr. Shiyong Lu Department of Computer Science Wayne State University.

Computing Essentials 2014 Programming and Languages © 2014 by McGraw-Hill Education. This proprietary material solely for authorized instructor use. Not.

Software Engineering 2 Software Testing Claire Lohr pp 413 Presented By: Feras Batarseh.

CSC 395 – Software Engineering Lecture 10: Execution-based Testing –or– We can make it better than it was. Better...faster...agiler.

Verification and Validation Assuring that a software system meets a user's needs.

Programming and Languages

Best practices from The Coca-Cola Company in using technology for improving change management Saurabh Parikh, Director BI & Appdev, Coca-Cola Chris Trueman,

P6 BTEC Level 3 Subsidiary Diploma in ICT. Automation The end user of a spreadsheet may be proficient in using the software, but the more that you automate.

Chapter 2.11 Program Validation. Reliable System = Reliable Hardware AND Reliable Software AND Compatible Hardware and Software.

X3D: Real Time 3D Solution for the web Web3D Tech Talk – SIGGRAPH 2008 Octaga Bringing enterprise data to life.

CSI 1340 Introduction to Computer Science II Chapter 1 Software Engineering Principles.

Objectives 4 Identify the meaning of software maintenance and it’s importance in the project life cycle 4 Understand why maintenance is needed.

A way to develop software that emphasizes communication, collaboration, and integration between development and IT operations teams.

Procedural programming Procedural programming is where you specify the steps required. You do this by making the program in steps. Procedural programming.

In today’s lesson we will be looking at: what we mean by the software development lifecycle the phases in the lifecycle We will focus particularly on testing:

2014 Empowering the People (ACM SigCHI) Margaret Burnett Oregon State University October 2014 #GHC

Softdial Contact Center Guide

The Components of Information Systems

The Software Development Cycle

Verification and Validation

The Components of Information Systems

ADMIN TRAINING SESSION

Systems Design, Implementation, and Operation

SDLC The systems development life cycle is the foundation for many systems development methodologies such as RAD and agile Systems development life cycle.

COS 260 DAY 16 Tony Gauvin.

Defense Automatic Addressing System (DAAS)

Developing Web Specifications

Chapter 2. Problem Solving and Software Engineering

Information System Building Blocks

THE OLD WAY AND THE NEW Conventional software engineering has numerous well-established principles. Many are still valid; others are obsolete. A modern.

The Software Development Cycle

E Pluribus Unum for end-user programming

Presentation transcript:

WEUSE I: Paradigms and Techniques Margaret Burnett Oregon State University Project Director, EUSES Consortium

2 May 21, 2005Margaret Burnett Dimensions of Paradigms and Techniques 1. Programming paradigms supported by EUSE Which language paradigms are we supporting and which other ones are still out there?

3 May 21, 2005Margaret Burnett Dimensions (cont.) 2. Paradigms for use of EUSE techniques What problem-solving approaches are we supporting with our techniques? eg, declarative versus procedural approaches? eg, automated versus user-led approaches? Prevented Errors Auto. Detected Errors Collaboratively Detected Errors

4 May 21, 2005Margaret Burnett Dimensions (cont.) 3. Paradigms of doing EUSE research HCI perspective: bring in SE/analysis. SE/analysis perspective: bring in HCI. Both are valid -- when both are talking to each other. Software Engineering and Languages HCI and Psychology Education

5 May 21, 2005Margaret Burnett Dimensions (cont.) 4. Techniques -- what support they offer. Software lifecycle view: requirements, design, coding, testing, debugging, maintenance. Task-oriented view: creating new programs, comprehending old ones, adding new features, finding/fixing errors. Degree of automation view: system, user, or both.

6 May 21, 2005Margaret Burnett Session Format Discuss relevant work via these dimensions: 1. Programming paradigms supported by EUSE. 2. Paradigms for use of EUSE techniques. 3. Paradigms of EUSE research. 4. Techniques and what they support. Desired outcome: Better understand open issues, unexplored areas. Increase attention to each other’s progress, decrease/avoid reinventing.

7 May 21, 2005Margaret Burnett The Landscape (Turn to the handout for details.) Language paradigms represented: Spreadsheets, web services, MatLab, screen transitions, scientific, database, grid, control flow, dataflow, event. Paradigms for use of EUSE techniques: automatic, collaborative, user (supported). What vs. how: about 50/50.

8 May 21, 2005Margaret Burnett The Landscape (cont.) Paradigms of research: Analysis + people. Focus mainly on analysis. Focus mainly on people. Focus on market needs. Lifecycle/tasks supported: Create, test, debug, automate failure/fault detection. Little on requirements, maintenance, design.

9 May 21, 2005Margaret Burnett Summary/Take-Aways One mark of a successful research subarea: Shared understanding of the current state. Attention to each other’s progress, presence of citations within the subarea, not reinventing same wheel. A desired outcome today: Provide means for continued and increasing progress.