DSpace logo

Please use this identifier to cite or link to this item: http://142.54.178.187:9060/xmlui/handle/123456789/13721
Full metadata record
DC FieldValueLanguage
dc.contributor.authorAziz, Y.-
dc.contributor.authorAziz, T.-
dc.contributor.authorMalik, M. I.-
dc.contributor.authorBaig, M. K.-
dc.contributor.authorAli, M. Z.-
dc.contributor.authorBaqer, M.-
dc.date.accessioned2022-10-26T09:57:12Z-
dc.date.available2022-10-26T09:57:12Z-
dc.date.issued2017-03-15-
dc.identifier.citationBehutiye, W., Karhapää, P., Costal, D., Oivo, M., & Franch, X. (2017, November). Non-functional requirements documentation in agile software development: challenges and solution proposal. In International conference on product-focused software process improvement (pp. 515-522). Springer, Cham.en_US
dc.identifier.issn2313-7770-
dc.identifier.urihttp://142.54.178.187:9060/xmlui/handle/123456789/13721-
dc.description.abstractAgile Software Development (ASD) is very popular worldwide for developing software applications efficiently according to dynamic user's requirements. Previously, Traditional Software Engineering (TSE) was used but unplanned changes in customer's requirements raised a need for agile software development technology. Both mentioned techniques of software development have significant pros and cons like: ASD bases on modeling rather than documentation while TSE bases on documentation rather than modeling. In order to overcome the drawbacks, this paper particularly focuses on analysis of some methods and approaches like Non-functional Requirements Model for Agile Process (NORMAP), Method of Elicitation, Documentation & Validation (MEDoV) and Dual Application Model so that benefits of both TSE and ASD can be achieved.en_US
dc.language.isoenen_US
dc.publisherTaxila:University of Engineering and Technology(UET)Taxila, Pakistanen_US
dc.subjectAgile Requirements Engineeringen_US
dc.subjectDual Application Modelen_US
dc.subjectFunctional Requirementsen_US
dc.subjectMEDoVen_US
dc.subjectNon Functional Requirementsen_US
dc.subjectNORMAPen_US
dc.subjectTraditional Requirement Engineeringen_US
dc.subjectUML Use Caseen_US
dc.titleNon Functional Requirement in Agile Softwareen_US
dc.typeArticleen_US
Appears in Collections:Issue No. 1

Files in This Item:
File Description SizeFormat 
14-Non%20Functional%20Requirement%20in%20Agile%20Software%20Development.htm196 BHTMLView/Open


Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.