Dealing with Completeness in Requirements Engineering

The Requirements Engineering (RE) goal is to sys-tematize the process of requirements construction and management (Maculay, 1993; Reubenstein & Waters, 1991; Maté & Silva, 2005) along with the creation of a compromise among clients and users with develop-ers, since both human groups mu...

Descripción completa

Guardado en:
Detalles Bibliográficos
Autores principales: Hadad, Graciela D. S., Litvak, Claudia S., Doorn, Jorge H., Ridao, Marcela
Formato: Artículo
Lenguaje:Inglés
Publicado: Universidad de Belgrano - Facultad de Ingeniería y Tecnología Informática - Proyectos de Investigación 2015
Materias:
Acceso en línea:http://repositorio.ub.edu.ar/handle/123456789/4860
Aporte de:
id I36-R142-123456789-4860
record_format dspace
institution Universidad de Belgrano
institution_str I-36
repository_str R-142
collection Repositorio Institucional - Universidad de Belgrano (UB)
language Inglés
topic Completeness
Requirements Engineering
Requisitos de Ingeniería
lo completo
Ingeniería
engineering
spellingShingle Completeness
Requirements Engineering
Requisitos de Ingeniería
lo completo
Ingeniería
engineering
Hadad, Graciela D. S.
Litvak, Claudia S.
Doorn, Jorge H.
Ridao, Marcela
Dealing with Completeness in Requirements Engineering
topic_facet Completeness
Requirements Engineering
Requisitos de Ingeniería
lo completo
Ingeniería
engineering
description The Requirements Engineering (RE) goal is to sys-tematize the process of requirements construction and management (Maculay, 1993; Reubenstein & Waters, 1991; Maté & Silva, 2005) along with the creation of a compromise among clients and users with develop-ers, since both human groups must participate and collaborate together. To accomplish such tasks, the requirements engineers should understand and par-ticipate in the definition of the context of use for the software system to be developed. The requirements engineers usually ignore totally or partially both, the current and the foreseen future context of use. The latter must be conceived having as a resource the new tool: the system software itself. Frequently, nobody knows in detail such future context of use. To be able to participate in the definition of the future business process, the requirements engineers must understand the current business process in advance. Therefore, the Requirements Engineering process involves, as the first step, elicitation and modeling of the current business process and later, definition and modeling of the future business process. Both models have different purposes. The first one is used as a help for understanding the current business process and as a tool to validate with clients and users such understanding. The second one is used as a help for the planning of the future busi-ness process, to validate such plans with the clients and users, to specify the software requirements and to give an environment reference for software designers. The Requirements Engineering process consists of three main activities: elicitation, modeling, and analysis of the application domain (Kotonya & Som-merville, 1998; Sommerville & Sawyer, 1997). Analysis includes the sub-activities of verification, validation and negotiation. The difficulties that requirements engineers must face to understand and elicit the clients and users’ necessities are widely known. The more complex the application domain, the more difficult the definition or construction of software requirements becomes. Many times, requirements engineers must become themselves problem domain experts during the acquisition of knowledge about the application domain. Concurrently, Requirements Management deals with the changes in the existent requirements and the irruption of new ones (Kotonya & Sommerville, 1998; Sawyer & Kotonya, 2004)
format Article
author Hadad, Graciela D. S.
Litvak, Claudia S.
Doorn, Jorge H.
Ridao, Marcela
author_facet Hadad, Graciela D. S.
Litvak, Claudia S.
Doorn, Jorge H.
Ridao, Marcela
author_sort Hadad, Graciela D. S.
title Dealing with Completeness in Requirements Engineering
title_short Dealing with Completeness in Requirements Engineering
title_full Dealing with Completeness in Requirements Engineering
title_fullStr Dealing with Completeness in Requirements Engineering
title_full_unstemmed Dealing with Completeness in Requirements Engineering
title_sort dealing with completeness in requirements engineering
publisher Universidad de Belgrano - Facultad de Ingeniería y Tecnología Informática - Proyectos de Investigación
publishDate 2015
url http://repositorio.ub.edu.ar/handle/123456789/4860
work_keys_str_mv AT hadadgracielads dealingwithcompletenessinrequirementsengineering
AT litvakclaudias dealingwithcompletenessinrequirementsengineering
AT doornjorgeh dealingwithcompletenessinrequirementsengineering
AT ridaomarcela dealingwithcompletenessinrequirementsengineering
bdutipo_str Repositorios
_version_ 1764820529315840003