Sponsor of SIREN 2017

Location: Blekinge Institute of Technology
Time: 11-12 May, 12 to 12.
Room: Thursday (May 11): J1270, Friday (May 12): J1650
Host: Krzysztof Wnuk

How to get there, see:

VENUE information

Scandic Karlskrona:
Hotel Clarion Carlscrona:
First Hotel Statt Karlskrona:
First Hotel JA Karlskrona:
Hotel Conrad:
Hotel Aston:

You can also find information about hotels in Karlskrona via RE14’s website:

Confirmed presenters

  • Stefan Eekenulv, INCEPTIVE - "Can Sisyfos actually get the stone to the top with the right thinking tools?"
  • Eric Oluf Svee, Stockholm University - "Utilizing User Values to Generate System Requirements for a Geographically - dispersed Workforce"
  • Alexandru-Tudor Caldare and Jelena Zdravkovic, Stockholm University - "Improving System Requirements Processing: An approach of using Behavioral Driven Development for requirements management – the Scrum case"
  • Michael Unterkalmsteiner, Blekinge Institute of Technolog - "Which requirements artifact quality defects are automatically detectable?"
  • Johan Linåker, Lund University - "A Contribution Management Framework for Firms Engaged in Open Source Software Ecosystems"
  • Jennifer Horkoff, Chalmers | University of Gothenburg - "Modeling, Reasoning, and Creativity for Early Requirements Engineering"
  • Rashida Kasauli, Chalmers | University of Gothenburg - "Towards RE for Agile Development of Safety Critical Systems"
  • Tony Gorschek/Richard Berntsson Svensson, Blekinge Institute of Technology - "PROMPT"
  • AGENDA (tentative - subject to change)

    General Notes: All talks are scheduled for 45min. This implies a MAXIMUM of 30 min presentation then 15 min QnA.

    Day One: May 11
    **12-13: Welcome, coffee and "smörgås", mingling

    **13-13.30: Introduction (Richard Berntsson Svensson/Krzysztof Wnuk)

    **13.30-14.15: Utilizing User Values to Generate System Requirements for a Geographically - dispersed Workforce (Eric Oluf Svee)
    Abstract: A geographically-dispersed workforce presents challenges for requirements engineering of enterprise systems, with problems such as limited access to stakeholders, the lack of trust between distant users and developers, and the lack of informal communication. Not only must the different standard organizational and personnel issues be taken into consideration, geographic dispersal also significantly hampers the steps of the requirements engineering process. This research investigates whether a method based on psychological methods for measuring personal values can be used to develop requirements for geographically-dispersed outposts within the same organization. The value profiles for frontline security guards distributed across Sweden were collected through the use of both a psychological questionnaire and interviews, and the results were used to generate requirements for field equipment and the concomitant information systems needed to support them, with goal- and feature models generated as a final result.

    **14.20-15.05: PROMPT (Tony Gorschek/Richard Berntsson Svensson)
    Abstract: TBA

    **15.05-15.20: Coffee and Refreshments - mingling

    **15.20-16.05: Can Sisyfos actually get the stone to the top with the right thinking tools? (Stefan Eekenulv)
    Abstract: I will talk about my current assignment at Trafikkontoret in Goteborg. How difficult it can be to work with processes and change management when the customer does not know what they really want and need. And how to work without having a clear mandate to to implement ideas and changes and still make changes. Specifically the methods and thinking behind the RACI(PeSQ)-model (an extended version of the traditional RACI- model) and the results in the organisation working with the model as a strategic tool to get focus on role-definitions and overlapping responsibility. Short presentation of results from a minor survey and notes from interviews, documents and meetings along the way.

    **16.10-16.55: Towards RE for Agile Development of Safety Critical Systems (Rashida Kasauli)
    Abstract: TBD

    **17.00-18.30: The future of RE research in Sweden
    Abstract: First, Björn Regnell with give his personal view on the relevance and impact of RE research, then we will work in small groups to discuss the future RE research in Sweden, and finally we have a common discussion where all ideas/views are presented and discussed.

    **18:30 Hotel Check-in etc.

    **20.00: SIREN dinner
    Abstract: Fooid and excellent company.
    Details: The dinner will be at Nivå Bar & Stekhus

    Day Two: May 12
    **08.30-09.15: Which requirements artifact quality defects are automatically detectable? (Michael Unterkalmsteiner)
    Abstract: [Context:] The quality of requirements engineering artifacts, e.g. requirements specifications, is acknowledged to be an important success factor for projects. Therefore, many companies spend significant amounts of money to control the quality of their RE artifacts. To reduce spending and improve the RE artifact quality, methods were proposed that combine manual quality control, i.e. reviews, with automated approaches. [Problem:] So far, we’ve seen various approaches to automatically detect certain aspects in RE artifacts. However, we still lack an overview what can and cannot be automatically detected. [Approach:] Starting from an industry guideline for RE artifacts, we classify 166 existing rules for RE artifacts along various categories to discuss share and characteristics of those rules that can be automated. For those rules, that cannot be automated, we discuss the main reasons. [Contribution:] We estimate that 53% of the 166 rules can be checked automatically either perfectly or with a good heuristic. Most rules need only simple techniques for checking. The main reason why some rules resist automation is due to imprecise definition. [Impact:] By giving first estimates and analyses of automatically detectable and not automatically detectable rule violations, we aim to provide an overview of the potential of automated methods in requirements quality control.

    **09.15-10.00: A Contribution Management Framework for Firms Engaged in Open Source Software Ecosystems (Johan Linåker)
    Abstract: Contribution Management helps firms engaged in Open Source Software ecosystems to create contribution strategies which motivate what they should contribute and when, but also what they should focus their resources on and to what extent. The motivation for developing tailored contribution strategies is to maximize return on investment and sustain the influence needed in the ecosystem. Through a design science approach, we aim to develop a decision-support to help firms answer questions implied by the contribution management process. In this talk I will present some current and upcoming work related to this decision-support.

    **10.00-10.30 Coffee and Refreshments - mingling

    **10.30-11.15: Modeling, Reasoning, and Creativity for Early Requirements Engineering (Jennifer Horkoff)
    Abstract: The discovery of system requirements in the early stages of Software Engineering comes with a series of challenges: how to understand, reason, and select over a space of possible requirements? How to manage and reason over requirements uncertainty? How to ensure that the requirement space is sufficiently creative, supporting system and business innovation? In this talk, I summarize past and current efforts to address these questions, focusing on methods and tools for interactive reasoning and creativity support for Early Requirements Engineering.

    **11.15-12.00: Improving System Requirements Processing: An approach of using Behavioral Driven Development for requirements management – the Scrum case (Alexandru-Tudor Caldare and Jelena Zdravkovic)
    Abstract: Abstract: One dominant innovation regarding software development is still represented by the Agile methodology since the establishment of the Agile Manifesto in 2001. Agile is an iterative approach that offers more flexibility while having less documentation and focuses on short and quick product releases in software engineering. Scrum is a successful and broadly used Agile methodology offering a complete framework regarding coverage of the whole project and process of system development. Although Scrum has wide usage, it does not provide a clear model of how to manage system requirements specification. In this context, system requirements should be represented clearly and with a focus on the delivery of behaviors described as what the system must do. Behavioral Driven Development (BDD) allows developers and domain experts to specify requirements represented as the behavior of the system. BDD can be seen as an evolved Agile technique that has many capabilities about requirements specification and management that can relate to the different phases of the Scrum framework. The goal of this research is to extend the Scrum framework by using BDD concepts and processes to better support the representation of system requirements in software development.

    **12.00-12.10: Wrap up (Richard Berntsson Svensson)

    (If you are not on the list you are not planned to be a participant! If you want to come then you need to email me ASAP).

    Contact: rbs [AT]