No abstract

Software bug localization is an essential step within the software maintenance activity, consuming about 70% of the time and cost of the software development life cycle. Therefore, the need to enhance the automation process of software bug localization is important. This paper surveys various software bug localization techniques. Furthermore, a running motivational example is utilized throughout the paper. Such motivational example illustrates the surveyed bug localization techniques, while highlighting their pros and cons. The motivational example utilizes different software artifacts that get created throughout the software development lifecycle, and sheds light on those software artifacts that remain poorly utilized within existing bug localization techniques, regardless of the rich wealth of knowledge embedded within them. This research thus presents guidance on what artifacts should future bug localization techniques focus, to enhance the accuracy of bug localization, and speedup the software maintenance process.

Design phase is considered one of the most important phases of software development process. Considering design quality is a significant indicator to guarantee a good product. Despite the fact that this phase is more important, it takes less effort in processing but it can take a large part of the total effort consumed in correcting earlier issues that resulted from bad design decisions. If the design quality of a product wasn't previously considered, the cost of fixing bad design issues after software delivery will be very high. Recently researchers have introduced several object oriented metrics for identifying design problems and avoiding such issues at earlier development phases. This paper initiates a survey regarding object-oriented metrics and their quality attributes. Also it shows the relationship between internal and external quality attributes and identify a group of practical and common used metrics which having a significant impact on design quality.

No abstract

Traffic Incident Managers (TIMs) coordinate first responders and help resolve traffic-related incidents. Currently, some use over fifteen different software applications with unique functionalities across three monitors to manage incidents, leading to redundant data entry, unnecessary task switching, and delayed responses. 40 hours of TIMs' screens were recorded during their normal work hours at the Iowa Department of Transportation (DoT). The resulting task analysis from these videos greatly influenced the design of a simplified, web-based, user interface (UI) prototype. The new UI offers a 42.9% reduction in the steps required to manage an incident by combining the functionality of the fifteen different applications used in the existing system into a single, structured UI. This research approach offers a UI model to other DoTs that can lead to faster and more effective incident management.