Support Requirements Engineering Research Articles

SEMKIS-DSL: A Domain-Specific Language to Support Requirements Engineering of Datasets and Neural Network Recognition

Neural network (NN) components are being increasingly incorporated into software systems. Neural network properties are determined by their architecture, as well as the training and testing datasets used. The engineering of datasets and neural networks is a challenging task that requires methods and tools to satisfy customers’ expectations. The lack of tools that support requirements specification languages makes it difficult for engineers to describe dataset and neural network recognition skill requirements. Existing approaches often rely on traditional ad hoc approaches, without precise requirement specifications for data selection criteria, to build these datasets. Moreover, these approaches do not focus on the requirements of the neural network’s expected recognition skills. We aim to overcome this issue by defining a domain-specific language that precisely specifies dataset requirements and expected recognition skills after training for an NN-based system. In this paper, we present a textual domain-specific language (DSL) called SEMKIS-DSL (Software Engineering Methodology for the Knowledge management of Intelligent Systems) that is designed to support software engineers in specifying the requirements and recognition skills of neural networks. This DSL is proposed in the context of our general SEMKIS development process for neural network engineering. We illustrate the DSL’s concepts using a running example that focuses on the recognition of handwritten digits. We show some requirements and recognition skills specifications and demonstrate how our DSL improves neural network recognition skills.

HANDLING OF EXPLICIT UNCERTAINTY IN REQUIREMENTS CHANGE MANAGEMENT

AbstractInnovation projects are characterized by numerous uncertainties. Typical concepts in development management like the application of safety coefficients imply limitations of the solution space. In contrast, explicit handling of uncertainties can support engineers in understanding the problem space and in utilising the full potential of the design space along iterative product development steps. As a result from literature analysis, there is a lack of a support for product development that addresses the specific problem of uncertainty and risk in the context of requirement changes. The aim of the contribution at hand is to enhance the efficient development of complex interdisciplinary systems by enabling uncertainty handling in requirements change management. Based on a classification of uncertainty types resulting in a descriptive model, risk management measures are identified to support requirements engineers. The proposed method includes identification & modelling, analysis, treatment and monitoring of risks and counter-measures. By applying this method, engineers are supported in adopting agile approaches and enabling flexible Requirements Engineering.

Identifying Cross-Domain Linkage Types to Support Engineering Change Management and Requirements Engineering

Suitable product models are essential to support development of complex products like today’s vehicles. Using these models, different views upon the product are represented, product evolution over different lifecycle phases can be documented and communication on and exchange of product information is performed. However, to derive an adequate representation of a complex product is challenging, since on the one hand elements of the product designed by different engineering domains (mechanics, electric/electronics, software) need to be considered. On the other hand, linkages between domain specific models and their elements have to be captured, for instance, to handle changes and derive or test requirements across domain borders. As a basis for adequate models in product design, this paper describes the concept of system views in particular focusing on linkages between elements within the technical perspective. Therefore, linkage types (e.g. spatial relation, material transfer) between product elements are analyzed by a literature review and their relevance for engineering domains involved in the product design process is discussed. In order to trigger and guide cross-domain engineering activities in particular regarding engineering change management and requirements engineering in the vehicle design process, a set of domain-specific and cross-domain linkage types is derived and applied using the vehicle as example. Finally, criteria and a procedure to indicate the cross-domain nature of a linkage type and therefore the need for cross-domain interaction in the design process of complex products are presented.

DALTON: a Generic Meta-Model to Support Business Rules and Requirements Engineering in a PLM System

This paper deals with the management of business rules and requirements to be integrated to a PLM system during the SE process. It proposes a rule and requirement management process made of four stages: the expression of the rule, the activation of the rule, the application of the rule and the checking of the requirement. To support this process, a generic meta-model is presented. The proposed model is called DALTON for “DAta Linked Through Occurrences Network” because it is based on a data network. The model is validated with a use case taken from the nuclear industry, and algorithms in Java were developped to implement the associated reasoning automating the process of rules and requirements engineering.

PERSA: A Requirements Specification Process for Self-Adaptive Systems Based on Fuzzy Logic and NFR-Framework

Self-Adaptive Systems are able to change their behavior at runtime according to the environment where they are. This study presents an approach to specify the requirements for self-adaptive systems based on the concepts of Fuzzy Logic, which deals with factors such as ambiguity, uncertainties and vague information on the solution of problems; and NFR-Framework, which deals with the non-functional requirements which, very often, vaguely and full of uncertainties present themselves. Adaptive systems consist of (functional and non-functional) requirements, which hold the capacity to modify themselves during the runtime with little or no human intervention at all. Requirements that carry out the feature of wide variability are called adaptive requirements. PERSA (acronym from “Processo de Especificação de Requisitos Adaptativos”, in Portuguese) is reported in this work, using the Fuzzy Logic and the NFR-Framework as a basis, since both offers resources to manage uncertainties, an inherent attribute of self-adaptive systems. This process aims the approach of specification of adaptive requirements in a systematic way providing a guide to support requirements engineers. PERSA Process is settled in three mains phases subdivided into several steps. Two case studies were developed to validate it: the first deals with an automated system to prepare steaks, which needs to adapt to its several types; the second relates to a system for automation for canine diets, which must be adapted to different breeds of dogs according to their size, weight and classification. The case studies provide a first approach of the use and benefits of PERSA Process. In these studied the theoretical proposal was evaluated and discussed in order to establish the degree of understanding, the clarity of activities and the necessary adjustments to improve the proposed achievements, thus obtaining a satisfactory though early assessment which answers the purpose of specifying the requirements for self-adaptive systems.

