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

2. 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. 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. 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. 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. 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. 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. 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. 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.