Interested in improving your requirements engineering process? Try requirement patterns!
Visualitza/Obre
Estadístiques de LA Referencia / Recolecta
Inclou dades d'ús des de 2022
Cita com:
hdl:2117/16874
Tipus de documentText en actes de congrés
Data publicació2011
EditorDuEPublico, University Duisburg-Essen
Condicions d'accésAccés obert
Llevat que s'hi indiqui el contrari, els
continguts d'aquesta obra estan subjectes a la llicència de Creative Commons
:
Reconeixement-NoComercial-SenseObraDerivada 3.0 Espanya
Abstract
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).
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. "17th International Working Conference on Requirements Engineering: Foundation for Software Quality (REFSQ 2011): 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 (ICB-Research Report No. 44, September 2011)". DuEPublico, University Duisburg-Essen, 2011, p. 161-162.
ISBN1866-5101
Versió de l'editorhttp://www.icb.uni-due.de/researchreports/reportliste/
Col·leccions
- GESSI - Grup d'Enginyeria del Software i dels Serveis - Ponències/Comunicacions de congressos [197]
- inSSIDE - integrated Software, Service, Information and Data Engineering - Ponències/Comunicacions de congressos [332]
- Departament d'Enginyeria de Serveis i Sistemes d'Informació - Ponències/Comunicacions de congressos [529]
Fitxers | Descripció | Mida | Format | Visualitza |
---|---|---|---|---|
refsq11ef-franch-et-al-camera-ready.pdf | 84,21Kb | Visualitza/Obre |