scispace - formally typeset
Proceedings ArticleDOI

QuOnt: an ontology for the reuse of quality criteria

TLDR
This work presents an ontology that supports the reuse of quality criteria in the input stage of software product audits and shows that the same quality criteria can be applied to different software products.
Abstract
Software product audits are knowledge-intensive tasks in which architectural knowledge plays a pivotal role. In the input stage of a software product audit, quality criteria are selected to which the software product should conform. These quality criteria resemble architectural tactics and can be viewed as a definition of the Soll-architecture of the product. Like tactics, the same quality criteria can be applied to different software products. However, there are currently no models that support the codification of quality criteria as reusable assets. In this work, we present an ontology that supports the reuse of quality criteria in the input stage of software product audits.

read more

Content maybe subject to copyright    Report

Citations
More filters
Journal ArticleDOI

A Reference Architecture for provisioning of Tools as a Service

TL;DR: A Reference Architecture for designing cloud-based Tools as a service SPACE (TSPACE), which can provision a bundled suite of tools following the Software as a Service (SaaS) model, is presented.
Proceedings ArticleDOI

SE-EQUAM - An Evolvable Quality Metamodel

TL;DR: This research introduces SE-EQUAM a novel ontology-based quality assessment metamodel that was designed from ground up to support model reuse and evolvability and presents a case study that illustrates the reusability and evlvability of this approach.
Proceedings Article

An Ontology Model to Support the Automated Evaluation of Software

TL;DR: An extensible ontology model for representing software evaluations and evaluation campaigns, i.e., worldwide activities where a group of tools is evaluated according to a certain evaluation specification using common test data is presented.
Book ChapterDOI

Quality concerns in large-scale and complex software-intensive systems

TL;DR: A conceptual model for software quality framework is provided together with the current approaches for SQA in this paper, and some of the identified challenges and future challenges regarding SQA are discussed.
Journal ArticleDOI

Knowledge sharing and discovery across heterogeneous research infrastructures

TL;DR: The development process of a knowledge management system for ENVironmental Research Infrastructures, which are crucial pillars for environmental scientists in their quest for understanding and interpreting the complex Earth System are presented.
References
More filters
Book

Software Architecture in Practice

TL;DR: This second edition of this book reflects the new developments in the field and new understanding of the important underpinnings of software architecture with new case studies and the new understanding both through new chapters and through additions to and elaboration of the existing chapters.

An Ontology of Architectural Design Decisions in Software-Intensive Systems

TL;DR: A possible ontology of architectural design decisions, their attributes and relationships, for complex, software-intensive systems, is presented.
ReportDOI

Deriving Architectural Tactics: A Step Toward Methodical Architectural Design

TL;DR: Initial evidence is provided that there is, in fact, a systematic relationship between general scenarios, concrete scenarios, architectural tactics, and design fragments that satisfy the scenario.
Book ChapterDOI

Architectural knowledge: getting to the core

TL;DR: In this article, a model of architectural knowledge is proposed to characterize the use of the architectural knowledge in four different organizations, and four perspectives on architectural knowledge management are identified and adjusted to better align theory with practice.
Journal ArticleDOI

Controversy Corner: On the similarity between requirements and architecture

TL;DR: It is argued that there is no fundamental distinction between architectural decisions and architecturally significant requirements and this new view on the intrinsic relation between architecture and requirements allows us to identify areas in which closer cooperation between the Architecture and requirements engineering communities would bring advantages for both.
Related Papers (5)