Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software...

58
ICSE 2009 1 Reflections on 40+ years of software engineering research and beyond an insider's view Carlo Ghezzi DeepSE Group Dipartimento di Elettronica e Informazione Politecnico di Milano, Italy carloghezzi@polimiit

Transcript of Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software...

Page 1: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

ICSE 2009 1

Reflections on 40+ years of software engineering research and beyond

an insider's view Carlo Ghezzi DeepSE Group Dipartimento di Elettronica e Informazione Politecnico di Milano, Italy carloghezzi@polimiit

Page 2: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Outline of the talk

ICSE 2009 2

•  A journey through 40+ years of software engineering research, mostly observed through ICSE

•  What did we produce? •  How can their success (impact) be "defined"? •  How can it be measured? •  What can we learn from past? •  Can we do better? •  Will the paradigms followed in the past survive in the

future?

Page 3: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Part 1: Looking backwards

•  Where does ICSE come from?

•  What can we learn by mining ICSE data?

ICSE 2009 3

Page 4: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

A bit of history •  The roots are in the NATO meetings in Garmisch-Partenkirchen (1968)

and Roma (1969) •  ICSE started in 1975, this is the 31-st

–  first conference called ICSE is actually ICSE2 •  ICSE1 was NCSE---1st National Conf on Software Engineering, Sept 1975

–  became annual in 1987 •  TSE started in March 1975 •  ESEC started in 1987, FSE started in 1993, they joined in 1997 •  TOSEM started in January 1992

ICSE 2009 4

Page 5: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Mining ICSE data •  International Conference on Software Engineering

–  How much international? –  How are the different engineering research stakeholders

(academia, industry) represented? •  scientific leadership, contributors

•  Paper demographics –  Is ICSE an attractive venue?

•  Research areas –  How did they evolve?

ICSE 2009 5

Page 6: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

ICSE PCs

ICSE 2009 6

avg

1

12

32

55

Page 7: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

ICSE PCs: industry/academia

ICSE 2009 7

Page 8: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

ICSE 2009 8

average 44

Page 9: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Submitted/accepted

ICSE 2009 9

Page 10: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

ICSE papers: geographical distribution

ICSE 2009 10

average 1% 10% 24% 65%

Page 11: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Papers: industry vs. academia

ICSE 2009 11

average AC 70% IND 30%

average 1976-1994 AC 56% IND 44%

average 1995-2008 AC 83% IND 17%

Page 12: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Preliminary findings ICSE is nurtured by an international community

PC

papers

High number of submissions, high selection rate There is a consensus that ICSE is a prestigious venue

ICSE 2009 12

NorthAmerica Europe AsiaPacific RestOfWorld 55% 32% 12% 1% 46% 40% 11% 3%

NorthAmerica Europe AsiaPacific RestOfWorld 65% 24% 10% 1% 60% 27% 11% 2%

all -5 yrs

all -5 yrs

Page 13: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Preliminary findings

•  Industry participation decreased over time –  research labs of large corporations disappeared –  ICSE became more research oriented

•  initially: tool fair •  then: tutorials •  now: workshops

–  now mostly co-authored papers (academia/industry)

ICSE 2009 13

Page 14: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 14

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 15: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 15

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 16: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 16

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 17: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 17

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 18: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 18

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 19: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 19

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 20: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Topics

ICSE 2009 20

Topic %

Testing&Analysis 17

Design&Software Architecture 17

Specification&Verification 15

Tools&SDEs 11

Management&Costs 9

Empirical Studies 7

Existing Systems 6

Others (13 topics) 18

Page 21: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Programming languages

ICSE 2009 21

Page 22: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Some findings

•  Large variety of topics •  Trend from "methodology oriented", informal approaches to

systematic and formally-based approaches •  Increased attention on empirical evaluations •  Still little on paradigmatic examples or domain-specific

approaches

ICSE 2009 22

Page 23: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Can we identify our best products?

•  Which criteria to follow? – Quantitative

•  Citation count •  Downloads count •  Others?

– Qualitative •  Most influential -10 years? •  Others?

ICSE 2009 23

