Incorporating Security Requirements Engineering into the Dynamic Systems Development Method

Mead, Nancy R.; Viswanathan, Venkatesh; Padmanabhan, Deepa

doi:10.1109/compsac.2008.85

Cited by 19 publications

(9 citation statements)

References 2 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Benefícios reportados pelo uso de métodos ágeis relacionados às atividades de ER envolvem melhoria da comunicação e compreensão das necessidades, redução da ambiguidade e capacidade de responder a mudanças. Foram identificadas ainda lições aprendidas reportados nos trabalhos analisados, tais como, o fato de se utilizar diferentes técnicas de elicitação auxilia no levantamento dos requisitos ( [8], [22], [30] e [36]); a adoção de práticas da ER tradicional e com práticas ágeis traz resultados positivos ( [7], [14], [15] e [17]); assim como faz surgir um perfil de profissional com características híbridas entre os dois modelos ( [7] e [44]).…”

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

“…Em termos de produtos de trabalho, Schön, Thomaschewski, e Escalona[36] identificaram que os principais artefatos utilizados nos métodos ágeis são: histórias de usuário, protótipos, casos de uso e cartões de histórias. Outros autores,[14],[30] e[36], citam que os requisitos podem estar documentados nos casos de testes. Apesar desta variedade de produtos de trabalho, quando há prejuízo da documentação em projetos que usam métodos ágeis, conhecimentos importantes podem ser perdidos durante e após o desenvolvimento do sistema[35].…”

unclassified

See 1 more Smart Citation

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

Belo Horizonte -MG -Brasil mwerneck@pucminas.br RESUMOPor não possuírem características prescritivas, não há, nos métodos ágeis, uma definição formal sobre como as atividades de Engenharia de Requisitos (ER) devem ser executadas. Isso faz com que haja uma variedade de formas de se definir como serão levantados, priorizados, especificados e validados os requisitos. Assim, torna-se necessário compreender como as pesquisas em ER ágil têm caracterizado estas atividades. O objetivo deste trabalho foi, por meio de uma revisão sistemática da literatura, identificar as práticas e técnicas utilizadas para cada processo da ER em projetos ágeis. O trabalho identificou ainda importantes desafios e lições aprendidas que devem direcionar as evoluções nesta área. ABSTRACTSince agile methods do not have prescriptive characteristics, there is not a formal definition on how Requirements Engineering (RE) activities should be executed. This situation leads to a variety of different forms of defining how requirements are elicited, prioritized, documented and validated. So, it is necessary to comprehend how research on RE have characterized such activities. By using a systematic review approach, the objective of this study was to identify practices and techniques that have been used for each RE process in agile projects. The study also identified challenges and lessons learned that should direct improvements in this area. CCS Concepts• Software and its engineering Software creation and management Software development process management Agile software development • Software and its engineering Software creation and management Designing Software Requirements Analysis.

show abstract

Section: Tabela 2 Distribuição Dos Métodos Deunclassified

unclassified

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Fraga

Barbosa

2017

Anais Do Simpósio Brasileiro De Sistemas De Informação (SBSI)

View full text Add to dashboard Cite

show abstract

“…Most of the software development methodologies are more focusing on how to speed up the development of the product with functional requirements but the above methodologies have inability to elicit nonfunctional requirements as the primary artifacts. [17] [18]. In the traditional approach they are treating the NFRs as secondary artifacts [19] [20] [21] [22].…”

Section: Importance Of Non Functional Requirements Eliciation Anmentioning

confidence: 99%

Design of Patient Monitoring System(PMS) Application using Security Design Patterns in Architecture Phase of Secure SDLC

Aruna¹,

Reddy²,

Sunitha³

2016

IJMTER

View full text Add to dashboard Cite

A successful Software product is achieved through fulfillment of all the functional Requirements and nonfunctional Requirement (NFR)s. In SDLC the design decisions must be resolved by encompassing the functional requirement along with the nonfunctional requirements at early stages to avoid the problems in further evolving stages. This paper focuses on representation of NFR (security) in architecture phase of Software Development Life Cycle (SDLC) and proposes a methodology to include security feature using security design patterns. We believe "Security design patterns representation in Architecture phase as a resistant tool to insecure features". This enables the software development team understanding to reconcile the software's requirements and the architecture in the context of security. Including of security features as security patterns in Architecture phase makes the product more secure in further phases, by making this we can redefine the SDLC as secure SDLC. As a case study we have illustrated this methodology to Patient Monitoring System (PMS) Application.

show abstract

“…The SWEBOK Guide can refer to the Security Quality Requirements Engineering (SQUARE) methodology, which consists of nine steps that generates a final deliverable of categorized and prioritized security requirements (Mead, Hough, & Stehney, 2005). Papers on incorporating security requirements engineering into the dynamic systems development method and into the rational unified process have also been presented at conferences (Mead, Venkatesh, & Padmanabhan, 2008;Mead, Venkatesh, & Zhan, 2008).…”

Section: Suggestions For Enhancing the Swebok Guidementioning

confidence: 99%

Secure Software Engineering: A New Teaching Perspective Based on the SWEBOK

Talib¹,

Khelifi²,

Jololian³

2010

IJIKM

View full text Add to dashboard Cite

Lack of a suitable set of controls during the development life cycle of software will lead to mistakes in the requirements, design, or code of software and, therefore, result in significant security vulnerabilities. This paper proposes a software engineering course from the security perspective, which can be taught at both the undergraduate and graduate levels. It will prepare students to successfully cope with the technical challenges as well as the non technical issues associated with the software development process, while integrating security into each phase of the process. The course materials are derived from the Guide to the Software Engineering Body of Knowledge (SWEBOK) published by the IEEE Computer Society with the support of a consortium of industrial sponsors.

show abstract

Incorporating Security Requirements Engineering into the Dynamic Systems Development Method

Cited by 19 publications

References 2 publications

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

A Engenharia de Requisitos nos métodos ágeis: uma revisão sistemática da literatura

Design of Patient Monitoring System(PMS) Application using Security Design Patterns in Architecture Phase of Secure SDLC

Secure Software Engineering: A New Teaching Perspective Based on the SWEBOK

Contact Info

Product

Resources

About