1 / 38

Visualisation for Software Management

Visualisation for Software Management. Claire Knight C.R.Knight@durham.ac.uk. Outline. General introduction Background The importance of “e” Examples Future Opinions. Introduction. BT Fellowship Program comprehension Visualisation Distributed system comprehension and visualisation

aline-osborn
Download Presentation

Visualisation for Software Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Visualisation for Software Management Claire Knight C.R.Knight@durham.ac.uk

  2. Outline • General introduction • Background • The importance of “e” • Examples • Future • Opinions

  3. Introduction • BT Fellowship • Program comprehension • Visualisation • Distributed system comprehensionand visualisation • Jigsaw

  4. Background • Corporate Data • Planning for future changes • Non-delete approach • Decision recording • Management tool • What-if…

  5. e-Science Culture • Different focus • Generalisation vs Parameterisation • Solutions that work (at least now) • Extensible solutions • Research challenges for all • Cultural differences

  6. Organisational Effects • Worst case – the entire system • Best case – system accommodates necessary changes, minimal change • Compound impact - unseen ripple effects • Managerial not appreciating the technical

  7. e-Issues I • Different conceptual model • Interoperability • Communication • Transactions • Overheads

  8. e-Issues II • Non-localised resources • Control and responsibility • Paradigm shift for cost/expenditure • Reliant on new technologies, themselves in infancy andsubject to rapid change

  9. Visualisation

  10. Planning for the Future • Key concept - plan and record • Know current state • Handle “What if …” • Reduce future search space givennew constraints • Use historical knowledge forfuture decisions

  11. Colour Coding • Traffic light system • Extra means of visual presentation • Distinction between parts • Parameterised andcustomisable

  12. Timelines • Trace through time • Visual display of change • System stack created, timelines as specific paths through • Object representations pinpoint where exact information is known

  13. Versions and Variants • Objects – generic visual representation • Present known facts • Used for: • Versions – next release • Variants – forking • Colour/filtering useful addition

  14. Example – Objects

  15. Example – Objects

  16. Example – Objects

  17. Example – Objects

  18. Example – Timelines

  19. Example – Timelines

  20. Example – Timelines

  21. Example – Timelines

  22. Example – Timelines

  23. Example – Timelines

  24. Example – Projections

  25. Example – Scenario

  26. Example – Scenario

  27. Example – Scenario

  28. Example – Scenario

  29. Example – Scenario

  30. Example – Scenario

  31. Shaping e-Science Projects

  32. Software System Evolution • Inherent • Technology • Management/User Requirements • External • Hidden impacts • Different distributed rates

  33. Software Comprehension • Hard problem • Compounded by distribution • Problems: • Code interactions • Debugging and repeatability • Unreliability of external sources

  34. Distributed… • …Project [Management] • Or … [Project] Management • Distinction important • Influences decisions • Central repository/planning/visualisation

  35. Summary • Background • Initial issues to consider • Organisational • “e” • Visualisation example • Additional concerns

  36. What You Can Do • Archive decisions • Preserve historical data • Plan for the future • Visualise • For understanding • For communication

  37. Questions? C.R.Knight@durham.ac.uk http://vrg.dur.ac.uk/

More Related