A Novel Framework for Evaluating Application Performance in Distributed Systems

Lipoprotein(a) in various conditions: To keep a sense of proportions

Die Sprunggelenksendoprothetik hat sich in den letzten 10 Jahren als Alternative zur Versteifung des oberen Sprunggelenkes etabliert. In dieser Übersichtsarbeit werden Probleme nach Sprunggelenksendoprothesen exzidiert analysiert, als auch die wissenschaftliche Dokumentation von Problemen dargestellt und ferner werden eigenständige Erfahrungen für das Versagen bzw. des Misserfolges einer OSG-Prothesenimplantation aufgezeigt. Es wird das Spektrum der Revisionsmöglichkeiten vom Belassen der Prothese bis hin zum kompletten Wechsel, als auch der Explantation mit konsekutiver Versteifung algorithmisch dargelegt. Ein weiteres Problem des Misserfolges der Prothesenimplantationen besteht auch in der flachen Learningcurve bei mangelnder Routine der Operateure, gepaart mit schwieriger Pathologie bei teilweiser Fehlstellung und Einsteifung der Sprunggelenke.

PurposeTo compare measurements of lower and higher order aberrations (HOA) obtained with four different wavefront aberrometers and to assess their reproducibility.MethodsThis prospective study included pseudophakic otherwise healthy patients. Four wavefront aberrometers were compared. Three of the aberrometers in this study are combined with coneal topographers. Two of the devices use a Hartmann‐Shack sensor (WASCA, Carl Zeiss Meditec AG; iDesign Advanced WaveSan aberrometer, Abbott Medical Optics), one device works on the basis of ray tracing (iTrace, Tracey Technologies), one device utilizes automated retinoscopy (OPD‐ScanIII; NIDEK Co. Ltd.). All patients are measured with an autorefractometer (Topcon, Japan) and also a subjective refraction has been performed. In addition a Purkinjemeter measurement has been done.ResultsIn total, 51 eyes of 51 patients were included. No patient was lost to follow‐up. Mean difference concerning root mean square of all higher order aberrations was 0.013 µm between Wasca and iDesign and 0.113 µm between Wasca and OPD, respectively. Reproducibility was found to be between 0.09 µm (SD:0.06) (iDesign) and 0.41 µm (SD: 0.12) (iTrace). Details for higher order aberrations will be presented at the meeting.ConclusionsFeasibility was found to be excellent for Wasca and iDesign and was high for iTrace but for the OPD Scan there was a flat learning curve. Reproducibility was found to be good for all devices but slightly weaker for the iTrace device.

Laparoscopic surgery can be demanding, resulting in longer operating time and a longer time before reaching proficiency compared with open surgery. Robotic assistance allows stereoscopic vision and improves dexterity, potentially leading to faster and safer laparoscopic surgery and a shortening of the learning curve. Duration and accuracy were measured in inexperienced participants, performing basic and advanced laparoscopic tasks using both conventional laparoscopy and the daVinci Surgical System. Eight participants performed 176 laparoscopic tasks. Robotic assistance resulted in faster and more accurate performance of laparoscopic tasks. However, conventional laparoscopy showed faster skill acquisition. Robotic assistance resulted in faster and more accurate performance of laparoscopic tasks. However, learning curves favored conventional laparoscopy. These data suggest robotic assistance might be most beneficial in inexperienced subjects. The relatively flat learning curve in robot-assisted laparoscopy suggests robotic assistance might be less (or marginally) beneficial in experienced surgeons. This could explain why robotic assistance has failed to show clear benefit in several clinical studies. Extensive conventional laparoscopic training might lead to faster, safer, and less expensive surgery, further marginalizing the role for robotic assistance in laparoscopic surgery.

In this paper, we identify a set of factors that may be used to forecast software productivity and software development time. Software productivity was measured in function points per person hours, and software development time was measured in number of elapsed days. Using field data on over 130 field software projects from various industries, we empirically test the impact of team size, integrated computer aided software engineering (ICASE) tools, software development type, software development platform, and programming language type on the software development productivity and development time. Our results indicate that team size, software development type, software development platform, and programming language type significantly impact software development productivity. However, only team size significantly impacts software development time. Our results indicate that effective management of software development teams, and using different management strategies for different software development type environments may improve software development productivity.

A growing number of mobile applications for health education are being utilized to support different stakeholders, from health professionals to software developers to patients and more general users. There is a lack of a critical evaluation framework to ensure the usability and reliability of these mobile health education applications (MHEAs). Such a framework would facilitate the saving of time and effort for the different user groups. This paper describes a framework for evaluating mobile applications for health education, including a guidance tool to help different stakeholders select the one most suitable for them. The framework is intended to meet the needs and requirements of the different user categories, as well as improving the development of MHEAs through software engineering approaches. A description of the evaluation framework is provided, with its efficient hybrid of selected heuristic evaluation (HE) and usability evaluation (UE) factors. Lastly, an account of the quantitative and qualitative results for the framework applied to the Medscape and other mobile apps is given. This proposed framework – an Evaluation Framework for Mobile Health Education Apps – consists of a hybrid of five metrics selected from a larger set during heuristic and usability evaluation, the choice being based on interviews with patients, software developers and health professionals.

