Location: Stockholm University (SU)
Room: L30, Building NOD, Borgarfjordsgatan 12 Time: 26-27 May, 12 to 12.
Host: Jelena Zdravkovic and Janis Stirna
How to go to SU: Metro guideline: You can travel with the blue metro line (number 11) from Kungsträdgården or T-centralen (direction Akalla) to Kista (estimated travel time from T-centralen is 20 minutes). Walk out through the north ticket hall, in train direction if you arrive from Stockholm City and turn right after the escalator. Pass straight forward through Kista Galleria, pass over the footbridge, keep left, pass the Forum Building, pass over the footbridge, and turn right to the NOD (DSV) building.
* Ibis Styles Stockholm Kista is located in Kista only 10 minutes from the conference venue by foot. http://www.accorhotels.com/gb/hotel-3121-ibis-styles-stockholm-kista/index.shtml
* StayAt Kista's 166 hotel apartments are tailored to meet our guests' needs, whether they are single, couples or entire families. http://stayat.se/en/
* Hotel Gamla Stan is located in The Old Town of Stockholm about 30 minutes from the conference venue by metro. http://www.hotelgamlastan.se/
* Fridhemsplan City Hostel and Hotel is a low-cost hotel in the City of Stockholm about 25 minutes from the conference venue by metro. http://www.fridhemsplan.se/en/
* First Hotel Solna is a low-cost hotel in the Solna suburb about 20 minutes from the conference venue by metro. http://www.urbanhostels.se/index.php/vara-hotell-vandrarhem/solna
The SIREN dinner will be held at Jensens Böfhus in Kista, http://www.jensens.se/restauranger/kista/
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 26
**12-13: Welcome, coffee and "smörgås", mingling
**13-13.30: Introduction (Richard Berntsson Svensson)
**13.30-14.15: Managing cross-cutting requirements using Aspect-Oriented Business Process Management (Amin Jalali)
Abstract: Managing business processes is a challenging activity that requires considering different sort of requirements. These requirements specify different concerns that should be fulfilled in different business processes. Some of these concerns are scattered over others, which makes other concerns tangled to them. These concerns are known as cross-cutting concerns, and aspect orientation is a modularization technique to encapsulate these concerns. Several studies investigate how these concerns should be encapsulated in the programming, requirement engineering, and business process design areas. However, there is no investigation that specifies how these concerns should be enacted. In this study, we specifies how cross-cutting requirements should be modelled and enacted in business processes.
**14.20-15.05: Specification Tool for Supporting Agile and Efficient Development of Safety Critical Systems (Mattias Nyberg)
Abstract: Abstract: The automotive area has recently got their functional safety standard ISO26262. In combination with new complex and safety critical applications like autonomous vehicles, this puts challenges on the automotive companies to revise their development practices. These new development practices contain both new methods, like formal verification and are also generally more rigorous, especially with a focus on traceability. At the same time, development speed and efficient development with agile methods must not be compromised. A cornerstone in safety critical development is specifications with clearly identified safety requirements. To support this, Scania has together with KTH and within a Vinnova-funded project, developed a new specification tool for development of both safety critical and non-safety critical application using an agile approach. Traceability is managed by using the principles of Linked Data and OSLC.
**15.05-15.20: Coffee and Refreshments - mingling
**15.20-16.05: Engineer-friendly formal requirements specification and analysis (Predrag Filipovikj)
Abstract: Abstract: Formal verification techniques such as model-checking can be applied to guarantee safety and liveness properties of system models. Formalizing natural language requirements represents a way of precisely describing the semantics of the requirements and the main prerequisite for applying model-checking techniques on semantically well-defined models. For real-world industrial systems, natural language requirements can be complex so their formal specification might become an intricate process that requires knowledge in formal logics thus rendering the formalization process not engineer-friendly. We present results from the VeriSpec project, a collaboration between Mälardalen University, Scania and Volvo GTT on methodologies and tools for engineer-friendly formal requirements specification and analysis. First, we review a methodology called Specification Pattern System for semi-formal and formal requirements specification, based on the best practices for system description and suitable for the automotive domain. Second, we present our tool, called SESAMM Specifier that facilitates adoption of the proposed methodology in industrial settings, by providing flexible integration within the existing industrial tool-chains. Lastly, provided that the system requirements specification have been formally encoded, we present a technique for checking consistency of system requirements specification in the early stages of development, prior to existence of any behavioral model.
**16.10-16.55: A Model-based Approach for Capturing Consumer Preferences from Crowdsources: the Case of Twitter (Eric-Oluf Svee)
Abstract: In this study we collect consumer preferences through crowdsourcing, and
in particular Twitter, because of its increasing popularity as a source
of up-to-date comments and information about current services and
products. The tweets of four major American airlines were processed
using different techniques from natural language processing (NLP) that
enabled the classification of their objectives, content, and importance
within a conceptualization of consumer preferences—the Consumer
Preference Meta-Model (CPMM). These were the basis for deciding what
would be considered to be developed into supporting information
systems and services. Next, mapping the highest-ranked results from CPMM to goal models enabled a model-based linkage from a corpus of preferences contained within the short texts (tweets) to high-level requirements for systems and services.
**17.00-17.45: Towards solving traceability challenges for suppliers in the automotive domain (Salome Maro)
Abstract: Traceability in software development refers to the ability to link software artifacts like requirements, code and tests throughout the development life cycle. Despite the fact that there is a lot of research done on this area, the subject still remains an open problem. This is especially true in the automotive domain that deals with complex and safety-critical embedded systems. The aim of the study presented in this talk is to investigate traceability challenges that exist in the automotive industry in practice and compare them to those reported in literature. We also look at how proposed solutions in literature compare to those applied in practice. The study consists of a literature review, interviews and observations in two departments of a large automotive supplier, and a comparative analysis. Our preliminary results uncover a set of persisting challenges and why proposed solutions are not feasible in practice.
**18.15: SIREN dinner
Abstract: Food and excellent company. After dinner we can stay and mingle.
Details: The dinner will be at Jensens Böfhus in Kista http://www.jensens.se/restauranger/kista/
**After dinner --> Hotel Check-in etc.
Day Two: May 27
**08.30-09.15: Statistical methods in requirements engineering (Panagiota Chatzipetrou)
Abstract: The large number of requirements and the different views of the employees participating in a survey, define what are the most important requirements and therefore deserve higher priority makes the problem of decision-making extremely difficult and complex. Those data are collected from questionnaires in which special methods are applied (Cumulative Voting). The questionnaires are completed by the stakeholders in such research containing their views coded into numerical "scores" for the prioritization of various requirements. Although the simple sum of the scores from all participants shows which requirements are the most important, the overall information that exists in the data conceals considerable variability and deserves further investigation. Special methods of multivariate analysis required for such data, since the usual regularity assumptions and independence does not apply here. These methods will have to answer to several questions related to the level of alignment between the stakeholders, the conflicting nature of the requirements, with the grouping of views and the comparison of views among the inherit groups of stakeholders. Τhe management of software projects, the appropriate allocation of resources in the various software phases in relation to the investigation of the high complexity of the distribution of effort are interesting problems which should be studied with multivariate methods. Multivariate statistical frameworks like Compositional Data Analysis (CoDA) are introduced. This analysis includes a wide variety of techniques that aspire to answer critical questions about the priorities of quality requirements as defined by people who behave and express an opinion according to the position they occupy in an organization and the perspective from which the prioritize the quality of the software.
**09.15-10.00: Quality Requirements for an Integration Design Methodology (Iyad Zikra)
Abstract: The technical overhead of integrating information systems is substantial, which limits the added value expected by organizations. Furthermore, The quality of the designed integration is not well understood. A holistic methodology for integration design is being developed to facilitate the creation of integration solutions with established quality criteria. The methodology is divided into three stages. It starts with analysing the integrated systems to populate model instances of the Unifying Meta-Model (UMM), a MDD approach for modelling the organization and its information systems. In the next stage, the models are extended and developed to design the integration solution, including a model of the platform-specific implementation. The final stage covers transforming the models into a system implementation deployed in a production environment. This study explores the quality requirements that affect the integration design methodology. How should the methodology be designed to minimize organizational and technical overhead? How do model quality criteria affect the methodology? What is the role of the tooling environment and integration patterns? Finally, how will the overall improvement offered by the methodology be measured?
**10.00-10.30 Coffee and Refreshments - mingling
**10.35-11.20: Contribution Strategies and Stakeholder Profiles (Johan Linåker)
Abstract: Abstract: Open Source Software (OSS) has proved to play a pivotal part in many software-intensive firms' product strategies and Open Innovation (OI) business models. One reason for this lies in the access to an external workforce, which may imply that costs can be reduced due to lower internal maintenance and higher product quality, as well as a faster time-to-market and increased product and process innovation. However, to gain these benefits of OSS and OI, firms need to establish policies for how they plan to use an OSS project in relation to their business model, and how they should interact with the project's surrounding ecosystem. Firms need to know what to reveal, when and how. A wrong focus may imply unnecessary internal maintenance and patch-work, un-synced release cycles and the give-away of valuable functionality to competitors. In this talk we will describe ongoing research on how firms can structure their work with a contribution strategy framework. Creation of such strategies and guidelines for what parts that are to be considered contributable, and when, can hopefully help firms to better focus their internal resources on value creating activities and still maintain a competitive edge.
**11.25-12.10: A Hazard Domain Ontology for Safety-Critical Systems (Zhou Jiale)
Abstract: Preliminary hazard analysis (PHA) is a crucial activity, applied during the early stages of safety-critical systems (SCSs) development process. The main goal of the PHA is to provide stakeholders, throughout the development process, with a general understanding of potential hazards that are likely to involve the SCSs under analysis. There have been different PHA techniques proposed in the literature to support the identification of hazards. However, to our best knowledge, there are few pieces of work that formally discuss the nature of hazards, i.e., conceptualize the knowledge of hazards to answer questions such as what is the formal definition of hazard and what are the relations between the factors that constitute a hazard. With the increasing complexity of the SCSs, various stakeholders will be involved in the development process. Therefore, a sharing conceptualization of hazard is of significant importance to achieve the goal of PHA. In this work, we propose a hazard domain ontology, i.e., the Hazard Ontology (HO), to define a conceptualization of hazard and the relations between the factors that constitute a hazard. In addition, the HO is grounded in the Unified Foundational Ontology (UFO) to utilize the benefits provided by taking foundational concepts into account. Finally, two sets of hazard descriptions are utilized to evaluate the HO, and the results have provided evidence that our ontology can adequately capture the knowledge of hazards.
**12.10-12.20: 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] bth.se