REquirements, Aspects and Software Quality: the REASQ model.

Castillo, Isi; Losavio, Francisca; Matteo, Alfredo; Bøegh, Jørgen

doi:10.5381/jot.2010.9.4.a4

Cited by 15 publications

(9 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The case study proposed is based on a simplified version of an online toy store (an e-commerce web-based application). This case is introduced in previous study (Castillo, Losavio, Matteo, & Boegh, 2010) with aim to obtain a common terminology to develop models associated with requirements, aspects, and quality of a software product. Table 6) ExpiredSession Direct metric (see Table 7) [0,1] MinMaxRange…”

Section: Case Study: Instantiating the Final Ontologymentioning

confidence: 99%

An ontology to document a quality scheme specification of a software product

2017

View full text Add to dashboard Cite

Pressman's (2010) definition of software quality is the conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software. The achievement of quality is a complex activity that is related with the process quality and product quality. However, still, it is not clear how product quality should apply in the development process. Frequently, the development team does not know what characteristics influence a specific entity and how these characteristics compose the quality of the product. This lack of knowledge reflects the need to define some document that serve as a valid quality specification that should be evaluated along the development process. This contribution addresses this need by introducing an ontology for document a quality scheme based on the product quality model of ISO/IEC 25010. The proposal follows this model with aims to clarify the properties that are normally present in a product and its meaning. The ontology incorporates the metric concept to represent the way in which quality should be measure. The ontology was implemented using Protégé, and it was evaluated using a set of metrics that estimate the required structural characteristics.

show abstract

Section: Case Study: Instantiating the Final Ontologymentioning

confidence: 99%

An ontology to document a quality scheme specification of a software product

2017

View full text Add to dashboard Cite

show abstract

“…ISO developed a quality model that was further known as ISO/IEC 9126 Model [10] proposed a conceptual quality model to elucidate the AOSD evolving technologies like aspect, composition concern, and quality requirement for software system [13]. REASQ Model is another name of this model which integrates ISO/IEC 9126 Model and ISO/IEC 25030 model in addition to articulated in UML.…”

Section: Related Workmentioning

confidence: 99%

A Framework for Assessing the Software Reusability using Fuzzy Logic Approach for Aspect Oriented Software

Singh¹,

Sangwan²,

Singh³

et al. 2015

IJITCS

View full text Add to dashboard Cite

Software reusability is very important and crucial attribute to evaluate the system software. Due to incremental growth of software development, the software reusability comes under attention of many researcher and practitioner. It is pretty easier to reuse the software than developing the new software. Software reusability reduces the development time, cost and effort of software product. Software reusability define the depth to which a module can be reused again with very little or no modification. However the prediction of this quality attribute is cumbersome process. Aspect oriented software development is new approach that introduce the concerns to overcome the issues with modular programming and object oriented programming. However many researcher worked on accessing the software reusability on object oriented system but the software reusability of aspect oriented system is not completely explored. This paper explores the various metric that affects the reusability of aspect oriented software and estimate it using fuzzy logic approach.

show abstract

“…En esta disciplina se propone la utilización de una plantilla que permita identificar y relacionar los concerns de calidad de cada descripción de requisitos (ver tabla 1). El análisis e identificación propuesto en AOQuaRE comprende la clasificación y organización de los requisitos iniciales siguiendo el estándar de calidad sobre categorización de requisitos ISO/IEC 25030 [10], también de la serie SquaRE y la terminología propuesta en el modelo REASQ [3]; esta categorización propuesta se hace en términos de "concerns" relacionando y organizando tales concerns en grupos coherentes (concerns funcionales, concerns de calidad). Adicionalmente, el análisis incluye la asignación de prioridades y negociación de los concerns identificados.…”

Section: Ii1 Disciplina: Análisis E Identificación De Concernsunclassified

