DSpace DSpace UPC
 Català   Castellano   English  

E-prints UPC >
Altres >
Enviament des de DRAC >

Empreu aquest identificador per citar o enllaçar aquest ítem: http://hdl.handle.net/2117/16874

Arxiu Descripció MidaFormat
refsq11ef-franch-et-al-camera-ready.pdf84,22 kBAdobe PDFThumbnail

Citació: Franch, J. [et al.]. Interested in improving your requirements engineering process? Try requirement patterns!. A: International Working Conference on Requirements Engineering: Foundation for Software Quality. "Proceedings of the REFSQ 2011 Workshops REEW, EPICAL and RePriCo, the REFSQ 2011 Empirical Track (Empirical Live Experiment and Empirical Research Fair), and the REFSQ 2011 Doctoral Symposium". Essen: 2012, p. 161-162.
Títol: Interested in improving your requirements engineering process? Try requirement patterns!
Autor: Franch Gutiérrez, Javier Veure Producció científica UPC; Guerlain, Cindy; Palomares Bonache, Cristina Veure Producció científica UPC; Quer Bosor, Maria Carme Veure Producció científica UPC; Renault, Samuel
Data: 2012
Tipus de document: Conference report
Resum: Requirement elicitation is the process of acquiring the system requirements from the system stakeholders. This process is critical in all software projects: if not all the requirements are elicited, or if some elicited requirements do not describe real stakeholder needs, or if the quality of the requirements is poor (e.g., they suffer from ambiguities), the chance of project failure increases. Techniques supporting requirements elicitation (interviews, meetings, storyboards...) are mostly oriented to obtain requirements from scratch and they may hardly take advantage of a fundamental observation: When specifying a system, it is quite usual that a significant proportion of requirements is recurrent and belongs to a relatively small number of categories, especially in the case of non-functional requirements. Our motivation is to consider this observation for improving the effectiveness of the requirement elicitation process. We are using the concept of software requirement pattern [1] (SRP). An SRP basically consists of a template that generates one or more requirements, and some information to identify its need in a particular project, and how it may be tailored to this project. The main benefits of using SRPs may be summarized as: 1) more effective requirement elicitation (requirements are not built from scratch; a process guides the engineer by giving advices, suggesting information, ...); 2) improved quality and consistency of requirements documents (by using a uniform style); 3) improved requirements management (e.g., clear traceability from requirements to goals).
ISBN: 1860-2770
URI: http://hdl.handle.net/2117/16874
Versió de l'editor: http://www.icb.uni-due.de/researchreports/reportliste/
Apareix a les col·leccions:Altres. Enviament des de DRAC
GESSI - Software Engineering for Information Systems Group. Ponències/Comunicacions de congressos
Departament d'Enginyeria de Serveis i Sistemes d'Informació. Ponències/Comunicacions de congressos

Stats Mostra les estadístiques d'aquest ítem

SFX Query

Aquest ítem (excepte textos i imatges no creats per l'autor) està subjecte a una llicència de Creative Commons Llicència Creative Commons
Creative Commons


Valid XHTML 1.0! Programari DSpace Copyright © 2002-2004 MIT and Hewlett-Packard Comentaris
Universitat Politècnica de Catalunya. Servei de Biblioteques, Publicacions i Arxius