International Conference on Computer Networks and Information Technology 2011
DOI: 10.1109/iccnit.2011.6020890
|View full text |Cite
|
Sign up to set email alerts
|

A survey on issues in non-functional requirements elicitation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
22
0
1

Year Published

2012
2012
2023
2023

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 31 publications
(23 citation statements)
references
References 7 publications
0
22
0
1
Order By: Relevance
“…Pattern based methods appear to be suitable for naval platform NFRs as they provide a means of replicating existing naval platform NFR knowledge. NFR Patterns also provide "...a better solution for managing the complexity of the NFR elicitation process" (Ullah et al, 2011). Further suitability of pattern based methods of NFR elicitation and traceability, such as using a pattern of predetermined NFRs, is suggested by Gabb and Henderson with (Gabb and Henderson, 1995: p. 13): "All NFRs need to be considered and specified.…”
Section: Non-functional Requirements Evaluation Criteriamentioning
confidence: 99%
“…Pattern based methods appear to be suitable for naval platform NFRs as they provide a means of replicating existing naval platform NFR knowledge. NFR Patterns also provide "...a better solution for managing the complexity of the NFR elicitation process" (Ullah et al, 2011). Further suitability of pattern based methods of NFR elicitation and traceability, such as using a pattern of predetermined NFRs, is suggested by Gabb and Henderson with (Gabb and Henderson, 1995: p. 13): "All NFRs need to be considered and specified.…”
Section: Non-functional Requirements Evaluation Criteriamentioning
confidence: 99%
“…If Functional Requirements sketch out the functionality that the system has to be performed, Non-Functional Requirements (also called Extra-Functional Requirement) compel the restrictions on this functionality (such as performance, security, reliability, etc.) [13]. The notion of NFR is flawed, but when analyzing the definitions proposed in literature, we can conclude that Non functional Requirement is a constraint, property, and characteristic that describes not what the software will do, but how the software will do it.…”
Section: B On Non-functional Requirementsmentioning
confidence: 99%
“…Requirements-related: repeated errors [25], re-work cost, budget overruns, poor quality systems, stakeholder dissatisfaction, project failure [16,18,61], process and tools mis-alignment [22], errors, uncertainities [54], poor requirements [74], high maintenance costs, frequent changes [31], conceptual inconsistency [72], incomplete domain knowledge [51], flaws in resultant system [73].…”
Section: )mentioning
confidence: 99%