2012
DOI: 10.1111/j.1468-0394.2012.00625.x
|View full text |Cite
|
Sign up to set email alerts
|

Eliciting and prioritizing quality requirements supported by ontologies: a case study using the ElicitO framework and tool

Abstract: As software complexity grows and clients demand higher quality software, quality requirements can no longer be considered to be of secondary importance. Thus, eliciting, specifying, prioritizing and validating quality requirements is a prerequisite to the development of effective and efficient information systems. Despite the critical importance of quality requirements, there is a considerable gap in the breadth and depth of quality requirements engineering (RE) support in most RE approaches. In practice, it i… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
14
0
3

Year Published

2014
2014
2022
2022

Publication Types

Select...
7
1

Relationship

0
8

Authors

Journals

citations
Cited by 23 publications
(17 citation statements)
references
References 66 publications
0
14
0
3
Order By: Relevance
“…This is an alternative to the approaches that promote determining the NFR after the functional requirements are defined [19,33]. In this case using an ontology based NFR elicitation framework, such as ElicitO [1], in combination with SCRAM-CK could provide a more complete set of requirements. This would be an important enhancement with the potential of easing the transition from prototyping to development of high quality production applications.…”
Section: Discussionmentioning
confidence: 99%
“…This is an alternative to the approaches that promote determining the NFR after the functional requirements are defined [19,33]. In this case using an ontology based NFR elicitation framework, such as ElicitO [1], in combination with SCRAM-CK could provide a more complete set of requirements. This would be an important enhancement with the potential of easing the transition from prototyping to development of high quality production applications.…”
Section: Discussionmentioning
confidence: 99%
“…As discussed in previous section, specifically related to requirement validation work [13,14,15,16] indicated the progress in field of validation, some are converting requirement into formal model for purposes of validation, other are using formal model and traceability, yet issues involves are again lot of human effort and minimum accuracy. A few work highlighted the ontological solution here [1,9] but an again pre-mature model, however no work is addressing requirement validation issues in GDD environment.…”
Section: Sub Question No 2: How Use Of Ontology Can Minimize the Limmentioning
confidence: 99%
“…However any deviation from customer needs create defective software project that cannot be validated in it operational environment [18,29]. This propagation of defects into later phase of software development results in major cost impact as statistics shows that requirements contribution due to validations defect are proportionally high; however improving these defects play a significant role in success of software projects [9].…”
Section: Introductionmentioning
confidence: 99%
“…The use of ontologies to support different aspects of software engineering has increase in the last years. A lot of the research work done refers to the elicitation process (Al Balushi, Sampaio, & Loucopoulos, ; Couto, Ribeiro, & Campos, ; Jwo & Cheng, ; Pires et al, ) and to the specification of ontologies for intermediate products (Abebe & Tonella, ; De Graaf, Liang, Tang, Van Hage, & Van Vliet, ). Other works focus on the development of tools based on ontologies that help to support the development process (García‐Peñalvo, Colomo‐Palacios, García, & Therón, ; Henderson‐Sellers, ; Reinhartz‐Berger, Sturm, & Wand, ).…”
Section: Background and Motivationmentioning
confidence: 99%