2018
DOI: 10.1007/s10115-018-1182-1
|View full text |Cite
|
Sign up to set email alerts
|

A fuzzy ontology-based approach for tool-supported decision making in architectural design

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0
1

Year Published

2018
2018
2022
2022

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 30 publications
(16 citation statements)
references
References 45 publications
0
15
0
1
Order By: Relevance
“…An architecture for the IoT process management consists of seven core components which can be used to describe the core components of an ECM. These components of an EC architecture include; goal manager, adaptation manager, context manager, enactment engine, business rules, domain ontology and system KB [61,[63][64][65]. The responsibilities of these components are explained subsequently.…”
Section: Architectural Description Of An Ec Process Managementmentioning
confidence: 99%
“…An architecture for the IoT process management consists of seven core components which can be used to describe the core components of an ECM. These components of an EC architecture include; goal manager, adaptation manager, context manager, enactment engine, business rules, domain ontology and system KB [61,[63][64][65]. The responsibilities of these components are explained subsequently.…”
Section: Architectural Description Of An Ec Process Managementmentioning
confidence: 99%
“…In [34], authors use FOs to manage fuzzy roles in risk-based environments. In [35], a DSS that uses a fuzzy OWL 2 ontology is presented. In [36], description logics are used in order to define the multi-criteria group decision making problem.…”
Section: Fuzzy Ontologiesmentioning
confidence: 99%
“…• Add categories hardware-software requirements and requirements for support functioning from the proposed classification scheme. Di Noia et al [26] elaborate the application of the fuzzy logic to non-functional requests. The proposed classification scheme provides the opportunity for the selection of several requests for one functionality.…”
Section: Integrationmentioning
confidence: 99%
“…BABOK classification scheme of requests incorporates the following requests: business, stakeholder, product (functional and non‐functional) and transitional requirements. The authors propose the following integration of request categories into the BABOK classification scheme: Business category expands with business and organisational requests from the proposed classification scheme. A sub‐category of non‐functional requests of the solutions requirement category expands with the category security requirements and requests from the sub‐category general PKI services and components of the component PKI Components and services requirement. Add categories hardware–software requirements and requirements for support functioning from the proposed classification scheme. Di Noia et al [26] elaborate the application of the fuzzy logic to non‐functional requests. The proposed classification scheme provides the opportunity for the selection of several requests for one functionality.…”
Section: Application Of the Proposed Classification Scheme And Its mentioning
confidence: 99%