16
Put it In Reverse Using Eclipse to Understand Code that has Already Been Written Del Myers

Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

Embed Size (px)

DESCRIPTION

Slides presented for talk at EclipseCon

Citation preview

Page 1: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

Put it In Reverse

Using Eclipse to Understand Code that has

Already Been WrittenDel Myers

Page 2: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

2

Software Is Complex

?

Page 3: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

3

Browsing Source Code

Page 4: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

4

That’s a Lot of Reading

Page 5: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

5

That’s a Lot of Reading

Page 6: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

6

That’s a Lot of Reading

Page 7: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

7

That’s a Lot of Reading

Page 8: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

8

That’s a Lot of Reading

Page 9: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

9

Dynamic Interactive Views For Reverse Engineering

!

Page 10: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

10

Focus on Features

What is it doing?Where does it

happen?Why does it happen?How does it happen?

Page 11: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

Demo

Page 12: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

12

Trace Focused UI

Rotate

Move

Resume Game Mouse Click

Quit Game

Page 13: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

13

Trace Focused UI

Rotate

Page 14: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

14

Summary

Focus on featuresIsolate functionalityAnalyze using Sequence

DiagramsAnswer what, where, why,

and howLink different viewsScale up to production software

Page 15: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

15

AcknowledgementsSupervisor

Dr. Margaret-Anne Storey

Research Collaborations

Martin SaloisDavid Ouellet

Philippe CharlandChris Bennett

Daniel GermanJim Buckley

Page 16: Put It In Reverse: Using Eclipse to Understand Code that has Already Been Written

More InformationDel Myers

[email protected]://diver.sf.net

http://delaltctrl.blogspot.comEclipse MarketPlace

Yoxosp2:

http://diver.svn.sourceforge.net/svnroot/diver/Development