Performance-related completions for software specifications
Proceedings of the 24th International Conference on Software Engineering
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Designing Software Product Lines with UML: From Use Cases to Pattern-Based Software Architectures
Performance by Design: Computer Capacity Planning By Example
Performance by Design: Computer Capacity Planning By Example
Performance by unified model analysis (PUMA)
Proceedings of the 5th international workshop on Software and performance
Automatic Inclusion of Middleware Performance Attributes into Architectural UML Software Models
IEEE Transactions on Software Engineering
Efficient Performance Models in Component-Based Software Engineering
EUROMICRO '06 Proceedings of the 32nd EUROMICRO Conference on Software Engineering and Advanced Applications
Non-Functional Modeling and Validation in Model-Driven Architecture
WICSA '07 Proceedings of the Sixth Working IEEE/IFIP Conference on Software Architecture
Towards automatic derivation of a product performance model from a UML software product line model
WOSP '08 Proceedings of the 7th international workshop on Software and performance
Non-functional requirements analysis modeling for software product lines
MISE '09 Proceedings of the 2009 ICSE Workshop on Modeling in Software Engineering
On Non-Functional Requirements in Software Engineering
Conceptual Modeling: Foundations and Applications
Integrating Quality Modeling with Feature Modeling in Software Product Lines
ICSEA '09 Proceedings of the 2009 Fourth International Conference on Software Engineering Advances
Parametric performance completions for model-driven performance prediction
Performance Evaluation
MARTE mechanisms to model variability when analyzing embedded software product lines
SPLC'10 Proceedings of the 14th international conference on Software product lines: going beyond
Model based analysis process for embedded software product lines
Proceedings of the 2011 International Conference on Software and Systems Process
Automatic Derivation of a Product Performance Model from a Software Product Line Model
SPLC '11 Proceedings of the 2011 15th International Software Product Line Conference
Optimizing User Guidance during Decision-Making
SPLC '11 Proceedings of the 2011 15th International Software Product Line Conference
Automated reasoning on feature models
CAiSE'05 Proceedings of the 17th international conference on Advanced Information Systems Engineering
SFM'12 Proceedings of the 12th international conference on Formal Methods for the Design of Computer, Communication, and Software Systems: formal methods for model-driven engineering
Proceedings of the Eighth International Workshop on Variability Modelling of Software-Intensive Systems
| Hi-index | 0.00 |
A Software Product Line (SPL) is a set of similar software systems that share a common set of features. Instead of building each product from scratch, SPL development takes advantage of the reusability of the core assets shared among the SPL members. In this work, we integrate performance analysis in the early phases of SPL development process, applying the same reusability concept to the performance annotations. Instead of annotating from scratch the UML model of every derived product, we propose to annotate the SPL model once with generic performance annotations. After deriving the model of a product from the family model by an automatic transformation, the generic performance annotations need to be bound to concrete product-specific values provided by the developer. Dealing manually with a large number of performance annotations, by asking the developer to inspect every diagram in the generated model and to extract these annotations is an error-prone process. In this paper we propose to automate the collection of all generic parameters from the product model and to present them to the developer in a user-friendly format (e.g., a spreadsheet per diagram, indicating each generic parameter together with guiding information that helps the user in providing concrete binding values). There are two kinds of generic parametric annotations handled by our approach: product-specific (corresponding to the set of features selected for the product) and platform-specific (such as device choices, network connections, middleware, and runtime environment). The following model transformations for (a) generating a product model with generic annotations from the SPL model, (b) building the spreadsheet with generic parameters and guiding information, and (c) performing the actual binding are all realized in the Atlas Transformation Language (ATL).