2017
DOI: 10.1002/inst.12160
|View full text |Cite
|
Sign up to set email alerts
|

An Initial Ontology for System Qualities

Abstract: This paper presents an initial ontology for reasoning about a system's System Qualities (SQs), ilities, or non‐functional requirements (reliability, usability, affordability, and more). The need for such ontology is based primarily on two factors. One is the importance of getting the SQs sufficiently well defined such that the system's definition, development, and evolution result in a satisfactory balance of SQ values for the system's success‐critical stakeholders, given the frequent system shortfalls and ove… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
12
0

Year Published

2018
2018
2023
2023

Publication Types

Select...
4
1

Relationship

0
5

Authors

Journals

citations
Cited by 10 publications
(12 citation statements)
references
References 24 publications
0
12
0
Order By: Relevance
“…This helped everyone in the project better understand the product, their individual role in bringing the product to life, and where in the lifecycle that product currently resided. This understanding included not only the functional aspects of the product but also the non-functional aspects which support the quality attributes of that product (Boehm and Kukreja 2017). Further, the maturity expectations (or, more precisely in this case, the expectations of product immaturity) helped define phases where the agile developers could have extensive freedom in terms of design flexibility and creativity.…”
Section: Resultsmentioning
confidence: 99%
“…This helped everyone in the project better understand the product, their individual role in bringing the product to life, and where in the lifecycle that product currently resided. This understanding included not only the functional aspects of the product but also the non-functional aspects which support the quality attributes of that product (Boehm and Kukreja 2017). Further, the maturity expectations (or, more precisely in this case, the expectations of product immaturity) helped define phases where the agile developers could have extensive freedom in terms of design flexibility and creativity.…”
Section: Resultsmentioning
confidence: 99%
“…Many further examples of such concepts have been discussed in the engineering research literature, for example resilience, sustainability, adaptiveness, recyclability, maintainability, upgradability, manufacturability, affordability, scalability, survivability, versatility, interoperability, modularity, flexibility, and agility (Boehm & Kukreja, ; Madni, ; Adam M. Ross & Rhodes, ; Watson & Griffin, ; Watson et al, ). We note that most of these attibutes are subsumed under the general rubric of ilities, but that this may be due to insuffiencient attention being paid to other kinds of systemic virtues.…”
Section: What Makes a Design Good?mentioning
confidence: 99%
“…This was immediately problematic, as the terms as used in practice do not have consistent definitions. This issue is well known and has been a subject of research in recent times (Boehm & Kukreja, ; Dou, Wang, Tang, Ross, & Sullivan, ; Adam M. Ross & Rhodes, , ). Our view is that progress in this area will be crucial for building a theory of design elegance that strongly exhibits the theoretical virtues.…”
Section: In Search Of Principles and Laws For Design Elegancementioning
confidence: 99%
See 2 more Smart Citations