Technical Research Papers

Technical research papers report original results from basic and/or applied requirements engineering research. The focus is on the development of new theories, models, processes or techniques that have undergone some validation, perhaps using examples, but have yet to undergo experimental and empirical validation. Technical research papers will be reviewed for the originality of contribution (new or novel integration of previous research), quality and rigour of research that led to the contribution, and potential utility of the research to requirements engineering.

Prototypical technical research papers from the last 2 Requirements Conferences include:

• De Landtsheer R., Letier E. & van Laamsweerde A., 2003, "Deriving Tabular Event-Based Specifications from Goal-Oriented Requirements Models", Proceedings 11^th International IEEE Conference on Requirements Engineering, IEEE Computer Society Press, 200-210.
• Robinson W.N., 2003, "Monitoring Web-Service Requirements", Proceedings 11^th International IEEE Conference on Requirements Engineering, IEEE Computer Society Press, 65-74.

Research Experience Papers

Research experience papers report the application of original research results using experimental, empirical and analytic methods. The original research results are either reported in the paper or published in an earlier paper. The focus is on a sound scientific method to investigate research hypotheses that are of interest to the wider requirements engineering community. Experimental studies should report research hypotheses that are tested using well-defined and controlled population groups. Empirical studies should investigate well-formulated research questions using a controlled environment. Analytic methods should be reported in sufficient detail to explain their detailed workings to the reader. The focus should be on quantitative data analysis and, where appropriate, statistical analyses.

Prototypical research experience papers from the last 2 Requirements Engineering conferences include:

• Feather M.S. & Menzies T., 2002, "Converging on the Optimal Attainment of Requirements", Proceedings Joint IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, 263-270.

Sutcliffe A.G. & Gregoraides A., 2002, "Validating Functional System Requirements with Scenarios", Proceedings 11^th International Conference on Requirements Engineering, IEEE Computer Society Press, 181-188.

Empirical Study Papers

Empirical results report the use of requirements processes, techniques and tools in practical settings, with particular emphasis on general lessons learned. The focus is on detailed description of the use of the processes, techniques and tools in the setting, objective reporting of the results of their use (quantitative as well as qualitative data), and presentation of lessons learned that are interesting to the wider requirements engineering community. Lessons must be grounded in the reported results, although authors are not required to provide detailed rationale for each lesson. These lessons should be on interest to practitioners wishing to improve their requirements practices and researchers seeking knowledge to inform their basic and applied research.

Prototypical empirical study papers from the last 2 Requirements Engineering conferences include:

• Mavin A. & Maiden N.A.M., 2003, "Determining Socio-Technical Systems Requirements: Experiences with Generating and Walking Through Scenarios", Proceedings 11^th International Conference on Requirements Engineering, IEEE Computer Society Press, 213-222.

• Damian D.E. & Zowghi D., 2002, "The Impact of Stakeholders' Geographical Distribution on Managing Requirements in a Multi-Organisation Site", Proceedings Joint IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, 319-328.

Case Study Papers

Case studies report the use of requirements processes, techniques and tools in a practical setting, describing the setting, results obtained and any conclusions that can be drawn. The focus is on the importance and the report of the application, the setting and the results, so that the paper can provide the reader with sufficient description to draw conclusions from the paper relevant to their own experiences and research. Case studies will often report qualitative rather than quantitative data.

Prototypical case study papers from the last 2 Requirements Engineering conferences include:

• Alexander I., 2002, "Initial Experience of Misuse Cases in Trade-off Analysis", Proceedings Joint IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, 61-68

• Bergman M. & Mark G., 2002, "Exploring the Relationship between Project Selection and Requirements Analysis: An Empirical Study of the New Millennium Program", Proceedings Joint IEEE International Conference on Requirements Engineering, IEEE Computer Society Press, 247-254

• Lutz R.R. & Mikulski I.C., 2003, "Resolving Requirements Discovery in Testing and Operations", Proceedings 11^th International Conference on Requirements Engineering, IEEE Computer Society Press, 33-41.

Industry Experience Reports

Industry experience reports describe the application of requirements engineering processes, methods, techniques and tools to a real-world application. The focus is on description of the requirements engineering work undertaken, any outcomes from that work, and communication of the work to others. Unlike empirical study and case study papers, there is no attempt to draw lessons or analyse results.