Methods for Monitoring Productivity in Applicative Software Development

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.

Uptake of HCI and usability engineering by software development organisations can be terminally impeded by lack of appreciation of the benefits of HCI activities. However, descriptions of HCI offerings in terms of activities (e.g. task analysis, user mapping, allocation of function, interaction design) and methods (e.g. user profiling, prototyping, GOMS modelling) do not convey to product managers a readily comprehensible conception of the value of such offerings. Similarly, descriptions of HCI activities and methods give little indication of how these are to be associated and managed with reference to stages and deliverables in a software development life cycle. This lack of clear association between usability engineering and software engineering contributes to the marginalisation of usability related activities. Even when investment is made in usability resources its eventual pay off can be minimal, with resulting disillusionment on both sides. Specification of usability deliverables can provide a solid basis for a manageable usability perspective on the development of software products. The article identifies usability deliverables and describes their content and relation to deliverables in a software design and development process. More general implications for an approach to the specification of quality processes for the creation of interactive software products are discussed.

Businesses and consumers all want more software faster. The seemingly ever-increasing demand for more software suggests the need to not only increase production capabilities but also to produce more with the resources available for production. In other words, software development productivity needs to increase. But what is software development productivity anyway? In this talk, I will explore various ways in which productivity, both in general and for software development, has been characterized and will explore ways in which mining software repository information can help accelerate both software development productivity and innovation.

