Elicitation of Nonfunctional Requirements in Agile Development Using Cloud Computing Environment
Open Access
- 27 August 2020
- journal article
- research article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Access
- Vol. 8, 209153-209162
Abstract
Nonfunctional requirements are ignored because functional requirements are considered to be more important than nonfunctional requirements, lack of knowledge and methodologies to accomplish nonfunctional requirement elicitation and the nature of agile software development process. This ignorance of nonfunctional requirements become the cause to failure of projects. Furthermore, cloud computing helps to practice twelve (12) agile principles including nonfunctional requirement elicitation. This study proposed a semi-automated methodology for eliciting nonfunctional requirement in agile development and cloud computing environment. The methodology used an NLP based automatic NFR extraction approach to fast the NFR elicitation process. The methodology is evaluated by applying on eProcurement dataset. The results are improved as compared to existing studies.Keywords
Funding Information
- Universiti Teknologi Malaysia (06G23)
This publication has 36 references indexed in Scilit:
- Issues in Adopting Agile Development Principles for Mobile Cloud Computing ApplicationsProcedia Computer Science, 2015
- Cloud-Based Software CrowdsourcingIEEE Internet Computing, 2014
- Introducing Agility in Cloud Based Software Development through ASDInternational Journal of u- and e- Service, Science and Technology, 2013
- Envisioning the Cloud-Induced Transformations in the Software Engineering Discipline2013
- Impact of Cloud Adoption on Agile Software Development2013
- EHRs Get a Failing Grade on UsabilityInternal Medicine News, 2010
- On Non-Functional Requirements in Software Engineering2009
- Using quality models in software package selectionIEEE Software, 2003
- Agile software development, the people factorComputer, 2001
- Identifying quality-requirement conflictsIEEE Software, 1996