%0 Conference Paper %1 ulah_aSurveyOnIssuesInNFRElicitation_2011 %A Ullah, S. %A Iqbal, M. %A Khan, A.M. %B Computer Networks and Information Technology (ICCNIT), 2011 International Conference on %D 2011 %K London ambulance analysis; design;DP development elicitation;projects engineering;software failure;requirement industry;software industry;system management;systems requirements requirements;nonfunctional system;functional %P 333 -340 %R 10.1109/ICCNIT.2011.6020890 %T A survey on issues in requirements elicitation %X One of the primary responsibilities of requirement engineer is the elicitation of non-functional and functional requirements. Functional requirements sketch out the functionality, the system has to be performed while non-functional requirements compel the restrictions on this functionality. Software industry is raising its demand for not only the required functionality but the necessity of non-functional requirements too such as performance, security, usability, security, privacy etc. The current practice in the industry is to deal with functional requirements as first class requirements while non-functional requirements are only catered at design and implementation level. This approach leaves a serious flaw in the system design towards user satisfaction and often results in the failure of projects such as the classic example of London Ambulance System1. The chances of software success can be maximized when dealing with NFR at the requirements level. This literature survey is a first effort of its kind to seek key NFR challenges and issues while elicitation level of requirement engineering. It also find-outs the approaches and methods that are suggested in literature to deal with these issues.

@inproceedings{ulah_aSurveyOnIssuesInNFRElicitation_2011, abstract = {One of the primary responsibilities of requirement engineer is the elicitation of non-functional and functional requirements. Functional requirements sketch out the functionality, the system has to be performed while non-functional requirements compel the restrictions on this functionality. Software industry is raising its demand for not only the required functionality but the necessity of non-functional requirements too such as performance, security, usability, security, privacy etc. The current practice in the industry is to deal with functional requirements as first class requirements while non-functional requirements are only catered at design and implementation level. This approach leaves a serious flaw in the system design towards user satisfaction and often results in the failure of projects such as the classic example of London Ambulance System[1]. The chances of software success can be maximized when dealing with NFR at the requirements level. This literature survey is a first effort of its kind to seek key NFR challenges and issues while elicitation level of requirement engineering. It also find-outs the approaches and methods that are suggested in literature to deal with these issues.}, added-at = {2013-02-28T11:13:35.000+0100}, author = {Ullah, S. and Iqbal, M. and Khan, A.M.}, biburl = {https://www.bibsonomy.org/bibtex/2947d20ca7eb44b98ea09ce4dcc811600/fritzsolms}, booktitle = {Computer Networks and Information Technology (ICCNIT), 2011 International Conference on}, doi = {10.1109/ICCNIT.2011.6020890}, interhash = {b8dac3eedac81ea5fab641e631caccd6}, intrahash = {947d20ca7eb44b98ea09ce4dcc811600}, issn = {2223-6317}, keywords = {London ambulance analysis; design;DP development elicitation;projects engineering;software failure;requirement industry;software industry;system management;systems requirements requirements;nonfunctional system;functional}, month = {july}, pages = {333 -340}, timestamp = {2013-02-28T11:14:18.000+0100}, title = {A survey on issues in requirements elicitation}, year = 2011 }