Bruno González-Baixauli's research while affiliated with Universidad de Valladolid and other places
What is this page?
This page lists the scientific contributions of an author, who either does not have a ResearchGate profile, or has not yet added these contributions to their profile.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
It was automatically created by ResearchGate to create a record of this author's body of work. We create such pages to advance our goal of creating and maintaining the most comprehensive scientific repository possible. In doing so, we process publicly available (personal) data relating to the author as a member of the scientific community.
If you're a ResearchGate member, you can follow this page to keep up with this author's work.
If you are this author, and you don't want us to display this page anymore, please let us know.
Publications (35)
People with communication problems can use personal communicators as a low-cost help in their everyday life. The diversity
of individual situations has guided us towards a solution based on the software product line paradigm. Multiple options can
be easily incorporated to each product, allowing the adequate customization of the final application to...
Information systems designers have been increasingly convinced about the importance of dealing with quality issues at early stages of development. Over the landscape of quality issues, several proposals have been published as to help with respect to security. On the other hand, designers do also need to care about other quality issues; for instance...
Development of software product lines is a challenge for small organizations. Although the use of feature models is necessary
to manage variability, we propose to use conventional tools for the rest of development activities. Traceability between the
features and the UML architectural models is achieved by means of the package merge mechanism of UM...
Goal modeling fits model-driven engineering (MDE) in that it captures stakeholder concerns and the interdependencies using concepts that are much less bound to the underlying implementation technology and are much closer to the problem languages. Aspect-oriented software development (AOSD) provides language constructs to facilitate the representati...
A fundamental problem with requirements engineering (RE) is to validate that a design does satisfy stakeholder requirements. Some requirements can be fulfilled locally by designed modules, where others must be accommodated globally by multiple modules together. These global requirements often crosscut with other local requirements and as such lead...
One of the most important issues in the development of software product lines is the elicitation, management, and representation of the variability. In this context, one of the most used instruments is the feature model. But a feature model (due to the open definition of feature) usually contains an amalgamation of various different variability asp...
Feature models are the basic instrument to analyze and configure the variability and commonality of a software product line. But feature models embody various different variability facets (structural, behavioral, non-functional, etc.). Features, used as core model, must be completed with other techniques (i.e. goals or UML models) to fulfill these...
One of the most important issues in the development of software product lines is the elicitation, management, and representation of the variability. In this context, feature models are the basic instrument to analyze and configure the variability and communality of the product line. But a feature model can be considered as an amalgamation of variou...
One of the key problems in the development of software product lines is the representation and management of variability and commonality. The customary way to define both aspects is by means of feature models that also allow the configuration of each specific application within the product line to be selected. However the control of traceability be...
Aspects promote a clear separation of concerns so that tangled and scattered concerns are modularized throughout software development. We propose a framework to trace aspects identified during goal-oriented requirements analysis to code and testing. Two types of checks are performed to validate the resulting system in light of stakeholders' cross-...
Variability analysis techniques have an important drawback: the analysis of Non-Functional Requirements. Usually, these techniques do not fully deal with them and only mention that they should be considered. In our framework, we use an intentional model-based approach where the functional models are used to define the variability space and the non-...
Abstract i-star (i*) modeling ,uses the actor concept to ground the intentions of a given Universe of Discourse. Our work contributes to the ,understanding of the actor concept as used in i*. We have ,used a collaborative ,approach ,to better understand ,the actor concept. The authors met 9 times to discuss ,the topic. The goal was ,to discuss ,i*...
On our ongoing research on variability analysis, two major drawbacks have been identified: a) the lack of an effective tracing from the rationale to the selected variant, and b) the lack of an effective support to decide what variability should be implemented. In order to perform variability analysis we propose to combine goal-oriented requirements...
Complex goal oriented information models such as i* and the non functional requirements framework bring up the need to model relationships between goals. In particular when dealing with non-functional goals, also known as softgoals, the modeler faces the problem of how to elicit the complex web of intertwined relationships that exist between them....
One of the most important factors of success in the development of a software product line is the elicitation, management, and representation of variability. Feature models, are used as a key artifact to express requirements variability and are the basis for the domain architecture design. In this context, this article explores the possible advanta...
One of the main approaches to Requirements Engineering is Goal-Oriented Requirement Engineering. This approach, based in Artificial Intelligence models, argues that goals are a natural and high level abstraction concept to elicit and represent requirements. Another advantage of goals is that they help non-functional requirements representation and...
One of the most important factors of success in the development of a software product line is the elicitation, management, and representation of variability. In this context, this article explores the possible advantages of adoption of the Model Driven Engineering (MDE) paradigm in the variability specification. Feature graphs and Goal models can b...
One of the most important factors of success in the development of a software product line is the elicitation, management, and representation of the variability. In this context, this article explores the advantages of adopting the Model Driven Development (MDD) paradigm in the variability management, including the transformation of feature graphs...
One of the most important factors of success in the development of a product line is the elicitation, management, and representation of the variability. In this context, this article explores the possible advantages of recent proposals such as Goal Oriented Requirements Engineering and the Model Driven Architecture (MDA) initiative. Goals and featu...
La Ingeniería de Requisitos es un área considerada clave en la Ingeniería del Software. Dentro de esta área, uno de los principales enfoques es el de la orientación a objetivos. Según este enfoque, que se basa en ideas de inteligencia artificial, los objetivos son un concepto natural y de alto nivel de abstracción para la elicitación y representaci...
One of the benefits of goal-oriented requirements engineering is the possibility of conducting formal analysis in order to evaluate alternative solutions of goal models. Superficially, goal analysis seems like an optimization technique. In contrast to such techniques, however, goal analysis does not aim at optimal solutions, but rather "good enough...
Traditional PL requirements approaches present several problems in requirements analysis, mainly in variants analysis and selection. The main handicap is dealing with non-functional requirements. These problems can be solved with the introduction of the goal/softgoal paradigm. This paradigm introduces intentionality ("whys") and allows relating fun...
Conventional software processes such as the Unified Process do not include reuse techniques among their disciplines. In this
article, we present an extension of the Unified Process that introduces software reuse with minimal disturbance by means of
the definition of a new process for product line engineering and the adaptation of standard disciplin...
Software reuse is accepted as a source of important benefits, expressed in productivity and quality terms, when an industrial approach is introduced in the software process. However, mainstream software processes such as unified process do not include reuse techniques among the tools that software engineers must deal with. We present a proposal to...
The study of the variability in software systems has become a primary aspect of software development, in particular in the fields of software customization or software product lines. The customary way to manage the variability in product lines is by means of feature models that also allow the configuration of each specific application within the pr...
The study of the variability in software systems has become a central aspect of software development, in particular in the fields of software customization and software product lines. One of the key problems in the development of software product lines is the representation and management of variability and commonality. The feature models are gener...
Citations
... We aim to simplify the change from a conventional development process towards the product line paradigm. To achieve this, we use standard UML elements to represent the SPL architecture variations with conventional CASE and IDE tools [9]. We have used that approach to build an e-Commerce SPL and with several mobile systems. ...
... There are several approaches to model variability of QAs such as extensions to feature models (Benavides et al. 2006), goalbased models (González-Baixauli et al. 2004), Bayesian belief networks (Zhang et al. 2003), or frameworks like COVAMOF (Sinnema et al. 2006). All these methods are compared in (Etxeberria et al. 2007), but none of them have became a de-facto approach for modelling the variability of QAs, nor do they deal with the reconfiguration of QAs at runtime. ...
... • uniquely supports non-functional requirements, a feature only available in Tropos [5], however, not as a way to define alternative tasks that achieve the soft-goals as in Tropos, but as requirements that influence the way to implement a system [37] • uniquely offers a process fragment for validating analysis phase models against nonfunctional requirements such as performance and scaling [53] We are currently in the process of transferring the ASEME tools to the web. This will make it more accessible to practitioners that now have to install a specific Eclipse package and then some extensions and, finally, the ASEME dashboard. ...
Reference: The ASEME methodology
... Merging MDD and product lines is not new, we know of examples that explicitly use features in MDD [9,8,10,11,12,22]. One is BoldStroke: a product-line for supporting a family of mission computing avionics for military aircraft [12] . ...
... Desde una perspectiva constructivista, una persona atribuye significados a acontecimientos que le ocurren a lo largo de su vida siendo denominados como constructos personales. En palabrasde Montesano, Feixas y Varlotta (2009) un constructo es un elemento de conocimiento con dos polos opuestos.De acuerdo con Kelly (1955; como se citó enGonzález et al., 2004), el conjunto de constructos de una persona presenta relaciones entre ellos, lo cual conforma la base de los juicios y comportamientos de dicha persona, permitiéndole hacer tanto hipótesiscomo conclusiones acerca de sí mismo y de los demás.Los acontecimientos que le ocurren a la persona pueden provocar modificaciones en su estructura cognitiva, por lo que consideramos que la experiencia de enfermar y de adaptarse a la noción de ser un "enfermo crónico", puede provocar cambios sustanciales al ciclo de la experiencia. Esta situación desde el marco de la Teoría de Kelly(Feixas y Botella, 1998) puede alterar la construcción del sí mismo y de la percepción sobre los demás, que es lo que se pretende indagar en este estudio. ...
... In this work, OCL is also presented as a suitable approach to define model constraints, but as the correspondences between feature models and class diagrams are not precisely defined, there is no automatic generation of OCL invariants. In turn, [13] do present a set of QVT rules to automatically generate class diagrams from feature models. However, in this case, neither model constraints nor configuration definitions support is presented. ...
... The resulting UML model must be XMI-based; therefore any UML compliant case tool could be a valid option. A first implementation, using a XML style sheet, is given in [11]. TheFigure 4 shows a feature model expressed with the XFeature tool, and the class diagram obtained from the resulting XMI file, after the application of the style sheet. ...
Reference: Product lines, features, and mdd
... John and Muthig [16] suggest the application of use case templates, although they do not distinguish between optional, alternative or obligatory variants. However, Halman and Pohl propose in [17] to make use of UML 2 package merge, based on [6], as a tool for the variability representation and configuration in PLs. As opposed to the mentioned proposals, our solution is centered in one behavior specification model of a PL, as are the SCs, introducing a clearly defined formal sustenance. ...
Reference: Specification of Products and Product Lines
... These variability models are represented by means of a modeling formalism. In our literature research, we have found quite a number of variability modeling formalisms, such as FODA (Feature-Oriented Domain Analysis) [9], Orthogonal Variability Models (OVM) [13], UML classes [26], DOPLER [5] and Goals [6]. To represent and reason on these models, a number of approaches and tools exist in the literature. ...
... Software product lines (SPL) are a proven reuse approach in industrial environments, due to the combination of systematic development and the reuse of components that include the common and variable parts of the product line [2] [4]. Our approach to product line development [9] uses the package merge mechanism of UML 2 [12] as a representation of the variability in the product line. This is directly reflected in the relationships between packages in the architectural models, so that the traceability of configuration decisions is straightforward. ...