Case Studies describe the application of a software product line technique, tool, or process in an industrial or organizational setting. A case study provides the rationale for the key decisions made during the development of a software product line along with the accomplished qualitative results.

Experience Reports describe the history of a software product line accompanied by a critical review of experience within more or one development phases within domain and/or application engineering. An experience report describes lessons learned from the experience.

Experimental Reports: In contrast to an experience report and a case study, an experiment systematically controls the influencing factors and results in quantitative data about some aspect of software product line engineering.

Problem Statements describe problems encountered during the development or use of a software product line. A good problem statement clearly describes the problem and includes a discussion of why state-of-the-art principles, techniques, methods, processes or tools are not able to solve the problem.

Research Papers describe original research contribution (theoretical, conceptual) to the field of software product line engineering. A research paper should clearly describe the problem tackled, the state of the art with respect to the problem, the solution suggested and the potential - or even better the evaluated - benefits of the contribution.