Relevant bibliographies by topics / Security Requirement Elicitation

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Book chapters
  4. Conference papers

Academic literature on the topic 'Security Requirement Elicitation'

Author: Grafiati
Published: 11 September 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Security Requirement Elicitation.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "Security Requirement Elicitation"

1

GUTIERREZ, C., E. FERNANDEZ-MEDINA, and M. PIATTINI. "Web Services-Based Security Requirement Elicitation." IEICE Transactions on Information and Systems E90-D, no. 9 (September 1, 2007): 1374–87. http://dx.doi.org/10.1093/ietisy/e90-d.9.1374.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Kumar, B. Sathis. "EVALUATION OF CAPTURING ARCHITECTURALLY SIGNIFICANT REQUIREMENTS." Asian Journal of Pharmaceutical and Clinical Research 10, no. 13 (April 1, 2017): 122. http://dx.doi.org/10.22159/ajpcr.2017.v10s1.19589.

Full text
Abstract:
Every software development organization strives for customer satisfaction. It is universally accepted that the success of software development lies in the clear understanding of the client requirements. During requirement elicitation and analysis stage, the system analyst identifies the functional and non-functional requirements from the customer. Security, usability, reliability, performance, scalability and supportability are the significant quality attributes of a software system. These quality attributes are also referred as non-functional requirements. Only a few functional and quality attributes requirement help to identify and shape the software architecture. A software system’s architecture is the set of prime design decisions made about the system. If the requirement influences the architectural design decision then, it is referred as Architecturally Significant Requirement (ASR). Identifying and specifying all the possible ASR are important tasks in the requirement elicitation and analysis stage.In this research, general problems that are faced while capturing and specifying ASR in requirement elicitation and analysis is studied. Among the different requirement elicitation techniques, use case diagram has been identified and enhanced to solve the problem of capturing and specifying ASR during the requirement elicitation and analysis phase
APA, Harvard, Vancouver, ISO, and other styles
3

Kumar, Devendra, Anil Kumar, and Laxman Singh. "Non-functional Requirements Elicitation in Agile Base Models." Webology 19, no. 1 (January 20, 2022): 1992–2018. http://dx.doi.org/10.14704/web/v19i1/web19135.

Full text
Abstract:
The elicitation of non-functional and functional needs is one of the most critical jobs of a requirement engineer. This scenario involves the imposition of limits on non-functional needs, whereas functional requirements call for the operation of a system in order to carry out functionality. Over the last few years, agile software development approaches have gained widespread acceptance in the software industry as a problem-solving paradigm. Non-functional requirements (NFRs) are frequently cited as a point of contention in non-functional requirements (NFR) approaches. As well as functional requirements like speed and efficiency, security is desired, amongst a host of other things. Aspects like usability, security, and privacy must all be taken into account. Functional needs must be treated as though they were first-class under the current industry standard of practice. Functional requirements are distinguished from non-functional requirements by the fact that only implemented requirements can be evaluated. To give an example, this method attracts the attention of the system's end users to a critical defect in its architecture. Projects of this type frequently fail because to dissatisfaction among the target audience. If you'd like a great demonstration, consider the London Ambulance System. When dealing with non-compliance to the necessary degree of detail, it is feasible to raise the likelihood of software success this is the first study of its kind in its sector to bring attention to the most critical NFR issues. The problems that arise during the elicitation stage of requirement engineering in agile base models. It also outlines the techniques and strategies that are being considered. Proposed in the literature as a means of dealing with these problems.
APA, Harvard, Vancouver, ISO, and other styles
4

Beckers, Kristian, Isabelle Côté, Ludger Goeke, Selim Güler, and Maritta Heisel. "A Structured Method for Security Requirements Elicitation concerning the Cloud Computing Domain." International Journal of Secure Software Engineering 5, no. 2 (April 2014): 20–43. http://dx.doi.org/10.4018/ijsse.2014040102.

