Requirements elicitation has since long been recognized as critical to the success of requirements engineering, hence also to the success of systems engineering. Achieving sufficient scope and quality in the requirements elicitation process poses a great challenge, given the limited slices of budget and time available for this relatively sizeable activity. Among all predominant requirements elicitation techniques and approaches, operational scenarios development has a special standing and character. The set of operational scenarios is acknowledged as a constituent deliverable in the requirements engineering process, serving many purposes. Hence, ensuring success in the development of operational scenarios constitutes a consequential area of research. In this paper we present the results from an industrial survey on experienced and presumptive success factors in the development of operational scenarios. The survey was done using a strength-based approach, involving engineers and managers in two organizations developing cyber-physical systems in the transportation and construction equipment businesses. Our results suggest that operational scenarios reusability and a collaborative operational scenarios development environment are two prime areas for success. Our study provides two contributions. First, we provide an account of success factors in the view of practitioners. This is fundamental knowledge, since a successful deployment of any state-of-the-art approach and technology in a systems engineering organization needs to take the views of the practitioners into consideration. Second, the study adds input to the body of knowledge on requirements elicitation, and can thereby help generate suggestions on direction for future work by researchers and developers.

This article describes the architecture life cycle effect analysis (ALCEA) method, a structured method for evaluating proposed new architectures for software-intensive systems. The method evaluates a proposed architecture by quantifying its effect on the performance of system life-cycle phases. The method is instantiated by identifying the relevant life-cycle phases of the system under investigation and a set of evaluation functions that capture, in terms of basic factors, the effect of different architectural decisions on key life-cycle PAs, such as revenue, operating resources, and investments. The method results in a transparent cost and revenue structure, documented in a tabular form, based on quantifiable factors from the developing organization. The results of the method can be used directly as part of a business case, and their robustness can be estimated by sensitivity analysis. The ALCEA method is designed for system-level architectural analysis, covering both software and hardware aspects. In this article, we introduce the ALCEA method and provide a detailed example of how to apply it in the evolution of embedded systems. Moreover, we share early experiences of using the method in large-scale industrial settings.

The author of this article explores the question, what is human trafficking. In order to answer this question, definitions of human trafficking are examined, as well as the causes, types of trafficking, recruitment strategies, and the significant problems in conquering human trafficking internationally. Trafficking in human beings affects all regions and most countries of the world. According to official data, Bosnia and Herzegovina is a transit country, but certain reports indicate that it is becoming a country of origin and destination. In order to exemplify the issue of human trafficking on the concrete case study, there is further exploration of how the law of Bosnia and Herzegovina defines it, and how approachs to this problem. Taking into account the increase of human trafficking in the world, especially among countries in transition, it is extremely important to find effective solutions for the prevention of such cross-border criminal activity.

Model-based product line engineering applies the reuse practices from product line engineering with graphical modeling for the specification of software intensive systems. Variability is usually described in separate variability models, while the implementation of the variable systems is specified in system models that use modeling languages such as SysML. Most of the SysML modeling tools with variability support, implement the annotation-based modeling approach. Annotated product line models tend to be error-prone since the modeler implicitly describes every possible variant in a single system model. To identifying variability-related inconsistencies, in this paper, we firstly define restrictions on the use of SysML for annotative modeling in order to avoid situations where resulting instances of the annotated model may contain ambiguous model constructs. Secondly, inter-feature constraints are extracted from the annotated model, based on relations between elements that are annotated with features. By analyzing the constraints, we can identify if the combined variability- and system model can result in incorrect or ambiguous instances. The evaluation of our prototype implementation shows the potential of our approach by identifying inconsistencies in the product line model of our industrial partner which went undetected through several iterations of the model.

Model-based product line engineering applies the reuse practices from product line engineering with graphical modeling for the specification of software intensive systems. Variability is usually described in separate variability models, while the implementation of the variable systems is specified in system models that use modeling languages such as SysML. Most of the SysML modeling tools with variability support, implement the annotation-based modeling approach. Annotated product line models tend to be error-prone since the modeler implicitly describes every possible variant in a single system model. To identifying variability-related inconsistencies, in this paper, we firstly define restrictions on the use of SysML for annotative modeling in order to avoid situations where resulting instances of the annotated model may contain ambiguous model constructs. Secondly, inter-feature constraints are extracted from the annotated model, based on relations between elements that are annotated with features. By analyzing the constraints, we can identify if the combined variability- and system model can result in incorrect or ambiguous instances. The evaluation of our prototype implementation shows the potential of our approach by identifying inconsistencies in the product line model of our industrial partner which went undetected through several iterations of the model.

