Software systems are becoming increasingly complex. Their ubiquitous presence makes users more dependent on their correctness in many aspects of daily life. As a result, there is a growing need to make software systems and their decisions more comprehensible, with more transparency in software-based decision making. Transparency is therefore becoming increasingly important as a non-functional requirement

Modeling of natural language requirements, especially for a large system, can take a significant amount of effort and time. Many automated model-driven approaches partially address this problem. However, the application of state-of-the-art neural network architectures to automated model element identification tasks has not been studied. In this paper, we perform an empirical study on automatic model

The design of data warehouses (DWs) is based on both their data sources and users’ requirements. The more closely the DW multidimensional schema reflects the stakeholders’ needs, the more effectively they will make use of the DW content for their OLAP analyses. Thus, considerable attention has been given in the literature to DW requirements analysis, including requirements elicitation, specification

The research in this paper adds to the discussion linked to the challenge of capturing and modeling tacit knowledge throughout software development projects. The issue emerged when modeling functional requirements during a project for a client. However, using the design science research methodology at a particular point in the project helped to create an artifact, a functional requirements modeling

Telos is a conceptual modeling language intended to capture software knowledge, such as software system requirements, domain knowledge, architectures, design decisions and more. To accomplish this, Telos was designed to be extensible in the sense that the concepts used to capture software knowledge can be defined in the language itself, instead of being built-in. This extensibility is accomplished

Software Product Line Engineering (SPLE) is a promising paradigm for reusing knowledge and artifacts among similar software products. However, SPLE methods and techniques require a high up-front investment and hence are profitable if several similar software products are developed. Thus in practice adoption of SPLE commonly takes a bottom-up approach, in which analyzing the commonality and variability

For a firm in an open source software (OSS) ecosystem, the requirements engineering (RE) process is rather multifaceted. Apart from its typical RE process, there is a competing process, external to the firm and inherent to the firm’s ecosystem. When trying to impose an agenda in competition with other firms, and aiming to align internal product planning with the ecosystem’s RE process, firms need to

Process mining helps infer valuable insights about business processes using event logs, whereas goal modeling focuses on the representation and analysis of competing goals of stakeholders and systems. Although there are clear benefits in mining the goals of existing processes, goal-oriented approaches that consider logs during model construction are still rare. Process mining techniques, when generalizing

Traceability is crucial for many activities in software and systems engineering including monitoring the development progress, and proving compliance with standards. In practice, the use and maintenance of trace links are challenging as artifacts undergo constant change, and development takes place in distributed scenarios with multiple collaborating stakeholders. Although traceability management in

We report experience in requirements elicitation of domain knowledge from experts in clinical and cognitive neurosciences. The elicitation target was a causal model for early signs of dementia indicated by changes in user behaviour and errors apparent in logs of computer activity. A Delphi-style process consisting of workshops with experts followed by a questionnaire was adopted. The paper describes

By increasing the importance of the performance in industrial and business software systems, efficient approaches to model-based performance engineering are becoming an inherent part of the development life cycle. Performance engineering at abstract levels of the software development process has an important effect on concluding the success of the software by obtaining the knowledge of optimal alternative

In incremental software development approaches, the product is developed in various releases. In each release, a set of requirements is proposed for the development. Usually, due to lack of funds, lack of time and dependency between requirements, there is no possibility to develop all the required requirements. There are two conflicting objectives for choosing an optimal subset of the requirements:

Planning an information system (IS) is challenging, especially for inexperienced IS analysts, including students. One area that often causes particular difficulty is defining the requirements of the future system—a phase that is crucial to the success of any IS project. While serving as advisers for students carrying out their first IS projects, we observed that “imagining” the future system’s functionality

Much research is ongoing to assess and improve compliance to laws and regulations. As this domain continues to grow and mature, and with more modelling methods introduced to support compliance tasks, important questions need to be asked. What exactly are these methods used for? Where have they been applied? What benefits do they offer? This paper explores how goal-oriented and non-goal-oriented modelling

App features are one of the most important factors that people consider when choosing apps. In order to satisfy users’ needs and attract their eyes, deciding what features should be added in next release becomes very important. Different from traditional requirement elimination, app stores provide a new platform for developers to gather requirements and perform market-wide analysis. Considering that

Completeness is one of the key attributes for a high-quality software requirements specification. Although incomplete requirements frequently occur in the requirements specification, it is rarely discovered. This turns out to be one of the major causes of software project failure. In order to handle this issue, this paper proposes an automatic approach to recommending omitted steps in a use case-based

