A Tagging Approach to Extract Security Requirements in Non-Traditional Software Development Processes

Tetmeyer, Annette; Hein, Daniel; Saiedian, Hossein

doi:10.4018/ijsse.2014100102

Cited by 4 publications

(4 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Justification: In cases where ASD teams, customers, and management have limited knowledge regarding QRs, they may not recognize, specify, and handle QRs properly. ASD teams may ignore and not document QRs until there is a specific request for handing them or until the impact of neglecting QRs becomes visible [5], [6], [10], [11], [38], [39].…”

Section: ) Recognize the Significance Of Qrsmentioning

confidence: 99%

“…For instance, customers in the energy domain may overlook important QRs such as security [41]. Related Work: [5], [6], [8], [10], [30], [38]- [41] 2) RECOGNIZE THE NEED FOR OPTIMAL DOCUMENTATION OF QRs Description: Agile teams should acknowledge the need for optimal documentation of QRs (i.e., a satisfactory level of QR documentation that will not compromise agility and product quality). They should take actions to meet the need for optimal documentation of QRs and start documenting QRs at early stages.…”

Section: ) Recognize the Significance Of Qrsmentioning

confidence: 99%

See 1 more Smart Citation

Quality Requirement Documentation Guidelines for Agile Software Development

2022

View full text Add to dashboard Cite

In agile software development (ASD), where minimal documentation and rapid delivery are the focus, Quality requirements (QRs) are often underspecified and not documented. Guidelines supporting QR documentation task are scarce. The study developed the Agile QR-Doc QR documentation guidelines, which aim to support QR documentation in ASD. We applied a design science research methodology (DSRM) to build the Agile QR-Doc. We used a survey questionnaire and open discussion with ten software practitioners, from two ASD companies to validate the Agile QR-Doc. The practitioners evaluated the guidelines in terms of usefulness, relevance, understandability, and coverage of important aspects for supporting QR documentation and their impact on the agility of the software development process. Agile QR-Doc list 12 recommendations that are grouped into two categories. The first category introduces three recommendations that focus on raising awareness about the significance of QRs, their documentation and related challenges. The second category lists nine recommendations that introduce artifacts, practices and important aspects for documenting QRs. The validation reveals the relevance, understandability and usefulness of the guidelines to support QR documentation in ASD. It also indicates that the guidelines consider important aspects for documenting QRs and that they do not negatively affect the agility of the software development process. Practitioners can utilize the practices, artifacts and knowledge from the guidelines to support QR documentation in ASD. Researchers can benefit from the knowledge on QR documentation in ASD, and application of DSRM in building artifacts.INDEX TERMS Agile software development, design science, documentation, quality requirement.

show abstract

Section: ) Recognize the Significance Of Qrsmentioning

confidence: 99%

Section: ) Recognize the Significance Of Qrsmentioning

confidence: 99%

Quality Requirement Documentation Guidelines for Agile Software Development

2022

View full text Add to dashboard Cite

show abstract

“…We also noticed that in ASD, QR awareness of both practitioners and customers affect documentation. The lack of QR awareness by customers is a challenge in ASD [5], [27]. When considering practitioners, QR awareness may be seen a necessity for roles such as project managers and product owners and deemed less important for developers in some cases.…”

Section: B Factors Influencing Documentation Of Qrs In Asdmentioning

confidence: 99%

How agile software development practitioners perceive the need for documenting quality requirements: a multiple case study

Behutiye

Rodríguez

Oivo

et al. 2020

2020 46th Euromicro Conference on Software Engineering and Advanced Applications (SEAA)

View full text Add to dashboard Cite

Agile software development (ASD) promotes minimal documentation and often prioritizes functional requirements over quality requirements (QRs). This may be beneficial in reducing the time to market of software. When considering QRs in ASD, the minimal documentation practice may be seen as a concern since QRs determine the success of software projects and are as well not easy to specify and document. Nevertheless, what do practitioners think of the necessity of documenting QRs in ASD? How do they perceive factors that may affect documentation of QRs in ASD? We conducted a multiple case study of three cases applying ASD, involving 12 participants. ASD practitioners identify that it is important to document QRs, and perceive that it contributes to ensuring quality, clarifying QRs, and helping in decision making. Time constraint, QR awareness and communication gaps on QRs influence the documentation of QRs in ASD. ASD teams may align their documentation practices to fit the sprint duration. The influence of QR awareness on documentation was dependent on project context and roles. Communication gaps can create confusion on QRs. Missing and outdated QR documentation may result in accruing technical debt, and lack of common understanding on QRs. The study synthesizes empirical evidence on the significance of documenting QRs in ASD and provides an insight into factors affecting documentation of QRs in ASD.

show abstract

“…Tetmeyer et al . introduce a new approach for capturing such security requirements early in the development.…”

Section: Next‐generation Features and Their Security Risksmentioning

confidence: 99%

Security in automotive telematics: a survey of threats and risk mitigation strategies to counter the existing and emerging attack vectors

Oyler

Saiedian

2016

Security Comm Networks

Self Cite

View full text Add to dashboard Cite

This manuscript surveys a variety of topics related to the security of connected vehicles and their associated services, often referred to as telematics. Current challenges as well as emerging and future security risks are discussed. A number of specific technologies and implementations are discussed, such as Next Generation Telematics Patterns, KeeLoq, vehicular ad hoc networks, and controller area network. Principles and practices are outlined to counter or minimize risks associated with the existing and potential attack vectors as well as reducing risks both on the internal vehicle network and the telematics service delivery platforms.

show abstract

A Tagging Approach to Extract Security Requirements in Non-Traditional Software Development Processes

Cited by 4 publications

References 10 publications

Quality Requirement Documentation Guidelines for Agile Software Development

Quality Requirement Documentation Guidelines for Agile Software Development

How agile software development practitioners perceive the need for documenting quality requirements: a multiple case study

Security in automotive telematics: a survey of threats and risk mitigation strategies to counter the existing and emerging attack vectors

Contact Info

Product

Resources

About