Technical solution papers present solutions for requirements–related problems that are novel or significantly improve on existing solutions. These papers are mainly evaluated with regard to problem relevance, novelty, clarity of presentation, technical soundness, and evidence for its benefits. New: Technical solution papers must not exceed 10 pages for the main body and 2 additional pages for the references. There are 3 main kinds of solutions and corresponding evaluation criteria.<br>Scientific evaluation papers evaluate existing problem situations or evaluate real–world artefacts or validate/refute proposed solutions by scientific means. This includes, e.g., experiments, case studies, and surveys reporting qualitative or quantitative data and findings. The papers are mainly evaluated with regard to the soundness of research questions and appropriateness/correctness of study design, data analysis, and threats to validity. Replications are welcome. For papers reporting on the application of some solutions, lessons learned are particularly important. New: Scientific evaluation papers must not 10 pages for the main body, and 2 additional pages for the references.<br>Perspective papers explore the history, successes, and challenges of requirements related practices and research agendas, and outline research roadmaps for the future. Literature reviews are also included in this category and must distil novel knowledge, present new insights and not be merely a compilation. These papers are evaluated based on the insights they offer to the reader and the corresponding arguments, and on their potential to shape future research. Perspective papers may have more than 2 pages of references, but under no circumstances may the body of the paper exceed 10 pages or may the combined body of the paper and the references exceed 12<br>ages.<br>=== Topics of Interest ===<br>Elicitation and stakeholders: requirements elicitation, prioritisation, and negotiation, design thinking and open innovation, innovation through creativity, crowdsourcing and social media, social, cultural, and cognitive factors, user feedback and usage monitoring, capturing and understanding users’ needs.<br>Requirements analysis, specification and validation: natural language approaches, model–driven approaches, formal approaches.<br>Requirements management: traceability, evolution and release planning, reuse, tools and standards.<br>Pragmatic requirements engineering: good–enough requirements engineering, agile and lean approaches, requirements engineering in open source<br>Large–scale requirements engineering: complex systems, product lines and value chains, software ecosystems, artificial intelligence, big data, and cloud technologies, requirements engineering for smart cities, cyber–physical systems, and systems of systems.<br>Global requirements engineering: geographically–dispersed teams, culturally–divergent requirements efforts.<br>Domain–specific requirements engineering: embedded systems, open source software, privacy and security, sustainability, services, mobility, cyber–physical systems.<br>Quality engineering: user experience, quality factors, safety and security, test approaches.<br>Product management: value creation techniques, product evolution, requirements and marketing, requirements and law.<br>Industry and research collaboration: learning from practice, transferring technology from academia to industry, transferring technology across industries, transferring technology across domains, identifying best practices, improving productivity.<br>Requirements engineering education and training<br>Empirical studies, measurements and prediction<br>
Abbrevation
RE
City
BanffAB
Country
Canada
Deadline Paper
Start Date
End Date
Abstract