Agile Software Development

2012 ◽  
pp. 1-15
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Implementation Team ◽  
Agile Methodologies ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

scholarly journals Agile Software Development

2010 ◽  
Vol 1 (3) ◽  
pp. 71-85 ◽  
Author(s):  
Torstein Nicolaysen ◽  
Richard Sassoon ◽  
Maria B. Line ◽  
Martin Gilje Jaatun
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Development Effort ◽  
Implementation Team ◽  
Development Organizations ◽  
Development Lifecycle ◽  
Software Development Lifecycle ◽  
Agile Software

In this article, the authors contrast the results of a series of interviews with agile software development organizations with a case study of a distributed agile development effort, focusing on how information security is taken care of in an agile context. The interviews indicate that small and medium-sized agile software development organizations do not use any particular methodology to achieve security goals, even when their software is web-facing and potential targets of attack. This case study confirms that even in cases where security is an articulated requirement, and where security design is fed as input to the implementation team, there is no guarantee that the end result meets the security objectives. The authors contend that security must be built as an intrinsic software property and emphasize the need for security awareness throughout the whole software development lifecycle. This paper suggests two extensions to agile methodologies that may contribute to ensuring focus on security during the complete lifecycle.

Agile Enablers and Adoption Scenario in Industry Context

2015 ◽  
pp. 157-178
Author(s):  
Vinay Kukreja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
User Requirements ◽  
Distributed Environment ◽  
Team Members ◽  
Agile Methodologies ◽  
Software Development Methodologies ◽  
Agile Software

In the globalization of fast changing business and technology environment, it becomes very important to respond quickly to changing user requirements. Traditional methodologies are not appropriate for the projects where user requirements are not fixed. Agile methodologies have been developed to cope up with user changing requirements and emphasize more on working software and customer collaboration. Agile is an umbrella term and it is used for many software development methodologies which shares common characteristics. This chapter mainly focuses on the working methodology of agile development and the usage areas of industry where agile development is implemented. Agile software development is difficult in distributed environment as the team members are at distributed locations. This chapter discusses agile industry applicability enablers which are useful for agile software development in distributed environment.

Threat Modeling in Agile Software Development

2022 ◽  
pp. 480-490
Author(s):  
Martin Gilje Jaatun ◽  
Karin Bernsmed ◽  
Daniela Soares Cruzes ◽  
Inger Anne Tøndel
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Risk Assessments ◽  
Limited Resources ◽  
Agile Development ◽  
Security Testing ◽  
Threat Modeling ◽  
Development Organizations ◽  
Agile Software

Threat modeling is a way to get an overview of possible attacks against your systems. The advantages of threat modeling include tackling security problems early, improved risk assessments, and more effective security testing. There will always be limited resources available for security, and threat modeling will allow you to focus on the most important areas first. There is no one single “correct” way of doing threat modeling, and “agile” is no excuse for not doing it. This chapter describes the authors' experiences with doing threat modeling with agile development organizations, outlining challenges to be faced and pitfalls to be avoided.

Case Study: Applying an Agile Development Methodology to XML Schema Construction

2016 ◽  
Author(s):  
Dianne Kennedy
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Xml Schema ◽  
Third Party ◽  
Agile Development ◽  
Print Quality ◽  
Brand Quality ◽  
Measurement Tools ◽  
Agile Software

To assure brand integrity, brands such as Coca-Cola and Proctor & Gamble, assisted by third party brand quality experts, receive, score and track the quality of their print suppliers over time. Currently this is difficult and expensive because printers use many different measurement tools and report print quality using a wide variety of proprietary formats that cannot be directly utilized by brand scoring and tracking systems. In 2015 Idealliance members launched an effort to develop a standard XML-based print quality exchange message. This specification, known as Print Quality eXchange (PQX), was developed by applying agile software development techniques to the construction of the PQX XSD. This case study highlights how agile software development principles can be applied to the construction of an XML schema.

scholarly journals Towards Adopting Software Quality Assurance in Agile Development Methodology

2021 ◽  
Vol 12 (3) ◽  
pp. 2152-2157
Author(s):  
Rosnani Shuib Et.al
Keyword(s):  
Quality Assurance ◽  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Agile Methodology ◽  
Agile Methodologies ◽  
Development Methodology ◽  
Quality Assurance Mechanism ◽  
Software Product ◽  
Agile Software

In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product.  However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology.  Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.

Threat Modeling in Agile Software Development

2019 ◽  
pp. 1-14 ◽  
Author(s):  
Martin Gilje Jaatun ◽  
Karin Bernsmed ◽  
Daniela Soares Cruzes ◽  
Inger Anne Tøndel
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Risk Assessments ◽  
Limited Resources ◽  
Agile Development ◽  
Security Testing ◽  
Threat Modeling ◽  
Development Organizations ◽  
Agile Software

Threat modeling is a way to get an overview of possible attacks against your systems. The advantages of threat modeling include tackling security problems early, improved risk assessments, and more effective security testing. There will always be limited resources available for security, and threat modeling will allow you to focus on the most important areas first. There is no one single “correct” way of doing threat modeling, and “agile” is no excuse for not doing it. This chapter describes the authors' experiences with doing threat modeling with agile development organizations, outlining challenges to be faced and pitfalls to be avoided.

Software Maintainability Estimation in Agile Software Development

2022 ◽  
pp. 1002-1017
Author(s):  
Parita Jain ◽  
Arun Sharma ◽  
Laxmi Ahuja
Keyword(s):  
Software Development ◽  
Fuzzy Inference ◽  
Agile Software Development ◽  
Agile Development ◽  
Quality Factors ◽  
Agile Methodologies ◽  
Neuro Fuzzy ◽  
Software Maintainability ◽  
Agile Process ◽  
Agile Software

Agile methodologies have gained wide acceptance for developing high-quality products with a quick and flexible approach. However, until now, the quality of the agile process has not been validated quantitatively. Quality being important for the software system, there is a need for measurement. Estimating different quality factors will lead to a quality product. Also, agile software development does not provide any precise models to evaluate maintainability. Therefore, there is a need for an algorithmic approach that can serve as the basis for estimation of maintainability. The article proposes an adaptive neuro-fuzzy inference system (ANFIS) model for estimating agile maintainability. Maintainability is one of the prominent quality factors in the case of agile development. The proposed model has been verified and found to be effective for assessing the maintainability of agile software.

scholarly journals Enabling the Usability Heuristics of Agile Base Systems to Improve Quality of Local Software Industry

2019 ◽  
Vol 38 (2) ◽  
pp. 341-350 ◽  
Author(s):  
Kiran Saeed ◽  
Yaser Hafeez ◽  
Sadia Ali ◽  
Muhammad Usman Shahid ◽  
Naila Iqbal
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Software Products ◽  
Agile Methodologies ◽  
Proposed Model ◽  
Interaction Interaction ◽  
Agile Software ◽  
Software Development Practices

Many agile software development practices are promoted to improve the quality of software products. In recent years agile software development overlooked the usability features that effected system productivity.Usability is a main feature of interaction. Interaction is a way of a farming relationship between people and designed objects. An interactive model provides the way to band application together to achieve target user’s need. Usability gained attention of researchers and engineers because of its own importance. Agile software methods and usability engineering played a major role for producing better and reliable products, because both of them are concepts of methods as well as practices. The purpose of this research was to highlight the need of usability practices. The proposed model demonstrates that usability heuristics were much compatible with agile methodologies and would help to improve its productivity by reducing time and cost. Action research was applied for the development of framework proposed. The framework was evaluated using case study and further results were compared with existing related work.

Sign in / Sign up

Export Citation Format

Share Document