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

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...

Full description

Saved in:
Bibliographic Details
Published in:Revista IEEE América Latina 2016-01, Vol.14 (1), p.331-338
Main Authors: Zubcoff, Jose Jacobo, Garrigos, Irene, Casteleyn, Sven, Mazon, Jose Norberto, Aguilar, Jose Alfonso
Format: Article
Language:English
Subjects:
Adaptation models
Analytical models
Applications programs
Complement
Context modeling
Decisions
Design analysis
goal-oriented requirements
Interviews
Lists
Modelling
NFRs Optimization
Optimization
Pareto Efficiency
Pareto optimality
Reliability
Requirements analysis
Software reviews
Usability
Web Engineering
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary: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 trade-off, where competing NFRs must be balanced. In this paper, we outline how the Pareto efficiency can complement a goal-oriented requirement analysis modelling to evaluate and select optimal configurations of requirements for a Web application, while NFRs are balanced and maximized according to a priority list. We hereby focus on an empirical evaluation to verify whether our Pareto method improves the accuracy of design decisions during the requirements analysis phase, and/or if it reduces the time needed by designers.
ISSN:1548-0992
1548-0992
DOI:10.1109/TLA.2016.7430098