Using popular social network sites to support requirements elicitation, prioritization and negotiation

Social networks have changed our daily life and they have the potential to significantly influence and support Requirements Engineering (RE) activities. Social network-based RE approaches will allow us to overcome limitations of traditional approaches and allow end users to play a more prominent role in RE. They are key stakeholders in many software projects. However, involving end users is challenging, particularly when they are not within organizational reach. The goal of our work is to increase end user involvement in RE. In this paper we present an approach where we harness a social network to perform RE activities such as elicitation, prioritization and negotiation. Our approach was applied in three studies where students used Facebook to actively participate in RE activities of different projects. Although there are limitations, the results show that a popular social network site can support distributed RE.

Applications of ontologies in requirements engineering: a systematic review of the literature

There is an increase use of ontology-driven approaches to support requirements engineering (RE) activities, such as elicitation, analysis, specification, validation and management of requirements. However, the RE community still lacks a comprehensive understanding of how ontologies are used in RE process. Thus, the main objective of this work is to investigate and better understand how ontologies support RE as well as identify to what extent they have been applied to this field. In order to meet our goal, we conducted a systematic literature review (SLR) to identify the primary studies on the use of ontologies in RE, following a predefined review protocol. We then identified the main RE phases addressed, the requirements modelling styles that have been used in conjunction with ontologies, the types of requirements that have been supported by the use of ontologies and the ontology languages that have been adopted. We also examined the types of contributions reported and looked for evidences of the benefits of ontology-driven RE. In summary, the main findings of this work are: (1) there are empirical evidences of the benefits of using ontologies in RE activities both in industry and academy, specially for reducing ambiguity, inconsistency and incompleteness of requirements; (2) the majority of studies only partially address the RE process; (3) there is a great diversity of RE modelling styles supported by ontologies; (4) most studies addressed only functional requirements; (5) several studies describe the use/development of tools to support different types of ontology-driven RE approaches; (6) about half of the studies followed W3C recommendations on ontology-related languages; and (7) a great variety of RE ontologies were identified; nevertheless, none of them has been broadly adopted by the community. Finally, we conclude this work by showing several promising research opportunities that are quite important and interesting but underexplored in current research and practice.

NLP-KAOS for Systems Goal Elicitation: Smart Metering System Case Study

This paper presents a computational method that employs Natural Language Processing (NLP) and text mining techniques to support requirements engineers in extracting and modeling goals from textual documents. We developed a NLP-based goal elicitation approach within the context of KAOS goal-oriented requirements engineering method. The hierarchical relationships among goals are inferred by automatically building taxonomies from extracted goals. We use smart metering system as a case study to investigate the proposed approach. Smart metering system is an important subsystem of the next generation of power systems (smart grids). Goals are extracted by semantically parsing the grammar of goal-related phrases in abstracts of research publications. The results of this case study show that the developed approach is an effective way to model goals for complex systems, and in particular, for the research-intensive complex systems.

A mapping model for assessing project effort from requirements

Since the effort required to develop a system depends on its requirements, it is important to consider the resulting effort when deciding on the requirements. Miscalculating the effort may lead to requirements that cannot be implemented within given budget constraints. In order to support requirements engineers in calculating the effort resulting from the requirements they elaborate correctly, we develop a mapping model for assessing project effort from requirements (MMAPER) in this paper. MMAPER incorporates effort estimation into requirements engineering and thereby enables engineers to proactively assess project effort without demanding that they spend significant additional time on this task. MMAPER measures system size using function point analysis and assesses the resulting effort using the Constructive Cost Model 2. The theoretical underpinning of the methods stems from theoretical perspectives from which we derive theories of how requirements determine the resulting project effort. We also take into consideration that it is important to distinguish requirements of different size but also implemented in different contexts for estimating the resulting effort. We empirically evaluate the model using data from five case studies which we conducted with a financial services organization. The developed model provides very accurate effort estimations, across both controlled experiments and field applications.

A graphic SDL support environment

An SDL toolset is presented which is based on the semantics and syntax of the design language SDL recommended by the CCITT. SDL has been developed for the specification of telecommunication systems. In the meantime it has been accepted by a wider user community for the description of various real time systems. In this way a first version of the SDL tool is currently being used in the development of the telephone exchange HICOM as well as in the field of automation technology. The toolset supports the design phase and initiates the implementation and test phase. The drawing of SDL block diagrams, process diagrams, tree diagrams and sequence charts is essentially facilitated by workstations with raster graphics. At present the SDL tool is implemented on the SICOMP WS 30 UNIX workstation. The diagrams can be syntactically checked and there is the possibility of an automatic generation of different target codes. In addition validation tools are incorporated such as to check liveness properties or to simulate the dynamic behaviour before implementation. Further, connections to other software tools are planned that support requirements engineering.