Functional size measurement (FSM), a powerful tool for managing software projects, provides an objective and quantitative base for management decisions. In this paper, we discuss FSM for Internet of things (IoT) real-time embedded software (RTES), and propose a guideline using Arduino (a DIY - Do It Yourself - microcontroller widely used especially in the IoT domain) as a measurement example. As an illustration of the potential benefit of using FSM in the context of IoT, the use of functional size ranges is proposed for managing energy consumption of IoT RTES.

[email protected] has appeared as a new paradigm for continuously monitoring software systems execution to enable self-adaptation. This adaptation happens whenever a change, a failure or a bug is introduced within the execution environment. It is done by a causal bidirectional connection between design and execution artifacts supported by feedback-loop information. We developed an approach to integrate a secure lightweight dynamic adaptation of access control policies when new security requirements are introduced at runtime. The proposed runtime adaptation is supported by a fast checking of design models at runtime against security constraints. A vehicle-2-x security case study is used to demonstrate the benefits of our approach.

Automating functional size measurement (FSM) is important for organizations needing to measure a large number of projects within a short timeframe, provided, of course, that the results automatically generated are accurate, particularly when such measurement is based on an international measurement standard. A literature review has shown that very little work has been conducted on verifying measurement results produced by FSM automation. This paper presents a verification protocol designed to provide evidence of the accuracy of an automated FSM tool using the COSMIC ISO 19761 measurement standard. Also included are: an example of its use for the verification of an AUTOSAR-based FSM automation prototype tool developed at ESTACA, and a case study on the application of the proposed verification protocol on another prototype tool developed at Renault S.A.

Functional size measurement is considered a complicated, tedious and time-consuming task when performed manually. Automating FSM is one solution to help in applying it and using it. Another solution is designing simple and easy-to-apply FSM procedures. The Synchronous Languages (SL) are built on solid mathematical foundations and used for correctly designing safety-critical reactive real-time systems. They are known for their strong semantic soundness, allowing the design of explicit safely-constructed formal models where the interpretation of a model is unique and reader-independent. These properties are very useful in the context of FSM because they help create simple FSM procedures and hence speed up the measurement process. In this paper, we propose a fast functional size measurement (FSM) procedure, based on the COSMIC method-ISO 19761, for safety-critical real-time systems described with the synchronous language LUSTRE.

COSMIC-based functional size measurement (FSM) procedures should all produce the same measurement results, no matter what design decisions are made when modeling the functional requirements of the software to be measured. When the FSM procedure proposed in [14] is applied to different models of the same functional requirements, the measurement results vary. This problem is addressed, and a refined FSM procedure for real-time embedded software is proposed. The revised rules of this refined FSM procedure are based on an analysis of the issues detected in [14], and a solution to the variance issue is offered as a result.

In their early age, E/E (electrical and electronic) systems were OEM (Original Equipment Manufacturers) specific. Adapting existing components to different environments was both time and effort consuming. AUTOSAR (AUTomotive Open System Architecture) is both a consortium founded by the major automotive companies and an architecture standard that allows collaboration on basic E/E functions while providing a platform to develop new innovative ones. One of AUTOSAR main objectives is to standardize a large number of E/E software modules in order to benefit from the reuse of these modules, it also aims to prepare for the increase in functional scope of E/E systems. Functional size measurement (FSM) has become an important task in software development projects for real-time embedded systems. Functional size can be used to estimate development effort, to manage project scope changes, to measure productivity, to benchmark, and to normalize quality and maintenance ratios. Hence, FSM goes hand in hand with AUTOSAR objectives in terms of managing automotive software projects. This paper discusses FSM in connection with AUTOSAR. In particular, it presents a guideline for measuring ECU (Electronic Control Unit) Application Software in the context of AUTOSAR.

To obtain the functional size of software and reduce measurement variance caused by the interpretations of individual measurers, a number of measurement procedureshave been designed based on measurement methods approved as international standards. To date, most of these procedures have targeted Management Information Systems software, while only a few were designed for real-time and reactiveembedded software. In this paper, we propose a functional size measurement (FSM) procedure for real-time embedded software, based on the COSMIC method, version 3.0.1 (ISO 19761), and with requirements documented using the Simulinkmodel. The design of this FSM procedure is based on the mapping of key concepts in both Simulink and COSMIC, and the identification of the mapping rules for extracting the information stored in the Simulink files that is required formeasurement. This procedure therefore provides the foundation for automating the measurement of software requirements documented using Simulink. The backgroundstudy for this procedure was conducted at Renault SAS using ECU (Electronic Control Unit) functional requirements expressed with the Simulink tool.