Introducing requirements traceability support in model-driven development of web applications

Valderas, Pedro; Pelechano, Vicente

doi:10.1016/j.infsof.2008.09.008

Cited by 20 publications

(8 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…[Liu 2009]), requirements to design (e.g. [Valderas and Pelechano 2009]), or design to test (e.g. [Samuel et al 2007]) were not considered to validate the taxonomy.…”

Section: External Validitymentioning

confidence: 99%

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

Requirements Engineering and Software Testing are mature areas and have seen a lot of research. Nevertheless, their interactions have been sparsely explored beyond the concept of traceability. To fill this gap we propose a definition of requirements engineering and software test (REST) alignment, a taxonomy that characterizes the methods linking the respective areas, and a process to assess alignment. The taxonomy can support researchers to identify new opportunities for investigation, as well as practitioners to compare alignment methods and evaluate alignment, or lack thereof. We constructed the REST taxonomy by analyzing alignment methods published in literature, iteratively validating the emerging dimensions. The resulting concept of an information dyad characterizes the exchange of information required for any alignment to take place. We demonstrate use of the taxonomy by applying it on five in-depth cases and illustrate angles of analysis on a set of thirteen alignment methods. In addition we developed an assessment framework (REST-bench), applied it in an industrial assessment, and showed that it, with a low effort, can identify opportunities to improve REST alignment. Although we expect that the taxonomy can be further refined, we believe that the information dyad is a valid and useful construct to understand alignment.

show abstract

“…[Liu 2009]), requirements to design (e.g. [Valderas and Pelechano 2009]), or design to test (e.g. [Samuel et al 2007]) were not considered to validate the taxonomy.…”

Section: External Validitymentioning

confidence: 99%

A taxonomy for requirements engineering and software test alignment

Unterkalmsteiner

Feldt

Gorschek

2014

ACM Trans. Softw. Eng. Methodol.

View full text Add to dashboard Cite

show abstract

“…This taxonomy provides an overview of the tasks that users must perform to interact with web applications hierarchically [15].…”

Section: Task-driven Approachmentioning

confidence: 99%

Approach of Agile Methodologies in the Development of Web-Based Software

Ríos

Souto

2019

Information

View full text Add to dashboard Cite

The current inclusion of agile methodologies in web-oriented projects has been considered on a large-scale by software developers. However, the benefits and limitations go beyond the comforts that project managers delimit when choosing them. Selecting a methodology involves more than only the associated processes or some documentation. Based on the above, we could define as the main concerns the approach with which we identify the methodology, the needs of the company, the size, and qualities of the project, and especially the characteristics of agile development that they possess. However, there are several difficulties in selecting the most appropriate methodology due to the features in common; Will it be suitable for my project? What challenges will be presented in the process? Will my team understand each stage? Will I be able to deliver software that satisfies the client? Project managers create these questions, which seem manageable but have huge effects. This paper presents a systematic literature review based on the analysis of the approaches of six web development methodologies. The aim of the study is to analyze the approaches presented by relevant methodologies, identifying their common agile characteristics and managing to contrast both its benefits and limitations during a project. As a result, we could itemize five common features, which are presented within the processes; (1) flexibility, (2) constant communication of the workgroup, (3) use of UML, (4) the inclusion of the end-user and (5) some documentation.

show abstract

“…In the context of MDD, automated transformation techniques provide capabilities for traceability (Valderas and Pelechano, 2009;Behrens, 2007). Due to the extensive use of transformations (i.e.…”

Section: Traceability Between Modelsmentioning

confidence: 99%

A framework for developing home automation systems: From requirements to code

Sánchez

Jiménez

Rosique

et al. 2011

Journal of Systems and Software

View full text Add to dashboard Cite

a b s t r a c tThis article presents an integrated framework for the development of home automation systems following the model-driven approach. By executing model transformations the environment allows developers to generate executable code for specific platforms. The tools presented in this work help developers to model home automation systems by means of a domain specific language which is later transformed into code for home automation specific platforms. These transformations have been defined by means of graph grammars and template engines extended with traceability capabilities. Our framework also allows the models to be reused for different applications since a catalogue of requirements is provided. This framework enables the development of home automation applications with techniques for improving the quality of both the process and the models obtained. In order to evaluate the benefits of the approach, we conducted a survey among developers that used the framework. The analysis of the outcome of this survey shows which conditions should be fulfilled in order to increase reusability.

show abstract

Introducing requirements traceability support in model-driven development of web applications

Cited by 20 publications

References 30 publications

A taxonomy for requirements engineering and software test alignment

A taxonomy for requirements engineering and software test alignment

Approach of Agile Methodologies in the Development of Web-Based Software

A framework for developing home automation systems: From requirements to code

Contact Info

Product

Resources

About