Many organizations developing software-intensive systems face challenges with high product complexity and large numbers of variants. In order to effectively maintain and develop these product variants, Product-Line Engineering methods are often considered, while Model-based Systems Engineering practices are commonly utilized to tackle product complexity. In this paper, we report on an industrial case study concerning the ongoing adoption of Product Line Engineering in the Model-based Systems Engineering environment at Volvo Construction Equipment (Volvo CE) in Sweden. In the study, we identify and define a Product Line Engineering process that is aligned with Model-based Systems Engineering activities at the engines control department of Volvo CE. Furthermore, we discuss the implications of the migration from the current development process to a Model-based Product Line Engineering-oriented process. This process, and its implications, are derived by conducting and analyzing interviews with Volvo CE employees, inspecting artifacts and documents, and by means of participant observation. Based on the results of a first system model iteration, we were able to document how Model-based Systems Engineering and variability modeling will affect development activities, work products and stakeholders of the work products.

Software-intensive systems in the automotive domain are often built in different variants, notably in order to support different market segments and legislation regions. Model-based concepts are frequently applied to manage complexity in such variable systems. However, the considered approaches are often focused on single-product development. In order to support variable products in a model-based systems engineering environment, we describe a tool-supported approach that allows us to annotate SysML models with variability data. Such variability information is exchanged between the system modeling tool and variability management tools through the Variability Exchange Language. The contribution of the paper includes the introduction of the model-based product line engineering tool chain and its application on a practical case study at Volvo Construction Equipment. Initial results suggest an improved efficiency in developing such a variable system.

Product Line Engineering is an approach to reuse assets of complex systems by taking advantage of commonalities between product families. Reuse within complex systems usually means reuse of artifacts from different engineering domains such as mechanical, electronics and software engineering. Model-based systems engineering is becoming a standard for systems engineering and collaboration within different domains. This paper presents an exploratory case study on initial efforts of adopting Product Line Engineering practices within the model-based systems engineering process at Volvo Construction Equipment (Volvo CE), Sweden. We have used SysML to create overloaded models of the engine systems at Volvo CE. The variability within the engine systems was captured by using the Orthogonal Variability Modeling language. The case study has shown us that overloaded SysML models tend to become complex even on small scale systems, which in turn makes scalability of the approach a major challenge. For successful reuse and to, possibly, tackle scalability, it is necessary to have a database of reusable assets from which product variants can be derived.

This paper describes an Internet Of Things-based wearable system for physical rehabilitation monitoring and characterization. The system is recording movement data with 3-axial accelerometer and gyroscope sensors. Data recorded by the sensors are used for characterization of movement, thus allowing for monitoring and estimation of the patients' state at all times. Main three parts of the system are: data acquisition unit, data processing unit, and cloud-based service for remote access to data. Hardware implementation is described and shown for each of the three parts. The system is demonstrated for monitoring of elbow rehabilitation. Results show that the device can be used for highly precise and accurate monitoring of elbow flexion and extension characteristics, thus allowing for remote rehabilitation tracking through the use of the cloud-based service.

Solar Car Optimized Route Estimation (SCORE) has been proposed in an earlier publication as an alternative navigation principle for solar cars, conducting route optimization based on both distance and solar irradiance data. This paper gives details about the implementation and discusses results of SCORE's use, suggesting possible limitations and future research directions. The results show limited applicability of solar irradiance data for route optimization, but suggesting that parking place selection is an important aspect that needs to be taken care of. The implementation uses both a MATLAB testbed application and C/C++ code for TI's ARM Cortex-M4F based TM4C123G LaunchPad, and the final version of the SCORE client is placed in a custom built solar vehicle. Combined with the previously developed server for sensor data collection and data processing and sensor transmitter infrastructure for solar irradiation, the route optimization system is fully operational.

This paper describes an embedded system for the automation of scheduling systems such as school bells, factory shift changes, military drills etc. The system consists of two parts: a remote node used for remote control and setup of the system and the real time actuator node which controls a physical object, for example, a bell system. The hardware and software structure are illustrated in detail for both parts of the system through the implementation as an automatic school bell system.

This paper focuses on sensor data management in the Solar Car Optimized Route Estimation (SCORE) system which is currently being developed. The data collection is split into two phases: the a priori phase related to the environment and the real time phase related to the solar vehicle. The hardware and software architecture for a priori phase is illustrated in detail, while the real time phase is discussed as a part of the embedded car computer. The full system description for SCORE is presented with guidelines for the future work and implementation of it.