Continuous the research Software Engineering. Cycle through Test-Driven Search the teaching

Size: px

Start display at page:

Download "Continuous the research Software Engineering. Cycle through Test-Driven Search the teaching"

Gwen Boyd
6 years ago
Views:

1 Overview 1 1. Find out why software engineering is important see some software engineering failures 2. Integrating Get acquainted with Reuse into the Rapid, the Chair of Software Engineering Continuous the research Software Engineering the people Cycle through Test-Driven Search the teaching Position RCoSE - 4th International Workshop on Rapid Continuous Software Engineering Gothenburg, Sweden Marcus Kessel and Colin Atkinson kessel@informatik.uni-mannheim.de Software Engineering Group 1

2 Software Reuse vs Agile Practices 2 Goal: Delivery of high-quality software in short time frames with minimal amount of effort Software Reuse Exploits existing domain knowledge Preplanned: like software product lines high upfront costs Unanticipated: like ad hoc and/or pragmatic reuse high risk, low ROI Agile Practices Short, iterative and incremental development cycles support a wide range of development activities primarily focus on from-scratch development Software Engineering Group 2

3 Software Reuse vs Agile Practices 3 Goal: Delivery of high-quality software in short time frames with minimal amount of effort Software Reuse Agile Practices Exploits existing domain Short, iterative and knowledge Reuse == Discontinuous? incremental development Preplanned: like cycles software How product can lines we integrate support it a wide range into agile practices? high upfront costs of development activities Unanticipated: like ad hoc and/or primarily focus on pragmatic reuse from-scratch development high risk, low ROI Software Engineering Group 3

4 Rapid, Continuous Code Reuse 4 CoSE has the potential to promote unanticipated reuse domain knowledge contained in software repositories artifacts produced by agile practices like Test-Driven Development (TDD) and Continuous Integration (CI) Rapid, continuous reuse of software components exploit the increasing use of tests in automated CI by test-driven search technology (TDS) Goal: Complement from-scratch development increase efficiency in agile projects (unanticipated) reuse and CI are synergistic and can effectively complement each other Software Engineering Group 4

explore, rank & select Base64 Example Signature Base64(encode(char[]):char[];) Test Cases

5 Semantic Code Search: Test-Driven Search 5 1) Create Unit Tests exec. specification 2) query search system Test-Driven Search Engine Developer (reuser) 4) explore, rank & select Base64 Example Signature Base64(encode(char[]):char[];) Test Cases (Input/Output) e.g. RCoSE2018 UkNvU0UyMDE4 3) passing candidates Component index Ranking Engine Software Engineering Group 5

6 Enabler: Test-Driven Search Technology 6 1) Create Unit Tests exec. specification 2) query search system Test-Driven Search Engine Developer (reuser) 4) explore, rank & select Base64 Example Signature Base64(encode(char[]):char[];) Test Cases (Input/Output) e.g. RCoSE2018 UkNvU0UyMDE4 3) passing candidates Component index Ranking Engine Software Engineering Group 6

Test-Driven Search Evaluation Retrieve textual candidates Run candidates against test

7 Enabler: Test-Driven Search Technology 7 1) Create Unit Tests exec. specification 2) query search system Test-Driven Search Engine Developer (reuser) Test-Driven Search Evaluation Retrieve textual candidates Run candidates against test class 3) passing candidates Component index 4) explore, rank & select Ranking Engine Software Engineering Group 7

8 Enabler: Test-Driven Search Technology 8 1) Create Unit Tests exec. specification 2) query search system Test-Driven Search Engine Developer (reuser) Ranking according to reuse utility Functional requirements Non-functional requirements 3) passing candidates Component index 4) explore, rank & select Ranking Engine Software Engineering Group 8

Explore recommended reuse candidates View source code Metrics (static/dynamic)

9 Enabler: Test-Driven Search Technology 9 1) Create Unit Tests exec. specification 2) query search system Test-Driven Search Engine Developer (reuser) Explore recommended reuse candidates View source code Metrics (static/dynamic) Metadata 3) passing candidates Component index 4) explore, rank & select Ranking Engine Software Engineering Group 9

Engine (merobase web service) Central Filters 2) Explore

10 Test-Driven Search: merobase prototype platform 10 1) Test Specification Editor JUnit Test Class Test-Driven Search Engine (merobase web service) Central Filters 2) Explore Passed Candidates Goal-oriented Ranking Criteria Software Engineering Group 10

11 Test-Driven Search Integrated into CI Cycle 1 Software Engineering Group 11

12 Scenarios: Test-First Development 2 Reactive reuse unobtrusive/no change for developers Proactive reuse optimize for testdriven reuse Software Engineering Group 12

(e.g. Jenkins CI) 1b) E-Mail Notifications

13 Recommending Reusable Candidates 3 1a) Dashboard Reporting (e.g. Jenkins CI) 1b) Notifications 2) Explore & Select Reusable Candidates Software Engineering Group 13

14 Challenges of Rapid Reuse 14 Software reuse cover all reuse phases: select, adapt and integrate [Krueger 92] specify both desired functional/non-functional requirements [Kessel 16] Agile teams: Principles & policies violated? see: Simplicity--the art of maximizing the amount of work not done--is essential. [Agile Manifesto] Triggering: Scalable and efficient strategies for initiating test-driven searches in CI; identify -- how developers practice TDD in CI environments when and what has changed (on commit level) what is being tested (CUTs) and how is it tested? (e.g. unit vs integration tests) Software Engineering Group 14

15 Q/A 5 Thank you for your Attention! Software Engineering Group 15

Future Work: Next Steps 16 Analysis of code version histories to identify testing strategies Mining software repositories TravisTorrent dataset [TravisTorrent] Ask developers Start

16 Future Work: Next Steps 16 Analysis of code version histories to identify testing strategies Mining software repositories TravisTorrent dataset [TravisTorrent] Ask developers Start with unobtrusive reactive reuse causes no change for developers replay commits from existing projects let test-driven search engine run in the background Software Engineering Group 16

17 Literature 17 [Agile Manifesto] [Kessel 16] M. Kessel and C. Atkinson, Ranking software components for reuse based on non-functional properties. Inf Syst Front (2016) 18: 825 [Krueger 92] Charles W. Krueger Software reuse. ACM Comput. Surv. 24, 2 (June 1992), [TravisTorrent] M. Beller, G. Gousios and A. Zaidman, "TravisTorrent: Synthesizing Travis CI and GitHub for Full-Stack Research on Continuous Integration," 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR) pp [merobase] Software Engineering Group 17

Chair of Software. Engineering. Overview. School of Business Informatics and Mathematics. 1. Find out why software engineering is important

Chair of Software. Engineering. Overview. School of Business Informatics and Mathematics. 1. Find out why software engineering is important 1 Overview 1. Find out why software engineering is important Chair of Software see some software engineering failures Engineering 2. Get acquainted with the Chair of Software Engineering the research the