Learn More
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 advantages of(More)
Correct requirements determination is a critical factor in software development as it takes resources and it is an error prone activity which can bring tragic consequences to the rest of the software life cycle. Having stored reusable requirements elements, both qualified and classified, in a repository might contribute to taking advantage of software(More)
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 between the(More)
The requirements of an Information System come of very diverse formats. Their storage in a repository and the relationships between them and with another reusable elements could condition the success or failure of a reuse program. It is necessary to introduce a minimum degree of normalization in the requirements, so that they can be really reusable. This is(More)
This paper presents a proposal that aims to cover some tasks required in the Database Reengineering process, mainly in the Conceptual Abstraction phase. The principal tasks are: the transformation of enriched logical schema to object-oriented schema, support for process iterations and support for data migration from the legacy database to the new database.(More)
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. In this paper, we present a(More)
decisión de alto nivel (los objetivos del usuario) y permiten incorporar los requisitos no funcionales (RNF). Durante los últimos años los sistemas software cada vez tienden a soportar una mayor variabilidad. Esta variabilidad se debe principalmente a dos causas: a las demandas de los usuarios de sistemas más adaptables a sus necesidades (sistemas altamente(More)
Durante los últimos años los sistemas software cada vez tienden a soportar una mayor variabilidad, definida como la habilidad de cambio o de personalización de un sistema [14]. Esta variabilidad se debe principalmente a dos causas: a las demandas de los usuarios de sistemas más adaptables a sus necesidades (sistemas personalizables [8]) y a la presión del(More)
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(More)