90 likes | 278 Views
WEUSE I: Paradigms and Techniques. Margaret Burnett Oregon State University Project Director, EUSES Consortium. Dimensions of Paradigms and Techniques. Programming paradigms supported by EUSE Which language paradigms are we supporting and which other ones are still out there?. Auto.
E N D
WEUSE I:Paradigms and Techniques Margaret BurnettOregon State University Project Director, EUSES Consortium
Dimensions of Paradigms and Techniques • Programming paradigms supported by EUSE • Which language paradigms are we supporting and which other ones are still out there?
Auto. Detected Errors Prevented Errors Collaboratively Detected Errors Dimensions (cont.) • 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?
Software Engineering and Languages HCI and Psychology Education Dimensions (cont.) • 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.
Dimensions (cont.) • 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.
Session Format • Discuss relevant work via these dimensions: • Programming paradigms supported by EUSE. • Paradigms for use of EUSE techniques. • Paradigms of EUSE research. • Techniques and what they support. • Desired outcome: • Better understand open issues, unexplored areas. • Increase attention to each other’s progress, decrease/avoid reinventing.
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.
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.
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.