Defect Bash - Literature Review
Defect bash is a co-located testing session performed by a group of people. We performed a systematic review of the academic and grey literature, i.e. informally published writings, of the defect bash. Altogether, we found 44 items (17 academic and 27 grey literature sources) that were identified useful for the review. Based on the review the definition of defect bash is presented, benefits and limitations of using defect bash are given. Finally, the process of doing defect bash is outlined. This review provides initial understanding on how defect bash could be useful in achieving the software quality and lays foundation for further academic studies of this topic.
The Management Spectrum
While leadership dominates the attention of many, it is management that drives the work at hand. Julian Birkinshaw and Jules Goddard suggest that you reconsider the management model you practice daily to see if it's really working inside your company.
Cost-effective Detection of Software Defects through Perspective-based Inspections
Software organizations must deliver high quality products on time and within budget to remain competitive in the marketplace. However, the reliable and predictable development of high quality software continues to be a major problem, largely due to the inadequate and late removal of defects. One of the proposed solutions for early detection and removal of defects is software inspection (Fagan, 1976), (Gilb and Graham, 1993). A software inspection requires a team of qualified persons to scrutinize software documents for defects. It applies to any development methodology and to any phase in the software development process. The value of an inspection stems from the fact that it improves quality and saves defect costs, since it minimizes the time between insertion of a defect and its discovery. This is important because the cost of finding and fixing a defect increases significantly each time it propagates to the next development phase. To fully achieve the expected benefits, two practical questions related to software inspection need to be answered: how to organize a particular inspection in a development project with a large volume of documentation and how to provide technical support for the defect detection activity of an inspection with reading techniques (Basili, 1997). This research presents a new strategy for inspection organization. The basis for this strategy is the distinction between logical entities and their documentation. This distinction is necessary because, in contrast to other engineering disciplines, the entities in software engineering are invisible and cannot be inspected per se. It is only the documentation of the entities that can be scrutinized for defects. The strategy, dubbed architecture-centric inspection organization, suggests partitioning and grouping the documentation to be inspected according to logical entities rather than characteristics of the documentation, such as their type or size. Following this strategy, the most appropriate unit to inspect can be determined. This unit refers to documentation that contains relevant information about one or several logical entities. Organizing an inspection in this manner avoids a decline in the cost-effectiveness of inspection because of fatigue effects or loss of motivation. Although the architecture-centric approach is generally applicable, it is particularly valuable