From Variability to Viability

Socially and industrially globalized environment generates the need for flexibility of enterprises acting, cooperating and preserving their identity in various value and supply chains and socio-technical ecosystems. Achieving required flexibility, ability to cooperate, and ability to care for enterprise identity is possible via use of information systems that can provide a high level of variability of systemically organized information services. The points of variation may reside in types of information provided, in information, data, software, hardware, and network architectures, systems development methods, and in types of chosen information sources in enterprises and their environment. Vigorous models are needed to handle the variability in enterprises in general and in information systems in particular. St. Beer\u27s Viable Systems Model known in organizational cybernetics is one of the candidates for handling and utilizing the variability to achieve enterprise viability via viable information systems

Requirements-based Simulation Execution for Virtual Validation of Autonomous Systems

The complexity of software is rapidly increasing in many domains. Therefore, simulations have become established as a testing tool in recent years. Especially the virtual validation of autonomous systems leads to increasingly complex simulation environments. Nevertheless, the scenarios and the simulation results are not linked to the requirements. To close this gap, we develop a lightweight approach that allows the user to extract functional information. Simulation results can then be presented in different levels of detail in the original requirements. This replaces difficult translations of requirements and allows permanent comparison at all test levels

How Can Personality Influence Perception on Security of Context-Aware Applications?

[Context and Motivation] Our lives are being transformed by context-aware software applications with important social, environmental, and economic implications. [Question/Problem] Experts recognized that quality attributes, e.g. security, are the cornerstone to get healthy social implications of these applications. However, do end-users (service consumers) perceive these attributes as so important? [Methodology] To answer this question, we designed a survey, to understand how end-users perceive security of context-aware software applications and how the users’ personality traits might influence their perceptions. To this end, we did a web-based survey that embeds two animated-demonstration videos in order to present i) the functionality of a context-aware mobile app, and ii) some vulnerabilities of the mobile app. It involved 48 subjects divided in two groups: subjects with software engineering (SE) background (Group A) and subjects without any SE background (Group B). [Results] Our study found that the importance of confidentiality and integrity is more clearly perceived by subjects with SE backgrounds (Group A). Accountability is more difficult to be perceived by subjects. And this difficulty can be even more pronounced for subjects without any SE background (Group B). Our findings suggest that importance preferences on security are influenced by personality types. For instance, open-minded people have a higher propensity to perceive the importance of confidentiality and integrity. Whilst, people with a high level of agreeableness hold quite different perceptions regarding the importance of authenticity and accountability. Analyzing the level of association between personality and the perceived importance on security, we found that the importance perceptions on confidentiality are influenced by the personality of subjects from Group B. And, the changes (positive an negative) in the importance perception on confidentiality are very strongly influenced by personality, even more so by the personality of subjects from Group B.</p

A Systematic Literature Review of Requirements Engineering Education

Requirements engineering (RE) has established itself as a core software engineering discipline. It is well acknowledged that good RE leads to higher quality software and considerably reduces the risk of failure or budget-overspending of software development projects. It is of vital importance to train future software engineers in RE and educate future requirements engineers to adequately manage requirements in various projects. To this date, there exists no central concept of what RE education shall comprise. To lay a foundation, we report on a systematic literature review of the feld and provide a systematic map describing the current state of RE education. Doing so allows us to describe how the educational landscape has changed over the last decade. Results show that only a few established author collaborations exist and that RE education research is predominantly published in venues other than the top RE research venues (i.e., in venues other than the RE conference and journal). Key trends in RE instruction of the past decade include involvement of real or realistic stakeholders, teaching predominantly elicitation as an RE activity, and increasing student factors such as motivation or communication skills. Finally, we discuss open opportunities in RE education, such as training for security requirements and supply chain risk management, as well as developing a pedagogical foundation grounded in evidence of effective instructional approaches

Live study proposal: collecting natural language trace queries

[Context & motivation:] Software traceability links which are created during the development process are subsequently underutilized because project stakeholders lack the skills they need to compose trace queries. TiQi addresses this problem by accepting natural language trace queries and transforming them to executable SQL. [Question/problem:] The TiQi engine depends on the presence of a domain model. This can best be constructed through collecting samples from potential users.We are interested to learn what trace queries would be of interest to potential stakeholders and what terminology they would choose to express those queries. [Principal ideas/results:]In this live study we will demonstrate TiQi in action, and lead the participants through a series of carefully crafted ’what-if’ scenarios designed to capture a variety of sample queries. [Contribution:] The study is expected to lead to a more extensive domain model which will improve the accuracy of TiQi’s query transformation process.Zuerst erschienen in: REFSQ-JP 2015, REFSQ workshops, research method track, and poster track : joint proceedings of REFSQ-2015 workshops, research method track, and poster track : co-located with the 21st International Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2015) : Essen, Germany, March 23, 2015 URN: urn:nbn:de:0074-1342-0 Page 207-21

Enterprise Modeling Support for SOA Migration

The migration to a Service Oriented Architecture (SOA) is a complex undertaking in terms of aligning business and IT concerns as well as analysis of technical aspects, such as identifying legacy systems in need of wrapping. Conceptual modeling can be particularly helpful for supporting SOA migration in terms of (1) bridging the gap between business and IT concerns, and (2) analyzing the as-is and to-be IT infrastructures. In this paper, based on the identified requirements, we extend a language for IT infrastructure modeling, called ITML. Using an extensively documented SOA migration scenario we show how extended ITML, in tandem with other languages from the MEMO language family, can be used for SOA migration analysis. Finally, we provide a scenario-based comparison between the extended ITML and ArchiMate

