Presentation for 24th International Conference on Advanced Information Systems Engineering (CAiSE'12) Gdańsk, Poland, 25 – 29 June 2012 http://www.caise2012.univ.gda.pl/

1. Wiki Refactoring as
Mind Map Reshaping
ONEKIN Research Group
University of the Basque Country (Spain)
29th June, 2012
CAiSE’12, Gdansk, Poland
Gorka Puente
Oscar Díaz

2. G. Puente 2
Corporate
Wiki
Conclusions

3. G. Puente
CORPORATE WIKI
3

4. G. Puente
Definition
Wiki framed within an organization
Wiki oriented to support a function
United States Intelligence
Community wiki
Microsoft
Bluepedia
Corporate Wiki
4

5. G. Puente
Situation
5
Intranet 2.0 Global Survey, Toby Ward from Prescient Digital Media (December 2011)
1.400 participants
Corporate Wiki

6. G. Puente
Situation
6
Intranet 2.0 Global Survey, Toby Ward from Prescient Digital Media (December 2011)
61% have intranet wikis
Corporate Wiki

7. G. Puente 7
Wiki organic growth
Corporate Wiki
Organic growth Evolution
Huge structures
Refactoring

8. G. Puente
WIKI REFACTORING
8

9. G. Puente
Wiki Refactoring
Code Refactoring: restructure code without
changing its “external behaviour”
Wiki Refactoring:
• change the internal structure for the sake of
navigability, accessibility or comprehension
• content and its authorship should be kept
immutable.
9

10. G. Puente
Wiki Refactoring: Merging
10

11. G. Puente
Wiki Refactoring: Merging
11

12. G. Puente
Wiki Refactoring: Merging
12
Edit
Copy

13. G. Puente
Wiki Refactoring: Merging
13
Paste
content
Create the
new page

14. G. Puente
Wiki Refactoring: Merging
14
Create edit
summary in the
first article

15. G. Puente
Wiki Refactoring: Merging
15
Edit
Copy

16. G. Puente
Wiki Refactoring: Merging
16
Create edit
summary
Paste
content

17. G. Puente
Wiki Refactoring: Merging
17
Create edit
summary in the
second article

18. G. Puente
Wiki Refactoring: Merging
18
Edit summary
Content

19. G. Puente
Wiki Refactoring: Merging
19
Open article StructuralEvents
Copy content
Create article Realization
Paste content from StructuralEvents
Add edit summary in StructuralEvents
Open article LocalStorage
Copy content
…
Too Many Steps

20. G. Puente
Wiki Refactoring
20
Not natively supported by the wiki engine
Left to the user interpretation
• Not consistency in the refactoring strategy
Not ensured reliability
• Refactoring operations are transactions

21. G. Puente
OUR APPROACH: A NEW
SETTING
21

22. G. Puente
Wiki Refactoring: our Approach
22
Open: refactoring conducted by users
Observable: traceable and preserving
authorship attribution.

23. G. Puente
Wiki Refactoring: Independence
23
Readership independence:
• Inform where the content has been moved to
• Preserve URL
Authorship independence:
• Refactoring must preserve authorship

24. G. Puente
Wiki Refactoring: WikiWhirl
24
FreeMind plugin for wiki refactoring
Same operations as in MediaWiki
• Productivity
• Accessibility
• Reliability

25. G. Puente
FreeMind
25

26. G. Puente
A REFACTORING SESSION
26

27. G. Puente
Process
27
Import a wiki as a Mind Map
Apply refactoring operations
as node manipulation
Save changes preserving
authorship and readership

28. G. Puente
Process
28
Import a wiki as a Mind Map
Apply refactoring operations
as node manipulation
Save changes preserving
authorship and readership

29. G. Puente
Import a Wiki as a Mind Map
29

30. G. Puente
Process
30
Import a wiki as a Mind Map
Apply refactoring operations
as node manipulation
Save changes preserving
authorship and readership

31. G. Puente 31
Apply refactoring operations
as node manipulation: split

32. G. Puente 32
Apply refactoring operations
as node manipulation: merge

33. G. Puente 33
Apply refactoring operations
as node manipulation: move

34. G. Puente
Process
34
Import a wiki as a Mind Map
Apply refactoring operations
as node manipulation
Save changes preserving
authorship and readership

35. G. Puente 35
Save changes preserving
authorship and readership

36. G. Puente 36
Save changes preserving
authorship and readership
Merge
Move

37. G. Puente
CONCLUSIONS
37

38. G. Puente 38
Conclusions
Wikis are imported as Mind Maps
Users perform refactoring operations as re-
arrangements of nodes
Changes are saved preserving authorship
and readership

39. G. Puente 39
@gorkapuente
gorka.puente@ehu.es