Full text
Abstract:
Cloud computing systems offer an attractive alternative to traditional IT-systems, because of economic benefits that arise from the cloud's scalable and flexible IT-resources. The benefits are of particular interest for SME's. The reason is that using Cloud Resources allows an SME to focus on its core business rather than on IT-resources. However, numerous concerns about the security of cloud computing services exist. Potential cloud customers have to be confident that the cloud services they acquire are secure for them to use. Therefore, they have to have a clear set of security requirements covering their security needs. Eliciting these requirements is a difficult task, because of the amount of stakeholders and technical components to consider in a cloud environment. Therefore, the authors propose a structured, pattern-based method supporting eliciting security requirements and selecting security measures. The method guides potential cloud customers to model the application of their business case in a cloud computing context using a pattern-based approach. Thus, a potential cloud customer can instantiate our so-called Cloud System Analysis Pattern. Then, the information of the instantiated pattern can be used to fill-out our textual security requirements patterns and individual defined security requirement patterns, as well. The presented method is tool-supported. Our tool supports the instantiation of the cloud system analysis pattern and automatically transfers the information from the instance to the security requirements patterns. In addition, they have validation conditions that check e.g., if a security requirement refers to at least one element in the cloud. The authors illustrate their method using an online-banking system as running example.
APA, Harvard, Vancouver, ISO, and other styles
5

Rehman, Shafiq, and Volker Gruhn. "An Effective Security Requirements Engineering Framework for Cyber-Physical Systems." Technologies 6, no. 3 (July 12, 2018): 65. http://dx.doi.org/10.3390/technologies6030065.

Full text
Abstract:
Context and motivation: Cyber-Physical Systems (CPSs) are gaining priority over other systems. The heterogeneity of these systems increases the importance of security. Both the developer and the requirement analyst must consider details of not only the software, but also the hardware perspective, including sensor and network security. Several models for secure software engineering processes have been proposed, but they are limited to software; therefore, to support the processes of security requirements, we need a security requirements framework for CPSs. Question/Problem: Do existing security requirements frameworks fulfil the needs of CPS security requirements? The answer is no; existing security requirements frameworks fail to accommodate security concerns outside of software boundaries. Little or even no attention has been given to sensor, hardware, network, and third party elements during security requirements engineering in different existing frameworks. Principal Ideas/results: We have proposed, applied, and assessed an incremental security requirements evolution approach, which configures the heterogeneous nature of components and their threats in order to generate a secure system. Contribution: The most significant contribution of this paper is to propose a security requirements engineering framework for CPSs that overcomes the issue of security requirements elicitation for heterogeneous CPS components. The proposed framework supports the elicitation of security requirements while considering sensor, receiver protocol, network channel issues, along with software aspects. Furthermore, the proposed CPS framework has been evaluated through a case study, and the results are shown in this paper. The results would provide great support in this research direction.
APA, Harvard, Vancouver, ISO, and other styles
6

Faroom, Saeed. "A Review of Requirement Engineering Process Models, Tools & Methodologies." International Journal of Energetica 4, no. 1 (June 30, 2019): 44. http://dx.doi.org/10.47238/ijeca.v4i1.86.

Full text
Abstract:
As we are living in the Era of Computer Science and almost all individuals and the organizations are completely relying on software systems. The requirement engineering is the most vital and important aspect in the success of any software engineering project. Requirement Engineering is a set of different process that works at different levels, which are incorporated at individual and organizational level Projects We need to consult different sources to find requirements. We need to involve personals from the different fields to find a set of quality requirements. The security issues undergoes as soon as early in the 1st phase of requirements. It is shown from the studies that if we consider Quality Process of Requirement Engineering at the phase it results in saving of million dollars. This paper contains the details study and comparison of different RE Process Models and Requirement Elicitation techniques. This paper elaborates the vital aspects of different Requirement Engineering Process models that help in the selection of appropriate model for the Requirement Engineers and practitioners working in the industry. This Paper also Focus on the giving a detailed view of Elicitation techniques and comparative study including the characteristics and their strengths and weakness. Some strengths and weakness found during detailed study are also structured and listed that is also the helpful for the Appropriate selection of RE Process model.
APA, Harvard, Vancouver, ISO, and other styles
7

Vegendla, Aparna, Anh Nguyen Duc, Shang Gao, and Guttorm Sindre. "A Systematic Mapping Study on Requirements Engineering in Software Ecosystems." Journal of Information Technology Research 11, no. 1 (January 2018): 49–69. http://dx.doi.org/10.4018/jitr.2018010104.

