Model based analysis process for embedded software product lines

Belategi, Lorea; Sagardui, Goiuria; Etxeberria, Leire

doi:10.1145/1987875.1987886

Cited by 7 publications

(4 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Although MARTE was not defined for product lines, the paper proposes to combine it with existing mechanisms for representing variability, but it does not explain how this can be achieved. A model analysis process for embedded SPL is presented in [9] to validate and verify quality attributes variability. The concept of multilevel and staged feature model is applied by introducing more than one feature models that represent different information at different abstraction levels; however, the traceability links between the multilevel models and the design model are not explained.…”

Section: Performance Resultsmentioning

confidence: 99%

Software Performance Modeling

Petriu

Alhaj

Tawhid

2012

Formal Methods for Model-Driven Engineering

View full text Add to dashboard Cite

Abstract. Ideally, a software development methodology should include both the ability to specify non-functional requirements and to analyze them starting early in the lifecycle; the goal is to verify whether the system under development would be able to meet such requirements. This chapter considers quantitative performance analysis of UML software models annotated with performance attributes according to the standard "UML Profile for Modeling and Analysis of Real-Time and Embedded Systems" (MARTE). The chapter describes a model transformation chain named PUMA (Performance by Unified Model Analysis) that enables the integration of performance analysis in a UML-based software development process, by automating the derivation of performance models from UML+MARTE software models, and by facilitating the interoperability of UML tools and performance tools. PUMA uses an intermediate model called "Core Scenario Model" (CSM) to bridge the gap between different kinds of software models accepted as input and different kinds of performance models generated as output. Transformation principles are described for transforming two kinds of UML behaviour representation (sequence and activity diagrams) into two kinds of performance models (Layered Queueing Networks and stochastic Petri nets). Next, PUMA extensions are described for two classes of software systems: service-oriented architecture (SOA) and software product lines (SPL). IntroductionThe quality of many software intensive systems, ranging from real-time embedded systems to web-based applications, is determined to a large extent by their performance characteristics, such as response time and throughput. The developers of such systems should be able to assess and understand the performance effects of various design decisions starting at an early stage and continuing throughout the software life cycle. Software Performance Engineering (SPE) is an approach introduced by Smith [37], which proposes to use quantitative methods and performance models in order to assess the performance effects of different design and implementation alternatives during the development of a system. SPE promotes the integration of performance analysis into the software development process from its earliest lifecycle stages, in order to insure that the system will meet its performance objectives.

show abstract

Section: Performance Resultsmentioning

confidence: 99%

Software Performance Modeling

Petriu

Alhaj

Tawhid

2012

Formal Methods for Model-Driven Engineering

View full text Add to dashboard Cite

show abstract

“…L. Etxeberria and G. Sagardui [29] create a quality feature tree in a feature model to represent nonfunctional requirements. Another paper by L. Belategi, G. Sagardui and L. Etxeberria [30] also uses a quality feature tree to model non-functional requirements and a MARTE profile for platform resource representation. In addition, MARTE is also utilised for quality analysis in the design stage.…”

Section: B Integrated Variability Documentationmentioning

confidence: 99%

“…Non-functional requirements (quality attributes, in other words) such as response time, reliability and so on play a significant role during system requirement engineering, because they describe the conditions under which the Real-Time System's components should operate, leading to alternative design decisions [14] [15]. However, most of the Software PLE approaches concentrate on the functional aspects [16].…”

Section: Introductionmentioning

confidence: 99%

Model-based systems engineering with requirements variability for embedded real-time systems

Batmaz

Guan

et al. 2015

2015 IEEE International Model-Driven Requirements Engineering Workshop (MoDRE)

View full text Add to dashboard Cite

Additional Information:• it proposes a mechanism for the evolution of variability; 3. stakeholders' specifications for variable requirements are extended by the proposed approach; 4. it increases the consistency of system models by directly using SysML Activity Diagrams and Block Definition Diagrams as a base model for refining variability models for requirement representation. The proposed method is illustrated by an Aircraft Engine Control System case study.

show abstract

“…Existing tools that support the tasks to be performed are also described. Specifically, on the basis of [7], the contributions of this paper are the following:…”

Section: Introductionmentioning

confidence: 99%

Embedded software product lines: domain and application engineering model‐based analysis processes

Belategi

Sagardui

Etxeberria

et al. 2012

J Software Evolu Process

Self Cite

View full text Add to dashboard Cite

Nowadays, embedded systems are gaining importance. At the same time, the development of their software is increasing its complexity, having to deal with quality, cost, and time-to-market issues among others. With stringent quality requirements such as performance, early verification and validation become critical in these systems. In this regard, advanced development paradigms such as model-driven engineering and software product line engineering bring considerable benefits to the development and validation of embedded system software. However, these benefits come at the cost of increasing process complexity. This work presents a process based on UML and MARTE for the analysis of embedded model-driven product lines. It specifies the tasks, the involved roles, and the workproducts that form the process and how it is integrated in the more general development process. Existing tools that support the tasks to be performed in the process are also described. A classification of such tools and a study of traceability among them are provided, allowing engineering teams to choose the most adequate chain of tools to support the process.4.1.4. Real-time specification. Software product line design models (the set of models that represent the SPL: system's structure, behavior, platform, and deployment) must be modeled considering Figure 3. Feature model metamodel. 426 L. BELATEGI ET AL.

show abstract

Model based analysis process for embedded software product lines

Cited by 7 publications

References 15 publications

Software Performance Modeling

Software Performance Modeling

Model-based systems engineering with requirements variability for embedded real-time systems

Embedded software product lines: domain and application engineering model‐based analysis processes

Contact Info

Product

Resources

About