Pengembangan perangkat lunak adalah tugas kompleks dan membutuhkan adaptasi untuk mengakomodasi kebutuhan pengguna. Untuk membuat konsep dan perubahan perangkat lunak, dalam pemeliharaan, sekarang telah dikembangkan lebih mudah dalam pengembangan perangkat lunak, pola model-view-controller, yang merupakan arsitektur yang dapat membantu memfasilitasi dalam pengembangan dan pemeliharaan perangkat luna. Hal ini, karena dalam arsitektur model tiga-lapis, yaitu: tampilan dan pengontrolan dalam pembangunan dilakukan secara independen, sehingga dapat memberikan dahan dalam pengembangan dan pemeliharaan. Selain itu, arsitektur ini juga dapat melihat hal-hal yang sederhana dan menarik bagi pengguna. Software sistem on-line test adalah perangkat lunak yang memerlukan interaksi dengan pengguna, dan pemeliharaan perangkat adaptif. Karena sistem ujian on-line memerlukan pengembangan perangkat lunak untuk mengakomodasi kebutuhan ini berkembang dengan cepat. Makalah ini untuk menganalisis Model-View-Controller dan mencoba pembangunan, untuk menerapkannya dalam pengembangan perangkat lunak sistem pengujian on-line.

Software testing is an important process in software quality assurance(SQA). Software testing consumes the majority of the software developers' time and cost of all the phases of system development. An important problem in software testing is to determine whether a program has been tested enough with a testing criterion and when one could stop testing. On the other hand, software measurement is used to estimate the quality of a software. Complexity measures can be used to compare software quality and development cost. This paper proposes a new testing approach which choosing testing path based on path complexity. The process is to use a set of testing paths that satisfying all-uses testing criterion, and then choose the testing path with the most complexity to test. This process is continued until the program can be accepted. The proposed formula is used to determine if it is possible to stop testing before satisfying all-du-paths testing criterion. The main contribution of the paper is that software developers can choose a proper testing action with lower testing effort.

Evaluation of ensemble streamflow predictions in Europe

The capability of an enterprise to innovate and promptly and effectively respond to change requests coming from both internal and external drivers has nowadays become a measure of the competitiveness of the enterprise in all business sectors. Innovation often implies modifying the enterprise business processes and, as a consequence, requires the evolution of the enterprise software systems. In this context, the workshop on Evolution of Software Systems in a Business Context (ESSBC), held in Budapest, Hungary, as part of the IEEE Software Technology and Engineering Practice workshop series (STEP 2005), aimed at discussing experiences and research outcomes and identifying research issues in supporting the evolution of enterprise software systems to reach innovation goals

There are many devices with java embedded platform that allow executing generic Java applications. Some of the examples are smart phones, PDAs, set-top boxes, etc. Developers can create and users can download such applications to their devices. The number of embedded applications increases each year and developers should adapt efficient software development techniques in order to move their products to market in time and with high reliability level. There are currently so many software development frameworks and techniques for standalone or server applications that embedded software developers often miss out on them. One of the most important to follow practice is testing. The authors have developed several products for PC in Java where testing was formally defined and automated with JUnit. That experience demonstrated a value of regular test runs for product reliability and development stability.

Recently, AI agents are rapidly evolving in intelligence and are widely used in professional research applications, such as STEM, software development, and finance. Among these AI agents, deep research agent is a key category as it can perform long-horizon tasks and solve problems of greater complexity. However, there are few evaluation frameworks and benchmarks that systematically and automatically investigate the capabilities of these research agents. In addition, financial research problems have distinct complexity and subtlety. To fill in the gap, we propose FinResearchBench, which is a logic tree-based Agent-as-a-Judge and targets specifically for the financial research agents. It provides a comprehensive and automatic assessment of the research agents across 7 key types of tasks in the financial research domain. The contributions of this work are two-folded: (1) the first and innovative Agent-as-a-Judge system that extracts the logic tree of the research outcome and uses it as the intermediate information to present a comprehensive, reliable, and robust evaluation; (2) finance-oriented that it covers 70 typical financial research questions, spreading across 7 frequently-encountered types of task in the domain.

SUMMARYSoftware Process Improvement (SPI) encompasses the analysis and modification of the processes within software development, aimed at improving key areas that contribute to the organizations' goals. The task of evaluating whether the selected improvement path meets these goals is challenging. On the basis of the results of a systematic literature review on SPI measurement and evaluation practices, we developed a framework (SPI Measurement and Evaluation Framework (SPI‐MEF)) that supports the planning and implementation of SPI evaluations. SPI‐MEF guides the practitioner in scoping the evaluation, determining measures, and performing the assessment. SPI‐MEF does not assume a specific approach to process improvement and can be integrated in existing measurement programs, refocusing the assessment on evaluating the improvement initiative's outcome. Sixteen industry and academic experts evaluated the framework's usability and capability to support practitioners, providing additional insights that were integrated in the application guidelines of the framework. Copyright © 2013 John Wiley & Sons, Ltd.

7-1-7: an organising principle, target, and accountability metric to make the world safer from pandemics

Software metrics are measures of software. Their primary use is to help us plan and predict software development. We can better control software quality and development effort if we can quantify the software. This is especially true in the early stages of development. Research has been done in the area of predicting software maintenance effort from software metrics. In general, software metrics can be classified into two categories: software product metrics and software process metrics. Software product metrics are measures of software products such as source code and design documents. Software process metrics are measures of software development process. For example, the size of the software is a measure of the software product itself, thus a product metrics. The effort required to design a software system may be influenced by how the software is designed, thus a process metrics. In this article, only software product metrics are addressed.