Evolving the Software Engineering Toolbox CHRISTOPH REICHENBACH

Transcription

1 Evolving the Software Engineering Toolbox CHRISTOPH REICHENBACH

2 CV Highlights Helping software engineers with their everyday problems TU Darmstadt Student CU Boulder PhD Student PhD, Program Metamorphosis (Amer Diwan) UMass Amherst Postdoc Google Mountain View SW Engineer U Frankfurt Junior Professor R 2 Software & Systeme, Frankfurt CTO/CEO Lund U / LTH, WASP Senior Lecturer Oct 2017 Christoph Reichenbach Evolving the SE Toolbox 10th January /22

3 CV Highlights Helping software engineers with their everyday problems Automate: Dull, Dirty, Dangerous TU Darmstadt Student CU Boulder PhD Student PhD, Program Metamorphosis (Amer Diwan) UMass Amherst Postdoc Google Mountain View SW Engineer U Frankfurt Junior Professor R 2 Software & Systeme, Frankfurt CTO/CEO Lund U / LTH, WASP Senior Lecturer Oct 2017 Christoph Reichenbach Evolving the SE Toolbox 10th January /22

4 CV Highlights Helping software engineers with their everyday problems Automate: Dull, Dirty, Dangerous, Difficult TU Darmstadt Student CU Boulder PhD Student PhD, Program Metamorphosis (Amer Diwan) UMass Amherst Postdoc Google Mountain View SW Engineer U Frankfurt Junior Professor R 2 Software & Systeme, Frankfurt CTO/CEO Lund U / LTH, WASP Senior Lecturer Oct 2017 Christoph Reichenbach Evolving the SE Toolbox 10th January /22

5 Software is Big 100 > (avionics) Approx. source code size in million lines of code, Jan Christoph Reichenbach Evolving the SE Toolbox 10th January /22

6 and Software Engineering Software Engineering REQUIREMENTS DESIGN IMPLEMENTATION VALIDATION MAINTENANCE Christoph Reichenbach Evolving the SE Toolbox 10th January /22

7 and Software Engineering Software Engineering REQUIREMENTS Customer Requirements DESIGN IMPLEMENTATION VALIDATION MAINTENANCE HW hardware Christoph Reichenbach Evolving the SE Toolbox 10th January /22

8 and Software Engineering Software Engineering REQUIREMENTS DESIGN IMPLEMENTATION SWE Team VALIDATION Requirements MAINTENANCE HW hardware Christoph Reichenbach Evolving the SE Toolbox 10th January /22

9 and Software Engineering Software Engineering REQUIREMENTS DESIGN IMPLEMENTATION SWE Team VALIDATION Requirements artefacts SW source code MAINTENANCE HW hardware Christoph Reichenbach Evolving the SE Toolbox 10th January /22

10 and Software Engineering Requirements SW HW hardware Christoph Reichenbach Evolving the SE Toolbox 10th January /22

11 and Software Engineering Requirements SW Bug finding Formal Methods MDSE Domain-Specific Languages Integrated Development Environments Program Transformation Program Understanding HW hardware Compilers Profilers Christoph Reichenbach Evolving the SE Toolbox 10th January /22

12 and Software Engineering Requirements SW Bug finding Formal Methods MDSE Domain-Specific Languages Languages Integrated Development Environments Program Transformation Program Understanding HW hardware Compilers Profilers Christoph Reichenbach Evolving the SE Toolbox 10th January /22

13 and Software Engineering Requirements SW Bug finding Formal Methods MDSE Domain-Specific Languages Languages Integrated Development Environments Program Transformation Program Understanding HW hardware Compilers Profilers Christoph Reichenbach Evolving the SE Toolbox 10th January /22

14 : Predictive and Precise Bug Detection with: Kaituo Li (U Massachusetts, Amherst) Christoph Csallner (U Texas at Arlington) Yannis Smaragdakis (U Athens) In ISSTA 2012 (Best Paper Award), ACM TOSEM Volume 24 Issue 2, Christoph Reichenbach Evolving the SE Toolbox 10th January /22

15 Common Bug Patterns try { target.write(data); } catch (IOException e) { /* error ignored */ } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

16 Common Bug Patterns try { target.write(data); } catch (IOException e) { /* error ignored */ } Detected by Static Checker Findbugs: Dropped Exception Christoph Reichenbach Evolving the SE Toolbox 10th January /22

17 Common Bug Patterns try { target.write(data); } catch (IOException e) { /* error ignored */ } Detected by Static Checker Findbugs: Dropped Exception A.java B.java C.java D.java E.java Christoph Reichenbach Evolving the SE Toolbox 10th January /22

