After the symposium the chapters are submitted to be included in the edited volume:

Software Process & Knowledge
P. A. Nielsen & K. Kautz, editors
2006

Chapters will follow the genre of an IEEE Software paper. It should be an academic paper, but also written to practitioners. We will follow the writing style that was used in Learning to Improve Software Organizations.

Chapters will be referred to: Authors, Chapter title, in: Software Processes & Knowledge, P. A. Nielsen & K. Kautz, editors, 2006.

Template and formatting

The template must used. It contains detailed instructions that must be followed.

The bibliography for each chapter as well as the in-line referenes should be made with EndNotes. The EndNotes style must be the built-in DateYear format.

Submission and review

Themes

The book will address research on software process improvement. In particular we find the following themes interesting (but not at all limited to):

• Improvement:
  What is improved: process or practice? How has effective improvement activities been organised? How may we evaluate software practice, processes and process models.

• Knowledge:
  What a re we studying: knowledge or knowing? What is the role of knowledge/knowing in software processes and improvement? Can knowledge/knowing in software development be improved? How may that then be achieved?

• Research Processes:
  How may we study software processes, software process improvement, and knowledge in software processes and improvement? How can we organise research processes effectively? How do we address the issues of research validity, research data collection and analysis?

• Process models:
  Are process models sound? How do we know? How can we effectively measure compliance between processes, process models, maturity models, standards? What are the underlying assumptions in these models?