A case study on the misclassification of software performance issues in an issue tracking system

2016 ◽  
Author(s):  
Masao Ohira ◽  
Hayato Yoshiyuki ◽  
Yosuke Yamatani
Keyword(s):  
Tracking System ◽  
Software Performance ◽  
Performance Issues ◽  
Issue Tracking System

“I am not a guinea pig”: Parental opportunity hoarding and tracking reform in Germany

2021 ◽  
Vol 16 (1) ◽  
pp. 64-82
Author(s):  
Lana Apple ◽  
Mira Debs
Keyword(s):  
Social Capital ◽  
Discourse Analysis ◽  
Guinea Pig ◽  
Education System ◽  
Educational Inequality ◽  
Tracking System ◽  
School Structure ◽  
Student Background ◽  
Achievement Outcomes

PISA test data from 2000 to today have shown Germany’s education system is one of the most inequitable within the OECD, with high correlations between student background and achievement outcomes. Scholars have identified the highly differentiated school structure, which tracks students as young as 10 years old, as a central cause. This scholarship has not evaluated why German tracking has proved difficult to reform over the last 20 years, despite evidence of negative outcomes. Using a case study of parents’ actions in Hamburg, this paper employs a discourse analysis of debates surrounding a tracking reform to argue that opportunity hoarding—that is, parents with more social capital maintaining certain advantages through ingrained systems that are theoretically open to all—may contribute to why Germany’s early tracking system persists despite evidence showing that it increases educational inequality. The findings presented have implications for an international discussion of tracking reform and opportunity hoarding.

scholarly journals A reliability engineering case study of sugarcane harvesters

2020 ◽  
Vol 27 (4) ◽  
Author(s):  
Diego Carvalho do Nascimento ◽  
Pedro Luiz Ramos ◽  
André Ennes ◽  
Camila Cocolo ◽  
Márcio José Nicola ◽  
...  
Keyword(s):  
Tracking System ◽  
Meteorological Data ◽  
Reliability Engineering ◽  
Embedded Computer ◽  
Equipment Failures ◽  
Process Failures ◽  
A Company ◽  
Different Sources ◽  
Two Machines

Abstract: The present study aimed to analyze factors associated with the equipment failures of the sugarcane harvester, whose machineries has high importance in the harvest process and cost involved. Part of the data was originally provided by a company located in the countryside of Sao Paulo State, from two machines, collected from January 2015 to August 2017, corresponding to 2.5 crops. The overall dataset was obtained from three different sources: a stop-tracking system, which provides the track of a preventive and corrective maintenance historical of the analyzed equipment; telemetry data of the equipment, captured through embedded computer systems, installed in the machine’ type under study, which provide information on its operation; and meteorological data from the Brazilian National Institute of Meteorology. Multivariate analyzes were used such as principal components and multiple regression models, therefore creating a model for prediction considering the next equipment’ break, then pointing to causes of process failures. Thus, the results point to some improvements concerned with individualized reliability scheme in order to reduce the number of corrective stops given the equipment.

scholarly journals Partially observable Markov Decision Process to prioritize software defects

2021 ◽  
Author(s):  
Shirin Akbarinasaji
Keyword(s):  
Markov Decision Process ◽  
Decision Process ◽  
Tracking System ◽  
Dependency Graph ◽  
Relative Importance ◽  
Bug Reports ◽  
Markov Decision ◽  
Partially Observable Markov ◽  
Partially Observable ◽  
Issue Tracking System

Background: Bug tracking systems receive many bug reports daily. Although the software quality team aims to identify and resolve these bugs, they are never able to fix all of the reported bugs in the issue tracking system before the release deadline. However, postponing the bug fixing may have some consequences. Prioritization of bug reports will help the software manager decide which bugs to fix and which bugs to postpone. Typically, bug reports are prioritized based on the severity, priority, time and effort for fixing, customer pressure, etc. Aim: Previous studies have shown that these factors may not be appropriate for prioritization. Therefore, relying on them to automate bug prioritization might be misleading. In this dissertation, we aim to prioritize bug reports with respect to the consequence of not fixing the bugs in terms of their relative importance in the issue tracking system. Method: In order to measure the relative importance of bugs in the issue tracking system, we propose the construction of a dependency graph based on the reported dependency-blocking information in the issue tracking system. Two metrics, namely depth and degree, are used to measure the relative importance of the bugs. However, there is uncertainty in the dependency graph structure as the dependency information is discovered manually and gradually. Owing to this uncertainty, prioritization of bugs in the descending order of depth and degree may be misleading. To handle the uncertainty, we propose a novel approach of a partially observable Markov decision process (POMDP) and partially observable Monte Carlo planning (POMCP). Result: To check the feasibility of the proposed approach, we analyzed seven years of data from an open source project, Firefox, and a commercial project. We compared the proposed policy with the developer policy, maximum policy, and random policy. Conclusion: The results suggest that software practitioners do not consider the relative importance of bugs in their current practice. The proposed framework can be combined with practitioners’ expertise to prioritize bugs more effectively and take the depth and degree of bugs into account. In practice, the POMDP framework with the POMCP planner can help practitioners sequentially select bugs to minimize the connectivity of the dependency graph.

