A Security Evaluation Framework for U.K. E-Government Services Agile Software Development

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Download Full-text

Enabling and Limiting factors in eXtreme Programming (XP) with Evaluation Framework

SCITECH Nepal ◽

10.3126/scitech.v14i1.25534 ◽

2019 ◽

Vol 14 (1) ◽

pp. 50-62

Author(s):

Sundar Kunwar

Keyword(s):

Software Development ◽

Software Process Improvement ◽

Agile Software Development ◽

Evaluation Framework ◽

Extreme Programming ◽

Limiting Factors ◽

Project Characteristics ◽

Different Shapes ◽

Software Development Methodologies ◽

Agile Software

As agile software development methodologies are used in many domains and come with different shapes and sizes, it is one of the complex human endeavors. Extreme Programming (XP) is one of the well-known agile software development methodologies and is driven by a set of values including simplicity, communication, feedback and courage, but lacks the mechanism to measure these values demanding the evaluation framework to make it measurable and attainable. The main aim of this study is to build the software process improvement model that can be used for evaluating XP values and practices. The proposed XP evaluation framework in this study is XP focused and evaluates the XP project, product and practices. The XP evaluation framework is a collection of some new and validated metrics used for evaluating XP projects, XP practices, XP products and some additional factors concerned with XP. The evaluation framework for extreme programming is basically based on the assessment and evaluation of various project characteristics, extreme programming characteristics, product characteristics and other additional characteristics. The metrics used for assessments and evaluations of XP are designed to be simple, precise, understandable, economical, timely, consistent, accountable, unambiguous, suitable and reliable.

Download Full-text

Security Assurance in Agile Software Development Methods

Exploring Security in Software Architecture and Design - Advances in Information Security, Privacy, and Ethics ◽

10.4018/978-1-5225-6313-6.ch003 ◽

2019 ◽

pp. 47-68

Author(s):

Kalle Rindell ◽

Sami Hyrynsalmi ◽

Ville Leppänen

Keyword(s):

Software Development ◽

Agile Software Development ◽

Evaluation Framework ◽

Agile Methods ◽

Software Projects ◽

Security Engineering ◽

Security Incident ◽

Security Assurance ◽

Agile Software ◽

Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Download Full-text