Location: Chalmers/GU Gothenburg
Time: 3-4 May (Lunch to Lunch)
Host: Dr. Robert Feldt

VENUE information

The meeting will be held at Chalmers Lindholmen
House Jupiter at the center of the map)

Hotel 11:
First hotel G:
Grand hotel:

Hotel 11 is close to the restaurant we plan to visit, and 15min by boat to the venue. First hotel and Grand hotel are 10 min bus ride from the venue.

Logo Logo Logo Logo

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 3
**12-13: Welcome, coffee, mingling

**13-13.30: Introduction (Tony Gorschek)

**13.30-14.15: State-of-Art in Requirements Engineering (Samuel Fricker)
Abstract: Today our understanding of requirements engineering practice is anecdotal at best. Academics and consultants research and teach things that are not what practitioners really need. We look at preliminary survey results and discuss how practitioners work, how their practice has evolved, and how well aligned research and teaching are.

**14.20-15.05: Visualizing, Analyzing and Managing the Scope of Software Releases in Large-Scale Requirements Engineering (Krzysztof Wnuk)
Abstract: Research thesis presentation. See

**15.05-15.20: Coffee and Refreshments - mingling

**15.20-16.05: Requirements Engineering and Software Test Alignment - Assessment and Improvement (Michael Unterkalmsteiner)
Abstract: With alignment we mean the adjustment of requirements engineering (RE) and software testing (ST) activities for coordinated functioning and optimized product development. We have developed a taxonomy, based on information links, to characterize RE and ST alignment, leading to a better understanding how alignment can be achieved. In this presentation we exemplify the use of the taxonomy 1) to understand the impact of process changes to alignment, 2) to identify bottlenecks that impede alignment, and 3) to identify potential improvements in the RE and ST coordination..

**16.10-16.55: Comparative Metrics and Norms from Industry: Research proposal for SIREN (Ali Shahrokni & Emil Börjesson)
Abstract: We propose a design for a study to be conducted in collaboration with the SIREN participants. In this study, we aim to gather metrics andnorms in different phases and parts of the software development process in the Swedish software industry. Our proposal contains some basic metrics such as project and company information, lines of code, number of requirements, number of test cases and some more advanced metrics such as code coverage. Given this data, researchers and the industry can benchmark their projects compared to the industrial norms in the industry. The aim is to gather as much data as possible in order to create a large library where data can be extracted by searching based on any arbitrary criteria included in the study. A simple example of such data is number of LOC per requirement or number of test cases per requirement in different software intensive fields. The data gathering will be mainly done by questionnaires and if deemed necessary with follow-up meetings. We welcome your feedback on the design of the study and on the selection of the metrics

**17.00-17.45: Common understanding of terminology and usage of widely acknowledged techniques and methods - key factors for successful Requirements Engineering (Stefan Sturm)
Abstract: Certification models are important instruments for standardization. The three level CPRE certification model addresses the discipline of requirements engineering. The Foundation Level started in 2006 is international well established. In 2011 the two Advanced Level modules “Requirements Elicitation and Consolidation” and “Requirements Modeling” have been published. This presentation introduces the International Requirements Engineering Board (IREB e.V.) and the certification model “Certified Professional for Requirements Engineering”. The structure and setup of the certification model are explained and important differences to other certification models are highlighted. The advantages of a common understanding of the terminology and the usage of widely acknowledged techniques and methods are outlined. The intention of the presentation is to explain about IREB’s mission and to initiate a discussion between SIREN and IREB about possible cooperation in whatever way.

**17.50-18.35: Functional and Non-functional Requirements in Swedish Industry Practice: Some statistics (Ali Shahrokni)
Abstract: We present some statistics from recent studies in Swedish Software Industry on the number and type of requirements. In particular we discuss differences between functional and non-functional requirements of different types as well as between requirements documents at different levels/phases of development. The material is based on document analysis as well as semi-structured interviews.

**18.35--> Hotel Check-in etc.

**20.00: SIREN dinner
Abstract: Food and excellent company. After dinner we can stay and mingle, and be merry.
Details: The dinner will be at the River Cafe and will be sponsored by Nordforsk. (Thank you Richard and Robert!). The menu is pre-set (Skagen toast topped with Swedish whitefish roe, Roasted loin of veal with salsa Verde, red wine demi-glace, shallots, Pommes Anna and French beans, Fresh strawberries with vanilla ice cream).

Day Two: May 4
**08.30-09.15: Bringing Strategic Reasoning into Requirements Engineering (Constantinos Giannoulis)
Abstract: Goal Oriented Requirements Engineering techniques comply/follow to the generic Requirement Engineering (RE) process and share some fundamental methodological characteristics. These techniques aim at capturing why the system to be is needed, what the system to be should and should not do, who will and won't do it. An important factor considered is the system’s organizational context, which usually roots into the organization's strategy and drives development. In our research, we aim at providing a common and understandable interface between strategy and requirements, whether that is for systems development of enterprise architecture. We propose a unified business strategy meta-model (UBSMM), that encompasses strategy notions from established business strategy formulations that cover three different perspectives of strategy: the resource based-view with Strategy Maps and Balanced Scorecards, the industrial view with the Value Chain and its variations, and innovative view with Blue Ocean Strategy. Such conceptual unification constitutes UBSMM the focal point for relating requirement techniques to strategy, thus introducing the organization context expressed by strategy into system requirements using models, which are means known to practitioners. This approach aims at enriching existing business-IT alignment approaches by introducing a model-driven perspective (UBSMM to Enterprise Models and Enterprise Architecture).

**09.20-10.05: Enterprise Modeling and Model-Driven Development using a Unifying Meta-Model and Communication Analysis (Iyad Zikra)
Abstract: Enterprise Modeling (EM) aims to capture and represent organizational knowledge in terms of models that cover different views of the enterprise. The resulting enterprise models can be leveraged in the development of information systems. Investigating how to use them as input to Model-Driven Development (MDD) is still an open challenge. This paper explores how a holistic EM approach, represented by a unifying meta-model for EM, can benefit from integrating with a full-cycle MDD framework consisting of 1) Communication Analysis, a communication-oriented business process modeling and requirements engineering method, and 2) the OO-Method, an object-oriented conceptual modeling framework with code generation capabilities.

**10.05-10.30 Coffee and Refreshments - mingling

**10.35-11.20: Consumer Value-awareness in Requirements Engineering (Eric-Oluf Svee)
Abstract: Within the context of business modeling no standardized methods for transforming quality requirements as described by consumers/stakeholders to system functions, i.e. to design models and artifacts, exist. Although general RE and its various methods recognize the need for modeling user needs, they do not classify them nor do they provide means to obtain them. Under the larger goal of improving the alignment between business and IT, our research explores how to make Requirements Engineering (RE) aware of these consumer values. Results have been published linking consumer values to business strategy approaches, as well as enterprise architectures.

**11.25-12.10: Transition to Agile: Implications for Test and Requirements Engineering (Robert Feldt)

**12.10-12.20: Wrap up (Tony Gorschek)

(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: tony.gorschek [AT]