The article summarizes the trends in the development of the health care sector formed under the influence of the COVID-19 pandemic, namely: rising costs under the influence of inflation and supply chain problems, increasing the amount of investment in scientific research, growing demand for receiving care outside hospitals, deepening inequalities in access to medical services, shortage and exhaustion of medical workers, deterioration of mental health, increasing role of trusting personal relationship between patient and doctor, growing demand for affordable and safe treatment, remote monitoring and interaction between health care institutions, growing use of mobile applications (telemedicine, digital prescriptions and medical records, remote patient monitoring using wearables, personalized medicine and genomics, gaming applications, retail healthcare, clinical and fitness solutions, FinTech, mental health care. One notes that the sector health care as a component of the world economy is being transformed and improved under the influence of globalization and informatization processes, as well as under the influence of specific factors. The reports of the experts of the World Economic Forum, experts of the American Hospital Association, the National Management and Technology Consulting Firm “West Monroe”, the consulting firms “Precedence Research Healthcare IT Marke”, “Deloitte”, the International Independent Expert on the Quality of Informatization of Medical Care, the developers of HIMSS software products were analyzed and developers of software products. Medical technologies, telemedicine and predictive analytics sectors, as well as the use of artificial intelligence, are among the sectors with the highest growth intensity.

A reuse base for real-time software specifications

Component-based software development is an effective and efficient approach to improve productivity and quality of software development. So far, almost all the technologies of software components focus on component description and operation. But the software architecture which takes component as the basic unit has a great progress, and provides a software development process of the top-down through describing its structure and features. In order to improve the efficiency and quality of management information system (MIS), the reusable component technology has been introduced in MIS. Through the description of the structure and features, the reusable components are used in the structure and features of MIS in the development process such as demands analysis, system design, system implementation, system testing, and system maintenance. The result shows that supporting and implementing the assembly of MIS under the platform of component running has improved the stability quality and development efficiency of the existing MIS.

Software reuse is used to aid the software development process which in recent times can improve there quality and productivity of software development. There are a lot of free clinical software without any cost that provides better use to chance for designers to create medical tools at an efficient rate and in a quicker way. Therefore, the minor research work on shareware health care software faces some different situations for designing environments in clinical app growth. This research actually aims to support healthcare designers' great understanding of shareware public domain software by conducting detailed research on shareware public domain software monitored on GitHub repository. The main aim is that we make a specific method that gathers relevant data and then takes some action on the given GitHub data. After the different research in-depth, with its different ways like numeric research, theory-based research, and econometric research, that was handled to gain the main or actual theme and its different properties of open-source clinical software. Around 14,971 projects/software are paid but on the other hand, 12,919 software are open source, unpaid, or free of cost, which helps to make clinical software at a minimum cost and make clinical software more effective. The conclusion may handle different members, mainly beginners, in handling shareware and public domain software.

Software development productivity, code quality, and knowledge sharing have all increased dramatically with the use of AI code assistants like GitHub Copilot. These technologies provide real-time suggestions, expedite workflows, and speed up prototyping by utilising massive language models that have been trained on extensive code repositories. However, serious questions about software security, developer dependency, and ethical ramifications are brought up by their increasing use. The advantages and disadvantages of AI code helpers for safe software development are discussed in this study. It highlights how crucial human oversight, frequent security audits, ongoing model upgrades, and conformity to DevSecOps and OWASP guidelines are. In the end, software integrity cannot be jeopardised by including AI into development processes. In an increasingly automated development context, strategic implementation is crucial to maximising AI's benefits while protecting against new risks.

The ultimate aim of software engineering methods and tools is to reduce risks associated with the development of software products. Accepted risk management procedures recognize that software development is inherently risky, however fail to take into account the changing nature of both software products and the organizations undertaking their development. SE research has traditionally focused on the needs of very large corporations undertaking equally mammoth and complex development projects, thus most tools and methods are predicated on this model. Yet most software development is undertaken by small to medium enterprises. Consequently, these development efforts are either undertaken with little or no adherence to any SE standard process or by attempting to tailor processes intended for larger organizations. Neither of these alternatives is ideal, with both introducing new elements of risk. The rise of the Internet as a platform for commercial applications has partly driven this move away from monolithic software development and has also contributed to the proliferation of software products built using COTS components. Clearly there is a risk involved in the use of components not developed specifically for a particular application while Internet applications introduce an. entirely new set of possible risks. These newer risk factors directly affect the quality of the software product and the paper discusses these factors in detail, showing how they contribute to making software development today an even riskier proposition than previously.

Model-driven engineering (MDE) is a software engineering discipline focusing on models as the primary artifacts in the software development process while programs are mainly generated by means of model-to-code transformations. In particular, modeling languages tailored to specific application domains promise to increase the productivity and quality of software development. Nevertheless due to e.g. evolving requirements, modeling languages and their meta-models evolve which means that existing models have to be migrated correspondingly. In our approach, such co-evolutions are specified as related graph transformations ensuring well-typed model migration results. Based on our earlier work on co-transformations, we now consider the automatic deduction of migration rule schemes from given meta-model evolution rules. Rule schemes form the basis for user customizations on a high abstraction level. A rule scheme deduction algorithm is presented and several customized migration schemes for different co-evolution examples are discussed.

The low-code approach is an important area of research being developed to improve the rapid creation and performance of software applications. This approach allows developers and users to easily create software applications through an interactive interface. Existing research shows that the low-code approach accelerates the development process in innovative ways, saves effort and time, and reduces code complexity. This study analyses and compares automatic code generation and transformation techniques in low-code platforms. The study analyses the contributions of automatic code generation and transformation to software engineering processes and evaluates the impact of these techniques on software product quality and development speed. The importance of the Model-Based Development (MBD) approach in automated code generation processes is highlighted. It is stated that MBD provides benefits such as speeding up the software development process and reducing errors by enabling automatic code generation from high-level abstract models. In the study, various literature studies were evaluated to examine the impact of automatic code generation and transformation techniques on the application development process. These studies have shown how automatic code generation and transformation techniques are applied, what results are achieved and what contributions these techniques make to the software development process. The results of the study show that automatic code generation and transformation techniques have a great impact on the application development process. In particular, the acceleration of the software development process, the reduction of errors and the ability to produce more effective and efficient software products are important benefits of these techniques. In addition, it has been found that this approach increases the success of software projects by enabling software developers to produce fast and accurate solutions in complex systems. In this context, the importance of automatic code generation and transformation techniques plays an important role in software development processes.

This paper reports on a quantitative study, which examines the link between software characteristics, sought after consequences and personal values in software evaluation, whilst investigating the stakeholders' understanding of software quality. The study involved a survey of 403 subjects, which were then analyzed quantitatively with bi-variate analysis, and multivariate analysis of variance. The research argues that trade-offs in software development projects are often experienced in software development because of conflicts. These conflicts involve schedules, priorities and are very much caused by the different stakeholder views of quality, different desired consequences sought by the different stakeholders and more importantly influenced by the desired values of the different stakeholders. The research finds that different classes of stakeholders have different views of software quality. The research also finds that certain values sought by the stakeholder influences their sought after consequences required in the developed software product. However, it is not just any values that affect the stakeholder, but rather, it is the values affected by the evaluated software, which influences the selection of characteristics and sought after consequences. Values, which are important, but are not affected by software use, do not influence the stakeholder. As such, these results help us gain a better understanding of what types of values influence the choice of characteristics in software evaluation, and the desired consequences in a software product, and why conflicts exist during software development life-cycle. The results provide a number of important insights and suggest several conclusions. The study showed (1) that stakeholders differ in their priorities in the sought after consequences of the software being developed; (2) that the desired values, which are perceived to be affected by the software differ between stakeholders and influence the choice of characteristic and consequence; (3) that the consequence, value relationship as described in the Software Evaluation Framework can be valuable to understand the conflicts and trade-offs fond in software development.

Unless the business model that governs software production adjusts to new technology, it is unlikely that an investment in the technology will result in real productivity benefits. Commercial development always takes place in the context of a business model, and in that context an understanding of how business constraints influence commercial software development is imperative. As software markets become more competitive and business pressures shorten software development cycles, improved software development productivity continues to be a major concern in the software industry. Many believe that new software technology, such as object-oriented development, provides a breakthrough solution to this problem. Unfortunately, there is little quantitative evidence for this belief. In this paper we explore the relationship between the business model and the productivity that a software development methodology can achieve in a commercial environment under that model. We first examine empirical data from several commercial products developed using object-oriented methods. The results indicate that object-oriented development may not perform any better than "procedural" development in environments that lack incentives for early completion of intermediate project tasks. We then model and simulate the impact of the software task-completion incentives and deadlines on the productivity that might be expected from a technology with high-performance potential. We show how and why some common business practices might lower project productivity and project completion probability. We also discuss to what extent poor software process control and (im)maturity of the technology compounds the problem.

Typical design flows supporting the software development for multiprocessor systems are based on a board support package and high-level programming interfaces. These software design flows fail to support critical design activities, such as design space exploration or software synthesis. One can observe, however, that design flows based on a formal model of computation can overcome these limitations. In this article, we analyze the major challenges in multiprocessor software development and present a taxonomy of software design flows based on this analysis. Afterwards, we focus on design flows based on the Kahn process network (KPN) model of computation and elaborate on corresponding design automation techniques. We argue that the productivity of software developers and the quality of designs could be considerably increased by making use of these techniques.

Much of contemporary scienti c discussion regarding factors that in uence software de- velopment productivity is undertaken in various domains where there is an insu cient empirical basis for exploring socio-technical factors of productivity that are speci c to a software development organization. The purpose of the study is to characterize the mul- tidimensional nature of software development productivity and its social aspects as a set of latent constructs (i.e. variables that are not directly observed) for a medium-sized software company. To this end, we designed an exploratory in-depth eld study based on the hypothesized productivity constructs, which were modeled by a set of factors identi ed from literature reviews, and later re ned by industrial focus groups. In or- der to demonstrate the applicability of our approach, we conducted con rmatory factor analysis with the data attained from a questionnaire with 216 participants. To investigate factors of in uence further, we analyzed the impact of selected team- based variables over the latent constructs of productivity. Taken together, our ndings con rm that such an approach can be used to explore the quanti able in uence of socio- technical factors that would a ect productivity of a particular software development organization. Ultimately, the resulting model provides guidance to explore the compara- tive importance of a set of rm-speci c factors that may help to improve the productivity of the organization.