Software Architektur in der Wildnis

Size: px

Start display at page:

Download "Software Architektur in der Wildnis"

Alaina Hicks
7 years ago
Views:

1 Software Architektur in der Wildnis Software Architecture in the Wild Oscar Nierstrasz Software Composition Group scg.unibe.ch Entwicklertage 2013

2 Roadmap What is Software Architecture? Challenges Software Assessment

3 What is Software Architecture??!

4 The theory... Constraints govern enable Components/ Connectors Properties/ Analyses 4

5 What is SA in the Wild? 5

6 Impact of SA constraints constraint Impact (1-5) availability 4.2 response-time 4.0 authorization 3.9 authentication 3.6 communication 3.4 throughput 3.4 signature 3.4 software infrastructure 3.3 data integrity 3.3 recoverability 3.1 dependencies 3.1 visual design 3.0 data retention policy 3.0 hardware infrastructure 2.9 system behavior 2.9 data structure 2.9 event handling 2.9 code metrics 2.7 meta-annotation 2.6 naming conventions 2.6 file location 2.5 accessibility 2.5 software update 2.2 6

7 Tool support constraint no verif. code review blackbox test whitebox test tool availability response-time authorization authentication communication throughput signature software infrastructure data integrity recoverability dependencies visual design data retention policy hardware infrastructure system behavior data structure event handling code metrics meta-annotation naming conventions file location accessibility software update other 7

8 Architecture... depends on context 8

9 The architecture... is not in the code 9

10 The IDE focuses on code... not architecture 10

11 Software Assessment with Moose

12 Moose is a platform for software and data analysis 12

13 ConAn Van Hapax... CodeCrawler Smalltalk Extensible meta model Java Model repository COBOL C++ External Parser MSE Navigation Metrics Querying Grouping Smalltalk Nierstrasz et al. The Story of Moose. ESEC/FSE

14 System complexity Lanza et al. Polymetric Views. TSE

15 15

16 Mondrian Demo Demo: visualizing name cohesion within packages Meyer et al. Mondrian: An Agile Visualization Framework. SoftVis 2006

17 Case study: transaction scope in JEE applications Start a Transactions Inherit Transactions No attributes defined DB Data accessors base accessor Start an unnecessary Transactions Starts Unnecessary Transactions Supports Transactions DB Data Accessors base accessor Staring a starting Transactiona transaction 17

18 Start a Transactions Inherit Transactions No attributes defined DB Data accessors base accessor Start an unnecessary Transactions Starts Unnecessary Transactions Supports Transactions DB Data Accessors base accessor Staring a starting Transactiona transaction Recovery and Analysis of Transaction Scope from Scattered Information in Java Enterprise Applications, ICSM

19 Functional Component Presentation Layer Local Case study: framework customization Core Components Business Layer Local s Core Local s 19

20 Functional Component Presentation Layer Local Core Business Layer Local Core Java Package Java Package Java Package Java Package Java Package Java Package 20

21 Duplication Functional Component Presentation Layer Local Functional Component Presentation Layer Local Core Core Business Layer Business Layer Local Local Core Core 40 local/global duplications 21

22 Duplication Functional Component Presentation Layer Local Functional Component Presentation Layer Local Core Core Business Layer Business Layer Local Local Core Core 78 local duplications 22

23 23

24 Challenges for Agile Software Assessment Agile Modeling Customization Continuous Assessment

25 Agile Modeling Load the model in the morning, analyze it in the afternoon

26 Problems Unknown languages Heterogeneous projects Unstructured text 26

27 Ideas Exploit conventions to infer program parts Exploit indentation to infer structure Exploit PL similarity to compose parsers Focus on islands (not water) 27

28 Customization Build a new assessment tool in ten minutes

29 Problems Enormous scope What are the right metaphors? How to integrate tools into the workflow? 29

30 Ideas Moldable tools Analyze developer needs Active recommendations 30

31 Continuous Assessment What will my code change impact?

32 Problems Diverse views of SA SA is not in the code The IDE focuses on code 32

33 Ideas Uncovering Software Architecture in the Wild Architecture monitoring (beyond dependencies) 33

34 The bottom line SA is not just dependencies Developers need custom tools The system is not just code

How To Understand And Understand Smalltalk

How To Understand And Understand Smalltalk Lessons in Software Evolution Learned by Listening to Smalltalk Oscar Nierstrasz scg.unibe.ch Research Team Adrian Lienhard Adrian Kuhn Fabrizio Perin Lukas Renggli Jorge Ressia David Roethlisberger Niko