Rights accessRestricted access - publisher's policy
[Context and motivation] Software Requirement Patterns (SRP) are a type of artifact that may be used during requirements elicitation that also impact positively in other activities like documentation and validation. In our experiences, SRP show a great percentage of reuse for the non-functional requirements needed in call-for-tender requirement specifications. [Question/problem] We are facing the need of formulating the accurate definition of SRP for their use in call-for-tender processes to allow reasoning rigorously and know more about their semantics and applicability. [Principal ideas/results] In this paper we present a metamodel for SRP around three main concepts: 1) the structure of SRP themselves; 2) the relationships among them; 3) the classification criteria for grouping them. [Contribution] We provide a rigorous
definition that shows the concepts that are of interest when defining and applying SRP.
CitationFranch, J. [et al.]. A metamodel for software requirement patterns. A: International Working Conference on Requirements Engineering: Foundation for Software Engineering. "16th International Working Conference on Requirements Engineering: Foundation for Software Engineering". Essen: 2010, p. 85-90.
All rights reserved. This work is protected by the corresponding intellectual and industrial property rights. Without prejudice to any existing legal exemptions, reproduction, distribution, public communication or transformation of this work are prohibited without permission of the copyright holder. If you wish to make any use of the work not provided for in the law, please contact: firstname.lastname@example.org