From Android Bug Reports to Android Bug Handling Process

2016 ◽  
Vol 7 (4) ◽  
pp. 1-18
Author(s):  
Liguo Yu
Keyword(s):  
Project Management ◽  
Open Source ◽  
Tracking System ◽  
Software Project ◽  
Bug Reports ◽  
Bug Report ◽  
Bug Tracking ◽  
Android Development ◽  
Comprehensive Study

Android is an operating system for mobile devices. Its development is led by Google and some other companies. Because of the open-source property of Android, anyone can report a bug through its online bug tracking system. In this paper, we analyze the bug reports of Android operating systems. Specifically, through this study, we would like to answer the following questions regarding Android development and its project management: (1) Could Android bug reports be handled on time? (2) What is the distribution of different maintenance activities initiated by Android bug reports? (3) How long does it take to handle an Android bug report? (4) Are the number of followers and the number of following messages of an Android bug report related to the effort spent on handling this bug report? Through answering these questions, this paper presents a comprehensive study of Android bug reporting and handling process. The information and knowledge obtained through this case study could help us better understand open-source software project, such as its development process and project management.

Compliant gripper design, prototyping, and modeling using screw theory formulation

2020 ◽  
pp. 027836492094781
Author(s):  
Irfan Hussain ◽  
Monica Malvezzi ◽  
Dongming Gan ◽  
Zubair Iqbal ◽  
Lakmal Seneviratne ◽  
...  
Keyword(s):  
Mathematical Model ◽  
Screw Theory ◽  
Tracking System ◽  
Mathematical Formulation ◽  
Optical Tracking ◽  
Kinematic Structure ◽  
Optical Tracking System ◽  
Different Shapes ◽  
Manufacturing Parameters

This article investigates some aspects related to the design, modeling, prototyping, and testing of soft–rigid tendon-driven grippers. As a case study, we present the design and development of a two-finger soft gripper and exploit it as an example to demonstrate the application scenario of our mathematical model based on screw theory. A mathematical formulation based on screw theory is then presented to model gripper dynamics. The proposed formulation is the extension of a model previously introduced including the mechanical system dynamics. In this type of gripper, it is possible to achieve different behaviors, e.g., different fingertip trajectories, equivalent fingertip stiffness ellipsoids, etc., while keeping the same kinematic structure of the gripper and varying the properties of its passive deformable joints. These properties can be varied in the prototype by properly regulating some manufacturing parameters, such as percentage of printing infill density in a 3D printing process. We performed experiments with the prototype of the gripper and an optical tracking system to validate the proposed mathematical formulation, and to compare its results with other simplified formulations. We furthermore identified the main performance of the gripper in terms of payload and maximum horizontal resisted force, and verified the capabilities of the gripper to grasp objects with different shapes and weights.

Blue Dart Express Limited

1999 ◽  
Vol 24 (2) ◽  
pp. 45-52
Author(s):  
S.C. Bhatnagar ◽  
C. Ranganathan
Keyword(s):  
Information Technology ◽  
Tracking System ◽  
Top Management ◽  
Geographic Scope ◽  
It Applications

This case study describes the operations of Blue Dart Express Limited and documents the development of major IT applications by the company during 1987 to 1997. The company has been investing nearly one per cent of its revenue on developing IT applications during this period. The case describes the evolution of a consignment tracking application on which the current operations of Blue Dart are completely dependent. In 1997, the company was reviewing its plans for the next five years. The company plans to use the emerging information technology to enhance the existing applications and to widen the geographic scope of the application. The case lists some of the issues faced by Malcolm, the chief architect of the successful tracking system, in proposing the size and scope of t he next IT plan to the top management. Readers are invited to send their responses on the case to Vikalpa Office.

Sign in / Sign up

Export Citation Format

Share Document