Dynamic Situational Adaptation of a Requirements Engineering Process

Author(s):  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn ◽  
Viviana Alejandra Ledesma

Literature shows that the elicitation techniques used in a requirements engineering process are often chosen based on the particular characteristics of the application context, mainly related to the involved human sources of information. However, these particularities, usually called situational factors, are seldom taken into account in other activities of the requirements process. Most situational factors, when considered in software projects, have a high influence on the requirements process. Therefore, the different situations that may attempt against or may favor a successful requirements process should be identified at the beginning of the project. Additionally, some factors may evolve along with software development life cycle; this may imply re-planning the requirements process at later strategic milestones. In this chapter, a process for constructing and dynamically adapting a requirements process is proposed. The process uses different combinations of situational factors at specific variation points and manages a repository of process blocks to perform the tailoring.

Author(s):  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn ◽  
Viviana Alejandra Ledesma

Literature shows that the elicitation techniques used in a Requirements Engineering process are often chosen based on the particular characteristics of the application context, mainly related to the involved human sources of information. However, these particularities, usually called situational factors, are seldom taken into account in other activities of the requirements process. Most situational factors, when considered in software projects, have a high influence on the requirements process. Therefore, the different situations that may attempt against or may favor a successful requirements process should be identified at the beginning of the project. Additionally, some of such factors may evolve along with software development life cycle; this may imply re-planning the requirements process at later strategic milestones. In this chapter, a process for constructing and dynamically adapting a requirements process is proposed. The process uses different combinations of situational factors at specific variation points and manages a repository of process blocks to perform the tailoring.


2022 ◽  
pp. 709-725
Author(s):  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn ◽  
Viviana Alejandra Ledesma

Literature mainly focuses the adaptation of any requirements engineering process on the possible variations of elicitation techniques, mainly due to information sources characteristics. However, these particularities, usually called situational factors, are seldom considered in other activities of the requirements process. Most situational factors, when considered in software projects, have a high influence on the requirements process. Therefore, the different situations that may attempt against or may favor a successful requirements process should be identified at the beginning of the project. Additionally, some of such factors may evolve along software development life cycle; this should motivate a reengineering of the requirements process at some strategic milestones. In this chapter, a process for constructing and dynamically adapting a requirements process is proposed, focusing on the evolving factors. The process follows rules based on different combinations of situational factors at specific control points and manages a repository of process blocks to perform the tailoring.


Author(s):  
Graciela Dora Susana Hadad ◽  
Jorge Horacio Doorn ◽  
Viviana Alejandra Ledesma

Literature mainly focuses the adaptation of any requirements engineering process on the possible variations of elicitation techniques, mainly due to information sources characteristics. However, these particularities, usually called situational factors, are seldom considered in other activities of the requirements process. Most situational factors, when considered in software projects, have a high influence on the requirements process. Therefore, the different situations that may attempt against or may favor a successful requirements process should be identified at the beginning of the project. Additionally, some of such factors may evolve along software development life cycle; this should motivate a reengineering of the requirements process at some strategic milestones. In this chapter, a process for constructing and dynamically adapting a requirements process is proposed, focusing on the evolving factors. The process follows rules based on different combinations of situational factors at specific control points and manages a repository of process blocks to perform the tailoring.


Author(s):  
Taciana Novo Kudo ◽  
Renato De Freitas Bulcão Neto ◽  
Auri Marcelo Rizzo Vincenzi ◽  
Alessandra Alaniz Macedo

In the past few years, the literature has shown that the practice of reuse through requirement patterns is an effective alternative to address specification quality issues, with the additional benefit of time savings. Due to the interactions between requirements engineering and other phases of the software development life cycle (SDLC), these benefits may extend to the entire development process. This paper describes a revisited systematic literature mapping (SLM) that identifies and analyzes research that demonstrates those benefits from the use of requirement patterns for software design, construction, testing, and maintenance. In this extended version, the SLM protocol includes automatic search over two additional sources of information and the application of the snowballing technique, resulting in ten primary studies for analysis and synthesis. In spite of this new version of the SLM protocol, results still point out a small number of studies on requirement patterns at the SDLC (excluding requirements engineering). Results indicate that there is yet an open field for research that demonstrates, through empirical evaluation and usage in practice, the pertinence of requirement patterns at software design, construction, testing, and maintenance.


Sign in / Sign up

Export Citation Format

Share Document