Agile Literature Review

Background: Over the last 20 years the software development community has implemented agile techniques over the traditional approach to software development. Agile methods require less upfront costs and increase project flexibility; however, agile methodology is not infallible. Objective: This research seeks to validate the assumption that there is a lack of robust research regarding agile project management and its use in the software development industry. This extensive review of existing literature on the topic will serve as a basis for new research on areas with existing ambiguity. Method: The search engines used to identify relevant literature from 1987 to 2021 on the topic were Business Source Premier and Google Scholar. The procedure used to narrow the search queries was the use of deliberate keywords and phrases such as “agile software development” and “cost of requirement errors”. All results were cross-referenced on both search engines to validate the accuracy of each source. Results: 76 papers containing relevant information to agile project management within the software community have been identified: 55 academic journals, 1 book, 1 conference paper, 1 magazine article, 7 periodicals, 10 professional journals, and 1 textbook. 35 papers are critical of Agile methodology, 16 focus mostly on its strengths, 12 focus mainly on its weaknesses, and 13 contain relevant information regarding the cost of requirement errors

A semi-automatic verification tool for software requirements specification documents

Most software problems arise from deficiencies in the manner in which software requirements are elicited and expressed. Ensuring that the Software Requirements Specification document (SRS) has the necessary quality is crucial to the success of any software development project, since its information is used across all project stages. In this paper, we present a semiautomatic verification tool for SRS documents based on a comprehensive quality model.Sociedad Argentina de Informática e Investigación Operativ

Software Requirements Quality Evaluation: State of the art and research challenges

Quality models are important tools for quality management. In software development projects, they are useful as predictive tools for assessing the state of the product being developed and the process used. In order to achieve software quality, a high-quality Software Requirements Specification (SRS) is required. This document is generated at the beginning of a software development project, and is used in all stages. Thus, it is essential to evaluate the quality of the SRS in order to be able to take early corrective and enhancement actions. However, assessing the quality of a SRS is not a simple process, mainly by the multitude of proposals, often contradictory, of the attributes to be evaluated and the methodologies used for that purpose. Thus, it is mandatory to consider proven quality models for guiding this evaluation process. Related to this, this work performs an exploratory analysis of various quality models proposed in this area which can be used as a basis for SRS quality evaluation. Moreover, the work is intended to be a compendium of the most important tendencies and strategies in the field that serves as a starting point for developing comprehensive models and tools for quality attributes evaluation in a SRS.Sociedad Argentina de Informática e Investigación Operativa (SADIO

Software Requirements Quality Evaluation: State of the art and research challenges

Quality models are important tools for quality management. In software development projects, they are useful as predictive tools for assessing the state of the product being developed and the process used. In order to achieve software quality, a high-quality Software Requirements Specification (SRS) is required. This document is generated at the beginning of a software development project, and is used in all stages. Thus, it is essential to evaluate the quality of the SRS in order to be able to take early corrective and enhancement actions. However, assessing the quality of a SRS is not a simple process, mainly by the multitude of proposals, often contradictory, of the attributes to be evaluated and the methodologies used for that purpose. Thus, it is mandatory to consider proven quality models for guiding this evaluation process. Related to this, this work performs an exploratory analysis of various quality models proposed in this area which can be used as a basis for SRS quality evaluation. Moreover, the work is intended to be a compendium of the most important tendencies and strategies in the field that serves as a starting point for developing comprehensive models and tools for quality attributes evaluation in a SRS.Sociedad Argentina de Informática e Investigación Operativa (SADIO

Automated Tool for Software Requirements Inspection

The software inspection process is a very cost effective method of identifying defects in documents produced during the software life cycle, leading to higher quality software with lower field failures. Manual inspections are labor intensive and dependent on human factors (e.g., preparation, moderation, and cooperation among development and quality assurance teams). An automated software inspection tool replaces a labor intensive manual approach of performing the inspection process. An automated inspection tool will offer greater efficiencies than any techniques involving manual inspections. Automation allows stakeholders (e.g., authors, inspectors) to closely work in coordination using the tool. Authors can host documents, view comments posted by inspectors, assign users and delete them. Inspectors can participate in the inspection process by validating against a set of guidelines and detect faults in a specific frame of time using different fault and error based inspection techniques. It is human to err, and as a result some of the faults may be overlooked. Hence, provisions are made for iterative inspection cycles to maximize the number of defects found and minimize the number of overlooked ones

A semi-automatic verification tool for software requirements specification documents

Most software problems arise from deficiencies in the manner in which software requirements are elicited and expressed. Ensuring that the Software Requirements Specification document (SRS) has the necessary quality is crucial to the success of any software development project, since its information is used across all project stages. In this paper, we present a semiautomatic verification tool for SRS documents based on a comprehensive quality model.Sociedad Argentina de Informática e Investigación Operativ

Software Requirements Quality Evaluation: State of the art and research challenges

Quality models are important tools for quality management. In software development projects, they are useful as predictive tools for assessing the state of the product being developed and the process used. In order to achieve software quality, a high-quality Software Requirements Specification (SRS) is required. This document is generated at the beginning of a software development project, and is used in all stages. Thus, it is essential to evaluate the quality of the SRS in order to be able to take early corrective and enhancement actions. However, assessing the quality of a SRS is not a simple process, mainly by the multitude of proposals, often contradictory, of the attributes to be evaluated and the methodologies used for that purpose. Thus, it is mandatory to consider proven quality models for guiding this evaluation process. Related to this, this work performs an exploratory analysis of various quality models proposed in this area which can be used as a basis for SRS quality evaluation. Moreover, the work is intended to be a compendium of the most important tendencies and strategies in the field that serves as a starting point for developing comprehensive models and tools for quality attributes evaluation in a SRS.Sociedad Argentina de Informática e Investigación Operativa (SADIO

FAULT LINKS: IDENTIFYING MODULE AND FAULT TYPES AND THEIR RELATIONSHIP

The presented research resulted in a generic component taxonomy, a generic code-faulttaxonomy, and an approach to tailoring the generic taxonomies into domain-specific aswell as project-specific taxonomies. Also, a means to identify fault links was developed.Fault links represent relationships between the types of code-faults and the types ofcomponents being developed or modified. For example, a fault link has been found toexist between Controller modules (that forms a backbone for any software via. itsdecision making characteristics) and Control/Logic faults (such as unreachable code).The existence of such fault links can be used to guide code reviews, walkthroughs, testingof new code development, as well as code maintenance. It can also be used to direct faultseeding. The results of these methods have been validated. Finally, we also verified theusefulness of the obtained fault links through an experiment conducted using graduatestudents. The results were encouraging