Towards Ontology-based SQA Recommender for Agile Software Development

Agility is heavily dependent on tacit knowledge, skilled and motivated employees, and frequent communications. Although, the Agile Manifesto claims fast and light software development process while maintaining high quality, it is however not very clear how current agile practices and methods attain quality under time pressure and unstable requirements. In this paper, we present an ontological approach for process-driven Quality Assurance support for agile software development. Challenges related to the role of Quality Assurance in agile projects are addressed by developing a process-driven recommender that provides tailored resources to user’s queries. The proposed ontological model embeds both conceptual and operational SQA knowledge about software processes and their requirements, including quality attributes, SQA measurements, SQA metrics and related SQA techniques and procedures

INTEGRATION OF SOFTWARE SAFETY ASSURANCE PRINCIPLES WITH AN AGILE DEVELOPMENT METHOD

Agile software development has had success in different domains. However there is one area where the implementation of agile methods still needs significant development – that is in the field of agile and safety-critical system development. In this field, software engineering processes need to be justified against the requirements of software safety assurance standards (such as ISO 26262 in the automotive domain). It is therefore important that agile development processes can be justified to levels of assurance equivalent to that provided by traditional development approaches. While there is existing literature concerning the integration of agile methods with specific safety-critical system development standards and agile methods, the question of how fundamental software safety assurance principles can be addressed within agile methods has received little attention. In this thesis we describe the results of practitioner surveys that highlight the primary concerns regarding the use of agile methods within safety-critical development. In the context of this survey, and of existing work on software safety assurance principles, we then present an initial proposal as to how assurance could be addressed with an existing agile development method – Scrum. This proposal was submitted to practitioners for initial feedback and evaluation. The results of this evaluation are also presented

Examining the relationship between agile adoption motivation factors and agile practice clusters used by software startups in Kingdom of Saudi Arabia

Agile software development methodology (ASDM) has been increasingly adopted in organizations. Despite many benefits offered by ASDM, successful ASDM adoption is a big challenge for organizations. Many studies show that these methods were adopted partly by selecting a set of agile practices. Therefore, it is difficult for new adopters to choose agile practice sets that fit their organization needs as ASDM has a big pool of available practices or clusters. Agile practices should be selected based on motivation factors that include the organization needs in order to maximize the benefit of adopting them. The aim of this study is to identify the relationships between organization’s ASDM adoption motivation factors and the agile practices clusters. This study used a quantitative approach to evaluate the relationships between these variables. The study was conducted using a questionnaire with 76 software practitioners from software startups in the Kingdom of Saudi Arabia (KSA). The analysis generated 4 clusters; each is associated with a list of practices. These clusters are labeled as project management, quality assurance, software process, and incremental and iterative clusters. This study finds that three adoption motivation factors (a motivation for increased software quality, increased efficiency, or increased effectiveness) are associated with the quality assurance, software process, and incremental and iterative clusters. By understanding these factors in terms of ASDM adoption and which types of agile practice cluster is more suitable will help to increase the success of the agile adoption process. Furthermore, the study will help to understand how the startups selected the practices used. Also, the study could help new startups to easily choose the proper agile practices based on their motivation and needs. The findings will help the organization to select suitable agile practices cluster by matching the motivation factors that correspondingly affect the ASDM successful adoption

INFORMATION SECURITY IN AGILE SOFTWARE DEVELOPMENT PROJECTS: A CRITICAL SUCCESS FACTOR PERSPECTIVE

The importance of information security in software development projects is long recognised, with many comprehensive standards and procedures in use to provide assurance of information security. The agile development paradigm conflicts with traditional security assurance by emphasising the delivery of functional requirements and a reduction in structured and linear development styles. Through a series of thirteen qualitative interviews, this study identifies practices that address this problem which have been successfully adopted by agile practitioners. The findings present four categories of practices – organisational, team, project, and technical – and twelve critical success factors that should be explicitly considered by practitioners to assure agile security. The critical success factors provide a foundation for practitioners to strategically identify and develop best practices to embed information security in agile development projects. The identified categories also highlight the importance of agile security practices centring around individuals and culture and contributes to the literature by providing a representation of agile security practices that encompasses a broad range of focal areas

Agile Approach to Adding Assurance and Mitigating Overall Mission Risk for Orion Software on EM-1

