KIELER Meeting 2009-09-11

• moderator: haf
• protocol: cmot

Agenda

• SyncChart-Klepto-KEV Demo
• Interesting Aspects of DiwiSH Innovative Software Development
• KIELER Reviews
• KIELER Poster
• CheckStyle Package
• General Anouncements
• KIELER Release

SyncChart-Klepto-KEV Demo

• KEV shown together w/ KlePto SyncChart simulation
• Traffic-Light-Example
• KlePto feautures
  • Priorities
  • Normal-Termination
  • Absence-Analysis of local signals
  • Pure statemachines
  • Inner-, Entry-, Exit-Actions (maybe in the future)
  • History connector

Interesting Aspects of DiwiSH Innovative Software Development

• XPand fully synchronized XText editor
• Textual table calculation in XText for SAP-Application (GUI)
• Team-oriented processmodel SCRUM,
  • code-reviews: partner-review
  • 1week programming -> 2h review
  • checklists

KIELER Reviews

• May cost some time but necessary
• Team-review (1:1 or 1:2 person)
• Review-Protocol, may be in the files
  • Taglet for JavaDoc (for future use)
  • State of the code (e.g., colors)
• Regular reviews!
• Max 2h
• In the morning
• Details will be discussed w/ Miro and Hauke (TICKET #394, @haf @msp)

KIELER Poster

• Hauke presents the current KIELER poster
• Structual editing
• Bullets adapted
• Presented-Tag
• Missing screenshot -> cmot (TICKET #395, @cmot)
• Poster accepted in the meeting
• Poster will be printed in the beginning of the next week

CheckStyle Package

• Wiki: Step-by-step manual
• Use at early as possible
• Getter and setter always needed?
  • Add to "software practice" (TICKET #396, @haf)
  • Maybe compiler is clever enough
  • Check possible performance lags, e.g., tptp (Ticket #397, @msp)
  • May only be omitted for (really) internal classes for performance reasons
• Empty block
  • No text or no code
  • Empty catch blocks
  • Comment in your empty catch blocks, why this should be empty
• Magic numbers
  • Mathematical formulars are excepted from this rule
    • Test whether exceptions to checkstyle checks can be solved with special comments or options (Ticket #398, @haf)
  • Progressbar: Introduce constants here
  • Index calculations: Offset should be named constants
• DO NOT CHECK IN THE ".CHECKSTYLE" FILE!

General Anouncements

• Read your email
  • State how important or for whome this email may be important (mailing list)
  • Do this in the subject or the beginning of the E-Mail
  • For the KIELER mailing list: write preferably in english (but german is also ok)
  • We need an additional user-mailing list, separate to the devel-mailing list (DONE bye haf)
• Organize your to-do-list
• Read the "software practice" part in the wiki
  • Do this esp. if you just begin your student/diploma thesis
  • A link to the "software practice" part should be in RT-Group Manual (haf: done)
• Read KIELER protocols (esp. if you could not attend)
• Close tickets and accept new ones, respond if necessary
• Eclipse qualifier will be adapted (vqualifier->qualifier) by Miro (DONE by msp, chsch)

KIELER Release

• Example missing
• DEMO "Tag der Informatik", maybe test w/ 3.5.1
• Branch for experimental use now
• Trunk version MUST run for DEMO
• Communicate API changes to other KIELER developers that may use your code
  • Do this before you check in these changes!