SIREN SIGNAL MEETING 2015 (SIGNAL’15)

SIREN SIGNAL MEETING 2015 (SIGNAL’15)

The SIREN dinner will be held at Brasserie Stadsparken, http://www.brasseriestadsparken.se/

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 25

**12-13: Welcome, coffee, mingling

**13-13.30: Introduction (Richard Berntsson Svensson)

**13.30-14.15: TBA (Grischa Liebel)
Abstract: TBA

**14.20-15.05: Enterprise Modeling and Requirements Engineering for Capability-Driven Development (Janis Stirna and Jelena Zdravkovic)
Abstract: Lately the notion of capability is gaining much presence within the field of Information Systems Engineering, due to a number of factors: the notion directs business investment focus, it can be used as a baseline for business planning, and it leads directly to service specification and design. Historically, it has been examined in Economics, Sociology, and Management Science. More recently, it has been considered in the context of Enterprise Modeling, for the specification and design of Information Systems using business planning as the baseline. The need for organizations to operate in changing environments is addressed by proposing a capability-oriented approach that integrates organizational development with IS development taking into account changes in the application context of the solution. This is referred to as Capability Driven Development (CDD). To ensure the needs of business stakeholders for variety of business contexts that an organization faces, and thus facilitate successful systems delivery, capability- driven development includes a method for requirements engineering, as well as early confirmations in practices.

**15.05-15.20: Coffee and Refreshments - mingling

**15.20-16.05: A Study of Value in Agile Software Development Organizations (Hiva Alahyari)
Abstract: The Agile manifesto focuses on the delivery of valuable software. In Lean the principles emphaise value, where every activity that does not add value is seen as waste. Despite the strong focus on value, and that the primary critical susscess factor for software intensive product development lies in the value domain, no empirical study has investigated specifically what value is. This presents a multiple case study that investigates how software value is interpreted and prioritized, and how value is assured and measured. Data was collected through semi-structured interviews with 23 participants from 14 agile software development organizations. The contribution of this study is fourfold. First, it examines what software value is. Second, it compares the perceptions and priorities of software value by domains and roles, respectively. Third, it includes an examination of what practices are used to realize software value in industry, and what hinders the realization of software value. Fourth, it characterizes what measurements are used to assure, and evaluate software value.

**16.10-16.55: Researching Requirements Engineering for an Open Innovation Context (Johan Linåker)
Abstract: During the last two decades a slow but steady change of external factors has set-up new conditions affecting the way in how software producing firms create and leverage innovations. Firms now need to look outside of their boundaries and start interacting with the open environment that encompasses them in order to stay innovative and keep a competitive advantage. To facilitate this shift Requirements Engineering needs to be adapted in order to manage the increase and complexity of new requirements sources as well as networks of stakeholders. Based on the research agenda described in this paper we expect to make a significant contribution by establishing guidelines and tools for how Requirements Engineering should be adapted to cope with challenges implied by Open Innovation, foremost in the areas requirements selection and decision making when using Open Source Software as a way to leverage Open Innovation.

**17.00-17.45: Integrating system, software and safety requirement engineering in an Agile and Lean fashion (Henrik Jonsson)
Abstract: TBA

**17.50-18.35: An Environment-Driven Ontological Approach to Requirements Elicitation for Safety-Critical Systems (Zhou Jiale)
Abstract: 

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

**20.00: SIREN dinner
Abstract: Food and excellent company. After dinner we can stay and mingle.
Details: The dinner will be at Brasserie Stadsparken http://www.brasseriestadsparken.se/ 

Day Two: May 26

**08.30-09.15: Flexible and scalable requirements artifacts in teaching and research with reqT.org (Björn Regnell)
Abstract: TBA

**09.20-10.05: TBA (Jenny Nordlund)
Abstract: 

**10.05-10.30 Coffee and Refreshments - mingling

**10.35-11.20: Requirement monitoring using Quality of Experience and challenges (Farnaz Fotrousi)
Abstract: Runtime requirement monitoring is useful to evaluate whether a software product or prototype operates requirements as expected (i.e. requirement verification), and in what level stockholders accept the requirements (i.e. requirement validation). Continuous feedback during the software runtime contributes to identify whether implemented requirements are in conformity with specification documents and capture real user needs to evolve the requirements. Quality of Experience (QoE) is a measure of stakeholders’ experiences during the usage of software in terms of how stakeholders perceive quality of the software and how they were satisfied with the functional requirements. Considering effects of contextual and behavioral factors on user perceptions, there is a need for an automated monitoring approach to receive user experience of a software use continuously, periodically from different groups of stakeholders. Here, a requirement monitoring solution is proposed that collects analytics of functional and non-functional requirements associated to a software usage as well as user perceptions about relevant requirements. The solution investigates the relations between requirements and their impacts on the users in order to evolve requirements based on users’ expectations. How the requirements are monitored frequently using QoE and what challenges are interfered are the subjects of this talk. 

**11.25-12.10: 

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

Questions: Contact: richard [AT] cse.gu.se