Requirements reuse and requirement patterns: a state of the practice survey

Context. Requirements engineering is a discipline with numerous challenges to overcome. One of these challenges is the implementation of requirements reuse approaches. Although several theoretical proposals exist, little is known about the practices that are currently adopted in industry. Objective. Our goal is to contribute to the investigation of the state of the practice in the reuse of requirements, eliciting current practices from practitioners, and their opinions whenever appropriate. Besides reuse in general, we focus on requirement patterns as a particular strategy to reuse. Method. We conducted an exploratory survey based on an online questionnaire. We received 71 responses from requirements engineers with industrial experience in the field, which were analyzed in order to derive observations. Results. Although we found that a high majority of respondents declared some level of reuse in their projects (in particular, non-functional requirements were identified as the most similar and recurrent among projects), it is true that only a minority of them declared such reuse as a regular practice. Larger IT organizations and IT organizations with well-established software processes and methods present higher levels of reuse. Ignorance of reuse techniques and processes is the main reason preventing wider adoption. From the different existing reuse techniques, the simplest ones based on textual copy and subsequent tailoring of former requirements are the most adopted techniques. However, participants who apply reuse more often tend to use more elaborate techniques. Opinions of respondents about the use of requirement patterns show that they can be expected to mitigate problems related to the quality of the resulting requirements, such as lack of uniformity, inconsistency, or ambiguity. The main reasons behind the lack of adoption of requirement patterns by practitioners (in spite of the increasing research approaches proposed in the community) are related to the lack of a well-defined reuse method and involvement of requirement engineers.Peer ReviewedPostprint (author's final draft

Unveiling the Life Cycle of User Feedback: Best Practices from Software Practitioners

User feedback has grown in importance for organizations to improve software products. Prior studies focused primarily on feedback collection and reported a high-level overview of the processes, often overlooking how practitioners reason about, and act upon this feedback through a structured set of activities. In this work, we conducted an exploratory interview study with 40 practitioners from 32 organizations of various sizes and in several domains such as e-commerce, analytics, and gaming. Our findings indicate that organizations leverage many different user feedback sources. Social media emerged as a key category of feedback that is increasingly critical for many organizations. We found that organizations actively engage in a number of non-trivial activities to curate and act on user feedback, depending on its source. We synthesize these activities into a life cycle of managing user feedback. We also report on the best practices for managing user feedback that we distilled from responses of practitioners who felt that their organization effectively understood and addressed their users' feedback. We present actionable empirical results that organizations can leverage to increase their understanding of user perception and behavior for better products thus reducing user attrition.Comment: 2024 IEEE/ACM 46th International Conference on Software Engineerin

Requirements Engineering that Balances Agility of Teams and System-level Information Needs at Scale

Context: Motivated by their success in software development, large-scale systems development companies are increasingly adopting agile methods and their practices. Such companies need to accommodate different development cycles of hardware and software and are usually subject to regulation and safety concerns. Also, for such companies, requirements engineering is an essential activity that involves upfront and detailed analysis which can be at odds with agile development methods. Objective: The overall aim of this thesis is to investigate the challenges and solution candidates of performing effective requirements engineering in an agile environment, based on empirical evidence. Illustrated with studies on safety and system-level information needs, we explore RE challenges and solutions in large-scale agile development, both in general and from the teams’ perspectives. Method: To meet our aim, we performed a secondary study and a series of empirical studies based on case studies. We collected qualitative data using interviews, focus groups and workshops to derive challenges and potential solutions from industry. Findings: Our findings show that there are numerous challenges of conducting requirements engineering in agile development especially where systems development is concerned. The challenges discovered sprout from an integration problem of working with agile methods while relying on established plan-driven processes for the overall system. We highlight the communication challenge of crossing the boundary of agile methods and system-level (or plan-driven) development, which also proves the coexistence of both methods. Conclusions: Our results highlight the painful areas of requirements engineering in agile development and propose solutions that can be explored further. This thesis contributes to future research, by establishing a holistic map of challenges and candidate solutions that can be further developed to make RE more efficient within agile environments

Beyond Traditional Feedback Channels: Extracting Requirements-Relevant Feedback from TikTok and YouTube

The increasing importance of videos as a medium for engagement, communication, and content creation makes them critical for organizations to consider for user feedback. However, sifting through vast amounts of video content on social media platforms to extract requirements-relevant feedback is challenging. This study delves into the potential of TikTok and YouTube, two widely used social media platforms that focus on video content, in identifying relevant user feedback that may be further refined into requirements using subsequent requirement generation steps. We evaluated the prospect of videos as a source of user feedback by analyzing audio and visual text, and metadata (i.e., description/title) from 6276 videos of 20 popular products across various industries. We employed state-of-the-art deep learning transformer-based models, and classified 3097 videos consisting of requirements relevant information. We then clustered relevant videos and found multiple requirements relevant feedback themes for each of the 20 products. This feedback can later be refined into requirements artifacts. We found that product ratings (feature, design, performance), bug reports, and usage tutorial are persistent themes from the videos. Video-based social media such as TikTok and YouTube can provide valuable user insights, making them a powerful and novel resource for companies to improve customer-centric development