Semantics of trace relations in requirements models for consistency checking and inferencing

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined. The application of requirements reasoning based on formal semantics resolves many of the deficiencies observed in other approaches. Our tool supports better understanding of dependencies between requirements

Clafer: Lightweight Modeling of Structure, Behaviour, and Variability

Embedded software is growing fast in size and complexity, leading to intimate mixture of complex architectures and complex control. Consequently, software specification requires modeling both structures and behaviour of systems. Unfortunately, existing languages do not integrate these aspects well, usually prioritizing one of them. It is common to develop a separate language for each of these facets. In this paper, we contribute Clafer: a small language that attempts to tackle this challenge. It combines rich structural modeling with state of the art behavioural formalisms. We are not aware of any other modeling language that seamlessly combines these facets common to system and software modeling. We show how Clafer, in a single unified syntax and semantics, allows capturing feature models (variability), component models, discrete control models (automata) and variability encompassing all these aspects. The language is built on top of first order logic with quantifiers over basic entities (for modeling structures) combined with linear temporal logic (for modeling behaviour). On top of this semantic foundation we build a simple but expressive syntax, enriched with carefully selected syntactic expansions that cover hierarchical modeling, associations, automata, scenarios, and Dwyer's property patterns. We evaluate Clafer using a power window case study, and comparing it against other notations that substantially overlap with its scope (SysML, AADL, Temporal OCL and Live Sequence Charts), discussing benefits and perils of using a single notation for the purpose

Modeling and Analysis of Unmanned Aerial Vehicle System Leveraging Systems Modeling Language (SysML)

The use of unmanned aerial vehicles (UAVs) has seen a significant increase over time in several industries such as defense, healthcare, and agriculture to name a few. Their affordability has made it possible for industries to venture and invest in UAVs for both research and commercial purposes. In spite of their recent popularity; there remain a number of difficulties in the design representation of UAVs, including low image analysis, high cost, and time consumption. In addition, it is challenging to represent systems of systems that require multiple UAVs to work in cooperation, sharing resources, and complementing other assets on the ground or in the air. As a means of compensating for these difficulties; in this study; we use a model-based systems engineering (MBSE) approach, in which standardized diagrams are used to model and design different systems and subsystems of UAVs. SysML is widely used to support the design and analysis of many different kinds of systems and ensures consistency between the design of the system and its documentation through the use of an object-oriented model. In addition, SysML supports the modeling of both hardware and software, which will ease the representation of both the system’s architecture and flow of information. The following paper will follow the Magic Grid methodology to model a UAV system across the SysML four pillars and integration of SysML model with external script-based simulation tools, namely, MATLAB and OpenMDAO. These pillars are expressed within standard diagram views to describe the structural, behavior, requirements, and parametric aspect of the UAV. Finally, the paper will demonstrate how to utilize the simulation capability of the SysML model to verify a functional requirement

Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems

International audienceSelf-Adaptive Systems modify their behavior at run-time in response to changing environmental conditions. For these systems, Non-Functional Requirements play an important role, and one has to identify as early as possible the requirements that are adaptable. We propose an integrated approach for modeling and verify- ing the requirements of Self-Adaptive Systems using Model Driven Engineering techniques. For this, we use Relax, which is a Requirements Engineering language which introduces flexibility in Non-Functional Require- ments. We then use the concepts of Goal-Oriented Requirements Engineering for eliciting and modeling the requirements of Self-Adaptive Systems. For properties verification, we use OMEGA2/IFx profile and toolset. We illustrate our proposed approach by applying it on an academic case study

Evaluation of Development Process and Methodology for Co-Models

An embedded control system often requires a tight association between computational and physical system components. In such cases, embedded system development is difficult, as it requires the collaboration among stakeholders with different backgrounds (software engineers, mechanical engineers, managers etc.). With the constant increase in design complexity, caused by advances in implementation technologies, new ways of approaching embedded system development are needed.This thesis presents an evaluation of a tool-oriented development process and methodology, supporting embedded system development. The philosophy of the development process and methodology, is that design complexity can be managed through collaborative work and multi-disciplinary modeling. To obtain input for the evaluation work, the development process is applied during a case study, involving the development of a route following robot and a model of this. To demonstrate the value of this model, it is simulated to predict route completion times for the physical robot.The evaluation work identifies possibilities and challenges of the development process and methodology, with respect to traditional physicalprototyping. This will support developers in choosing the most optimal way of approaching development. In addition to this, suggestions for extensions to the methodology are provided. These intend to increasethe value the development process and methodology may bring thedevelopment work

An Approach to Complement Model-Based Vehicle Development by Implementing Future Scenarios

Today, vehicle development is already in a process of substantial transformation. Mobility trends can be derived from global megatrends and have a significant influence on the requirements of the developed vehicles. The sociological, technological, economic, ecological, and political developments can be determined by using the scenario technique. The results are recorded in the form of differently shaped scenarios; however, they are mainly document-based. In order to ensure a holistic approach in the sense of model-based systems engineering and to be able to trace the interrelationships of the fast-changing trends and requirements, it is necessary to implement future scenarios in the system model. For this purpose, a method is proposed that enables the consideration of future scenarios in model-based vehicle development. The procedure of the method is presented, and the location of the future scenarios within the system architectures is named. The method is applied and the resulting system views are derived based on the application example of an autonomous people mover. With the help of the described method, it is possible to show the effects of a change of scenario (e.g., best-case and worst-case) and the connections with the highest level of requirements: stakeholder need