Search

Software requirement engineering (SRE) is the initial stage of the software engineering process and entails several challenges relating to the identification, implementation, evolution, and management of requirements for the development of software systems that meet the desired functionality quality standards. Agile software development (ASD) is a well‐known software development process that follows a lightweight and adaptive methodology to support the incremental development of software systems. Since the ASD follows an adaptive procedure (ie, a flexible, nanostructured, and dynamic approach) of software development, it becomes challenging to perform SRE that follows a structured approach for managing software requirements throughout the life cycle of software development. The primary challenges for SRE, while pursuing an ASD, include, but are not limited to, identification of incomplete requirements, implementation of vague requirements, prioritization of secondary functional requirements, and compromise on users' involvement that negatively impacts the software system's functionality and quality. To overcome these challenges, some of the recent research efforts have focused on managing different phases of SRE during software development using the ASD. However, there is a lack of solutions that provide software engineers/practitioners with a solution. Besides, frameworks to effectively manage all the phases of SRE as per the needs of the ASD are needed. We propose a framework that unifies joint requirements document (JRD) and SCRUM to incrementally (a) identify, (b) implement, (c) evolve, and (d) manage system requirements throughout the software development cycle. We have used the action research method to qualitatively validate the proposed framework based on data and user requirements collected from a product‐focused (multinational) Norway‐based software company. The results of the validation are based on statistical analysis that reflects the usefulness of the proposed framework for SRE in ASD‐based software engineering and development. Future research is the possible application of a machine learning approach (es) in the intended context for agile requirements elicitations. [ABSTRACT FROM AUTHOR]

While seemingly incompatible, combining global software development and agile practices is a challenge undertaken by many companies. Case study reports on the successful use of agile practices in small distributed projects already exist. How these practices can be applied to larger projects, however, remains unstudied. This paper reports a case study on agile practices in a 40-person development organization distributed between Norway and Malaysia. Based on seven interviews in the development organization, we describe how scrum practices were successfully applied, e.g. using teleconferencing and web cameras for daily scrum meetings, synchronized 4-week sprints, weekly scrum-of-scrums, and Jira for backlog management. Non-scrum agile practices included nightly builds, automated testing, and team rooms. Supportig global software development practices, e.g. frequent visits, unofficial distributed meetings, domain expert networks, and annual gatherings are described. Positive experiences of using scrum included improved communication, trust and motivation, as well as better perceived quality. Challenges included misunderstood requirements, lack of videoconferencing possibilities, and awkward communication in distributed meetings due to cultural and geographical distance. Copyright © 2008 John Wiley & Sons, Ltd. [ABSTRACT FROM AUTHOR]