Making the Most of User Changes, valeria murgia and leandro caniglia, ESUG 2008Amsterdam

1. valeria murgia
leandro caniglia
MAKING THE MOST OF USERMAKING THE MOST OF USER
CHANGES

2. DemoDemo
Usethesoftware
GeneratesomechangesGeneratesomechanges
Show thechangesbrowser
Replay them

3. Logging user changesLogging user changes
Change
Log

4. Command loggingCommand logging
!!
Change
(text)(text)

5. Change structureChange structure

6. Naming objectsNaming objects
r
a
2b2
b1
1c1
2c2
1b1

7. Creating changesCreating changes
doesNotUnderstand: aMessagedoesNotUnderstand: aMessage
privateprivate
doesNotUnderstand:
all user commands
add:add:
newThis:
newThat:
remove:
renameTo: arg
remove:
renameTo:

8. Classes involvedClasses involved

9. Replaying changesReplaying changes
Change
(text)
Execute the change
perform
!!!!

10. ApplicationsApplications
Recovery log
all thetimesaveevery changeon diskall thetimesaveevery changeon disk
Auditing
who changed what, when and howwho changed what, when and how
Local redo (can beused for undo)Local redo (can beused for undo)
right click on any object and list all itschanges
ScriptingScripting
usethechangessystem asascripting language

11. Applications continuedApplications continued
Demos&Tutorials
demo your system by replaying changesdemo your system by replaying changes
Overcomeback compatibility issues
recreateold projectsfrom their changesrecreateold projectsfrom their changes
MergingMerging
merging changesiseasier than merging objects
User supportUser support
solvetheuser sproblem and send back the
changeschanges

12. Applications continuedApplications continued
Bug reporting
send thechangesthat exhibit adefectsend thechangesthat exhibit adefect
don t know what you did?look at thechanges!
TestingTesting
look at thechangesto writeunit tests
Regression
build alibrary of scriptsto test your systembuild alibrary of scriptsto test your system
Learning (new programmers)
usethechangesasdebugging entry pointsusethechangesasdebugging entry points

13. Applications continuedApplications continued
Metrics
count thenumber of commandsyour userscancount thenumber of commandsyour userscan
perform
how many keystrokesdoesyour softwarerequire?how many keystrokesdoesyour softwarerequire?
measureuser dedication and productivity
which areasof your softwarearemoreheavilywhich areasof your softwarearemoreheavily
used?
understand users workflowsunderstand users workflows
discover bad practicepatterns

14. Applications continuedApplications continued
Teamwork
combinechangesfrom different contributorsintocombinechangesfrom different contributorsinto
thesamemodel
DatabaseconflictsDatabaseconflicts
let usersrecover conflicting changesthat did not
get committedget committed
Database: automated check-in/check-out
1. download aproject from thedatabase1. download aproject from thedatabase
2. work at home
3. apply your changesback to therepository3. apply your changesback to therepository

15. DemoDemo
Open aproject
Makesomefew changesMakesomefew changes
Createtwo scenarios
Edit & changethescenarios
Show thechangesShow thechanges

16. Decision analysis: scenariosDecision analysis: scenarios

17. Scenarios continuedScenarios continued

18. DemoDemo
DecisionTreedemo

19. Decision trees
ObjectParentObject
Decision trees
Child AObjectParentObject Child A
Child C
Child B
Child D

20. Applications continuedApplications continued
Scenarios
associatechangesetswith scenariosfor what-ifassociatechangesetswith scenariosfor what-if
analysis
Decision treesDecision trees
Organizechangesetsunder ahierarchical
structurestructure
MonteCarlo simulations
createonescenario for every random sample

21. DemoDemo
MonteCarlo demo

22. InfluencesInfluences

23. QuestionsQuestions
Haveyou implemented all theapplications
described here?described here?
Haveyou used thechangessystem to analyze
theworkflow of end-users?theworkflow of end-users?
Doesthechangessystem impact the
performance?performance?
What'stheoverhead for programmers?
What if argumentsarenot literals?What if argumentsarenot literals?
Can your system log any user action?