5,999 research outputs found
An Agile Process Model for Product Derivation in Software Product Line Engineering
Software Product Lines (SPL) and Agile practices have emerged as new paradigms for developing software. Both approaches share common goals; such as improving productivity, reducing time to market, decreasing development costs and increasing customer satisfaction. These common goals provide the motivation for this research. We believe that integrating Agile practices into SPL can bring a balance between agility and formalism. However, there has been little research on such integration. We have been researching the potential of integrating Agile approaches in one of the key SPL process areas, product derivation. In this paper we present an outline of our Agile process model for product derivation that was developed through industry based case study research
Tailoring the Scrum Development Process to Address Agile Product Line Engineering
Software Product Line Engineering (SPLE) is becoming widely used due to the improvement it means when developing software products of the same family. However, SPLE demands long-term investment on a product-line platform that might not be profitable due to rapid changing business settings. Since Agile Software Development (ASD) approaches are being successfully applied in volatile markets, several companies have suggested the idea of integrating SPLE and ASD when a family product has to be developed. Agile Product Line Engineering (APLE) advocates the integration of SPLE and ASD to address their lacks when they are individually applied to software development. A previous literature re-view of experiences and practices on APLE revealed important challenges about how to fully put APLE into practice. Our contribution address several of these challenges by tailoring the agile method Scrum by means of three concepts that we have defined: plastic partial components, working PL-architectures, and reactive reuse
A concrete product derivation in software product line engineering: a practical approach
Software Product Lines enable the development of a perfect family of products by reusing shared assets in a systematic manner. Product derivation is a critical activity in software product line engineering and one of the most pressing issues that a software product line must address. This work introduces an approach for automating the derivation of a product from a software product line. The software product line is part of a product family that evolved from a non-structured approach to managing variability. The automated derivation approach relies on product configurations and the refactoring of feature models. The approach was deployed and evaluated in the automotive domain using a real-world software product line. The outcome demonstrates that the approach generates a product in an automated and successful manner.This work has been supported by FCT – Fundação para a Ciência e Tecnologia within the R&D Units Project Scope: UIDB/00319/2020
Applying model-driven paradigm: CALIPSOneo experience
Model-Driven Engineering paradigm is being used by the research community in the last years, obtaining suitable results. However, there are few practical experiences in the enterprise field. This paper presents the use of this paradigm in an aeronautical PLM project named CALIPSOneo currently under development in Airbus. In this context, NDT methodology was adapted as methodology in order to be used by the development team. The paper presents this process and the results that we are getting from the project. Besides, some relevant learned lessons from the trenches are concluded.Ministerio de Ciencia e Innovación TIN2010-20057-C03-02Junta de AndalucÃa TIC-578
An Empirical Study on Decision making for Quality Requirements
[Context] Quality requirements are important for product success yet often
handled poorly. The problems with scope decision lead to delayed handling and
an unbalanced scope. [Objective] This study characterizes the scope decision
process to understand influencing factors and properties affecting the scope
decision of quality requirements. [Method] We studied one company's scope
decision process over a period of five years. We analyzed the decisions
artifacts and interviewed experienced engineers involved in the scope decision
process. [Results] Features addressing quality aspects explicitly are a minor
part (4.41%) of all features handled. The phase of the product line seems to
influence the prevalence and acceptance rate of quality features. Lastly,
relying on external stakeholders and upfront analysis seems to lead to long
lead-times and an insufficient quality requirements scope. [Conclusions] There
is a need to make quality mode explicit in the scope decision process. We
propose a scope decision process at a strategic level and a tactical level. The
former to address long-term planning and the latter to cater for a speedy
process. Furthermore, we believe it is key to balance the stakeholder input
with feedback from usage and market in a more direct way than through a long
plan-driven process
A Value-Driven Framework for Software Architecture
Software that is not aligned with the business values of the organization for which it
was developed does not entirely fulfill its raison d’etre. Business values represent what
is important in a company, or organization, and should influence the overall software
system behavior, contributing to the overall success of the organization. However, approaches
to derive a software architecture considering the business values exchanged
between an organization and its market players are lacking. Our quest is to address this
problem and investigate how to derive value-centered architectural models systematically.
We used the Technology Research method to address this PhD research question.
This methodological approach proposes three steps: problem analysis, innovation, and
validation. The problem analysis was performed using systematic studies of the literature
to obtain full coverage on the main themes of this work, particularly, business value
modeling, software architecture methods, and software architecture derivation methods.
Next, the innovation step was accomplished by creating a framework for the derivation
of a software reference architecture model considering an organization’s business values.
The resulting framework is composed of three core modules: Business Value Modeling,
Agile Reference Architecture Modeling, and Goal-Driven SOA Architecture Modeling.
While the Business value modeling module focuses on building a stakeholder-centric
business specification, the Agile Reference Architecture Modeling and the Goal-Driven
SOA Architecture Modeling modules concentrate on generating a software reference architecture
aligned with the business value specification. Finally, the validation part of
our framework is achieved through proof-of-concept prototypes for three new domain
specific languages, case studies, and quasi-experiments, including a family of controlled
experiments. The findings from our research show that the complexity and lack of rigor
in the existing approaches to represent business values can be addressed by an early requirements
specification method that represents the value exchanges of a business. Also,
by using sophisticated model-driven engineering techniques (e.g., metamodels, model
transformations, and model transformation languages), it was possible to obtain source
generators to derive a software architecture model based on early requirements value
models, while assuring traceability throughout the architectural derivation process. In conclusion, despite using sophisticated techniques, the derivation process of a software
reference architecture is helped by simple to use methods supported by black box
transformations and guidelines that facilitate the activities for the less experienced software
architects. The experimental validation process used confirmed that our framework
is feasible and perceived as easy to use and useful, also indicating that the participants
of the experiments intend to use it in the future
- …