CDNFRE: Conflict detector in non-functional requirement evolution based on ontologies

Liu, Chi-Lun

doi:10.1016/j.csi.2016.03.002

Cited by 18 publications

(11 citation statements)

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Dealing with NFRs is a major challenge in software development [1]. Analyzing conflicts in NFRs is a major task in large software systems development projects [6]. Throughout the requirement engineering process, when improving the quality of software, selecting effective strategies for every NFR is an essential activity in requirements engineering.…”

Section: Discussionmentioning

confidence: 99%

“…Then based on Chen and Sanguansat's fuzzy ranking method [27], calculating the areas Area − iL , Area − iR , Area + iL , and Area + iL on the negative side and the positive side in Eqs. (4), (5), (6), and (7), respectively. They denote the trapezoidal areas from the membership function curves of f L N i and f R N i , which are defined in Eqs.…”

Section: A Nfrs Obtaining and Assessmentmentioning

confidence: 99%

“…Neglecting NFRs during software development is a top-ten risk, and errors in considering them are the most expensive and difficult to correct [4], [5]. However, NFRs are often presented chaotically without a common standard and without sufficient analysis [6]. Moreover, the satisfactory degree of one NFR may be adversely affected by other NFRs.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

Zhang

Wang

2019

IEEE Access

View full text Add to dashboard Cite

The need for particular software non-functional requirements (NFRs) leads a project team to use specific design strategies to fulfill these NFRs. However, some of the strategies may cause deficiencies in other software NFRs. These strategies are called conflicting strategies. Making the tradeoff decision of these conflicting strategies for NFRs is crucial. Therefore, a conflicting NFRs tradeoff framework (CNTF) and the corresponding method are proposed. Firstly, the NFRs are obtained from stakeholders. Fuzzy set theory is used to express stakeholder assessments on the importance of each NFR. The assessment results are ranked using a fuzzy ranking method. Then, adapting from production theory in microeconomics, the degree of satisfaction by which NFRs are affected by conflicting strategies are plotted as tradeoff curves. Borrowing the concept from the linear programming in management science, a tradeoff method is presented to help software project teams make the best tradeoff decision for conflicting NFRs. Finally, feasibility and limitations of the CNTF are elaborated in a case study. INDEX TERMS Non-functional requirement, conflict, production theory, linear programming, tradeoff.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: A Nfrs Obtaining and Assessmentmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

Zhang

Wang

2019

IEEE Access

View full text Add to dashboard Cite

show abstract

“…In this section, we will review some of the works that are published after 2013 and assess if there has been a shift in the use of ontologies in the requirements engineering process . Liu [13], developed a mechanism for automatically detecting conflicts in nonfunctional requirements. He developed a tool, CDNFRE, that include four essential elements namely metadata, ontology, cause-and-effect relationship, and conflict detection rule.…”

Section: Related Workmentioning

confidence: 99%

The Use of Ontologies in Software elicitation: Review

2021

HNSJ

View full text Add to dashboard Cite

Research in recent years has probed the integration of research in the fields of Software Engineering and Semantic Web technologies in several domains. Semantic approaches in general have allowed a better understanding of domains that are known for their ambiguities and incompleteness. We have seen artificial intelligence in general being used to improve many stages of the software development process. Ontologies are being used successfully in the requirements engineering phase. This paper reviews some of the research related to the use of ontologies in requirements engineering (RE). specifically review some approaches, methods, and tools. The main objective of this work is to show how ontologies are used in requirement elicitation which is then first step of (RE). Requirement elicitation is a crucial phase of (RE) and the use of ontologies to manage and facilitate the activities undertaken during this phase is of great importance. In summary, the main findings of this work are:(1) there are empirical evidences of the benefits of using ontology's in (RE) in several domains for reducing ambiguity, inconsistency and incompleteness of requirements;(2) several research works have developed novel approaches for ontology usage in (RE); (3) some of which developed algorithms that improved and enhanced the (RE) process; (4) most studies addressed only functional requirements; (5) some studies focused on the use of ontologies in requirement modeling. Finally, we conclude this work by suggesting several areas of ontology in (RE) search opportunities in ontology and some issues that need to be addressed.

show abstract

“…NFR classification approach uses ontology realizing with metamodel based on cause-effect and inferences knowledge [19].…”

Section: Related Workmentioning

confidence: 99%

Non-functional Requirements (NFR) Identification Method using FR Characters based on ISO/IEC 25023

Nurbojatmiko¹,

Budiardjo²,

Wibowo³

2021

IJACSA

View full text Add to dashboard Cite

The researches show that software quality depends on Functional Requirements (FR) and Non-Functional Requirements (NFR). The developers identify NFR attributes by interviewing stakeholders. The difficulty in identifying NFR attributes makes quality requirements often ignored. The basic concept of software quality measurements is the quality measuring of the software product. During product-based quality measurement, the potential of software development process repetition will occur. Factors measuring software product quality are not suitable for NFR identification. These differences result in the software development process repeating itself and additional costs. This research proposes easy NFR attributes identification using FR characters. The NFR and FR tightly relations are obtained by extending the NFR measurement at ISO/IEC25023 to programming coding level, then generalizing to get the FR character. The generalization uses the Grounded Theory method. The result is the NFR attributes identification method using FR character based on ISO/IEC 25023. The analyst or programmer can identify the NFR attributes from the FR using the FR character in the requirements stage. This research produces an NFR Identification Method that has been validated by experimenting with several programmers and experts. Tests on programmers identify NFR using the FR character method. The test is to see the level of similarity of the resulting NFR. The result of the test shows level similarity upper 75%.

show abstract

CDNFRE: Conflict detector in non-functional requirement evolution based on ontologies

Cited by 18 publications

References 22 publications

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

Tradeoff Analysis for Conflicting Software Non-Functional Requirements

The Use of Ontologies in Software elicitation: Review

Non-functional Requirements (NFR) Identification Method using FR Characters based on ISO/IEC 25023

Contact Info

Product

Resources

About