Organizers

John Mylopoulos
University of Trento
Italy

Dimitris Karagiannis
University of Vienna
Austria
Web
e-mail

Goals and Areas of Interest

Both the Business Process Management (BPM) and Software Engineering (SE) communities have been actively exploring for a long time process-orientation and its implications respectively on business informatics and software. However, there has been little discussion of BPM’s role in SE. The aim of this workshop is to take a step towards filling this gap by launching a discussion that will hopefully lead to a better understanding of the role of BPM in SE.

a. Background
In both disciplines – SE and BPM – there are lifecycle models. In SE, for example, there is the classical Waterfall or V-Model, or more recent agile methods, e.g., XP (Extreme Programming) or DSDM (Dynamic Software Development Method). In BPM, proposed lifecycle models mainly come from industry but can be summed up to the following general phases: strategy and design, implementation, execution, monitoring/controlling and optimization.
One question that arises in this context is whether such lifecycle models can be combined to offer a holistic lifecycle view of socio-technical systems consisting of business processes and software systems. Another open question concerns the role BPM could play to improve SE processes by ensuring that they better address business needs and reduce the notorious Business/Technology divide.
The discussion on the major roles of BPM in SE can focus around the following areas: design & requirements engineering, transformation issues from design to implementation, execution environments for business process-oriented software systems and evaluation frameworks that span and bridge the business and technology perspectives.

b. Topics of Interest
The workshop wants to discuss approaches and methods mainly for the above mentioned areas from a business engineering perspective, a software engineering perspective and as well the integrated view of both disciplines. Relevant topics for the workshop therefore include, but are not limited to:

• Design and Requirements Engineering
  • BPM in its role as a “requirements supplier” for software engineering
  • BPM in model-driven approaches
  • Methods for business-driven software development
• Transformation
  • Integration frameworks approaches (e.g. business process, non-functional, functional requirements)
  • Transformation approaches from business to IT alignment
  • Tackling compliance issues for business process to software systems
  • Governance issues on the interface of business process management and software engineering
• Execution
  • Business-process-driven service discovery techniques
• Evaluation
  • Business Activity Monitoring, frameworks and models assessing IS success/effectiveness
  • Contribution of IS to improving business processes and their performance

Paper Review Process

The prospective workshop participants are invited to submit a paper related to the purpose of the workshop. The workshop will accept four types of submissions:

1. Completed research – this type of papers should include evidence to support the contribution and discussion on research findings and their theoretical and practical significance. The paper should not exceed 10 pages (excluding references and appendices). Accepted completed research papers will be allocated 30 minutes for presentation (including questions & answers) during the workshop.
2. Research-in-progress – this type of papers can report on research that is under way with preliminary results available at the time of the conference. The paper should not exceed 6 pages (excluding references and appendices). Accepted research-in-progress papers will be allocated 15 minutes for presentation (including questions & answers) during the workshop.
3. Experience and project papers – this type of paper can report on experiences on relevant topics and recently finished or ongoing projects (e.g. EU FP7). The paper should not exceed 6 pages. Accepted experience papers will be allocated 30 minutes for presentation (including questions & answers) during the workshop.
4. Position papers – this type of papers can include lucid and well-supported statements and suggestions on the topics e.g., directions for the discipline, open questions, criticism on the state-of-the-art, and novel approaches. The paper should not exceed 6 pages. Accepted position papers will be allocated 15 minutes for presentation (including questions & answers) during the workshop.

Paper Submission

Please check the Paper Formats, Submission and Publication Guidelines.

Important dates

Regular Paper Submission: April 06, 2010
Authors Notification: May 04, 2010
Final Paper Submission and Registration: May 19, 2010

Workshop Format

The workshop will comprise introductory contributions by the organizers and presentations of accepted papers and a concluding discussion.

1. Organizers view on the role of
   1. “BPM”
   2. “SE” and
   3. “BPM in Software Engineering”: How BPM supports the software engineering lifecycle.
2. Sessions organized around the four general topics
3. Concluding panel discussion

Contacts

o. Univ.-Prof. Dr. Dimitris Karagiannis
tel: +43 1 4277 39580
fax: +43 1 4277 39584
e-mail: dk@dke.univie.ac.at
web: http://www.dke.univie.ac.at