TRANSPARENT COMPONENTS FOR SOFTWARE SYSTEMS

Transcription

1 Fakultät Informatik, Institut für Software- und Multimediatechnik, Lehrstuhl für Softwaretechnologie TRANSPARENT COMPONENTS FOR SOFTWARE SYSTEMS Paul Peschel Dresden, summer term 2014

2 Content Transparent Software Components Evolution Development Today Motivation Solution Open Source Software Vision Central Managed Source Automatic Software Creation Systems Complexity Time/Cost Design Space Exploration Synthesizing Creation of a stable Software-System TU Dresden, summer term 2014 Transparent Components for Software Systems slide 2

3 Motivation Users/Customers Growing amount of embedded systems = Growing amount of software Upcoming Cyber Physical Systems (CPS)

4 Motivation Users/Customers Software complexity Growing amount of embedded systems = Growing amount of software Upcoming Cyber Physical Systems (CPS) TU Dresden, summer term 2014 Transparent Components for Software Systems slide 4

5 Motivation How do we achieve a quick and inexpensive software development? Keeping or even improving the software quality? TU Dresden, summer term 2014 Transparent Components for Software Systems slide 5

6 Solution: Open Source Software (OSS) Free available Huge community Open Source Software Integrated evolution Almost good code quality TU Dresden, summer term 2014 Transparent Components for Software Systems slide 6

7 Vision OSS! Transparent Software Components (TSC) Use Open Source Components directly High reusability High software quality TU Dresden, summer term 2014 Transparent Components for Software Systems slide 7

8 Transparent Software Components Evolution Automatic maintenance Innovations Higher software quality TU Dresden, summer term 2014 Transparent Components for Software Systems slide 8

9 What comes next Transparent Software Components Evolution Development Today Motivation Solution Open Source Software Vision Central Managed Source Automatic Software Creation Systems Complexity Time/Cost Design Space Exploration Synthesizing Creation of a stable Software-System TU Dresden, summer term 2014 Transparent Components for Software Systems slide 9

10 Centralized TSC Source [1] [2] Central component management Avoid redundancy Strict versioning TU Dresden, summer term 2014 Transparent Components for Software Systems slide 10

11 Synthesizer Tool Design Space - TSC Input Set A B C Feasible Solution Feasible Solution: Fits the functional and non-functional specifications Have to be explored (Design Space Exploration) TU Dresden, summer term 2014 Transparent Components for Software Systems slide 11

12 Design Space Exploration Multi-Objective Optimization B A C Find components that fit to the design specifications Multi-Objective Optimization Objectives: Latency, costs, memory consumption,... Pareto-Optimal: Generate a set of all components that have an optimal fit to the objectives without (or minimal) conflicting other components and their objectives.[3]

13 Design Space Exploration Multi-Objective Optimization Property Value B A C Find components that fit to the design specifications Multi-Objective Optimization Objectives: Latency, costs, memory consumption,... Pareto-Optimal: Generate a set of all components that have an optimal fit to the objectives without (or minimal) conflicting other components and their objectives.[3]

14 Design Space Exploration Multi-Objective Optimization Property Value Objective 1 Objective 2 Objective 3 B A C Find components that fit to the design specifications Multi-Objective Optimization Objectives: Latency, costs, memory consumption,... Pareto-Optimal: Generate a set of all components that have an optimal fit to the objectives without (or minimal) conflicting other components and their objectives.[3]

15 Design Space Exploration Multi-Objective Optimization Property Value Objective 1 Objective 2 Objective 3 B A C Conflict Find components that fit to the design specifications Multi-Objective Optimization Objectives: Latency, costs, memory consumption,... Pareto-Optimal: Generate a set of all components that have an optimal fit to the objectives without (or minimal) conflicting other components and their objectives.[3]

16 Design Space Exploration Multi-Objective Optimization Property Value Objective 1 Objective 2 Objective 3 B A C Conflict Find components that fit to the design specifications Multi-Objective Optimization Objectives: Latency, costs, memory consumption,... Pareto-Optimal: Generate a set of all components that have an optimal fit to the objectives without (or minimal) conflicting other components and their objectives.[3]

17 Synthesizer Tool Double Roof Model Figure : [4]

18 Synthesizer Tool Double Roof Model Design Specifications Figure : [4]

19 Synthesizer Tool Double Roof Model Design Specifications Design Space Figure : [4]

20 Synthesizer Tool Double Roof Model Design Specifications Design Space Refined Model / Structural Implementation Figure : [4]

21 Further Steps Keep the system running

22 Further Steps Keep the system running Simulate components

23 Further Steps Keep the system running Simulate components Monitor components

24 Further Steps Keep the system running Simulate components Monitor components Isolate components

25 Further Steps Keep the system running Simulate components re pl ac e Monitor components Isolate components

26 Conclusion High software quality Low development costs Low maintenance costs Less or even no authority over the components Evolution can kill a component Maybe slow bug fixing Low time-to-market TU Dresden, summer term 2014 Transparent Components for Software Systems slide 26

27 References berlios.de. ow2.org. Lars Boshold. Multikriterielle optimierung. seminar/boshold.ppt [Last access: ]. Jürgen Teich. Hardware/software codesign: The past, the present, and predicting the future. Proceedings of the IEEE, 100(Special Centennial Issue): , All images (except figures [1, 2, 4]) are under CC-license. TU Dresden, summer term 2014 Transparent Components for Software Systems slide 27

28 Additional Slides - Vision OSS! Transparent Software Components (1st view) Other developers (e.g. open source developers) look at the code Give advices to improve software quality

29 Additional Slides - Vision OSS! Transparent Software Components (1st view) Other developers (e.g. open source developers) look at the code Give advices to improve software quality

30 Additional Slides - Vision OSS! Transparent Software Components (1st view) Other developers (e.g. open source developers) look at the code Give advices to improve software quality

31 Additional Slides - Vision OSS! Transparent Software Components (1st view) Other developers (e.g. open source developers) look at the code Give advices to improve software quality TU Dresden, summer term 2014 Transparent Components for Software Systems slide 31

32 Component Composition How to compose Open Software Components? Static composition at design time Dynamic composition? How to create automatically stable software systems? TU Dresden, summer term 2014 Transparent Components for Software Systems slide 32

33 Dynamic Composition Component replacement/extension at runtime With roles A role is a dynamic view on an object (component) TU Dresden, summer term 2014 Transparent Components for Software Systems slide 33