Page 24: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Quantitative criteria •  Citation count

–  date of count Jan-March 2009 –  source Google Scholar –  version (conference/journal) both (if j expands c) –  precision ???

•  Number of downloads –  date, period Jan-March 2009, 12 months –  source ACM digital library –  version conference –  precision ???

ICSE 2009 24

Page 25: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Outstanding products based on citations 1.  Program slicing (ICSE'81) 2120 2.  Statemate: a working environment for the development of complex

reactive systems (ICSE'88) 1170 3.  N degrees of separation: multi-dimensional separation of concerns

(ICSE'99) 997 4.  Bandera : extracting finite-state models from Java source code

(ICSE'00) 791 5.  Software processes are software too (ICSE'87) 688 6.  Managing the development of large software systems: concepts and

techniques (ICSE'87) 667 7.  Executable object modeling with statecharts (ICSE'96) 622 8.  Designing software for ease of extension and contraction (ICSE'78) 605

ICSE 2009 25

Page 26: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Citations vs expert judgment most influential papers

ICSE 2009 26

1.  Program slicing (ICSE'81) 2120 2.  Statemate: a working environment for the development of complex

reactive systems (ICSE'88) 1170 3.  N degrees of separation: multi-dimensional separation of concerns

(ICSE'99) 997 4.  Bandera : extracting finite-state models from Java source code

(ICSE'00) 791 5.  Software processes are software too (ICSE'87) 688 6.  Managing the development of large software systems: concepts and

techniques (ICSE'87) 667 7.  Executable object modeling with statecharts (ICSE'96) 622 8.  Designing software for ease of extension and contraction (ICSE'78) 605

Page 27: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

MIP vs citations

ICSE 2009 27

380

Page 28: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

How do we compare with others?

ICSE 2009 28

Citations of most influential papers

Page 29: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

#Downloads (-12 months)? From ACM DL

1.  Automated Support for Development, Maintenance, and Testing in the Presence of Implicit Control Flow (ICSE'04): 781---13 cit

2.  Managing the development of large software systems: concepts and techniques (ICSE'87): 705---667 cit

3.  New directions on agile methods : a comparative analysis (ICSE'03): 567---161 cit

4.  Program slicing (ICSE'81): 520---2120 cit 5.  Quantitative evaluation of software quality ICSE'76: 495---212 cit 6.  Static detection of cross-site scripting vulnerabilities ICSE'08---396---8 cit 7.  Analysis and testing of Web applications ICSE'01: 375---195 cit 8.  Aspect-oriented programming and modular reasoning: ICSE'05: 300---32cit

ICSE 2009 29

Page 30: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Findings: #citations vs. #downloads •  Time factor (both #citations an #downloads)

–  my Jan-March numbers are different from the current ones –  how can you compare #cit of a 20 years and a 2 years old

paper? •  No significant correlation between citations and downloads •  #citations and #downloads express different merits

•  example: a highly downloaded paper may be useful in practice, but does not inspire further research

•  #downloads demonstrates longevity of ICSE contributions •  3 out of the top 5 highest #downloads are papers over 20 years

old, one is more than 30 ICSE 2009 30

Page 31: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Findings: #citations vs. expert judgment •  Citations and expert judgment are better correlated,

according to the ICSE experience – most highly cited papers have been recognized

as influential – …but several influential papers have low citations

ICSE 2009 31

Page 32: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

What do the numbers tell us? Do they indicate impact?

•  Does the number of paper citations indicate impact of a piece of work?

•  Do citations of papers in a journal/proceedings indicate impact of a venue?

•  Do citations of one's research measure impact of that research?

ICSE 2009 32

Page 33: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Part 2: A side road on numbers/citations

Joint Committee on Quantitative Assessment of Research Report CITATION STATISTICS Intl Mathematical Union (IMU) in cooperation with Intl Council of Industrial and Applied Math (ICIAM) and the Institute of Mathematical Statistics (IMS), 6/12/2008

R. Adler, J. Ewing, P. Taylor (Eds.)

ICSE 2009 33

Page 34: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

A side road on numbers/citations

Informatics Europe Report RESEARCH EVALUATION FOR COMPUTER SCIENCE Viewpoint article in CACM, April 2009 Eds. B. Meyer, C. Choppy, J. Staunstrup, J. van Leewen (Eds.)

Also D. Parnas, CACM nov 2007 STOP THE NUMBERS GAME

ICSE 2009 34

Page 35: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Facts •  Numbers increasingly used to assess/rank

–  papers –  journals and conferences---the (in)famous impact factor –  individuals

•  Motivations –  different stakeholders need to evaluate research –  peer review can be subjective –  peer review is expensive –  numbers are simple and objective

ICSE 2009 35

simplistic and misleading

Page 36: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Findings •  Much of the modern bibliometrics is flawed (statistics

improperly used) •  Objectivity and accuracy illusory

–  the meaning of a citation can be even more subjective than peer review

•  Sole reliance on citation data provides incomplete and shallow understanding of research –  only valid if reinforced by other judgments

ICSE 2009 36

numbers are not inherently superior to and cannot substitute complex judgement

Page 37: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Why are citations counted? From Thomson Scientific

"The value of information is determined by those who use it…the better way to measure the quality of work is by measuring the impact it makes on the community at large"

The statement makes an implicit equivalence assumption #citations = impact

ICSE 2009 37

Page 38: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Citations vs impact

•  Is the equality #citations = impact

justified? (When) does it work? •  It presupposes a highly rational and uniform model of

reference giving, but this is NOT true

ICSE 2009 38

Page 39: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

The complex sociology of citations Average citations per article

ICSE 2009 39

citation practices differ substantially among disciplines

Page 40: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

The complex sociology of citations

•  Citations are of two main kinds –  REWARD

•  intellectual dependency on the cited –  RHETORICAL

•  a way to carry out a scientific conversation –  reference included to show that topic is of interest to someone else or

to prove that the author knows the literature –  the cited explains some result, not necessarily of the cited author –  the cited represents another approach, or is an example of…

ICSE 2009 40

Page 41: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

The complex sociology of citations

•  Most citations are rhetorical •  Reward citations can be of many kinds

–  currency, negative credit, operational information, persuasiveness, positive credit, reader alert, social consensus

•  Obliteration effect –  incorporated into other work, which is cited

ICSE 2009 41

Page 42: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

An example

•  The impact of MESA on system design, by HC Lauer, EH Satterthwaite, ICSE'79 –  60 cit (highest of '79), 19 downloads … one of the few

papers on MESA BUT

•  Its impact evidenced by indirection –  Implementing remote procedure calls, by Birrell&Nelson,

ACM TOCS 1984, 1840 citations •  explicitly states its debt to MESA

ICSE 2009 42

Page 43: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

If impact is the question, are (citation) numbers the answer?

•  Citation data and statistics provide some valuable information –  very high citation numbers tell more than smaller

but only a limited and incomplete view of research quality •  Statistics derived from them often poorly understood and

misused •  Expert judgment cannot be eliminated •  Research too important to measure only with a coarse

tool ICSE 2009 43

Page 44: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Lost in the journey?

•  We started by looking back at SE research through ICSE as a magnifying lens

•  We tried to assess what we accomplished by identifying our impactful results

•  We got trapped by the number game

ICSE 2009 44

Should we look for better assessment methods? Why?

Page 45: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Should we care? •  Our social responsibility is to care about impact of research

–  understanding – measuring –  improving

•  If we don't, others will do –  governments, funding bodies

•  accountability, "return" to taxpayer or donor –  universities, schools, departments

•  competition (CS versus other sciences, SE versus other CS areas)

ICSE 2009 45

Page 46: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Part 3: Where do we go from here?

Towards •  understanding •  measuring •  improving impact of SE research

ICSE 2009 46

Page 47: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Do we understand what impact is? How can we measure it?

•  Not quite •  A notable counter-example

–  IMPACT project •  aims at demonstrating impact of SE research on practice •  focuses on specific research areas in SE

–  an initiative of ACM SIGSOFT •  the SIGSOFT Impact project.webarchive

–  area leaders responsible for research –  backed by sound science history methodology

ICSE 2009 47

Page 48: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Published results •  Osterweil, L.J., Ghezzi, C., Kramer, J., Wolf, A.L. Determining the Impact of Software

Engineering Research on Practice . IEEE Computer, March 2008. •  Estublier, J., Leblang, D., Hoek, A., Conradi, R., Clemm, G., Tichy, W., and Wiborg-Weber,

D.Impact of software engineering research on the practice of software configuration management. ACM TOSEM, Oct. 2005.

•  Ryder, B. G., Soffa, M. L., and Burnett, M. The impact of software engineering research on modern progamming languages. ACM TOSEMl, Oct. 2005.

•  Emmerich, W., Aoyama, M., Sventek, J. The Impact of Research on the Development of Middleware Technology. ACM TOSEM, August 2008.

•  Clarke, L. A. and Rosenblum, D. S. Historical Perspective on Runtime Assertion Checking in Software Development. SIGSOFT SEN, March 2008.

•  Rombach, D., Ciolkowski, M., Jeffery, R., Laitenberger, O., McGarry, F., Shull, S. Impact of research on practice in the field of inspections, reviews and walkthroughs: learning from successful industrial uses. In ACM SIGSOFT SEN, November 2008.

ICSE 2009 48

Page 49: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Some key findings/confirmations •  SE research has had impact on SE practice •  Maturation needs time

–  15-20 years between first publication of an idea and widespread availability in products

•  Substantially different mechanisms have been successful at causing impact –  people are key to knowledge transmission

•  people movement •  almost all impact traces lead back to PhD theses

49 ICSE 2009

Page 50: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Problems with impact definition/measurement

•  Scholarly assessment of impact of SE research on practice is a difficult and expensive –  it is research

•  Substantially different methods are needed to assess impact of –  journals/conference –  individual researchers/papers

ICSE 2009 50

Page 51: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Obstacles to impact •  The dominant reward/recognition system based on

publication count does not favor impact –  from D. Parnas, CACM 2007

•  "it encourages superficial research" •  "it encourages small, insignificant results" •  "it rewards publication of half-baked ideas" •  "it slow scientific progress: to increase their score,

researchers must avoid tackling the tough problems and problems that will require years of dedicated work and instead work on easier ones"

ICSE 2009 51

Page 52: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Obstacles to impact

•  Building on top of others' work too often too difficult or impossible –  TOSEM papers 2001-2006

•  60% refer to a tool, only 20% installable •  ICSE'06 paper by Zannier, Melnik, Maurer evaluates ICSE

empirical studies •  complete absence of replicated studies •  self-evaluations dominate empirical studies

ICSE 2009 52

Page 53: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Conclusions: on impact •  Research on impact of SE research must continue and

should become a community effort •  As a community we need to get to a common

understanding and articulate methods for definition and measurement of impact for –  journals/conferences –  individual research

•  define impactful research products beyond paper count •  We must be aware of risks

–  be rigorous, avoid being incestuous ICSE 2009 53

Page 54: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Conclusions: on enhancing research flow •  Define community challenges and support repeated

experiments –  catalogs of case-studies on which competing

approaches can be applied and compared •  Favor research products backed by tools, but verify that the

claimed results of their use can be replicated •  Use Internet facilities for community support

–  research-as-service •  Reward successful reuse of one's research rather than

paper citation ICSE 2009 54

Page 55: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

The end of the journey

ICSE 2009 55

In 40+ years we have gone far

Page 56: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Beginning of a new journey

ICSE 2009 56

We have been successful, but we can do more and better

Towards impact-aware research Can the ICSE community take the lead of this?

Page 57: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Acknowledgements

•  L. Osterweil, J. Kramer, A. Wolf and IMPACT project members for their insights into impact of research

•  Andrea Mocci, Mattia Monga, for helping me in mining data

ICSE 2009 57

Page 58: Reflections on 40+ years of software engineering research and beyond · 2009-05-24 · 5. Software processes are software too (ICSE'87) 688 6. Managing the development of large software

Thank you!!!

ICSE 2009 58