An architectural approach with separation of concerns to address extra-functional requirements in the development of embedded real-time software systems

AbstractA large proportion of the requirements on embedded real-time systems stems from the extra-functional dimensions of time and space determinism, dependability, safety and security, and it is addressed at the software level. The adoption of a sound software architecture provides crucial aid in conveniently apportioning the relevant development concerns. This paper takes a software-centered interpretation of the ISO 42010 notion of architecture, enhancing it with a component model that attributes separate concerns to distinct design views. The component boundary becomes the border between functional and extra-functional concerns. The latter are treated as decorations placed on the outside of components, satisfied by implementation artifacts separate from and composable with the implementation of the component internals. The approach was evaluated by industrial users from several domains, with remarkably positive results

Bounding the Effects of Resource Access Protocols on Cache Behavior

The assumption of task independence has long been consubstantial with the formulation of many schedulability analysis techniques. That assumption is evidently advantageous for the mathematical formulation of the analysis equations, but ill fit to capture the actual behavior of the system. Resource sharing is one of the system design dimensions that break the assumption of task independence. By shaking the very foundations of the real-time analysis theory, the advent of multicore systems has caused resurgence of interest in resource sharing and synchronization protocols, and also dawned the fact that the assumption of task independence may be forever broken. Research in cache-aware schedulability analysis instead has paid very little attention to the impact that synchronization protocols may have on cache behavior. A blocked task may in fact incur time penalties similar in kind to those caused by preemption, in that some useful code or data already loaded in the cache may be evicted while the task is blocked. In this paper we characterize the sources of cache-related blocking delay (CRBD). We then provide a bound on the CRBD for three synchronization protocols of interest. The comparison between these bounds provides striking evidence that an informed choice of the synchronization protocol helps contain the perturbing effects of blocking on the cache state

Budgeting Under-Specified Tasks for Weakly-Hard Real-Time Systems

In this paper, we present an extension of slack analysis for budgeting in the design of weakly-hard real-time systems. During design, it often happens that some parts of a task set are fully specified while other parameters, e.g. regarding recovery or monitoring tasks, will be available only much later. In such cases, slack analysis can help anticipate how these missing parameters can influence the behavior of the whole system so that a resource budget can be allocated to them. It is, however, sufficient in many application contexts to budget these tasks in order to preserve weakly-hard rather than hard guarantees. We thus present an extension of slack analysis for deriving task budgets for systems with hard and weakly-hard requirements. This work is motivated by and validated on a realistic case study inspired by industrial practice

Changes in renal function after nephroureterectomy for upper urinary tract carcinoma: analysis of a large multicenter cohort (Radical Nephroureterectomy Outcomes (RaNeO) Research Consortium)

Purpose To investigate prevalence and predictors of renal function variation in a multicenter cohort treated with radical nephroureterectomy (RNU) for upper tract urothelial carcinoma (UTUC). Methods Patients from 17 tertiary centers were included. Renal function variation was evaluated at postoperative day (POD)-1, 6 and 12 months. Timepoints differences were Delta 1 = POD-1 eGFR - baseline eGFR; Delta 2 = 6 months eGFR - POD-1 eGFR; Delta 3 = 12 months eGFR - 6 months eGFR. We defined POD-1 acute kidney injury (AKI) as an increase in serum creatinine by >= 0.3 mg/dl or a 1.5 1.9-fold from baseline. Additionally, a cutoff of 60 ml/min in eGFR was considered to define renal function decline at 6 and 12 months. Logistic regression (LR) and linear mixed (LM) models were used to evaluate the association between clinical factors and eGFR decline and their interaction with follow-up. Results A total of 576 were included, of these 409(71.0%) and 403(70.0%) had an eGFR < 60 ml/min at 6 and 12 months, respectively, and 239(41.5%) developed POD-1 AKI. In multivariable LR analysis, age (Odds Ratio, OR 1.05, p < 0.001), male gender (OR 0.44, p = 0.003), POD-1 AKI (OR 2.88, p < 0.001) and preoperative eGFR < 60 ml/min (OR 7.58, p < 0.001) were predictors of renal function decline at 6 months. Age (OR 1.06, p < 0.001), coronary artery disease (OR 2.68, p = 0.007), POD-1 AKI (OR 1.83, p = 0.02), and preoperative eGFR < 60 ml/min (OR 7.80, p < 0.001) were predictors of renal function decline at 12 months. In LM models, age (p = 0.019), hydronephrosis (p < 0.001), POD-1 AKI (p < 0.001) and pT-stage (p = 0.001) influenced renal function variation (ss 9.2 +/- 0.7, p < 0.001) during follow-up. Conclusion Age, preoperative eGFR and POD-1 AKI are independent predictors of 6 and 12 months renal function decline after RNU for UTUC

Definition, realization and evaluation of a software reference architecture for use in space applications

A recent initiative of the European Space Agency (ESA) aims at the definition and adoption of a software reference architecture for use in on-board software of future space missions. Our PhD project placed in the context of that effort. At the outset of our work we gathered all the industrial needs relevant to ESA and all the main European space stakeholders and we were able to consolidate a set of technical high-level requirements for the fulfillment of them. The conclusion we reached from that phase confirmed that the adoption of a software reference architecture was indeed the best solution for the fulfillment of the high-level requirements. The software reference architecture we set on building rests on four constituents: (i) a component model, to design the software as a composition of individually verifiable and reusable software units; (ii) a computational model, to ensure that the architectural description of the software is statically analyzable; (iii) a programming model, to ensure that the implementation of the design entities conforms with the semantics, the assumptions and the constraints of the computational model; (iv) a conforming execution platform, to actively preserve at run time the properties asserted by static analysis. The nature, feasibility and fitness of constituents (ii), (iii) and (iv), were already proved by the author in an international project that preceded the commencement of the PhD work. The core of the PhD project was therefore centered on the design and prototype implementation of constituent (i), a component model. Our proposed component model is centered on: (i) rigorous separation of concerns, achieved with the support for design views and by careful allocation of concerns to the dedicated software entities; (ii) the support for specification and model-based analysis of extra-functional properties; (iii) the inclusion space-specific concerns

Pitfalls and misconceptions in component-oriented approaches for real-time embedded systems: lessons learned and solutions

Abstract-When the task befalls you to devise a novel component-oriented approach for real-time embedded systems you first dutifully undertake a thorough scrutiny of the import and pitfalls of previous attempts. This is what we have done for the last couple of years, in the context of an initiative promoted by the European Space Agency for the creation of a component model to serve the development of new-generation on-board software. In this paper we recapitulate the lessons we learned in that effort