Cristina Palomares

Learn More
[Context and motivation] Software Requirement Patterns (SRP) are a type of artifact that may be used during requirements elicitation and that also impact positively in other activities like documentation and validation. In our preliminary experiences at the CITI-CPRHT department, SRP show a great percentage of reuse for the non-functional requirements(More)
— Software Requirement Patterns (SRP) have been proposed as an artifact for fostering requirements reuse. PABRE is a framework that promotes the use of SRP as a means for requirements elicitation, validation and documentation in the context of IT procurement projects. In this paper, we present a catalogue of non-technical SRP included in the framework and(More)
Software requirement patterns have been proposed as an artifact for fostering requirements reuse. When we define these patterns for the functional part of a software system, we realize that most of patterns are specific of a software domain. This paper presents and analyzes a catalogue of functional software requirement patterns for the domain of content(More)
1 Introduction Self-Adaptive Systems (SAS) and Cyber Physical Systems (CPS) continue to engage the academic of Software Engineering in general and Requirements Engineering in particular. While SAS are often seen as systems that are able to adapt to changing requirements at runtime, CPS develop ad-hoc networks to provide emerging function-ality at runtime.(More)
The final quality of software products and services depends on the requirements stated in the Software Requirements Specification (SRS). However, some problems like ambiguity, incompleteness and inconsistency, have been reported in the writing of SRS, especially when natural language is used. Requirements reuse has been proposed as a key asset for(More)
  • 1