PABRE: Pattern-based Requirements Elicitation

Renault, Samuel; Mendez-Bonilla, O.; Franch, Xavier; Quer, Carme

doi:10.1109/rcis.2009.5089271

Cited by 25 publications

(22 citation statements)

References 22 publications

(19 reference statements)

Supporting

Mentioning

Contrasting

Order By: Relevance

“…For instance, the NFR language [7] defines different types of qualified relationships like "hurt" or "break" for establishing conflicts and "support" and "help" for synergies. Approaches like [8] establish these types of relationships at the level of software requirement patterns. The level of analysis supported by these representation approaches is a key point in their adoption.…”

Section: Key Questionsmentioning

confidence: 99%

Conflicts and Synergies among Quality Requirements

Boehm

Franch

2017

2017 IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C)

Self Cite

View full text Add to dashboard Cite

Abstract-Analyses of the interactions among quality requirements (QRs) have often found that optimizing on one QR will cause serious problems with other QRs. As just one relevant example, one large project had an Integrated Product Team optimize the system for Security. In doing so, it reduced its vulnerability profile by having a single-agent key distribution system and a single copy of the data base -only to have the Reliability engineers point on that these were system-critical single points of failure. The project's Security-optimized architecture also created conflicts with the system's Performance, Usability, and Modifiability. Of course, optimizing the system for Security had synergies with Reliability in having high levels of Confidentiality, Integrity, and Availability. This panel aims at fostering discussion on these relationships among QRs and how the use of data repositories may help discovering them.

show abstract

Section: Key Questionsmentioning

confidence: 99%

Conflicts and Synergies among Quality Requirements

Boehm

Franch

2017

2017 IEEE International Conference on Software Quality, Reliability and Security Companion (QRS-C)

Self Cite

View full text Add to dashboard Cite

show abstract

“…We disregard the studies on feature extractions from model-based mentioning RR, for example work in Monzon (2008), Von Knethen et al (2002, and Robinson and Woo (2004). We also excluded the studies regarding extractions of source code such as in Marcus and Maletic (2003) or selection of components for reuse in SPL (Abraham and Aguilar, 2007), or RR through pattern (Renault et al, 2009). A literature review section in another published paper related to RR provided only seven studies (Barreto et al, 2013).…”

Section: The Reduction In Number Of Selected Studiesmentioning

confidence: 99%

Feature extraction approaches from natural language requirements for reuse in software product lines: A systematic literature review

Bakar

Kasirun

Salleh

2015

Journal of Systems and Software

View full text Add to dashboard Cite

“…Our previous experience in quality models [21] and in requirements engineering projects and the analysis of TUDOR SRS showed us that non-functional requirements and nontechnical requirements have higher reuse frequency than functional requirements. Then, our aim for the first version of the catalogue was to represent those SRP whose application leads to NFR that appear in the mentioned SRS [22]. From the experience gained, we recently finished the second version of the catalogue in which we added the SRP corresponding to the NTR, as presented in Section 5.6.…”

Section: Srp Catalogue Constructionmentioning

confidence: 99%

Constructing and Using Software Requirement Patterns

Franch

Quer

Renault³

et al. 2013

Managing Requirements Knowledge

View full text Add to dashboard Cite

Software requirement reuse strategies are necessary to capitalize and reuse knowledge in the requirements engineering phase. The PABRE framework is designed to support requirement reuse through the use of software requirement patterns. It consists of a meta-model that describes the main concepts around the notion of pattern; a method to conduct the elicitation and documentation processes; a catalogue of patterns; and a tool that supports the catalogue's management and use. In this chapter all these elements are presented in detail making emphasis on the construction, use and evolution of software requirement patterns. Furthermore, the chapter includes the construction of a catalogue of non-technical software requirement patterns for illustration purposes. catalogue of patterns for non-technical requirements. Finally, Section 5.7 presents some conclusions and future work. ContextThe work presented in this paper stems from the needs of the Public Research Centre Henri Tudor (TUDOR) at Luxembourg when conducting IT procurement projects over time. Since 2004, TUDOR works in collaboration with freelance and independent consultants. These consultants are federated in a business network that we refer as CASSIS. They are trained to innovative methods produced by research projects and they use these methods in industrial contexts. TUDOR monitors their activity to ensure that they do not deviate over the time. One of the main methodologies delivered to consultants is a requirement engineering method used to design Software Requirements Specification documents (SRS) for IT procurement projects in small and medium size companies [3].Consultants work in collaboration with customers to help them in identifying their needs for a new IT system supporting their business activities, and then selecting the most relevant system accordingly to their needs. In this particular context, requirements engineers' consultants define SRS for external customers and not for their internal purpose. Consultants' customers are usually looking both for an IT system and for its implementation. In other words, they have requirements towards an IT system and towards additional services. For this reason, the scope of the SRS often encompasses functional, non-functional and non-technical requirements.The initial goal of the SRS is to serve as a basis for a competitive procurement process. So their primary use is for IT sales managers to understand the needs of the customer and to propose a commercial bid. Only when this process is achieved, the SRS is used in second intend as source for the design or the customization of the selected IT system. So far, consultants and TUDOR have performed more than 40 projects in compliance with the methodology. The initial approach for capitalising requirements knowledge among the consultants was quite basic. It consisted in re-using fragments of a former SRS as a basis to build the new SRS. This approach was simple to use but required to be aware of the former projects, which was not easy for the consultants due to t...

show abstract

PABRE: Pattern-based Requirements Elicitation

Cited by 25 publications

References 22 publications

Conflicts and Synergies among Quality Requirements

Conflicts and Synergies among Quality Requirements

Feature extraction approaches from natural language requirements for reuse in software product lines: A systematic literature review

Constructing and Using Software Requirement Patterns

Contact Info

Product

Resources

About