eLearning systems have become a very important part of teaching, both as web-based systems for online education and as auxiliary tools for face-to-face study, where they provide an additional learning support for on-campus learners. To insure the sustainability of an eLearning system on both individual and social levels, we have to cover many aspects of sustainability requirements: human, technical

This paper proposes a unified knowledge management requirements engineering methodology (KM-REM) for tackling the complex nature of knowledge-intensive organizations. Despite the importance of KM for the success of knowledge-intensive organizations, the concept of RE for KM solutions is still vague lacking. Its definitions and guidelines for addressing the different facets of KM during the RE process

The article “Modular norm models: practical representation and analysis of contractual rights and obligations.

Requirements engineering (RE) involves the critical activities required to capture customers’ requirements/needs accurately. RE is a communication-intensive activity. As culture plays a major role in the way individuals communicate and perform a task, RE activities might be strongly influenced by individuals’ cultures. However, there are very few published works on this issue. The goal of this study

Cloud computing is used by consumers to access cloud services. Malicious actors exploit vulnerabilities of cloud services to attack consumers. The link between these two assumptions is the cloud service. Although cloud forensics assists in the direction of investigating and solving cloud-based cyber-crimes, in many cases the design and implementation of cloud services fall back. Software designers

Abstract Automotive manufacturers have historically adopted rigid requirements engineering processes. This allowed them to meet safety-critical requirements when producing a highly complex and differentiated product out of the integration of thousands of physical and software components. Nowadays, few software-related domains are as rapidly changing as the automotive industry. In particular, the needs

Abstract Companies and government organizations are increasingly compelled, if not required by law, to ensure that their information systems will comply with various federal and industry regulatory standards, such as the NIST Special Publication on Security Controls for Federal Information Systems (NIST SP-800-53), or the Common Criteria (ISO 15408-2). Such organizations operate business or mission

Abstract Companies that collect personal information online often maintain privacy policies that are required to accurately reflect their data practices and privacy goals. To be comprehensive and flexible for future practices, policies contain ambiguity that summarizes practices over multiple types of products and business contexts. Ambiguity in data practice descriptions undermines policies as an

'Socio-political' issues, such as emotions, values and people's feelings, are often cited as problems in the RE process. A method is described for analysing such issues. The method consists of a taxonomy of stakeholders' values, motivations and emotions (VME), with process guidance for eliciting and analysing these issues for the RE process and design implications. Values are personal attitudes or

Over the last two decades, much attention has been paid to the area of goal-oriented requirements engineering (GORE), where goals are used as a useful conceptualization to elicit, model, and analyze requirements, capturing alternatives and conflicts. Goal modeling has been adapted and applied to many sub-topics within requirements engineering (RE) and beyond, such as agent orientation, aspect orientation

In order to build resilient systems that can be operational for a long time, it is important that analysts are able to model the evolution of the requirements of that system. The Evolving Intentions framework models how stakeholders’ goals change over time. In this work, our aim is to validate applicability and effectiveness of this technique on a substantial case. In the absence of ground truth about

Requirements elicitation is one of the most important phases in the design process and applied by many engineering disciplines. A more recent application of the design process is to design the enterprise as an artefact, also called enterprise engineering (EE). Even though there are limits to formal enterprise design due to enterprise complexity, strategic intentions are not realised spontaneously or

In software reuse, the reuse of UML class diagram produced in design phase has received more attention due to the important influence on the following developing process. The reuse is based on similarity. The similarity between class diagrams contains semantic and structural aspects. The existing works focus on semantic similarity, while the structural similarity is little paid attention to. The structure

Stakeholder participation is a key success factor of Requirements Engineering (RE). Typically, the techniques used for identifying and involving stakeholders in RE assume that stakeholders can be identified among the members of the organizations involved when a software system is ordered, developed or maintained—and that these stakeholders can be told or even mandated to contribute. However, these

The replacement of legacy systems in the public sector is fraught with project delays, budgetary overruns, technological and business process complexities. Moreover, the software implemented to replace legacy systems is developed or configured to largely mimic their features and functionality in order to minimize the disruption to organizational operations that accompanies the introduction of new technology

Digital motivation refers to the use of software-based solutions to change, enhance, or maintain people’s attitude and behaviour towards specific tasks, policies, and regulations. Gamification, persuasive technology, and entertainment computing are example strands of such a paradigm. Digital motivation has unique properties which necessitate careful consideration of its analysis design methods. This