18 Common Bug Patterns try { target.write(data); } catch (IOException e) { /* error ignored */ } Detected by Static Checker Findbugs: Dropped Exception A.java B.java C.java D.java E.java Christoph Reichenbach Evolving the SE Toolbox 10th January /22

19 Common Bug Patterns try { target.write(data); } catch (IOException e) { /* error ignored */ } Detected by Static Checker Findbugs: Dropped Exception A.java B.java C.java D.java E.java Objection! False Positive: what if B, C, D can actually never fail? Christoph Reichenbach Evolving the SE Toolbox 10th January /22

20 Our Solution: Static Checker Tests Program Christoph Reichenbach Evolving the SE Toolbox 10th January /22

21 Our Solution: Static Checker Tests Program Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Christoph Reichenbach Evolving the SE Toolbox 10th January /22

22 Our Solution: Static Checker Tests Program Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Possible Objections Christoph Reichenbach Evolving the SE Toolbox 10th January /22

23 Our Solution: Static Checker Tests Program Instrument Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Possible Objections Christoph Reichenbach Evolving the SE Toolbox 10th January /22

24 Our Solution: Static Checker Tests Run Analyse Program Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Christoph Reichenbach Evolving the SE Toolbox 10th January /22

25 Our Solution: Static Checker Tests Run Analyse Program Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Evidence for bug Evidence against bug Christoph Reichenbach Evolving the SE Toolbox 10th January /22

26 Our Solution: Static Checker Tests Run Analyse Program prioritise Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Evidence for bug Evidence against bug Christoph Reichenbach Evolving the SE Toolbox 10th January /22

27 Our Solution: Static Checker Tests Run Analyse Program prioritise Bug: B.java: HE Bug: ACL.java: CN Bug: N.java: HE Bug: CPU.java: RR Bug: D.java: CN Evidence for bug Evidence against bug remove/deprioritise Christoph Reichenbach Evolving the SE Toolbox 10th January /22

28 Other Patterns Many patterns in FindBugs admit : Dropped Exception Christoph Reichenbach Evolving the SE Toolbox 10th January /22

29 Other Patterns Many patterns in FindBugs admit : Dropped Exception Equal Objects Must Have Equal Hashcodes Bad Covariant Definition of Equals Equals Method Overrides Equals in Superclass and May Not Be Symmetric Cloneable Not Implemented Correctly Non-Short-Circuit Boolean operator Read Return Should Be Checked Race Detection Christoph Reichenbach Evolving the SE Toolbox 10th January /22

30 Other Patterns Many patterns in FindBugs admit : Dropped Exception Equal Objects Must Have Equal Hashcodes Bad Covariant Definition of Equals Equals Method Overrides Equals in Superclass and May Not Be Symmetric Cloneable Not Implemented Correctly Non-Short-Circuit Boolean operator Read Return Should Be Checked Race Detection is widely applicable Christoph Reichenbach Evolving the SE Toolbox 10th January /22

31 Evaluation Tested 7 patterns Targets: JBoss, BCEL, NetBeans, Tomcat, JRuby, Apache CC, Groovy 436 static FindBugs reports dynamic evidence for 43 Dynamic reports bug non-bug undetermined 12 rejected reinforced total Christoph Reichenbach Evolving the SE Toolbox 10th January /22

32 Evaluation Tested 7 patterns Targets: JBoss, BCEL, NetBeans, Tomcat, JRuby, Apache CC, Groovy 436 static FindBugs reports dynamic evidence for 43 Dynamic reports bug non-bug undetermined 12 rejected reinforced total Non- bug reports: only 1 out of 10 were real > 75% precision with, 10% without Christoph Reichenbach Evolving the SE Toolbox 10th January /22

33 Agenda Hard to extend = Domain-Specific Language for describing bug patterns Focus on correctness = Performance bugs Focus on Java = C/C++ for High Performance Computing Reliance on heuristics = Machine Learning Christoph Reichenbach Evolving the SE Toolbox 10th January /22

34 Copy-and-Paste Redeemed with: Krishna Narasimhan (GU Frankfurt) In Automated Software Engineering (ASE), 2015 (Distinguished Paper Award) Christoph Reichenbach Evolving the SE Toolbox 10th January /22

35 int dist(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::max(dx, dy); } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

36 int dist(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::max(dx, dy); } int dist2(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::hypot(dx, dy) ; } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