Full text
Abstract:
Software ecosystems (SECOs) and open innovation processes have been claimed as a way forward for the software industry. A proper understanding of requirements is as important for SECOs as for more traditional ones. This article presents a mapping study on the issues of RE and quality aspects in SECOs. Our findings indicate that among the various phases or subtasks of RE, most of the SECO specific research has been accomplished on elicitation, analysis, and modeling. On the other hand, requirement selection, prioritization, verification, and traceability has attracted few published studies. Among the various quality attributes, most of the SECOs research has been performed on security, performance and testability. On the other hand, reliability, safety, maintainability, transparency, usability attracted few published studies. The article provides a review of the academic literature about SECO-related RE activities, modeling approaches, and quality attributes, positions the source publications in a taxonomy of issues and identifies gaps where there has been little research.
APA, Harvard, Vancouver, ISO, and other styles
8

ISSA, ATOUM. "REQUIREMENTS ELICITATION APPROACH FOR CYBER SECURITY SYSTEMS." i-manager’s Journal on Software Engineering 10, no. 3 (2016): 1. http://dx.doi.org/10.26634/jse.10.3.4898.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Matulevičius, Raimundas, Alex Norta, and Silver Samarütel. "Security Requirements Elicitation from Airline Turnaround Processes." Business & Information Systems Engineering 60, no. 1 (January 15, 2018): 3–20. http://dx.doi.org/10.1007/s12599-018-0518-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Schmitt, Christian, and Peter Liggesmeyer. "Getting Grip on Security Requirements Elicitation by Structuring and Reusing Security Requirements Sources." Complex Systems Informatics and Modeling Quarterly, no. 3 (July 30, 2015): 15–34. http://dx.doi.org/10.7250/csimq.2015-3.02.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Security Requirement Elicitation"

1

Islam, Gibrail, and Murtaza Ali Qureshi. "A Framework for Security Requirements Elicitation." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3448.

Full text
Abstract:
Context: Security considerations are typically incorporated in the later stages of development as an afterthought. Security in software system is put under the category of non-functional requirements by the researchers. Understanding the security needs of a system requires considerable knowledge of assets, data security, integrity, confidentiality and availability of services. Counter measures against software attacks are also a security need of a software system. To incorporate security in the earliest stages, i.e. requirement gathering, helps building secure software systems from the start. For that purpose researchers have proposed different requirements elicitation techniques. These techniques are categorized into formal and informal techniques on the basis of finiteness and clarity in activities of the techniques. Objectives: Limitations of formal methods and lack of systematic approaches in informal elicitation techniques make it difficult to rely on a single technique for security requirements elicitation. Therefore we decided to utilize the strengths of formal and informal technique to mitigate their weaknesses by combining widely used formal and informal security requirements elicitation techniques. The basic idea of our research was to integrate an informal technique with a formal technique and propose a flexible framework with some level of formality in the steps. Methods: We conducted a systematic literature review to see “which are the widely used security requirement elicitation techniques?” as a pre-study for our thesis? We searched online databases i.e. ISI, IEEE Xplore, ACM, Springer, Inspec and compendeX. We also conducted a literature review for different frameworks that are used in industry, for security requirement elicitation. We conducted an experiment after proposing a security requirements elicitation Framework and compared the result from the Framework with that of CLASP and Misuse cases. Results:Two types of analysis were conducted on results from the experiment: Vulnerability analysis and Requirements analysis with respect to a security baseline. Vulnerability analysis shows that the proposed framework mitigates more vulnerabilities than CLASP and Misuse Cases. Requirements analysis with respect to the security baseline shows that the proposed framework, unlike CLASP and Misuse cases, covers all the security baseline features. Conclusions:The framework we have proposed by combining CLASP, Misuse cases and Secure TROPOS contains the strengths of three security requirements elicitation techniques. To make the proposed framework even more effective, we also included the security requirements categorization by Bogale and Ahmed [11]. The framework is flexible and contains fifteen steps to elicit security requirements. In addition it also allows iterations to improve security in a system
APA, Harvard, Vancouver, ISO, and other styles
2

Bogale, Helen Yeshiwas, and Zohaib Ahmed. "A Framework for Security Requirements : Security Requirements Categorization and Misuse Cases." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5896.

