eXtreme Programming, Agile Methodologies, Software Project Management, Customer Role, Rigorous Testing

Agile software development methodologies are attracting attention from academics and practitioners for planning and managing software projects. The eXtreme Programming (XP) challenges conformist wisdom regarding software system development processes and practices as agile methodologies. To work efficiently in the current software development practice, characterized by requirements fuzziness, XP moves away from document-centric operations into people-centric management. In the XP-based software project, the customers play an essential role, having multiple responsibilities such as driving the project, gathering requirements (‘user stories'), and exercising quality control (or acceptance testing). Besides, the customers must liaise with external project stakeholders (e.g., funding authorities, end-users) while maintaining the development team's trust and the wider business. The success of such software project management practices relies on the quality result of each stage of development obtained through rigorous testing. This chapter describes three characteristics of XP project management: customer role, software testing feedback, and learning.

Adaptation of Modern Agile Practices in Global Software Engineering

Software engineering has been an active working area for many decades. It evolved in a bi-folded manner. First research and subsequently development. Since the day of its inception, the massive number of variants and methods of software engineering were proposed. Primarily, these methods are designed to cater the time-varying need of modern approach. In this connection, the Global Software Engineering (GSE) is one of the growing trends in the modern software industry. At the same time, the employment of Agile development methodologies has also gained the significant attention in the literature. This has created a rationale to explore and adopt agile development methodology in GSE. It gained rigorous attention as an alternative to traditional software development methodologies. This paper has presented a comprehensive review on the adaptation of modern agile practices in GSE. In addition, the strength and limitation of each approach have been highlighted. Finally, the open area in the said domain is submitted as one of the deliverables of this work.

Security in Agile Development, use Case in Typeform

Software development methodologies have evolved during the last years to reduce the time to market to the minimum possible. Agile is one of the most common and used methodologies for rapid application development. As the agile manifesto defines in its 12 principles, one of its main goals is to satisfy the customer needs through early and continuous delivery of valuable software. Significantly, that none of the principles refers to security. In this paper, we will explain how Typeform integrates security activities into the whole development process, reducing at the same time the phases on the S-SDLC to reduce friction and improve delivery while maintaining the security level.

Agile Software Development Techniques: A Survey

In this IT era, where there is a race of software development, it is necessary to introduce such types of software development techniques which will help the practitioners to deliver fast solutions. In the past, various traditional approaches were used for this purpose, but now agile techniques are getting more popular because conventional software development approaches are not efficient in managing the changing requirements. The agile software development process is one of the most emerging lightweight software development methodologies, which uses iterative and prototype development approaches to accommodate changes in software requirements. Final software products are delivered to the end-users in short iterations. One of the most noticeable drawbacks of agile methods is their limited courtesy to the structured and architectural design of the system. Hence this development approach will restrict small to medium design decisions only. In this paper, we have performed the analysis of different agile techniques, which will help the readers to understand their positive and negative points and select the most appropriate technique suited to their projects.

Impact of Agile Methodology on Software Development Life Cycle

Software engineering strategies had been hired for decades to create software products. The most challenging task for the development of software is to select appropriate software development methodologies. Software developers use agile techniques to reduce the problems faced by the traditional waterfall process. These days, the motivation behind most programming associations is to give programming in a fast time, inside financial plan and changing situations that propelled the conveyance of Agile. The strategy that utilizes iterative expansion and prototyping is generally utilized in an assortment of industry ventures as a lightweight advancement method that could fulfil the alterations of necessities. Short cycles are utilized which can be required for proficient item delivery. In the paper, we become mindful of the impacts that the coordinated strategy has programming improvement strategies with prominence to decent inside the authoritative, efficient, and social system. Coordinated methods are not in every case great, they have a few restrictions too. In this paper, we likewise clarify the estimations of Agile, its points of interest, and its weaknesses.

Ontology-Based Transformation and Verification of UML Qualified Association

UML class model is an essential element of today's software development process. In modern software development methodologies, it is considered a key contributor in every phase of software development. It may be automatically converted into other UML models and even in programming code. However, the erroneous model generates other erroneous models. The model verification technique checks the presence of error in the UML class model. This paper's main objective is to introduce a technique for the completely automatic and expressive transformation of the UML class model's qualified association into ontology. Because the current verification method does not support the transformation and verification of qualified associations. Later on, the ontology-based reasoning method is presented to verify qualified associations and their constraints.

Software Development Methodologies, HEIs, and the Digital Economy

Progressing digitalization of business, economy, and the society places higher education institutions (HEIs) in the center of the debate on how to effectively respond to challenges and opportunities that are thus triggered. Several facets of this process and corresponding challenges exist, including the complex question of how to match students’ skills and competencies with the demands and expectations of the industry. From a different angle, considering the changing nature of work, HEIs are responsible for equipping future employees with skills necessary to work in virtual, distributed, culturally diverse, and frequently global, teams. In the domain of software development, i.e., the backbone of the digital world, the challenge HEIs need to face is paramount. For this reason, the way software development is taught at HEIs is crucial for the industry, for the economy, for the students, and for the HEIs. As there is a tendency in the industry to embrace the scrum method and seek employees equipped with skills necessary for the scrum methodology use, it is necessary to ensure that HEIs offer the students the opportunity to get exposed to scrum. By querying the challenges of switching to agile software development methodologies in senior capstone projects, this paper makes a case that software development and software development methodology form the thrust of a multi-stakeholder ecosystem that defines today’s digital economy and society. In this context, the added value of this paper rests in the elaboration of a method enabling HEIs to move toward scrum in senior projects.

Clinical Decision Support Systems

The BACIS program is an example of an e-health decision support system, and therefore a chapter focusing on the topic of decision support systems is needed as part of the background and context to the BACIS program study. The chapter begins with a discussion of the design of decision support systems. In this discussion, the software development methodologies used in their development is explained. Then various architectures for their design are considered. This is followed by a section on implementation of decision support systems in developing country contexts. The chapter closes with a discussion of the Clinical Decision Support (CDS) roadmap of the International Medical Informatics Association.

An Objective Compliance Analysis of Project Management Process in Main Agile Methodologies with the ISO/IEC 29110 Entry Profile

Software Process Improvement efforts (SPI) are pursued by organizations for improving the overall quality of their software development processes. However, very small entities (VSEs) avoid them by the lack of required financial and other organizational resources. In contrast, VSEs use agile software development methodologies (ASDMs), but these ASDMs do not foster adherence to best scholastic practices promoted by SPI. Furthermore, while a new ISO/IEC standard (29110) has been recently released for VSEs, it was not designed taking account the ASDM approaches. Thus, we investigate the extent of adherence of main ASDMs (two industrial and one academic type) with this new standard. Initial results provide evidence on the strong need to enhance the two industrial ASDMs (XP and SCRUM). In contrast, the academic ASDM (UPEDU) fits the standard very well but it is scarcely used by VSEs. Hence, it is concluded that there is a knowledge gap between the praxis with ASDMs and the recommended scholastic software processes like the ISO/IEC 29110 standard for VSEs.