Abstract
Managing non functional requirements has been a challenge onto software engineers for a long time. Throughout the years, numerous strategies and methods have been proposed to enhance their elicitation, documentation and approval. Similarly, security requirements emphatically impact the building configuration of complex IT frameworks comparatively as non-functional requirements. Both security building and software engineering furnish strategies to manage such necessities. Nonetheless, there is still a basic crevice concerning the joining of techniques for these two different fields. In this paper we close this crevice as for security prerequisites by proposing a technique that joins software engineering technologies with the best in class security engineering standards. An efficient quality requirement based software model with security requirements is developed by fusing Group Search Optimization and genetic algorithm in our proposed methodology.
Similar content being viewed by others
Change history
06 June 2022
This article has been retracted. Please see the Retraction Notice for more detail: https://doi.org/10.1007/s12652-022-04048-9
References
Aurum A, Wohlin C (2005) Engineering and managing software requirements. Springer-Verlag, New York
Bechtsoudis A, Sklavos N (2012) Aiming at higher network security through extensive penetration tests. IEEE Latin Am Trans 10(3):1752–1756
Bezuglov DY, Trofimov MA (2016) Specialized software for testing components of integrated NPP security systems from different manufacturers for the possibility of integration. Nuclear Energy Technol 1(1):74–76
Claland-Huang J, Settimi R, Zou X, Solc P (2007) Automated classification of non-functional requirements. Require Eng 12(2):103–120
Cysneiro LM, Julio Cesar Sampaio do Prado Leite Department de Informatica PUC-Rio (2001) Using UML to reflect non-functional requirements. In: Proceedings of the 2001 conference of the centre for advanced studies on collaborative research. Toronto, Ontario
Dabbagh M, Lee SP (2014) An approach for integrating the prioritization of functional and non functional requirements. Spec Issue-Recent Adv Info Technol 2014:737626
Fabian B, Gurses S, Heisel M, Santen T, Schmidt H (2010) A comparison of security requirements engineering methods. Require Eng 15(1):7–40
Garousi V, Mantyla MV (2016) A systematic literature review of literature reviews in software testing. Inf Softw Technol 80:195–216
Haley CB, Laney R, Moffett JD, Member IEEE, Nuseibeh B, Member, IEEE Computer Society (2008) Security requirements engineering: a framework for representation and analysis IEEE transactions on software engineering. 34(1)
Hassan R, Eltoweissy M, Bohner S, El-Kassas S (2010) Formal analysis and design for engineering security automated derivation of formal software security specifications from goal-oriented security requirements. IET Softw 4(2):149–160
Hui Z, Huang S (2012) Comparison of SETAM with security use case and security misuse case: a software security testing study. Wuhan Univ J Nat Sci 17(6):516–520
Islam S, Falcarin P (2011) Measuring security requirements for software security. In: Proceedings of the 2011 10th IEEE international conference on cybernetic intelligent systems, September 1–2 London, UK
Jain S, Reader MCA Department SRGPGPI Indore, India, Maya Ingle Principal Indore Institute of Computer Application Indore, India (2011) Software security requirements gathering instrument. Int J Adv Comput Sci Appl 2(7)
Kassab M, Daneva M, O. Ormandjieva University of Twente, Enschede, The Netherlands Concordia University, Montreal, Canada (2007) Early quantitative assessment of non-functional requirements. ACM SIGOPS Operating Systems Review
Kooli M, Kaddachi F, Di Natale G, Bosio A, Benoit P, Torres L (2016) Computing reliability: on the differences between software testing and software fault injection techniques. Microprocess Microsys 50:102–112
Li H, Bao X, Ji S (2014) Research on elicitation of safety testing requirements for airborne software. Proc Eng 80:303–312
Luckey M, Baumann A, Mendez D, Wagner S (2010) Reusing security requirements using an extended quality model. In: Proceedings of 2010 ICSE ’98
Mazo R, Feltus C (2016) Framework for engineering complex security requirements patterns. Am J Eng Res 02(12):360–366
Odzaly EE, Greer D, Stewart D (2017) Agile risk management using software agents. J Ambient Intell Human Comput 9:823–841
Pavlovski CJ, Zou J (2008) Non-functional requirements in business process modeling. In: APCCM '08 Proceedings of the fifth Asia-Pacific conference on conceptual modelling, vol 79. pp 103–112
Ramachandran M (2016) Software security requirements management as an emerging cloud computing service. Int J Inf Manag 36(4):580–590
Sindre G, Opadhl AL (2005) Eliciting security requirements with misuse cases. Require Eng 10(1):34–44
Siy H, Aryal P, Winter V, Zand M (2007) Aspectual support for specifying requirements in software product lines. In: IEEE conference---early aspects at ICSE: workshops in aspect-oriented requirements engineering and architecture design (EARLYASPECTS'07)
Vijayakumar K, Arun C (2017) Automated risk Identification using NLP by building a model based on development environments. J Ambient Intell Human Comput. https://doi.org/10.1007/s12652-017-0503-7
Yusop N, Zowghi D, Lowe D (2006) The impact of non-functional requirements in web projects. In: European and Mediterranean conference on information systems (EMCIS) 2006, July 6–7 2006, Costa Blanca, Alicante
Author information
Authors and Affiliations
Corresponding author
Additional information
Publisher's Note
Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.
This article has been retracted. Please see the retraction notice for more detail: https://doi.org/10.1007/s12652-022-04048-9
About this article
Cite this article
Ramkumar, R., Mala, G.S.A. RETRACTED ARTICLE: Non functional requirement based software architecture scheme with security requirement using hybrid group search optimization and genetic algorithm. J Ambient Intell Human Comput 12, 4863–4876 (2021). https://doi.org/10.1007/s12652-020-01904-4
Received:
Accepted:
Published:
Issue Date:
DOI: https://doi.org/10.1007/s12652-020-01904-4