Full text
Abstract:
Context: Security Requirements engineering is necessary to achieve secure software systems. Many techniques and approaches have been proposed to elicit security requirements in the initial phases of development. With the growing importance of security and immense increase in security breaches over the past few years, researchers and practitioners have been striving to achieve a mature process of coping with security requirements. Much of the activities in this regard are seen in academia but industry still seems to be lacking in giving the required importance to security requirements engineering. That is why, security requirements engineering is still not always considered as a central part of requirements engineering. This study is targeted to bridge this gap between academia and industry in terms of security requirements engineering and to provide a concrete approach to efficiently elicit and specify security requirements. The Misuse case technique is proposed for this purpose. However it lacks in providing guidelines for enabling scalable use. This limitation has been addressed to achieve a mature process of security requirements elicitation. Objectives: In this study, we propose a framework to elicit security requirements early in the software development using misuse case technique. Objective is to make misuse case technique scalable and applicable to the real-world projects. The proposed framework was presented to two representatives from the Swedish Armed Forces (SWAF). The feedback received from the representatives was utilized to refine, update and finalize the framework. Methods: The study involved a systematic review to gain an insight of the academic perspective in the area of study. Document extraction was adopted to observe the industrial trends in the said subject. These were the software requirements specification documents of the real-world systems. Document extraction was supported with informed brainstorming because the study revolved around misuse case technique and informed brainstorming is considered to be the most suitable technique for this purpose. A workshop was conducted with two representatives of Swedish Armed Forces followed by two subsequent asynchronous communication rounds and a facilitated session to get feedback about the proposed solution. This feedback was utilized to refine, update and finalize the proposed solution. Results: The results of the systematic review were organized in tabular forms for a clear understanding and easy analysis. A security requirements categorization was obtained as a result which was finalized after an initial validation with the help of real-world projects. Furthermore, a framework was proposed utilizing this categorization to address the limitations of misuse case technique. The framework was created and refined through workshop and different communication rounds with representatives of SWAF. Their feedback was used as input to further improve the usefulness and usability aspects of the framework. Conclusions: The significance of security requirements engineering is undisputedly accepted both in academia and industry. However, the area is not a subject of practice in industrial projects. The reasons include lack of mature processes as well as expensive and time consuming solutions. Lack of empirical evidences adds to the problems. The conducted study and proposed process of dealing with this issue is considered as a one step forward towards addressing the challenges.
Säkerhet Kravhantering är nödvändigt för att uppnå säkra programvarusystem. Många tekniker och metoder har föreslagits för att framkalla säkerhetskraven i de inledande faserna i utvecklingen. Med den växande betydelsen av säkerhet och enorma ökning av brott mot säkerheten under de senaste åren har forskare och praktiker strävat efter att uppnå en mogen process för att klara säkerhetskraven. Mycket av verksamheten i detta avseende ses i den akademiska världen, men industrin fortfarande tycks saknas i att ge den nödvändiga betydelse för säkerheten kravhantering. Därför är säkerheten kravhantering fortfarande inte alltid som en central del av kravhantering. Denna studie är inriktad att överbrygga denna klyfta mellan akademi och näringsliv när det gäller säkerhet kravhantering och att ge en konkret strategi för att effektivt få fram och specificera säkerhetskrav. Missbruk fallet tekniken föreslås för detta ändamål. Men det saknar i att ge riktlinjer för att möjliggöra skalbar användning. Denna begränsning har åtgärdats för att uppnå en mogen process av säkerhetskrav elicitation.
+46 (0) 735 84 12 97, +46 (0) 760 60 96 55
APA, Harvard, Vancouver, ISO, and other styles
3

ROCHA, Simara Vieira da. "ELICITAÇÃO DE REQUISITOS BASEADA EM OBJETIVOS PARA POLÍTICAS DE SEGURANÇA E PRIVACIDADE EM COMÉRCIO ELETRÔNICO." Universidade Federal do Maranhão, 2005. http://tedebc.ufma.br:8080/jspui/handle/tede/395.