“…El artefacto resultante facilitará la creación de un modelo de casos de uso que incluye concerns de calidad, y por ende la identificación posterior de los concerns transversales, futuros aspectos candidatos. En esta tarea se sugiere tomar cada una de las descripciones iniciales de los requisitos y seguir la categorización de concerns del estándar ISO/IEC 25030 [10] y los términos del Modelo REASQ [3], donde los concerns de calidad son clasificados dentro de la taxonomía de los requisitos de propiedades inherentes, obteniéndose así una lista de los concerns de calidad. Una vez identificado el concern de calidad se expresa en términos de calidad del producto, siguiendo el nuevo estándar ISO/IEC 25010 [11] para el modelo de calidad del producto, asociándole la característica de calidad que corresponda.…”

Section: 2 Identificar Concerns De Calidadunclassified

A process for aspect-oriented quality requirements engineering: AOQuaRE

Castillo

Losavio

Matteo

2013

2013 XXXIX Latin American Computing Conference (CLEI)

Self Cite

View full text Add to dashboard Cite

The comprehension and correct specification of requirements increase with the complexity of present software systems, particularly if they have to respond to requirements going beyond the range of the main system functionality and that must be taken into account early during the development process. The Scientific community focuses now on the requirements engineering discipline, for the importance of nonfunctional or quality requirements with direct impact on the accomplishment of the main system's functionalities. This work models an aspect-oriented quality requirements engineering process (AOQuaRE), based on the treatment of non-functional requirements scattered and/or entangled among the functionalities of the system (crosscutting concerns), from the early steps of the development process.An important contribution of this work is the specification of quality requirements by the new standard ISO/IEC 25010 for software product quality.Keywords-crosscutting concern, aspect, software quality, AOSD, SQuaRE, AOQuaRE. I. INTRODUCCIÓNUna de las mejores prácticas de la ingeniería del software es seguir un proceso de desarrollo maduro. Así, la metodología del proceso de desarrollo ha evolucionado buscando mejoras para garantizar la calidad del producto de software resultante. Sin embargo, como describir y garantizar un producto de software de calidad de acuerdo a la madurez del proceso, es una actividad aún poco clara. Los métodos de desarrollo de software existentes son dirigidos más por la especificación de la funcionalidad del sistema que por la consideración de sus aspectos no funcionales. En general, estos aspectos no funcionales son considerados en etapas posteriores del desarrollo, contribuyendo con el enmarañamiento y la dispersión del código final, contradiciendo la propiedad de flexibilidad a cambios del desarrollo orientado a objetos.Por otra parte, la comprensión de los requisitos y la importancia de su correcta especificación, se incrementa drásticamente con la complejidad de los sistemas de software, particularmente si éstos tienen que responder a exigencias que van más allá del alcance de sus funcionalidades principales tales como interoperabilidad, adaptabilidad, disponibilidad, seguridad, entre otros. Estas exigencias pueden estar asociadas a las funcionalidades o no, pero deben ser consideradas oportunamente por los profesionales del software en el desarrollo de sus aplicaciones y deben dirigir la atención de la comunidad de investigadores hacia la disciplina de la ingeniería de requisitos, en particular hacia los requisitos no funcionales, los cuales tienen un impacto directo en el cumplimiento de la funcionalidad principal o servicio ofrecido por los componentes del software. Estos requisitos no funcionales asociados generalmente a las propiedades de calidad del software y que en muchos casos se diseminan y entrecruzan entre las funcionalidades principales (requisitos funcionales), dificultando su entendimiento, mantenimiento y reutilización, son reconocidos generalmente como incumbencias o concerns ...

show abstract

REquirements, Aspects and Software Quality: the REASQ model.

Cited by 15 publications

References 13 publications

An ontology to document a quality scheme specification of a software product

An ontology to document a quality scheme specification of a software product

A Framework for Assessing the Software Reusability using Fuzzy Logic Approach for Aspect Oriented Software

A process for aspect-oriented quality requirements engineering: AOQuaRE

Contact Info

Product

Resources

About