2016
DOI: 10.1109/tla.2016.7430098
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating the use of Pareto Efficiency to Optimize Non-Functional Requirements Satisfaction in i* Modeling

Abstract: Abstract-Due to the large, heterogeneous audience of Web applications, and its rapidly changing expectations, holistic requirement analysis approaches are crucial to ensure the success of Web engineering projects. To increase the quality of resulting Web applications, non-functional requirements (NFRs) must be considered. Satisfying them is a non-trivial task that depends on making decisions about which functional requirements (FRs) to implement, and how to prioritize the NFRs. A satisfactory solution is a tra… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(1 citation statement)
references
References 25 publications
0
1
0
Order By: Relevance
“…The authors Zubcoff, Garrigos, Casteleyn, Mazon, and Aguilar (2016), presented the Pareto method in which they considered the non-functional requirements during analysis and modeling of the requirements, in order to increase the quality of the web application, improve the design decision accuracy during the requirements analysis phase and they also stated the possibility for reducing the time needed by the designers [7]. Even though the issue of the non-functional requirements is initiated by above mentioned authors; Afreen, Khatoon and Sadiq (2016) in their article highlighted that most of the work is related to the functional requirements, while the non-functional requirements have received less consideration by the goal-oriented requirements engineering community [8].…”
Section: A Conceptual Modelmentioning
confidence: 99%
“…The authors Zubcoff, Garrigos, Casteleyn, Mazon, and Aguilar (2016), presented the Pareto method in which they considered the non-functional requirements during analysis and modeling of the requirements, in order to increase the quality of the web application, improve the design decision accuracy during the requirements analysis phase and they also stated the possibility for reducing the time needed by the designers [7]. Even though the issue of the non-functional requirements is initiated by above mentioned authors; Afreen, Khatoon and Sadiq (2016) in their article highlighted that most of the work is related to the functional requirements, while the non-functional requirements have received less consideration by the goal-oriented requirements engineering community [8].…”
Section: A Conceptual Modelmentioning
confidence: 99%