A Software Process Framework for PLE Development to Reduce Time and Costs of Widget Creation and Evolution Christian Prause
Software changes continuously <ul><li>Continuous change for improvement </li></ul><ul><ul><li>Changing requirements </li><...
Realization of change <ul><li>Change realized by developers </li></ul><ul><li>Change has a cost </li></ul><ul><li>Lower co...
Usability improvement requires change... in accordance with ISO-9126 view <ul><li>Developers must understand first </li></...
Development framework to support understanding of PLE software <ul><li>Algorithmic information theory view: </li></ul><ul>...
Structure: exploit conceptual structure <ul><li>Modifiable library of design patterns </li></ul><ul><ul><li>Collected best...
Preserve: motivate documenting activities <ul><li>Documentation preserves and communicates knowledge </li></ul><ul><ul><li...
Three reasons for documentation problem <ul><li>Developers do not like to write documentation </li></ul><ul><ul><li>It has...
Motivating developers to document <ul><li>Management issue </li></ul><ul><ul><li>Advertise advantages, create awareness </...
Conclusion <ul><li>Reduced cost of change leads to better usability </li></ul><ul><li>Cost reduction through better knowle...
Grafische Elemente Kästen, Pfeile, Verbindungen und Linien (Auswahl) <ul><ul><li>folgende Elemente können hier per Rechtsk...
Farben <ul><ul><li>folgende Farben können über die Powerpoint-Farbauswahl hier aufgenommen und damit in der neuen Präsenta...
ISO-9126: Process influences usability
Upcoming SlideShare
Loading in...5
×

Widget framework

263

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
263
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Widget framework"

  1. 1. A Software Process Framework for PLE Development to Reduce Time and Costs of Widget Creation and Evolution Christian Prause
  2. 2. Software changes continuously <ul><li>Continuous change for improvement </li></ul><ul><ul><li>Changing requirements </li></ul></ul><ul><ul><li>Bug fixes </li></ul></ul><ul><ul><li>... </li></ul></ul><ul><ul><li>Usability improvement </li></ul></ul>
  3. 3. Realization of change <ul><li>Change realized by developers </li></ul><ul><li>Change has a cost </li></ul><ul><li>Lower cost, more change </li></ul><ul><li>Better software </li></ul>
  4. 4. Usability improvement requires change... in accordance with ISO-9126 view <ul><li>Developers must understand first </li></ul><ul><li>Project knowledge must be learned </li></ul><ul><ul><li>“ understanding the problem is the problem” </li></ul></ul><ul><ul><li>40% to 60% of efforts for (re-)understanding software to change </li></ul></ul><ul><li>Goal: Learnability of project knowledge </li></ul>
  5. 5. Development framework to support understanding of PLE software <ul><li>Algorithmic information theory view: </li></ul><ul><ul><li>Full information = structural knowledge plus details </li></ul></ul><ul><li>Resulting framework for managing knowledge: </li></ul><ul><ul><li>Structure: exploit conceptual structure using patterns </li></ul></ul><ul><ul><li>Preserve: improve preservation of detail knowledge </li></ul></ul>
  6. 6. Structure: exploit conceptual structure <ul><li>Modifiable library of design patterns </li></ul><ul><ul><li>Collected best practice wisdom </li></ul></ul><ul><li>Common-grounds or lingua franca for PLE widget design </li></ul><ul><li>Named concepts carry meaning for developers </li></ul><ul><li>Reflected in various software project material </li></ul>
  7. 7. Preserve: motivate documenting activities <ul><li>Documentation preserves and communicates knowledge </li></ul><ul><ul><li>Purpose: impart knowledge </li></ul></ul><ul><ul><li>Wiki articles, requirements, bug tracker, source code </li></ul></ul><ul><li>But: documentation is missing in practice </li></ul><ul><li>Technical debt: interest can grind development to halt </li></ul>
  8. 8. Three reasons for documentation problem <ul><li>Developers do not like to write documentation </li></ul><ul><ul><li>It has few value for the individual </li></ul></ul><ul><li>Lack of enforcement structures </li></ul><ul><ul><li>Especially in distributed, multi-partner projects </li></ul></ul><ul><li>Low acceptance of software engineering rigor in research </li></ul><ul><ul><li>smiled upon and seen as overly bureaucratic </li></ul></ul><ul><ul><li>“ we can't afford bug, they have to be fixed” </li></ul></ul>
  9. 9. Motivating developers to document <ul><li>Management issue </li></ul><ul><ul><li>Advertise advantages, create awareness </li></ul></ul><ul><ul><li>Set up documentation-friendly environment, good software process </li></ul></ul><ul><li>Support through reputation systems </li></ul><ul><ul><li>Keep developers on track </li></ul></ul><ul><ul><li>Reward good behavior with social games </li></ul></ul>
  10. 10. Conclusion <ul><li>Reduced cost of change leads to better usability </li></ul><ul><li>Cost reduction through better knowledge management </li></ul><ul><li>Framework based on algorithmic information theory: </li></ul><ul><ul><li>Structure and preserve </li></ul></ul><ul><ul><li>Structure: Pattern library for PLE widget design </li></ul></ul><ul><ul><li>Preserve: Promote documentation activities with reputation systems </li></ul></ul>
  11. 11. Grafische Elemente Kästen, Pfeile, Verbindungen und Linien (Auswahl) <ul><ul><li>folgende Elemente können hier per Rechtsklick kopiert und an gewünschter Stelle in der neuen Präsentation per Rechtsklick wieder eingesetzt werden: </li></ul></ul><ul><li>Linien </li></ul><ul><li>Fraunhofer-Grün, bis 1 pt auch Schwarz </li></ul><ul><li>Linienstärke gestrichelt: 1 pt </li></ul><ul><li>Linienstärke durchgezogen: 1, 2, 3, 4 und 5 pt </li></ul><ul><li>Pfeile und Verbindungen </li></ul><ul><li>Fraunhofer-Grün </li></ul><ul><li>Kasten mit Outline </li></ul><ul><li>Fraunhofer-Grün </li></ul><ul><li>Linienstärke je nach Größe 2, 4, 6, 8 pt </li></ul><ul><li>Je größer der Kasten, desto stärker die Linie </li></ul><ul><li>Kasten gefüllt </li></ul><ul><li>Grau </li></ul><ul><ul><li>! DIESE FOLIE AUS FINALER PRÄSENTATION LÖSCHEN ! </li></ul></ul>
  12. 12. Farben <ul><ul><li>folgende Farben können über die Powerpoint-Farbauswahl hier aufgenommen und damit in der neuen Präsentation angewendet werden: </li></ul></ul><ul><ul><li>Überschriften / Fließtext / Quellenangaben / Bildunterschriften / Grafikauszeichnungen </li></ul></ul><ul><ul><li>Grafikauszeichnungen </li></ul></ul><ul><ul><li>Aufzählungen / Nummerierungen erster Ebene / grafische Elemente </li></ul></ul><ul><ul><li>Grafiken </li></ul></ul><ul><ul><li>Fonds hinter Grafiken </li></ul></ul><ul><ul><li>! DIESE FOLIE AUS FINALER PRÄSENTATION LÖSCHEN ! </li></ul></ul>
  13. 13. ISO-9126: Process influences usability
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×