Meeting May 27, 2011 @ 10.00-12.00h (Room 1210)

Topics

• Discussion of proposed thesis topic
• Release of Kieker Version 1.3 (May 19, 2011) (avh)
  • Release notes (final)?
  • Stabilize branch and merge back (due Apr 21 (Thu), 2011)
  • API freeze (due Apr 28 (Thu), 2011)
  • User's Guide (due May 05 (Thu), 2011)
  • Unit tests (due May 05 (Thu), 2011)
  • Tests based on User's Guide Linux/Win (due May 12 (Thu), 2011)
• SPEC RG (avh)
• Kieker-VL SEPVS (slides) (slides also on  Kieker web site)
• Status of current activities (brief reports)
  • Refactoring Kieker.Monitoring (jwa,rvm)
  • Benchmarks (jwa)
  • Metrics/Statistics Metamodel? (rju,avh,sfr)
  • Kieker.COM/.NET (avh)
  • Analysis Tool/IDE (jwa)
• Road Map
  • Version 1.4 (?Nov, 2011?)
  • Current Feature wish list (working document)?:
    • Integrated analysis tool / -> ticket/18
    • Basic statistics support (data structures, functions, ...) -> ticket/19
    • JMX reader/writer -> ticket/20
    • Database writer supporting additional record types other than OperationExecutionRecords. -> ticket/21
    • Database reader -> ticket/22
    • Replace OpenJMS-based implementation of JMS writer by alternative product -> ticket/35
    • Add alternative MOM-based writer -> ticket/36
    • Interoperability with other Trace Analysis/Visualization tools -> ticket/52
    • Support monitoring/reconstruction of asynchronous traces -> ticket/58
    • Additional models/visualizations:
      • Use Case Maps -> ticket/7
      • Timing diagrams -> ticket/59
      • UML Communication Diagrams -> ticket/60
    • Kieker Glossary, for example in order clarify terms like metrics, measures, observations etc.
• Tasks
  • Evaluate whether private (i.e. invisible to users that are not logged in) are possible by placing them in subdirectories: ticket/8
  • For future visualiations of Kieker's architecture: Turn database 90 degrees and label it with "monitoring log/stream" to emphasize that we include streams of monitoring data (e.g., for online analysis)
  • Automatic generation of user's guide in HTML format -> ticket/4
  • Employ static analysis tool such as FindBugs -> ticket/44
  • JavaDoc
    • Add JavaDoc for core classes and API methods: -> ticket/11
    • Cleanup -> ticket/43
  • Check test coverage, add JUnit tests
  • FAQ section on web site/in trac
  • Extract TODOs from source and create corresponding tickets -> ticket/27
• Publications
  • Paper
  • Tool Demo?