xii.308 hal.;28 c

x, 270 hal.: 24 cm; Index

Today e-waste are becoming a major problem for the developing countries. E-waste is defined something as a discarded parts of electronic devices which contains most of the times, hazardous chemicals which is deadly for our environment, example is computer components. Green Computing is the study and practice of designing, using, disposing and manufacturing electronic components in an eco-friendly manner and Green Computing is one of the solution to tackle with this hazardous e-waste problem which is an emerging concern towards the environment. The objective of this paper is to draw the attention towards the lack of awareness about green computing or we can say how green computing policies is being ignored by developing countries and how developed countries are adopting green IT policies seriously. This paper also discusses the analysis which has been done on how the amount of e-waste has been increased in developing countries in past years

The adoption of the 2030 Agenda for Sustainable Development marked a defining moment in the history of the United Nations and the creation of an unprecedented development paradigm bringing together the social, environmental, and economic development strands into one comprehensive, ambitious, and balanced framework. With seventeen interdependent Sustainable Development Goals (SDGs) and 169 targets, the Agenda replaces the narrower and more limited Millennium Development Goals, and has two important features: universality (applicable to all countries and populations); and a commitment to “leaving no one behind”—irrespective of population characteristics or place on the development-humanitarian continuum. SDG 3 (the “health goal”) is supported by nine substantive targets across a broad spectrum of health issues, and four means of implementation targets covering issues such as financing, human resources, and research and development. Given that the social determinants of health (e.g., education, employment, gender-equality) are the focus of other SDGs and the Agenda’s architects conceptualize the goals and targets as interdependent with cross-cutting approaches as well as intersectoral collaboration, in practice at least eleven goals and many more targets are health-related (see World Health Organization 2017, cited under Health-Related Goals, Targets, and Indicators in Agenda 2030). Accountability is key, and many countries have reoriented their national development strategies around the SDGs and have been enthusiastic in presenting Voluntary National Reviews to the annual UN High-Level Political Forum on Sustainable Development. Nonetheless, the SDGs have been critiqued for their omissions (from social mobilization to global health security) as well as their perceived failure to disrupt deep economic and structural injustices which are harmful to people and planet. In our review of the English language literature, we identified over fifty papers addressing some aspect of the SDGs and health. We are reluctant to conceptualize these as a single literature on the broad, diverse, and complex nature of sustainable development as it relates to human health, particularly since a significant proportion are commentaries rather than primary studies or new theoretical/conceptual ideas. We have grouped the papers into six areas: the genesis and significance of Agenda 2030 and its relationship to health; goals, targets, and indicators; projections of progress and financing implications; goal interdependence and intersectoral collaboration; human rights, participation, and the principle of leaving no one behind; critiques and criticisms. If any topic dominates, it is on universal health coverage, one of the thirteen targets in SDG3; conversely the literature tends to lack a detailed prescriptive guidance on how to move from analysis to action. Given the Agenda was only agreed upon in the past few years we are hopeful that policy- and practice-relevant literature on how to implement action and activities to reach the Goals will be forthcoming in the near future. The views contained herein do not necessarily reflect those of UNAIDS.

xvi.282 hal.;21 c

To build secure software, developers often work together during software development and maintenance to find, fix, and prevent security vulnerabilities. Examining the nature of developer interactions during their security activities regarding security introducing and fixing activities can provide insights for improving current practices. In this work, we conduct a large-scale empirical study to characterize and understand developers' interactions during their security activities regarding security introducing and fixing, which involves more than 16K security fixing commits and over 28K security introducing commits from nine large-scale open-source software projects. For our analysis, we first examine whether a project is a hero-centric project when assessing developers' contribution in their security activities. Then we study the interaction patterns between developers, explore how the distribution of the patterns changes over time, and study the impact of developers' interactions on the quality of projects. In addition, we also characterize the nature of developer interaction in security activities in comparison to developer interaction in non-security activities (i.e., introducing and fixing non-security bugs). Among our findings we identify that: most of the experimental projects are non hero-centric projects when evaluating developers' contribution by using their security activities; there exist common dominating interaction patterns across our experimental projects; the distribution of interaction patterns has correlation with the quality of software projects. We believe the findings from this study can help developers understand how vulnerabilitiesoriginate and fix under the interactions of software developers.

xvi.282 hal.;21 c

In this research paper of secure software systems, authors have discussed what the proper development process is when it comes to creating a secure software, which will be suited for developers and relevent stakeholders alike. Secure Software Development Process for Developers is of crucial importance for software engineers as more and more software-based devices are becoming commonly available, and cloud services are evolving which require for the software to be constantly connected to the internet. With this in mind, Secure Software Development needs to be transformed to something most developers can rely upon to make applied software safe and have the capability to mitigate against potential attacks by hackers. Furthermore, in this paper, existing Secure Software Development Process ideas and implementations are reviewed and investigated using the research paper pool available online. Thereafter, an approach is proposed to enhance the security aspect in software development process to resolve security issues. Lastly, the paper concludes with final remarks on practical implementation of security features in software development phases for production of secure and reliable software programs and systems.