Full text
Abstract:
Made available in DSpace on 2016-08-17T14:53:00Z (GMT). No. of bitstreams: 1 Simara Vieira da Rocha.pdf: 792628 bytes, checksum: 3ed7f28da8fc68945a5845f799bd0281 (MD5) Previous issue date: 2005-09-30
This work describes a method for the elicitation of requirements based on goals for electronic commerce systems in agreement with security and privacy polices of a site. The method integrates the UWA approach [33] with the GBRAM method [6] for developing requirements and policies for secure electronic commerce systems. The resulting method aims to guarantee that existent security and privacy policies do not become obsolete after the adoption of new functionalities to a site. For this reason, the method provides means to set the elicited requirements in conformity with these new functionalities. On the other hand, organizations that have not established their policies yet, the proposed approach suggests some models through which it is possible to create such policies. At last, the proposed method presents a model for the document of requirements specification in agreement with the approach described in this work, as way of establishing a standard means to specify software requirements that can be as useful for the developing teams, in the attempt of facilitating the construction of systems, as for the analyzing teams, in the future maintenances or increment of functionalities to a site.
Este trabalho descreve um método para elicitação de requisitos baseado em objetivos para sistemas de comércio eletrônico, em conformidade com as políticas de segurança e privacidade existentes em um site. O método é originado pela integração das abordagens UWA [33] com a instanciação do método GBRAM [6] para o desenvolvimento de políticas e requisitos de sistemas de comércio eletrônicos seguros. O método resultante tem por objetivo garantir que as políticas de segurança e privacidade existentes nunca se tornem obsoletas com a adoção de novas funcionalidades a um site. Para tanto, provê meios para que os requisitos elicitados estejam em conformidade com as mesmas. Por outro lado, caso as organizações não tenham estabelecido suas políticas, a abordagem proposta sugere modelos através dos quais é possível a criação de tais políticas. Por fim, o método proposto ainda apresenta um modelo para o documento de especificação de requisitos, como forma de estabelecer um meio padrão para especificar requisitos de software, o qual poderá ser útil tanto para as equipes de desenvolvimento, na tentativa de facilitar a construção de sistemas, quanto para as equipes de análises, nas futuras manutenções ou acréscimo de funcionalidades ao site.
APA, Harvard, Vancouver, ISO, and other styles
4

Soni, Krishna Chandra. "Designing Security Requirement Solutions Using Back Tracking Approach." Thesis, 2015. http://dspace.dtu.ac.in:8080/jspui/handle/repository/14316.

Full text
Abstract:
Current practices for developing secure information systems are still closer to art than to an engineering discipline. Security is still treated as an add-on and is therefore not integrated into software development practices and tools. Experienced security artisans are still the key to achieving acceptable levels of security. Security of software system means protection afforded to an automated information system in order to attain the applicable objectives of preserving the integrity, availability and confidentiality of information system resources (includes hardware, software, firmware, information/data, and telecommunications). Many methods have been proposed for framing the security requirements, but the main target is how to find the solutions fulfilling these security requirements, to produce complete secure information system. So, we propose a Model framework for finding a complete solutions of security requirements, which are identified during the security requirement elicitation stage, using back tracking analysis. After gathering security requirements, we do back tracking analysis of the approaches used to gather security requirements, to identify the solutions necessary to fulfill the gathered security requirements. On basis of back tracking analysis, we will find conceptual solutions and security services and corresponding mechanisms which encompass the complete security of software system.
Shalender Kumar Verma
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Security Requirement Elicitation"

1

Kirikova, Marite, Raimundas Matulevičius, and Kurt Sandkuhl. "The Enterprise Model Frame for Supporting Security Requirement Elicitation from Business Processes." In Communications in Computer and Information Science, 229–41. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-40180-5_16.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Rodríguez, Alfonso, Eduardo Fernández-Medina, and Mario Piattini. "M-BPSec: A Method for Security Requirement Elicitation from a UML 2.0 Business Process Specification." In Advances in Conceptual Modeling – Foundations and Applications, 106–15. Berlin, Heidelberg: Springer Berlin Heidelberg, 2007. http://dx.doi.org/10.1007/978-3-540-76292-8_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Souag, Amina, Camille Salinesi, Raúl Mazo, and Isabelle Comyn-Wattiau. "A Security Ontology for Security Requirements Elicitation." In Lecture Notes in Computer Science, 157–77. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-15618-7_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Goel, Rajat, Mahesh Chandra Govil, and Girdhari Singh. "Security Requirements Elicitation and Modeling Authorizations." In Communications in Computer and Information Science, 239–50. Singapore: Springer Singapore, 2016. http://dx.doi.org/10.1007/978-981-10-2738-3_20.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Ghiran, Ana-Maria, Robert Andrei Buchmann, and Cristina-Claudia Osman. "Security Requirements Elicitation from Engineering Governance, Risk Management and Compliance." In Requirements Engineering: Foundation for Software Quality, 283–89. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-77243-1_17.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Alwidian, Sanaa, and Jason Jaskolka. "Understanding the Role of Human-Related Factors in Security Requirements Elicitation." In Requirements Engineering: Foundation for Software Quality, 65–74. Cham: Springer Nature Switzerland, 2023. http://dx.doi.org/10.1007/978-3-031-29786-1_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Saeki, Motoshi, and Haruhiko Kaiya. "Security Requirements Elicitation Using Method Weaving and Common Criteria." In Models in Software Engineering, 185–96. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-642-01648-6_20.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Makri, Eleni-Laskarina, and Costas Lambrinoudakis. "Towards a Common Security and Privacy Requirements Elicitation Methodology." In Communications in Computer and Information Science, 151–59. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-23276-8_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Faßbender, Stephan, Maritta Heisel, and Rene Meis. "Problem-Based Security Requirements Elicitation and Refinement with PresSuRE." In Communications in Computer and Information Science, 311–30. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-25579-8_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Kim, Seung-Jun, and Seok-Won Lee. "Social Engineering Based Security Requirements Elicitation Model for Advanced Persistent Threats." In Communications in Computer and Information Science, 29–40. Singapore: Springer Singapore, 2018. http://dx.doi.org/10.1007/978-981-10-7796-8_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Security Requirement Elicitation"