Human-rated missions like Orion are becoming exceedingly complex in terms of software contribution to achieving mission objectives, and this creates a resource challenge for everyone whose job is to add assurance that the mission is going to fly safely. Orion IV&V has addressed this challenge by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V was evaluating areas of risk in much broader, and more static, terms. Due to the Agile software development cycle that Orion follows, IV&V findings were often reported months out of phase with the developer. As a result of evolving the approach to providing assurance on Orion, IV&V is able to incrementally deliver high-priority assurance data and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This presentation will discuss the principles which drive the design of our approach, results to date, and aspirations for long-term performance

Quality assurance in agile safety-critical systems development

© 2016 IEEE. In this position paper we examine how safety could be assured when increasingly complex systems are developed using agile software development methods. We first discuss the source and nature of complexity in software systems and how a probe - sense - learn approach recommended by the Cynefin Framework is appropriate for designing complex systems and a sense - analyse - learn approach is appropriate for developing a complicated system whose design has been determined. We then examine how quality assurance is incorporated into agile software development before pointing out that those characteristics of a self-managed team that produce so many benefits for software development of complex systems whose solution evolves with problem understanding, are also vulnerable to confirmation bias. This suggests that for safety critical system development, software systems developed by agile teams will need verification and validation by independent parties. We review current quality management practices for medical device software development before discussing how our earlier findings could be adopted into safety critical software quality management

Software Quality Assurance and Android Application Development: A Comparison among Traditional and Agile Methodology

This paper focuses on software quality assurance in android application development with focus on approaches to confirm software quality in android applications. In this work, we compare the waterfall model with agile-scrum methodologies to realize software quality assurance with special focus on mobile applications. This research allows us to answer, “Which process model and practices are available for android software development along with focus on quality assurance?” The other research focus in this paper is “How auditors, developers and testers play their defined roles to maintain quality in mobile application development?” Agility for software development has transformed into a preferred and favored method for mobile application development. The major aim of this research is to contribute for a better knowledge for mobile application development methodologies practiced by the organizations for the development of applications based on systematic literature review

Software Quality Assurance Using Agile Software Methodology in Education Assessment Industry

Contradictory directive between federal and state along with expensive investments in assessment strategies that may no longer work with new standards were just a few issues making educational assessment increasingly complicated. With evolution of rapid changing environment following student assessment practice, policy and analysis can be tough. This capstone project helped to build reliable and quality online solution which assisted to guard against system failures and scoring errors, and hold itself accountable for the security of the assessment process with use of cutting edge technology such as Agile in which incremental and iterative development of product through various cycles or feedback with involvement of cross functional and self-managing team helps to achieve product improvement

Software Quality Assurance Using Agile Software Methodology in Education Assessment Industry

Contradictory directive between federal and state along with expensive investments in assessment strategies that may no longer work with new standards were just a few issues making educational assessment increasingly complicated. With evolution of rapid changing environment following student assessment practice, policy and analysis can be tough. This capstone project helped to build reliable and quality online solution which assisted to guard against system failures and scoring errors, and hold itself accountable for the security of the assessment process with use of cutting edge technology such as Agile in which incremental and iterative development of product through various cycles or feedback with involvement of cross functional and self-managing team helps to achieve product improvement

Agile Approach to Assuring the Safety-Critical Embedded Software for NASA's Orion Spacecraft

Human-rated missions like NASA's Exploration Mission - 1 (EM-1) and the Orion Multi-Purpose Crew Vehicle are becoming exceedingly complex in terms of software's contribution to achieving mission objectives. The increasing complexity and inherent safety critical nature of the embedded flight software imposes a unique resource challenge to assurance providers responsible for affirming that the mission is going to fly safely. Another challenge NASA and other Government agencies are facing is that more and more software is being developed using an agile development methodology, which is divergent from the typical waterfall, iterative, and incremental development methodologies assurance providers generally observe in the development of safety-critical embedded software. Orion Independent Verification and Validation (IV&V) has addressed these challenges by providing focused assurance results of critical mission capabilities prioritized by a dynamic assessment of risk level. Prior to this approach, Orion IV&V evaluated areas of risk in much broader, and more static, terms. Due to the agile software development life cycle that Orion follows, IV&V findings were often reported months out of phase with the developer thereby imposing increased rework costs. As a result of evolving the approach to adding assurance on Orion, IV&V is able to incrementally deliver high-priority assurance conclusions and more impactful issues more in phase with the developer activities, thereby increasing the value of the findings to the project. The agile IV&V approach employed by the Orion IV&V team strives to achieve a cadence of delivery that matches the pace of development. This agile approach provides increased flexibility for the assurance provider to become more efficient in reporting assurance conclusions and issues. This paper and presentation will discuss the principles which drive the design of our approach, results to date, and stimulate thinking for groups looking to add assurance to software being developed using an agile methodology