Search

Bowling is a target sport that is popular among all age groups with professionals and amateur players. Delivering an accurate and consistent bowling throw into the lane requires the incorporation of motion techniques. Consequently, this research presents a novel IoT Cloud-based system for providing real-time monitoring and coaching services to bowling athletes. The system includes two inertial measurement units (IMUs) sensors for capturing motion data, a mobile application, and a Cloud server for processing the data. First, the quality of each phase of a throw is assessed using a Dynamic Time Warping (DTW)-based algorithm. Second, an on-device-level technique is proposed to identify common bowling errors. Finally, an SVM classification model is employed for assessing the skill level of bowler athletes. We recruited nine right-handed bowlers to perform 50 throws wearing the two sensors and using the proposed system. The results of our experiments suggest that the proposed system can effectively and efficiently assess the quality of the throw, detect common bowling errors, and classify the skill level of the bowler.

Human eye fixation is steadily interrupted by small, physiological or abnormal, eye movements. Square-wave jerks (SWJ) are the most common saccadic intrusion which can be readily seen at the bedside and also quantified using oculographic techniques. Various neurological, neuropsychiatric and psychiatric disorders display abnormal fixational eye movement patterns characterized by frequent SWJ. For the clinician, SWJ are particularly important because they can be readily observed at the bedside. Here, we will discuss the pathological conditions that present with SWJ and explore the expanding body of literature suggesting that SWJ may serve as a potential indicator for various clinical conditions.

Patients with movement disorders such as Parkinson’s disease (PD) living in remote and underserved areas often have limited access to specialized healthcare, while the feasibility and reliability of the video-based examination remains unclear. The aim of this narrative review is to examine which parts of remote neurological assessment are feasible and reliable in movement disorders. Clinical studies have demonstrated that most parts of the video-based neurological examination are feasible, even in the absence of a third party, including stance and gait—if an assistive device is not required—bradykinesia, tremor, dystonia, some ocular mobility parts, coordination, and gross muscle power and sensation assessment. Technical issues (video quality, internet connection, camera placement) might affect bradykinesia and tremor evaluation, especially in mild cases, possibly due to their rhythmic nature. Rigidity, postural instability and deep tendon reflexes cannot be remotely performed unless a trained healthcare professional is present. A modified version of incomplete Unified Parkinson’s Disease Rating Scale (UPDRS)-III and a related equation lacking rigidity and pull testing items can reliably predict total UPDRS-III. UPDRS-II, -IV, Timed “Up and Go”, and non-motor and quality of life scales can be administered remotely, while the remote Movement Disorder Society (MDS)-UPDRS-III requires further investigation. In conclusion, most parts of neurological examination can be performed virtually in PD, except for rigidity and postural instability, while technical issues might affect the assessment of mild bradykinesia and tremor. The combined use of wearable devices may at least partially compensate for these challenges in the future.

This work presents Source-o-grapher, a tool built with the aim to investigate software resilience aspects of Open Source Software (OSS) projects. The tool uses several metrics from the literature to evaluate an OSS project on four major dimensions: structural (source code), business and legal, integration and social (community of the project). Many of these metrics are automatically acquired by the tool using the Github repository of the project whereas some others are manually input by the expert who performs the analysis.

This article investigates how Process Mining may be used to check process conformance in enterprise information system development. The concept of using Process Mining beyond pure business processes is exemplified on the bug closure processes of two open-source enterprise systems. The process models and conclusions extracted are used for drawing some generic guidelines enterprise information project managers can adopt to assess the quality of their system development processes. Process conformance checking is performed in the Bugzilla databases of two open-source enterprise information systems using Disco. The extracted models are assessed based on the documentation of the projects and are compared to the bug closure process Bugzilla team suggests being used. The findings revealed that the processes followed in the projects are very similar to the ones presented in their documentation, conforming with Bugzilla guidelines. However, several variations are revealed under specific circumstances. Potential benefits from applying Process Mining techniques for information system development management are briefly summarized. This empirical research extends previous work that has been performed in the field of Process Mining and highlights the importance and necessity of Process Mining in enterprise information system development to help standardize and improve the internal processes of an organization and to serve as a proof of compliance by external collaborators developing software for an organization. In addition, it capitalizes on the adoption of inner source development model by many companies developing enterprise software nowadays.

Background: Game scenario is an important factor for achieving player enjoyment; consisting a key business success factor. Additionally, the production of early design artifacts is crucial for the success of the development process. However, representing scenarios is a non-trivial task: (a) multiple aspects of the game need to be visualized; and (b) there is a plethora of representation approaches, out of which the game designer needs to select from. Aim: The goal of this work is to provide a panorama of the current scenario representation approaches, to aid game engineers in selecting the most fitting scenario representation approach and understand the existing designing options. Method: We have performed a Systematic Mapping Study, using 4 digital libraries, since the main goal can be achieved through study classification. By following an established search and filtering process, we have identified 717 articles, and analyzed in detail 95. Results: Diagrams are the most common generic approach to represent scenario; Game story is the most usual part of the scenario being represented; Characters are the most common component; and Transitions are the most usual connectors. Conclusion: Researchers may get useful information for empirically investigating several game engineering aspects; whereas game engineers can efficiently select the most fitting approach.

Despite the extensive adoption of crowdsourcing for the timely, cost-effective, and high-quality completion of software development tasks, a large number of crowdsourced challenges are not able to acquire a winning solution, on time, and within the desired cost and quality thresholds. A possible reason for this is that we currently lack a systematic approach that would aid software managers during the process of designing software development tasks that will be crowdsourced. This paper attempts to extend the current knowledge on designing crowdsourced software development tasks, by empirically answering the following management questions: (a) what type of projects should be crowdsourced; (b) why should one crowdsource-in terms of acquired benefits; (c) where should one crowdsource-in terms of application domain; (d) when to crowdsource-referring to the time period of the year; (e) who will win or participate in the contest; and (f) how to crowdsource (define contest duration, prize, type of contest etc.) to acquire the maximum benefits-depending on the goal of crowdsourcing. To answer the aforementioned questions, we have performed a case study on 2,209 software development tasks crowdsourced through TopCoder platform. The results suggest that there are significant differences in the level to which crowdsourcing goals are reached, across different software development activities. Based on this observation we suggest that software managers should prioritize the goals of crowdsourcing, decide carefully upon the activity to be crowdsourced and then define the settings of the task.