Visualisation for Software Management Claire Knight [email protected].
38
-
Upload
alexis-haley -
Category
Documents
-
view
221 -
download
0
Transcript of Visualisation for Software Management Claire Knight [email protected].
Outline
• General introduction• Background• The importance of “e”• Examples• Future• Opinions
Introduction
• BT Fellowship• Program comprehension• Visualisation• Distributed system comprehension
and visualisation• Jigsaw
Background
• Corporate Data• Planning for future changes• Non-delete approach• Decision recording• Management tool• What-if…
e-Science Culture
• Different focus• Generalisation vs Parameterisation
• Solutions that work (at least now)• Extensible solutions
• Research challenges for all• Cultural differences
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
e-Issues I
• Different conceptual model• Interoperability• Communication• Transactions• Overheads
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
Visualisation
Planning for the Future
• Key concept - plan and record• Know current state• Handle “What if …”• Reduce future search space given
new constraints• Use historical knowledge for
future decisions
• Traffic light system
• Extra means of visual presentation• Distinction between parts• Parameterised and
customisable
Colour Coding
Timelines
• Trace through time• Visual display of change• System stack created, timelines as
specific paths through• Object representations pinpoint where
exact information is known
Versions and Variants
• Objects – generic visual representation• Present known facts• Used for:
• Versions – next release• Variants – forking
• Colour/filtering useful addition
Example – Objects
Example – Objects
Example – Objects
Example – Objects
Example – Timelines
Example – Timelines
Example – Timelines
Example – Timelines
Example – Timelines
Example – Timelines
Example – Projections
Example – Scenario
Example – Scenario
Example – Scenario
Example – Scenario
Example – Scenario
Example – Scenario
Shaping e-Science Projects
Software System Evolution
• Inherent• Technology• Management/User Requirements• External
• Hidden impacts• Different distributed rates
Software Comprehension
• Hard problem• Compounded by distribution• Problems:
• Code interactions• Debugging and repeatability• Unreliability of external sources
Distributed…
• …Project [Management]• Or … [Project] Management• Distinction important• Influences decisions• Central repository/planning/
visualisation
Summary
• Background• Initial issues to consider
• Organisational• “e”
• Visualisation example• Additional concerns
What You Can Do
• Archive decisions• Preserve historical data• Plan for the future• Visualise
• For understanding• For communication
