1 st weuse lessons learned
Download
Skip this Video
Download Presentation
1 st WEUSE Lessons Learned

Loading in 2 Seconds...

play fullscreen
1 / 7

1 st WEUSE Lessons Learned - PowerPoint PPT Presentation


  • 71 Views
  • Uploaded on

1 st WEUSE Lessons Learned. Sebastian Elbaum. Motivation. End-user programmers create large amounts of software in the form of spreadsheets, web authoring tools, matlab, … The software these users create is often undependable

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' 1 st WEUSE Lessons Learned ' - oliana


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
1 st weuse lessons learned

1stWEUSELessons Learned

Sebastian Elbaum

motivation
Motivation
  • End-user programmers create large amounts of software in the form of spreadsheets, web authoring tools, matlab, …
  • The software these users create is often undependable
  • Existing software engineering techniques and tools are not directly suitable to assist them
  • WEUSE aims at helping researchers to
    • understand problems faced by end-user programmers
    • be aware of latest developments in this area
    • establish connections with other researchers
what we agree on small list
What we agree on(small list)
  • Multidisciplinary nature of research problem
  • Interesting and valuable
qualified agreements on end user programmers
Qualified Agreementson end user programmers
  • End users are NOT like us
    • But in some domains…
  • Shallow programmers
    • How shallow? Gray areas…
  • Short-term view of life cycle
    • Difference from average programmer?
  • They know their domain
    • But they may not be able to explain it
awareness of dimensionality of small community
Awareness of dimensionalityof small “community”
  • Environments (web, spreadsheet, matlab, flow, …)
  • Usage (ways and levels of interaction)
  • Research (analytical, empirical on people, empirical on techniques, combinations)
  • Task-phase (lifecycle tasks, activities, objectives)
action items
Action items
  • Characterize end user population
  • Define “sufficient” dependability
  • Focus on cost-effectiveness
  • Build collage of studies for technique assessment,balance of control, cost and exposure
  • Build community
    • To accelerate progress
    • To promote ideas and raise awareness of impact
thank you
Thank you
  • PC members
    • Alan Blackwell, University of Cambridge
    • Margaret Burnett, Oregon State University
    • Jeffrey Carver, Mississippi State University
    • Prem Devanbu, University of California, Davis
    • Shriram Krishnamurthi, Brown University
    • Rob Miller, Massachusetts Institute of Technology
    • Brad Myers, Carnegie Mellon University
    • Orna Raz, Carnegie Mellon University
  • Theme leaders
    • Margaret Burnett, Oregon State University
    • Mary Shaw, Carnegie Mellon University
    • Brad Myers, Carnegie Mellon University
    • Gregg Rothermel, University of Nebraska, Lincoln
  • PARTICIPANTS!
ad