xv.271 hal.;23 c

As Large Language Models (LLMs), including ChatGPT and analogous systems, continue to advance, their robust natural language processing capabilities and diverse applications have garnered considerable attention. Nonetheless, despite the increasing acknowledgment of the convergence of Artificial Intelligence (AI) and Software Engineering (SE), there is a lack of studies involving the impact of this convergence on the practices and perceptions of software developers. Understanding how software developers perceive and engage with AI tools, such as ChatGPT, is essential for elucidating the impact and potential challenges of incorporating AI-driven tools in the software development process. In this paper, we conducted a survey with 207 software developers to understand the impact of ChatGPT on software quality, productivity, and job satisfaction. Furthermore, the study delves into developers' expectations regarding future adaptations of ChatGPT, concerns about potential job displacement, and perspectives on regulatory interventions.

xv.271 hal.;23 c

Low/No-code development is a software development method that provides users with a platform for visually creating applications with little or no coding. Companies and organizations need software applications and information systems for various business purposes like management in the technology era. Low/No-code development gives non-IT professionals a convenient tool for rapidly building simple business applications they need without or with little coding. In this paper, we explored the benefits & limitations of Low/No-Code development and modern Low/No-Code development platforms in the industry. In addition, we analyzed how it can be improved and prospected the impacts of Low/No-Code development on society and related industries in the future. In conclusion, we find that Low/No-code development is a promising trend that can significantly impact future software development and digital transformation.

A new workflow for software development (proof-driven development) is presented. An extension of test-driven development, the new workflow utilizes the paradigm of dependently typed programming. The differences in design, complexity and provability of software are discussed, based on the technique used to create the system. Furthermore, the difference in what properties can be expressed in a proof-driven development workflow versus a traditional test-driven development workflow or using test-last development.

The happy-productive worker thesis states that happy workers are more productive. Recent research in software engineering supports the thesis, and the ideal of flourishing happiness among software developers is often expressed among industry practitioners. However, the literature suggests that a cost-effective way to foster happiness and productivity among workers could be to limit unhappiness. Psychological disorders such as job burnout and anxiety could also be reduced by limiting the negative experiences of software developers. Simultaneously, a baseline assessment of (un)happiness and knowledge about how developers experience it are missing. In this paper, we broaden the understanding of unhappiness among software developers in terms of (1) the software developer population distribution of (un)happiness, and (2) the causes of unhappiness while developing software. We conducted a large-scale quantitative and qualitative survey, incorporating a psychometrically validated instrument for measuring (un)happiness, with 2220 developers, yielding a rich and balanced sample of 1318 complete responses. Our results indicate that software developers are a slightly happy population, but the need for limiting the unhappiness of developers remains. We also identified 219 factors representing causes of unhappiness while developing software. Our results, which are available as open data, can act as guidelines for practitioners in management positions and developers in general for fostering happiness on the job. We suggest considering happiness in future studies of both human and technical aspects in software engineering.

113 hal.: Ilust.; 20,5 cm

Software and system development is complex and diverse, and a multitude of development approaches is used and combined with each other to address the manifold challenges companies face today. To study the current state of the practice and to build a sound understanding about the utility of different development approaches and their application to modern software system development, in 2016, we launched the HELENA initiative. This paper introduces the 2nd HELENA workshop and provides an overview of the current project state. In the workshop, six teams present initial findings from their regions, impulse talk are given, and further steps of the HELENA roadmap are discussed.

ill.;105hal.;25c

Moldable development supports decision-making by making software systems explainable. This is done by making it cheap to add numerous custom tools to your software, turning it into a live, explorable domain model. Based on several years of experience of applying moldable development to both open-source and industrial systems, we have identified several mutually supporting patterns to explain how moldable development works in practice. This paper targets (i) readers curious to learn about moldable development, (ii) current users of the Glamorous Toolkit moldable IDE wanting to learn best practices, and (iii) developers interested in applying moldable development using other platforms and technology.

Buku ini memberikan infmasi tentang aliran melingkar kehidupan ekonomi sebagaimana dikondisikan oleh keadaan tertentu, fenomena fundamental dari pembangunan ekonomi, kredit dan modal, laba wirausaha, bunga atas modal, dan siklus bisnis.

In this paper we address the issue of designing developable surfaces with Bezier patches. We show that developable surfaces with a polynomial edge of regression are the set of developable surfaces which can be constructed with Aumann's algorithm. We also obtain the set of polynomial developable surfaces which can be constructed using general polynomial curves. The conclusions can be extended to spline surfaces as well.