FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES

Quality models for software architecture are taxonomies of quality attributes, commonly used to specify and evaluate nonfunctional requirements. Most quality models offer a two-level approach, distinguishing externally observable and internally measurable attributes, yielding stakeholder-specific co...

Descripción completa

Guardado en:

Detalles Bibliográficos
Autor principal:	Astudillo,Hernán
Lenguaje:	English
Publicado:	Universidad de Tarapacá. Facultad de Ingeniería 2005
Materias:	Software architecture software specification quality evaluation testing ontology computation versus design
Acceso en línea:	http://www.scielo.cl/scielo.php?script=sci_arttext&pid=S0718-13372005000100008
Etiquetas:	Agregar Etiqueta Sin Etiquetas, Sea el primero en etiquetar este registro!

id	oai:scielo:S0718-13372005000100008
record_format	dspace
spelling	oai:scielo:S0718-133720050001000082005-06-13FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURESAstudillo,Hernán Software architecture software specification quality evaluation testing ontology computation versus design Quality models for software architecture are taxonomies of quality attributes, commonly used to specify and evaluate nonfunctional requirements. Most quality models offer a two-level approach, distinguishing externally observable and internally measurable attributes, yielding stakeholder-specific composite quality criteria. Much effort is devoted to determine which internal attributes influence which external ones, and most models stick to a two-level hierarchy. This paper argues that this apparent dual order obscures the fact that requirements are made by different stakeholder about different subjects, and the word "architecture" means different things to each of them: the organization of a system, a description of such organization, and the process of elaborating such descriptions. The proposed scheme organizes architecture attributes according to five ontological (descriptive) levels, each of them with different concerns, types of users and available measurement techniques: computations, deployables (binaries/configurations), software (texts), specifications (of architecture and/or design), and architecture process. Finally, levels and stakeholders are related to specific architecture views.info:eu-repo/semantics/openAccessUniversidad de Tarapacá. Facultad de IngenieríaRevista Facultad de Ingeniería - Universidad de Tarapacá v.13 n.1 20052005-04-01text/htmlhttp://www.scielo.cl/scielo.php?script=sci_arttext&pid=S0718-13372005000100008en10.4067/S0718-13372005000100008
institution	Scielo Chile
collection	Scielo Chile
language	English
topic	Software architecture software specification quality evaluation testing ontology computation versus design
spellingShingle	Software architecture software specification quality evaluation testing ontology computation versus design Astudillo,Hernán FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
description	Quality models for software architecture are taxonomies of quality attributes, commonly used to specify and evaluate nonfunctional requirements. Most quality models offer a two-level approach, distinguishing externally observable and internally measurable attributes, yielding stakeholder-specific composite quality criteria. Much effort is devoted to determine which internal attributes influence which external ones, and most models stick to a two-level hierarchy. This paper argues that this apparent dual order obscures the fact that requirements are made by different stakeholder about different subjects, and the word "architecture" means different things to each of them: the organization of a system, a description of such organization, and the process of elaborating such descriptions. The proposed scheme organizes architecture attributes according to five ontological (descriptive) levels, each of them with different concerns, types of users and available measurement techniques: computations, deployables (binaries/configurations), software (texts), specifications (of architecture and/or design), and architecture process. Finally, levels and stakeholders are related to specific architecture views.
author	Astudillo,Hernán
author_facet	Astudillo,Hernán
author_sort	Astudillo,Hernán
title	FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
title_short	FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
title_full	FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
title_fullStr	FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
title_full_unstemmed	FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES
title_sort	five ontological levels to describe and evaluate software architectures
publisher	Universidad de Tarapacá. Facultad de Ingeniería
publishDate	2005
url	http://www.scielo.cl/scielo.php?script=sci_arttext&pid=S0718-13372005000100008
work_keys_str_mv	AT astudillohernan fiveontologicallevelstodescribeandevaluatesoftwarearchitectures
_version_	1714202097499504640

FIVE ONTOLOGICAL LEVELS TO DESCRIBE AND EVALUATE SOFTWARE ARCHITECTURES

Ejemplares similares