Requirements Engineering (RE) aims to capture intended system functionality and qualities. For that, requirements are often explicitly captured in various types of conceptual models. Such models allow for sharing a collaborative perception of requirements, can facilitate analysis, and can transform towards design, specification, and code. In practice, requirements activities often fall under the heading of Business Analysis (BA), determining how a business can make use of technology in order to improve its operations, meet targets, and thrive in a competitive economy. Use of models in this context allows for an explicit consideration of business strategy, including requirements specifying how such strategies can be operationalized through socio-technical systems. Moreover, conceptual modeling can be a core asset as part of a business intelligence initiative, using models to monitor and reason over the real-time achievement of business strategies.
The MREBA workshop aims to provide a forum for discussing the interplay between Requirements Engineering and Business Analysis topics and Conceptual Modeling. In particular, the workshop focuses on how requirements modeling can be effectively used as part of Business Analysis and Systems Engineering. We ask: What are the fundamental objectives and premises of RE/BA and conceptual modeling respectively, and how can they complement each other? What conceptual modeling techniques can be utilized in RE/BA? How can RE/BA modeling be applied successfully in a business environment? What lessons are there to be learned from industrial experiences? What empirical data can support cost-benefit analyses when adopting RE/BA methods? Are there applications, domains or types of project settings for which RE/BA approaches are particularly suitable or not? What degree of formalization and automation or interactivity is feasible and appropriate for which types of participants during RE/BA modeling?
Topics of Interest
Submissions should address the relation between Requirements Engineering and/or Business Analysis and conceptual modelling on the selected topic. Topics of interest include but are not limited to:
- Modelling for Business Analysis and Business Intelligence
- Elicitation, analysis and evaluation of requirements
- Agile approaches to requirements engineering
- Domain understanding and scenarios analysis
- Management and reuse of requirements
- Automation of requirements transformation to software development artifacts
- Capturing prioritization, customization and preferences
- Modelling methodologies, processes, and methods
- Stakeholder analysis and communication
- Requirements as part of Enterprise Modelling and Enterprise Architecture
- Goal/Intention-Oriented Requirements Engineering (GORE)
- Modelling as part of collaborative RE/BA
- RE/BA model scalability, complexity, and modularity
- Industrial or systems requirements modeling
- Model feedback and validation
- RE/BA language interoperability, integration, transformation
- Ontological perspectives on RE/BA models
- Capturing laws, regulation, and compliance
- Visual notation for RE/BA models
- Analysis and reasoning, including decision support
- Modelling security, privacy, risk, and safety
- Industrial experiences, empirical studies and tools related to RE/BA modelling
Format and Duration
We aim for a highly interactive forum. The intended workshop duration is three sessions (1.5 hours each), including at least one session of paper presentations and discussions. We intend to include a keynote and, depending on the number of accepted papers, a panel or interactive session.
See Call for Papers for types of papers and submission instructions.