A collaborative approach to describe the domain language through the language extended lexicon
- Autores
- Antonelli, Leandro; Rossi, Gustavo Héctor; Oliveros, Alejandro
- Año de publicación
- 2016
- Idioma
- inglés
- Tipo de recurso
- artículo
- Estado
- versión publicada
- Descripción
- Software development is a succession of descriptions in different languages in which every description is based on a previous one. Since the requirements specification is one of the first descriptions, it is important to begin software development with requirements that are as correct and as complete as possible. Although some literature holds the belief that correctness and completeness are two attributes that requirements specifications must satisfy, we know that these attributes are very difficult to meet. However, we have to find ways to diminish the level of incompleteness and deal with the possible conflicts that do arise in the requirements context. Defining the domain language before specifying the requirements is a way of coping with these problems. Nowadays, software systems involve many stakeholders and it is hard to engage all of them to produce a domain language specification. We rely on collaboration to foster the involvement and cooperation of the stakeholders, thus they are able to explore the differences constructively and provide a common understanding of the domain language beyond their own limited views. In this paper, we propose a strategy to capture the domain language in a collaborative way using the Language Extended Lexicon and we show a validation of the proposed strategy.
Fil: Antonelli, Leandro. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina
Fil: Rossi, Gustavo Héctor. Consejo Nacional de Investigaciones Científicas y Técnicas. Centro Científico Tecnológico Conicet - La Plata; Argentina. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina
Fil: Oliveros, Alejandro. Universidad Nacional de Tres de Febrero; Argentina. Universidad Argentina de la Empresa; Argentina - Materia
-
COLLABORATION
DOMAIN ANALYSIS
LANGUAGE EXTENDED LEXICON - Nivel de accesibilidad
- acceso abierto
- Condiciones de uso
- https://creativecommons.org/licenses/by-nc-nd/2.5/ar/
- Repositorio
- Institución
- Consejo Nacional de Investigaciones Científicas y Técnicas
- OAI Identificador
- oai:ri.conicet.gov.ar:11336/78146
Ver los metadatos del registro completo
id |
CONICETDig_e060cd7b7b0e04bdeea1c7de0ec50361 |
---|---|
oai_identifier_str |
oai:ri.conicet.gov.ar:11336/78146 |
network_acronym_str |
CONICETDig |
repository_id_str |
3498 |
network_name_str |
CONICET Digital (CONICET) |
spelling |
A collaborative approach to describe the domain language through the language extended lexiconAntonelli, LeandroRossi, Gustavo HéctorOliveros, AlejandroCOLLABORATIONDOMAIN ANALYSISLANGUAGE EXTENDED LEXICONhttps://purl.org/becyt/ford/1.2https://purl.org/becyt/ford/1Software development is a succession of descriptions in different languages in which every description is based on a previous one. Since the requirements specification is one of the first descriptions, it is important to begin software development with requirements that are as correct and as complete as possible. Although some literature holds the belief that correctness and completeness are two attributes that requirements specifications must satisfy, we know that these attributes are very difficult to meet. However, we have to find ways to diminish the level of incompleteness and deal with the possible conflicts that do arise in the requirements context. Defining the domain language before specifying the requirements is a way of coping with these problems. Nowadays, software systems involve many stakeholders and it is hard to engage all of them to produce a domain language specification. We rely on collaboration to foster the involvement and cooperation of the stakeholders, thus they are able to explore the differences constructively and provide a common understanding of the domain language beyond their own limited views. In this paper, we propose a strategy to capture the domain language in a collaborative way using the Language Extended Lexicon and we show a validation of the proposed strategy.Fil: Antonelli, Leandro. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; ArgentinaFil: Rossi, Gustavo Héctor. Consejo Nacional de Investigaciones Científicas y Técnicas. Centro Científico Tecnológico Conicet - La Plata; Argentina. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; ArgentinaFil: Oliveros, Alejandro. Universidad Nacional de Tres de Febrero; Argentina. Universidad Argentina de la Empresa; ArgentinaAssociation Internationale pour les Technologies Objets2016-06info:eu-repo/semantics/articleinfo:eu-repo/semantics/publishedVersionhttp://purl.org/coar/resource_type/c_6501info:ar-repo/semantics/articuloapplication/pdfapplication/pdfhttp://hdl.handle.net/11336/78146Antonelli, Leandro; Rossi, Gustavo Héctor; Oliveros, Alejandro; A collaborative approach to describe the domain language through the language extended lexicon; Association Internationale pour les Technologies Objets; Journal of Object Technology; 15; 3; 6-2016; 1-271660-1769CONICET DigitalCONICETenginfo:eu-repo/semantics/altIdentifier/url/http://www.jot.fm/contents/issue_2016_03/article3.htmlinfo:eu-repo/semantics/altIdentifier/doi/10.5381/jot.2016.15.3.a3info:eu-repo/semantics/openAccesshttps://creativecommons.org/licenses/by-nc-nd/2.5/ar/reponame:CONICET Digital (CONICET)instname:Consejo Nacional de Investigaciones Científicas y Técnicas2025-09-03T09:58:46Zoai:ri.conicet.gov.ar:11336/78146instacron:CONICETInstitucionalhttp://ri.conicet.gov.ar/Organismo científico-tecnológicoNo correspondehttp://ri.conicet.gov.ar/oai/requestdasensio@conicet.gov.ar; lcarlino@conicet.gov.arArgentinaNo correspondeNo correspondeNo correspondeopendoar:34982025-09-03 09:58:46.34CONICET Digital (CONICET) - Consejo Nacional de Investigaciones Científicas y Técnicasfalse |
dc.title.none.fl_str_mv |
A collaborative approach to describe the domain language through the language extended lexicon |
title |
A collaborative approach to describe the domain language through the language extended lexicon |
spellingShingle |
A collaborative approach to describe the domain language through the language extended lexicon Antonelli, Leandro COLLABORATION DOMAIN ANALYSIS LANGUAGE EXTENDED LEXICON |
title_short |
A collaborative approach to describe the domain language through the language extended lexicon |
title_full |
A collaborative approach to describe the domain language through the language extended lexicon |
title_fullStr |
A collaborative approach to describe the domain language through the language extended lexicon |
title_full_unstemmed |
A collaborative approach to describe the domain language through the language extended lexicon |
title_sort |
A collaborative approach to describe the domain language through the language extended lexicon |
dc.creator.none.fl_str_mv |
Antonelli, Leandro Rossi, Gustavo Héctor Oliveros, Alejandro |
author |
Antonelli, Leandro |
author_facet |
Antonelli, Leandro Rossi, Gustavo Héctor Oliveros, Alejandro |
author_role |
author |
author2 |
Rossi, Gustavo Héctor Oliveros, Alejandro |
author2_role |
author author |
dc.subject.none.fl_str_mv |
COLLABORATION DOMAIN ANALYSIS LANGUAGE EXTENDED LEXICON |
topic |
COLLABORATION DOMAIN ANALYSIS LANGUAGE EXTENDED LEXICON |
purl_subject.fl_str_mv |
https://purl.org/becyt/ford/1.2 https://purl.org/becyt/ford/1 |
dc.description.none.fl_txt_mv |
Software development is a succession of descriptions in different languages in which every description is based on a previous one. Since the requirements specification is one of the first descriptions, it is important to begin software development with requirements that are as correct and as complete as possible. Although some literature holds the belief that correctness and completeness are two attributes that requirements specifications must satisfy, we know that these attributes are very difficult to meet. However, we have to find ways to diminish the level of incompleteness and deal with the possible conflicts that do arise in the requirements context. Defining the domain language before specifying the requirements is a way of coping with these problems. Nowadays, software systems involve many stakeholders and it is hard to engage all of them to produce a domain language specification. We rely on collaboration to foster the involvement and cooperation of the stakeholders, thus they are able to explore the differences constructively and provide a common understanding of the domain language beyond their own limited views. In this paper, we propose a strategy to capture the domain language in a collaborative way using the Language Extended Lexicon and we show a validation of the proposed strategy. Fil: Antonelli, Leandro. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina Fil: Rossi, Gustavo Héctor. Consejo Nacional de Investigaciones Científicas y Técnicas. Centro Científico Tecnológico Conicet - La Plata; Argentina. Universidad Nacional de La Plata. Facultad de Informática. Laboratorio de Investigación y Formación en Informática Avanzada; Argentina Fil: Oliveros, Alejandro. Universidad Nacional de Tres de Febrero; Argentina. Universidad Argentina de la Empresa; Argentina |
description |
Software development is a succession of descriptions in different languages in which every description is based on a previous one. Since the requirements specification is one of the first descriptions, it is important to begin software development with requirements that are as correct and as complete as possible. Although some literature holds the belief that correctness and completeness are two attributes that requirements specifications must satisfy, we know that these attributes are very difficult to meet. However, we have to find ways to diminish the level of incompleteness and deal with the possible conflicts that do arise in the requirements context. Defining the domain language before specifying the requirements is a way of coping with these problems. Nowadays, software systems involve many stakeholders and it is hard to engage all of them to produce a domain language specification. We rely on collaboration to foster the involvement and cooperation of the stakeholders, thus they are able to explore the differences constructively and provide a common understanding of the domain language beyond their own limited views. In this paper, we propose a strategy to capture the domain language in a collaborative way using the Language Extended Lexicon and we show a validation of the proposed strategy. |
publishDate |
2016 |
dc.date.none.fl_str_mv |
2016-06 |
dc.type.none.fl_str_mv |
info:eu-repo/semantics/article info:eu-repo/semantics/publishedVersion http://purl.org/coar/resource_type/c_6501 info:ar-repo/semantics/articulo |
format |
article |
status_str |
publishedVersion |
dc.identifier.none.fl_str_mv |
http://hdl.handle.net/11336/78146 Antonelli, Leandro; Rossi, Gustavo Héctor; Oliveros, Alejandro; A collaborative approach to describe the domain language through the language extended lexicon; Association Internationale pour les Technologies Objets; Journal of Object Technology; 15; 3; 6-2016; 1-27 1660-1769 CONICET Digital CONICET |
url |
http://hdl.handle.net/11336/78146 |
identifier_str_mv |
Antonelli, Leandro; Rossi, Gustavo Héctor; Oliveros, Alejandro; A collaborative approach to describe the domain language through the language extended lexicon; Association Internationale pour les Technologies Objets; Journal of Object Technology; 15; 3; 6-2016; 1-27 1660-1769 CONICET Digital CONICET |
dc.language.none.fl_str_mv |
eng |
language |
eng |
dc.relation.none.fl_str_mv |
info:eu-repo/semantics/altIdentifier/url/http://www.jot.fm/contents/issue_2016_03/article3.html info:eu-repo/semantics/altIdentifier/doi/10.5381/jot.2016.15.3.a3 |
dc.rights.none.fl_str_mv |
info:eu-repo/semantics/openAccess https://creativecommons.org/licenses/by-nc-nd/2.5/ar/ |
eu_rights_str_mv |
openAccess |
rights_invalid_str_mv |
https://creativecommons.org/licenses/by-nc-nd/2.5/ar/ |
dc.format.none.fl_str_mv |
application/pdf application/pdf |
dc.publisher.none.fl_str_mv |
Association Internationale pour les Technologies Objets |
publisher.none.fl_str_mv |
Association Internationale pour les Technologies Objets |
dc.source.none.fl_str_mv |
reponame:CONICET Digital (CONICET) instname:Consejo Nacional de Investigaciones Científicas y Técnicas |
reponame_str |
CONICET Digital (CONICET) |
collection |
CONICET Digital (CONICET) |
instname_str |
Consejo Nacional de Investigaciones Científicas y Técnicas |
repository.name.fl_str_mv |
CONICET Digital (CONICET) - Consejo Nacional de Investigaciones Científicas y Técnicas |
repository.mail.fl_str_mv |
dasensio@conicet.gov.ar; lcarlino@conicet.gov.ar |
_version_ |
1842269540121051136 |
score |
13.13397 |