37 int dist(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::max(dx, dy); } int dist2(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::hypot(dx, dy) ; } Alternative: Abstraction int distg(coord a, coord b, int (*f)(int, int) ) int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return f (dx, dy); } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

38 Copy-and-Paste vs. Abstraction Small user study (5 C++ programmers, 5 programs): Christoph Reichenbach Evolving the SE Toolbox 10th January /22

39 Copy-and-Paste vs. Abstraction Small user study (5 C++ programmers, 5 programs): Programmers preferred to see Abstraction was 2-3 times faster to build Hypothesis: More abstractions slower programmers Christoph Reichenbach Evolving the SE Toolbox 10th January /22

40 Copy-and-Paste vs. Abstraction Small user study (5 C++ programmers, 5 programs): Programmers preferred to see Abstraction was 2-3 times faster to build Hypothesis: More abstractions slower programmers However: Literature on clone research mostly agrees that clones are maintenance problem Practitioner literature strongly advocates abstraction Christoph Reichenbach Evolving the SE Toolbox 10th January /22

41 Copy-and-Paste vs. Abstraction Small user study (5 C++ programmers, 5 programs): Programmers preferred to see Abstraction was 2-3 times faster to build Hypothesis: More abstractions slower programmers However: Literature on clone research mostly agrees that clones are maintenance problem Practitioner literature strongly advocates abstraction Can we somehow have both benefits? Christoph Reichenbach Evolving the SE Toolbox 10th January /22

42 Solution: Auto-Merge Refactoring int dist(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::max(dx, dy); } int dist2(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::hypot(dx, dy); } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

43 Solution: Auto-Merge Refactoring int dist(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::max(dx, dy); } int dist2(coord a, coord b) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return std::hypot(dx, dy); } merge abstraction = function pointer int distg(coord a, coord b, int (*f)(int, int)) { int dx = abs(a.x - b.x); int dy = abs(a.y - b.y); return f(dx, dy); } Christoph Reichenbach Evolving the SE Toolbox 10th January /22

44 Evaluation Selected near-clones from Open Source C++ projects Used our tool to merge Merge abstractions: Parameter Parameter lifted to pointer Template Global Variable Manual cleanup: Formatting, variable renaming Phase 1 (Early prototype, limited to two-way merge): Submitted Accepted Rejected Pending Phase 2: Submitted Accepted Rejected Pending Christoph Reichenbach Evolving the SE Toolbox 10th January /22

45 Agenda Abstract New abstraction patterns (OO class hierarchies, design patterns,... ) Christoph Reichenbach Evolving the SE Toolbox 10th January /22

46 Agenda Incremental abstraction New abstraction patterns (OO class hierarchies, design patterns,... ) Incremental abstraction Christoph Reichenbach Evolving the SE Toolbox 10th January /22

47 Agenda Abstract + Instantiate New abstraction patterns (OO class hierarchies, design patterns,... ) Incremental abstraction Bidirectionality in abstraction Christoph Reichenbach Evolving the SE Toolbox 10th January /22

48 Agenda? New abstraction patterns (OO class hierarchies, design patterns,... ) Incremental abstraction Bidirectionality in abstraction Assessing quality aspects (runtime, memory usage) of abstractions Christoph Reichenbach Evolving the SE Toolbox 10th January /22

49 Agenda New abstraction patterns (OO class hierarchies, design patterns,... ) Incremental abstraction Bidirectionality in abstraction Assessing quality aspects (runtime, memory usage) of abstractions Goal: Transparent Abstractions Christoph Reichenbach Evolving the SE Toolbox 10th January /22

50 with Noric Couderc, starting 2018 Christoph Reichenbach Evolving the SE Toolbox 10th January /22

51 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Christoph Reichenbach Evolving the SE Toolbox 10th January /22

52 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Compile time Christoph Reichenbach Evolving the SE Toolbox 10th January /22

53 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Compile time Security Christoph Reichenbach Evolving the SE Toolbox 10th January /22

54 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Compile time Security Portability Numeric range Robustness Scalability Parallelisability Re-entrance / thread-safety Traceability Christoph Reichenbach Evolving the SE Toolbox 10th January /22

55 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Compile time Security Portability Numeric range Robustness Scalability Parallelisability Re-entrance / thread-safety Traceability Latency and bandwidth needs (communications) Precision and recall (AI) Serialisability (data structures) Stability (containers, sorting) Christoph Reichenbach Evolving the SE Toolbox 10th January /22

