Feature models and their extensions have been proposed and used over the past 20 years for modeling the commonality and variability of software systems. However, the increasing runtime demands and post-deployment configuration procedures of self-adaptive, context-aware and pervasive systems has brought the need for modeling context features. In addition, many critical systems that demand stringent collaborative features at runtime need also to share information dynamically. In this research-in-progress paper, we sketch our vision of where feature modeling should go to support collaborative aspects of systems. Our proposal suggests identifying and annotating context features models with collaborative information that becomes particularly useful for critical and swarm-based systems that require information exchange at runtime.
{"title":"Collaborative Context Features for Critical Systems","authors":"Rafael Capilla, M. Hinchey, Francisco J. Díaz","doi":"10.1145/2701319.2701322","DOIUrl":"https://doi.org/10.1145/2701319.2701322","url":null,"abstract":"Feature models and their extensions have been proposed and used over the past 20 years for modeling the commonality and variability of software systems. However, the increasing runtime demands and post-deployment configuration procedures of self-adaptive, context-aware and pervasive systems has brought the need for modeling context features. In addition, many critical systems that demand stringent collaborative features at runtime need also to share information dynamically. In this research-in-progress paper, we sketch our vision of where feature modeling should go to support collaborative aspects of systems. Our proposal suggests identifying and annotating context features models with collaborative information that becomes particularly useful for critical and swarm-based systems that require information exchange at runtime.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"52 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"130988875","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Variability is a significant source of complexity in many large-scale software systems. Software variability must be managed in order to effectively tame the arising complexity. Consequently, variability management processes are at the heart of current software product line engineering practices. However, legacy software systems exist that have not been developed with such practices. Moreover, an increasing amount of software is developed in large, fragmented communities, also referred to as software ecosystems. Variability in such systems is often not explicitly managed and causes significant difficulties during software maintenance and evolution. Methods and tools for uncovering and explicitly managing this variability have been subject to ongoing research. This paper presents our research in progress of empirically studying the application and combination of such methods in the context of real-world industrial case study in the health care domain.
{"title":"Uncovering Variability Models for Software Ecosystems from Multi-Repository Structures","authors":"J. Weber, A. Katahoire, Morgan Price","doi":"10.1145/2701319.2701333","DOIUrl":"https://doi.org/10.1145/2701319.2701333","url":null,"abstract":"Variability is a significant source of complexity in many large-scale software systems. Software variability must be managed in order to effectively tame the arising complexity. Consequently, variability management processes are at the heart of current software product line engineering practices. However, legacy software systems exist that have not been developed with such practices. Moreover, an increasing amount of software is developed in large, fragmented communities, also referred to as software ecosystems. Variability in such systems is often not explicitly managed and causes significant difficulties during software maintenance and evolution. Methods and tools for uncovering and explicitly managing this variability have been subject to ongoing research. This paper presents our research in progress of empirically studying the application and combination of such methods in the context of real-world industrial case study in the health care domain.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"7 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132183548","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Source-code documentation is essential to efficiently develop and maintain large software products. Documentation is equally important for software product lines (SPLs), which represent a set of different products with a common code base. Unfortunately, proper support for documenting the source code of an SPL is currently lacking, because source code variability is not considered by current documentation tools. We introduce a method to provide source-code documentation for feature-oriented programming and aim to support developers who implement, maintain, and use SPLs. We identify multiple use cases for developers working with SPLs and propose four different documentation types (meta, product, feature, and context) that fulfill the information requirements of these use cases. Furthermore, we design an algorithm that enables developers to create tailor-made documentation for each use case. Our method is based on the documentation tool Javadoc and allows developers to easily write documentation comments that contain little overhead or redundancy. To demonstrate the efficiency of our method, we present a prototypical implementation and evaluate our method with regard to documentation effort for the SPL developers by documenting two small SPLs.
{"title":"Use-Case-Specific Source-Code Documentation for Feature-Oriented Programming","authors":"S. Krieter, R. Schröter, W. Fenske, G. Saake","doi":"10.1145/2701319.2701329","DOIUrl":"https://doi.org/10.1145/2701319.2701329","url":null,"abstract":"Source-code documentation is essential to efficiently develop and maintain large software products. Documentation is equally important for software product lines (SPLs), which represent a set of different products with a common code base. Unfortunately, proper support for documenting the source code of an SPL is currently lacking, because source code variability is not considered by current documentation tools. We introduce a method to provide source-code documentation for feature-oriented programming and aim to support developers who implement, maintain, and use SPLs. We identify multiple use cases for developers working with SPLs and propose four different documentation types (meta, product, feature, and context) that fulfill the information requirements of these use cases. Furthermore, we design an algorithm that enables developers to create tailor-made documentation for each use case. Our method is based on the documentation tool Javadoc and allows developers to easily write documentation comments that contain little overhead or redundancy. To demonstrate the efficiency of our method, we present a prototypical implementation and evaluate our method with regard to documentation effort for the SPL developers by documenting two small SPLs.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"1 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133983121","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
A. Felfernig, Stefan Reiterer, Martin Stettinger, J. Tiihonen
Knowledge about formal (semantic) interpretations of natural language domain descriptions is crucial for avoiding communication overheads between domain experts and knowledge engineers. In this paper we report preliminary results of an empirical study in which we investigated in which way natural language statements are formalized by knowledge engineers. We summarize the findings of our study and discuss aspects to be taken into account in order to avoid additional (often not needed) iterations in configuration knowledge engineering processes. This work is exploratory and intended to figure out open issues for future work.
{"title":"Towards Understanding Cognitive Aspects of Configuration Knowledge Formalization","authors":"A. Felfernig, Stefan Reiterer, Martin Stettinger, J. Tiihonen","doi":"10.1145/2701319.2701327","DOIUrl":"https://doi.org/10.1145/2701319.2701327","url":null,"abstract":"Knowledge about formal (semantic) interpretations of natural language domain descriptions is crucial for avoiding communication overheads between domain experts and knowledge engineers. In this paper we report preliminary results of an empirical study in which we investigated in which way natural language statements are formalized by knowledge engineers. We summarize the findings of our study and discuss aspects to be taken into account in order to avoid additional (often not needed) iterations in configuration knowledge engineering processes. This work is exploratory and intended to figure out open issues for future work.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114223657","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Highly-configurable software systems (also called software product lines) gain momentum in both, academia and industry. For instance, the Linux kernel comes with over 12 000 configuration options and thus, can be customized to run on nearly every kind of system. To a large degree, this configurability is achieved through variable code structures, for instance, using conditional compilation. Such source code variability adds a new dimension of complexity, thus giving rise to new possibilities for design flaws. Code smells are an established concept to describe design flaws or decay in source code. However, existing smells have no notion of variability and thus do not support flaws regarding variable code structures. In this paper, we propose an initial catalog of four variability-aware code smells. We discuss the appearance and negative effects of these smells and present code examples from real-world systems. To evaluate our catalog, we have conducted a survey amongst 15 researchers from the field of software product lines. The results confirm that our proposed smells (a) have been observed in existing product lines and (b) are considered to be problematic for common software development activities, such as program comprehension, maintenance, and evolution.
{"title":"Code Smells Revisited: A Variability Perspective","authors":"W. Fenske, Sandro Schulze","doi":"10.1145/2701319.2701321","DOIUrl":"https://doi.org/10.1145/2701319.2701321","url":null,"abstract":"Highly-configurable software systems (also called software product lines) gain momentum in both, academia and industry. For instance, the Linux kernel comes with over 12 000 configuration options and thus, can be customized to run on nearly every kind of system. To a large degree, this configurability is achieved through variable code structures, for instance, using conditional compilation. Such source code variability adds a new dimension of complexity, thus giving rise to new possibilities for design flaws. Code smells are an established concept to describe design flaws or decay in source code. However, existing smells have no notion of variability and thus do not support flaws regarding variable code structures. In this paper, we propose an initial catalog of four variability-aware code smells. We discuss the appearance and negative effects of these smells and present code examples from real-world systems. To evaluate our catalog, we have conducted a survey amongst 15 researchers from the field of software product lines. The results confirm that our proposed smells (a) have been observed in existing product lines and (b) are considered to be problematic for common software development activities, such as program comprehension, maintenance, and evolution.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"21 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"126532778","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Quality function deployment (QFD) is a method for quality assurance developed for application in production processes. One prominent tool for implementing QFD is the House of Quality (HoQ), whose basic design principles have been left unchanged for the last decades. Modern concepts for handling product variability, most notably feature models, represent intuitive means for a refurbished roof construction of the HoQ, and thus more expressiveness in the definition of functional requirements.
质量功能部署(QFD)是一种用于生产过程质量保证的方法。实现QFD的一个重要工具是质量屋(House of Quality, HoQ)，其基本设计原则在过去几十年里一直没有改变。处理产品可变性的现代概念，尤其是特征模型，代表了HoQ翻新屋顶结构的直观手段，因此在功能需求的定义中更具表现力。
{"title":"A Common Home for Features and Requirements: Retrofitting the House of Quality with Feature Models","authors":"E. Mätzler, Bernhard Wally, Alexandra Mazak","doi":"10.1145/2701319.2701334","DOIUrl":"https://doi.org/10.1145/2701319.2701334","url":null,"abstract":"Quality function deployment (QFD) is a method for quality assurance developed for application in production processes. One prominent tool for implementing QFD is the House of Quality (HoQ), whose basic design principles have been left unchanged for the last decades. Modern concepts for handling product variability, most notably feature models, represent intuitive means for a refurbished roof construction of the HoQ, and thus more expressiveness in the definition of functional requirements.","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"144 2 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2015-01-21","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"128827283","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","authors":"","doi":"10.1145/2701319","DOIUrl":"https://doi.org/10.1145/2701319","url":null,"abstract":"","PeriodicalId":232045,"journal":{"name":"Proceedings of the 9th International Workshop on Variability Modelling of Software-Intensive Systems","volume":"35 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"1900-01-01","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116923386","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
京公网安备 11010802042870号
京ICP备2023020795号-1
扫码关注我们
求助内容：
应助结果提醒方式：