Please use this identifier to cite or link to this item:
http://localhost:80/xmlui/handle/123456789/13721
Full metadata record
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Aziz, Y. | - |
dc.contributor.author | Aziz, T. | - |
dc.contributor.author | Malik, M. I. | - |
dc.contributor.author | Baig, M. K. | - |
dc.contributor.author | Ali, M. Z. | - |
dc.contributor.author | Baqer, M. | - |
dc.date.accessioned | 2022-10-26T09:57:12Z | - |
dc.date.available | 2022-10-26T09:57:12Z | - |
dc.date.issued | 2017-03-15 | - |
dc.identifier.citation | Behutiye, 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.issn | 2313-7770 | - |
dc.identifier.uri | http://142.54.178.187:9060/xmlui/handle/123456789/13721 | - |
dc.description.abstract | Agile 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.iso | en | en_US |
dc.publisher | Taxila:University of Engineering and Technology(UET)Taxila, Pakistan | en_US |
dc.subject | Agile Requirements Engineering | en_US |
dc.subject | Dual Application Model | en_US |
dc.subject | Functional Requirements | en_US |
dc.subject | MEDoV | en_US |
dc.subject | Non Functional Requirements | en_US |
dc.subject | NORMAP | en_US |
dc.subject | Traditional Requirement Engineering | en_US |
dc.subject | UML Use Case | en_US |
dc.title | Non Functional Requirement in Agile Software | en_US |
dc.type | Article | en_US |
Appears in Collections: | Issue No. 1 |
Files in This Item:
File | Description | Size | Format | |
---|---|---|---|---|
14-Non%20Functional%20Requirement%20in%20Agile%20Software%20Development.htm | 196 B | HTML | View/Open |
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.