56 Why we re-use Development Speed (Brooks, McIlroy) Take advantage of existing expertise to improve: Execution time Memory usage Compile time Security Trade-offs: Portability Who decides them? Numeric range When? Robustness Scalability How? Parallelisability Re-entrance / thread-safety Traceability Latency and bandwidth needs (communications) Precision and recall (AI) Serialisability (data structures) Stability (containers, sorting) Christoph Reichenbach Evolving the SE Toolbox 10th January /22

57 : Motivation Module search: User Christoph Reichenbach Evolving the SE Toolbox 10th January /22

58 : Motivation Module search: User Wants optimal Performance Size Portability Thread-safety Correctness Christoph Reichenbach... Evolving the SE Toolbox 10th January /22

59 : Motivation Module search: Domain expert Suggestions: A, B, C User Wants optimal Performance Size Portability Thread-safety Correctness... Christoph Reichenbach Evolving the SE Toolbox 10th January /22

60 : Motivation Module search: Domain expert Suggestions: A, B, C User Wants optimal Performance Size Portability Thread-safety Correctness... Validation Validation expert Christoph Reichenbach Evolving the SE Toolbox 10th January /22

61 : Motivation Module search: Domain expert Suggestions: A, B, C User Wants optimal Performance Size Portability Thread-safety Correctness... Validation Validation expert Christoph Reichenbach Evolving the SE Toolbox 10th January /22

62 : Motivation Module search: Domain expert Suggestions: A, B, C User Validation Validation expert Add C to program Christoph Reichenbach Evolving the SE Toolbox 10th January /22

63 : Motivation Module search: Domain expert Suggestions: A, B, C, D User Validation Validation expert New, superior module D developed Christoph Reichenbach Evolving the SE Toolbox 10th January /22

64 : Motivation Module search: Domain expert Suggestions: A, B, C, D User Validation Validation expert C D Who updates old code? Christoph Reichenbach Evolving the SE Toolbox 10th January /22

65 : Idea User Modulator Module Management Christoph Reichenbach Evolving the SE Toolbox 10th January /22

66 : Idea User Problem Domain Knowledge: qualitative requirements Modulator Module Management Christoph Reichenbach Evolving the SE Toolbox 10th January /22

67 : Idea Domain Expert DB Solution Domain Knowledge Implementation ideas Decision criteria User Problem Domain Knowledge: qualitative requirements Modulator Module Management Christoph Reichenbach Evolving the SE Toolbox 10th January /22

68 : Idea Domain Expert DB Solution Domain Knowledge Implementation ideas Decision criteria User Problem Domain Knowledge: qualitative requirements Modulator Module Management Validation procedures Validation Expert DB Christoph Reichenbach Evolving the SE Toolbox 10th January /22

69 : Idea Domain Expert DB Solution Domain Knowledge Implementation ideas Decision criteria User Problem Domain Knowledge: qualitative requirements Modulator Module Management Validation procedures Validation Expert DB Automatic updates Christoph Reichenbach Evolving the SE Toolbox 10th January /22

70 Agenda Set<Integer> = new HashSet<Integer>() Automate module choice Christoph Reichenbach Evolving the SE Toolbox 10th January /22

71 Agenda Set<Integer> = new Set<Integer>() Automate module choice Christoph Reichenbach Evolving the SE Toolbox 10th January /22

72 Agenda Set<Integer> = new Set<Integer>() Automate module choice Optimise module choice Determine / validate module qualities Distribute modules, trust management Machine-Learn Key Features for Module Choice Mine modules from Big Code Christoph Reichenbach Evolving the SE Toolbox 10th January /22

73 Leveraging Re-Use Common theme: re-use Residual Performance Investigation: re-use expert knowledge about programs & behaviour SW Requirements HW Christoph Reichenbach Evolving the SE Toolbox 10th January /22

74 Leveraging Re-Use Common theme: re-use Residual Performance Investigation: re-use expert knowledge about programs & behaviour : re-use expert knowledge about available software SW Requirements Modulator HW Christoph Reichenbach Evolving the SE Toolbox 10th January /22

75 Leveraging Re-Use Common theme: re-use Residual Performance Investigation: re-use expert knowledge about programs & behaviour : re-use expert knowledge about available software Transparent Abstractions: break down barriers between modules and abstraction layers SW Requirements Modulator HW Christoph Reichenbach Evolving the SE Toolbox 10th January /22

76 Leveraging Re-Use Common theme: re-use Residual Performance Investigation: re-use expert knowledge about programs & behaviour : re-use expert knowledge about available software Transparent Abstractions: break down barriers between modules and abstraction layers Future: Language SW Requirements Modulator HW Christoph Reichenbach Evolving the SE Toolbox 10th January /22