1

Ikram, Naveed, Surayya Siddiqui, and Naurin Farooq Khan. "Security requirement elicitation techniques: The comparison of misuse cases and issue based information systems." In 2014 IEEE Fourth International Workshop on Empirical Requirements Engineering (EmpiRE). IEEE, 2014. http://dx.doi.org/10.1109/empire.2014.6890114.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Belloir, Nicolas, Vanea Chiprianov, Manzoor Ahmad, Manuel Munier, Laurent Gallon, and Jean-Michel Bruel. "Using Relax Operators into an MDE Security Requirement Elicitation Process for Systems of Systems." In the 2014 European Conference. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/2642803.2642835.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Amin, Md Rayhan, and Tanmay Bhowmik. "Existing Vulnerability Information in Security Requirements Elicitation." In 2022 IEEE 30th International Requirements Engineering Conference Workshops (REW). IEEE, 2022. http://dx.doi.org/10.1109/rew56159.2022.00049.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Rabii, Anass, Saliha Assoul, and Ounsa Roudies. "Security requirements elicitation: A smart health case." In 2020 Fourth World Conference on Smart Trends in Systems Security and Sustainablity (WorldS4). IEEE, 2020. http://dx.doi.org/10.1109/worlds450073.2020.9210330.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Goel, Rajat, M. C. Govil, and Girdhari Singh. "Security Requirements Elicitation and Assessment Mechanism (SecREAM)." In 2015 International Conference on Advances in Computing, Communications and Informatics (ICACCI). IEEE, 2015. http://dx.doi.org/10.1109/icacci.2015.7275889.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lindvall, Mikael, Madeline Diep, Michele Klein, Paul Jones, Yi Zhang, and Eugene Vasserman. "Safety-Focused Security Requirements Elicitation for Medical Device Software." In 2017 IEEE 25th International Requirements Engineering Conference (RE). IEEE, 2017. http://dx.doi.org/10.1109/re.2017.21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Ionita, Dan, Jan-Willem Bullee, and Roel J. Wieringa. "Argumentation-based security requirements elicitation: The next round." In 2014 IEEE 1st Workshop on Evolving Security and Privacy Requirements Engineering (ESPRE). IEEE, 2014. http://dx.doi.org/10.1109/espre.2014.6890521.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Beckers, Kristian, Maritta Heisel, Isabelle Cote, Ludger Goeke, and Selim Guler. "Structured Pattern-Based Security Requirements Elicitation for Clouds." In 2013 Eighth International Conference on Availability, Reliability and Security (ARES). IEEE, 2013. http://dx.doi.org/10.1109/ares.2013.61.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Williams, Imano. "An Ontology Based Collaborative Recommender System for Security Requirements Elicitation." In 2018 IEEE 26th International Requirements Engineering Conference (RE). IEEE, 2018. http://dx.doi.org/10.1109/re.2018.00060.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Al-Zawahreh, Hanan, and Khaled Almakadmeh. "Procedural Model of Requirements Elicitation Techniques." In IPAC '15: International Conference on Intelligent Information Processing, Security and Advanced Communication. New York, NY, USA: ACM, 2015. http://dx.doi.org/10.1145/2816839.2816902.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Security Requirement Elicitation' for particular source types:
Journal articles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography