Search

Agile methods have been widely adopted by the industry and its teaching has seen a surge, particularly in the software development field. However, these methods have a number of limitations which affect product outcomes, such as the fact that many software development companies now use Scrum to get developers to work without interruption between iterations, rather than to maintain a sustainable rhythm. Agile experts have stated the importance of incorporating creativity into Scrum, and although there are several agile resources that help with the learning process, it seems essential to approach such learning from a practical point of view. Furthermore, none of these resources introduce creativity. In this paper, we present an educational resource in the form of a serious game that allows you to acquire all the key concepts of agile and creative methods. The game is based on the use of LEGO pieces to simulate a real project, applying the key concepts of the Scrum and Design Thinking frameworks in a gamified way. It was assessed in a professional training centre of computer science by using surveys through which participants evaluated their previous knowledge of agile and creativity methods. We analysed the improvement of these competences, as well as the general level of satisfaction with the game. After the game, the results showed that the participants' knowledge of the Scrum and Design Thinking frameworks had improved and that they were very satisfied with the whole experience. [ABSTRACT FROM AUTHOR]

Different software development approaches (SDAs) are developed with broad portfolios of development processes. Each of the approaches has certain exclusive principles, practices, thinking, and values, which are informally represented, implemented, and improperly institutionalized. Ontologies are developed for the representation, assessment, and adaptation of SDAs separately without having a shared terminology which may lead to terminological conflict and confusion affecting the simultaneous representation and implementation in software development industry and academia. The software engineering approaches does not consider and support sustainability as priority concern. However, the approaches have capabilities of supporting sustainable software development in different sustainability aspects. This research article aims for the designing and development of an integrated ontology of software engineering approaches (i.e., agile, lean, and green) named OntoSuSD (ontology for sustainable software development) to support sustainable software development knowledge, awareness, and implementation. The goal of OntoSuSD is to propose, design and develop a formal, generic, consistent, and shared knowledge base containing semantic terminology and description of concepts and relationships generated around the representation and implementation of lean, agile, and green approaches in software development processes, which will facilitate their simultaneous implementation and assessment for sustainable software development. The OntoSuSD is developed using practical ontology engineering methodology by reusing relevant ontologies and explicit concepts and properties are defined to fulfill knowledge requirements and representations of the domain. The OntoSuSD is evaluated, and results infer OntoSuSD has high ontological design, good domain coverage, potential applications and achieves purpose of the ontology development. [ABSTRACT FROM AUTHOR]

Application security is an important concern, and security activities to support software development lifecycle processes, such as specification, design, implementation, and testing are increasingly in need. Despite the plethora of knowledge available for secure software development in online and books, software systems are seldom secure as developers lack security knowledge. The primary reason for this paradox is the diversity and overwhelming nature of the available security knowledge. In this article, we propose to synthesize the well‐known secure software development practices for both linear and agile lifecycle models. Using the MediaWiki platform, we make this knowledge available to software developers and designers from a single source. [ABSTRACT FROM AUTHOR]

We live at an exciting time where software has become a dominant aspect of our everyday life. Although software provides opportunities for improving various aspects of our society, it also presents many challenges. One of them is development, deployment, and sustaining of high quality software on a broad scale. While agile methods (Scrum being one of the most prominent examples) ease the process, their popularity deteriorates the clarity and simplicity they were once meant to bring into software development. This article explores the synergy of Scrum and Essence, a domain model of software engineering processes, intending to become a common ground for software development methods, bringing clarity into the composition of methods from individual practices. This short communication motivates the interplay of Scrum and Essence, being accompanied with a set of videotutorials and 21 Scrum Essential cards to further guide more effective team's way of working. [ABSTRACT FROM AUTHOR]

Summary Though some software development teams are highly effective at delivering security, others either do not care or do not have access to security experts to teach them how. Unfortunately, these latter teams are still responsible for the security of the systems they build: systems that are ever more important to ever more people. We propose that a series of lightweight interventions, six hours of facilitated workshops delivered over three months, can improve a team's motivation to consider security and awareness of assurance techniques, changing its security culture even when no security experts are involved. The interventions were developed after an Appreciative Inquiry and Grounded Theory survey of security professionals to find out what approaches work best. We tested the interventions in a participatory action research field study where we delivered the workshops to three software development organizations and evaluated their effectiveness through interviews beforehand, immediately afterwards, and after twelve months. We found that the interventions can be effective with teams with limited or no security experience and that improvement is long‐lasting. This approach and the learning points arising from the work here have the potential to be applied in many development teams, improving the security of software worldwide. [ABSTRACT FROM AUTHOR]

This paper discusses the applicability of agile methods to aircraft embedded software development. It presents the main results of an experiment that combines agile practices from Scrum with model-based development and distributed development. The experiment consists of the development of an aircraft cockpit display system divided in five distributed teams. Three features are analysed and quantified, using the output artefacts of each team: the artefacts' quality, the adherence to agile methods, and the adherence to standard DO-178C. The main conclusion of the experiment is that there is a high correlation between the adherence to agile methods and the artefacts' quality, motivating the use of agile methods in aircraft industry. Also, the experiment evinced that agile methods does not specifically address the integration of distributed teams and the hardware/software integration. This lacuna affects the artefacts' quality. The results of the experiment emphasize the importance of concentrating future work in the proposal of specific agile practices for these activities. [ABSTRACT FROM AUTHOR]

The article discusses a study which investigated a mature Scrum team in a large organization and their interactions with the User Experience (UX) designers working on the same project. Particular focus is given to the difference between agile development and UX design methods for software development. Results of the study showed that ongoing articulation work by developers have led to cooperation between Agile developers and UX designers. Findings also revealed the themes which centre around the types of activities allowing the transformation of paper-based UX designs into working software.

The article discusses a study which examined whether agile methods are inappropriate for safety-critical software development. It cites the need for a process that ensures a high level of software reliability when introducing software technology in a life-dependent environment. It notes that agile methods are flexible and focus on continuous process management and code-level quality. Particular focus is given to experiences on the image-guided surgical toolkit (IGSTK), which is an open source software project that employs agile practices. It mentions the adoption of IGSTK by teaching hospitals and research labs.

The article discusses various topics related to agile software development including "Agile Methods for Safety-Critical Open Source Software," "User Experience Design and Agile Development: Managing Cooperation Through Articulation Work" and "Measuring the Flow in Lean Software Development."