A Metamodel for Software Requirement Patterns

  • Xavier Franch
  • Cristina Palomares
  • Carme Quer
  • Samuel Renault
  • François De Lazzer
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6182)


[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.


software requirement patterns requirements reuse metamodel 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Lam, W., McDermid, J.A., Vickers, A.J.: Ten Steps Towards Systematic Requirements Reuse. REJ 2(2) (1997)Google Scholar
  2. 2.
    Roberson, S., Robertson, J.: Mastering the Requirements Process, 2nd edn. Addison-Wesley, Reading (2006)Google Scholar
  3. 3.
    Alexander, C.: The Timeless Way of Building. Oxford Books (1979)Google Scholar
  4. 4.
    Henninger, S., Corrêa, V.: Software Pattern Communities: Current Practices and Challenges. In: PLoP 2007 (2007)Google Scholar
  5. 5.
    Durán, A., Bernárdez, B., Ruíz, A., Toro, M.: A Requirements Elicitation Approach Based in Templates and Patterns. In: WER 1999 (1999)Google Scholar
  6. 6.
    Moros, B., Vicente, C., Toval, A.: Metamodeling Variability to Enable Requirements Reuse. In: EMMSAD 2008 (2008)Google Scholar
  7. 7.
    Robertson, S.: Requirements Patterns Via Events/Use Cases. In: PLoP 1996 (1996)Google Scholar
  8. 8.
    López, O., Laguna, M.A., García, F.J.: Metamodeling for Requirements Reuse. In: WER 2002 (2002)Google Scholar
  9. 9.
    Konrad, S., Cheng, B.H.C.: Requirements Patterns for Embedded Systems. In: RE 2002 (2002)Google Scholar
  10. 10.
    Matheson, D., Ray, I., Ray, I., Houmb, S.H.: Building Security Requirement Patterns for Increased Effectiveness Early in the Development Process. In: SREIS 2005 (2005)Google Scholar
  11. 11.
    Mahfouz, A., Barroca, L., Laney, R.C., Nuseibeh, B.: Patterns for Service-Oriented Information Exchange Requirements. In: PLoP 2006 (2006)Google Scholar
  12. 12.
    Withall, J.: Software Requirements Patterns. Microsoft Press, Redmond (2007)Google Scholar
  13. 13.
    Yang, J., Liu, L.: Modelling Requirements Patterns with a Goal and PF Integrated Analysis Approach. In: COMPSAC 2008 (2008)Google Scholar
  14. 14.
    Krystkowiak, M., Bucciarelli, B.: COTS Selection for SMEs: a Report on a Case Study and on a Supporting Tool. In: RECOTS 2003 (2003)Google Scholar
  15. 15.
    Renault, S., Méndez, O., Franch, X., Quer, C.: A Pattern-based Method for building Requirements Documents in Call-for-tender Processes. IJCSA 6(5) (2009)Google Scholar
  16. 16.
    Carvallo, J.P., Franch, X., Quer, C.: Managing Non-Technical Requirements in COTS Components Selection. In: RE 2006 (2006)Google Scholar
  17. 17.
    Méndez, O., Franch, X., Quer, C.: Requirements Patterns for COTS Systems. In: ICCBSS 2008 (2008)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2010

Authors and Affiliations

  • Xavier Franch
    • 1
  • Cristina Palomares
    • 1
  • Carme Quer
    • 1
  • Samuel Renault
    • 2
  • François De Lazzer
    • 2
  1. 1.Universitat Politècnica de Catalunya (UPC), UPC – Campus NordBarcelonaSpain
  2. 2.CITI, CRP Henri TudorLuxembourgLuxembourg

Personalised recommendations