5,433 research outputs found
Recommended from our members
Implementation issues in product line scoping
Often product line engineering is treated similar to the waterfall model in traditional software engineering, i.e., the different phases (scoping, analysis, architecting, implementation) are treated as if they could be clearly separated and would follow each other in an ordered fashion. However, in practice strong interactions between the individual phases become apparent. In particular, how implementation is done has a strong impact on economic aspects of the project and thus how to adequately plan it. Hence, assessing these relationships adequately in the beginning has a strong impact on performing a product line project right. In this paper we present a framework that helps in exactly this task. It captures on an abstract level the relationships between scoping information and implementation aspects and thus allows to provide rough guidance on implementation aspects of the project. We will also discuss the application of our framework to a specific industrial project
Traceability for Model Driven, Software Product Line Engineering
Traceability is an important challenge for software organizations. This is true for traditional software development and even more so in new approaches that introduce more variety of artefacts such as Model Driven development or Software Product Lines. In this paper we look at some aspect of the interaction of Traceability, Model Driven development and Software Product Line
A variability taxonomy to support automation decision-making for manufacturing processes
Although many manual operations have been replaced by automation in the manufacturing domain, in
various industries skilled operators still carry out critical manual tasks such as final assembly. The
business case for automation in these areas is difficult to justify due to increased complexity and costs
arising out of process variabilities associated with those tasks. The lack of understanding of process
variability in automation design means that industrial automation often does not realise the full benefits
at the first attempt, resulting in the need to spend additional resource and time, to fully realise the
potential. This article describes a taxonomy of variability when considering automation of
manufacturing processes. Three industrial case studies were analysed to develop the proposed
taxonomy. The results obtained from the taxonomy are discussed with a further case study to
demonstrate its value in supporting automation decision-making
A variability taxonomy to support automation decision-making for manufacturing processes
Although many manual operations have been replaced by automation in the manufacturing domain, in
various industries skilled operators still carry out critical manual tasks such as final assembly. The
business case for automation in these areas is difficult to justify due to increased complexity and costs
arising out of process variabilities associated with those tasks. The lack of understanding of process
variability in automation design means that industrial automation often does not realise the full benefits
at the first attempt, resulting in the need to spend additional resource and time, to fully realise the
potential. This article describes a taxonomy of variability when considering automation of
manufacturing processes. Three industrial case studies were analysed to develop the proposed
taxonomy. The results obtained from the taxonomy are discussed with a further case study to
demonstrate its value in supporting automation decision-making
Review of Requirement Engineering Approaches for Software Product Lines
The Software Product Lines (SPL) paradigm is one of the most recent topics of interest for the software engineering community. On the one hand, the Software Product Lines is based on a reuse strategy with the aim to reduce the global time-to-market of the software product, to improve the software product quality, and to reduce the cost. On the other hand, traditional Requirement Engineering approaches could not be appropriated to deal with the new challenges that arises the SPL adoption. In the last years, several approaches have been proposed to cover this limitation. This technical report presents an analysis of specific approaches used in the development of SPL to provide solutions to model variability and to deal with the requirements engineering activities. The obtained results show that most of the research in this context is focused on the Domain Engineering, covering mainly the Feature Modeling and the Scenario Modeling. Among the studied approaches, only one of them supported the delta identification; this fact implies that new mechanisms to incorporate new deltas in the Domain specification are needed. Regarding the SPL adoption strategy, most of the approaches support a proactive strategy. However, this strategy is the most expensive and risk-prone. Finally, most of the approaches were based on modeling requirements with feature models giving less support to other important activities in the requirements engineering process such as elicitation, validation, or verification of requirements. The results of this study provide a wide view of the current state of research in requirements engineering for SPL and also highlight possible research gaps that may be of interest for researchers and practitioners.Blanes DomĂnguez, D.; Insfrán Pelozo, CE. (2011). Review of Requirement Engineering Approaches for Software Product Lines. http://hdl.handle.net/10251/1023
Software Product Line for Metaverse: Preliminary Results
The Metaverse is a network of eXtended Reality applications (XR apps)
connected to each other, over the Internet infrastructure, allowing network
users, systems, and devices to access them. It is very challenging to implement
solutions for XR apps, due to the combination of complex concerns that should
be addressed: multiple users with non-traditional input and output devices,
different hardware platforms that should be addressed, forceful interactive
rates, and experimental interaction techniques, among other issues. Therefore,
this work aims to present a Software Product Line (SPL)-based approach to
support the development of Web XR apps. More specifically, we define a features
model that represents similarities and variables (domain analysis); we defined
a core composed of generic and reusable software artifacts (domain project);
and we developed an interface to support the instantiation of a Web XR app
family, named MetaSee Features Model Editor (domain implementation). This
approach integrates with a component of the MetaSEE architecture (Metaverse for
Software Engineering Education). A preliminary assessment found that Features
Model has conceptual consistency from the point of view of the complexity of
Web XR Apps multimodal interaction. As future work, features model and
artifacts will be increased with improvements and an evaluation with a
significant number of participants will be made
Software Product Line
The Software Product Line (SPL) is an emerging methodology for developing software products. Currently, there are two hot issues in the SPL: modelling and the analysis of the SPL. Variability modelling techniques have been developed to assist engineers in dealing with the complications of variability management. The principal goal of modelling variability techniques is to configure a successful software product by managing variability in domain-engineering. In other words, a good method for modelling variability is a prerequisite for a successful SPL. On the other hand, analysis of the SPL aids the extraction of useful information from the SPL and provides a control and planning strategy mechanism for engineers or experts. In addition, the analysis of the SPL provides a clear view for users. Moreover, it ensures the accuracy of the SPL. This book presents new techniques for modelling and new methods for SPL analysis
- …