PRINCIPLES OF BUILDING SYSTEMS FOR INSTALLING INTEGRATED BOARDS

Video-conferencing and video calls are common nowadays. However, without being able to physically touch or feel each other, we cannot have full immersive communication achieved. Unlike earlier attempts of joining video and haptic communication into one integrated system, we propose to setup an asynchronous method of exchanging haptic interaction data while using traditional ways of video communication. The data packets are exchanged over the Internet cloud server where only participating haptic interface point coordinates, orientation angles of the device handles are transmitted. We also explore more options like using depth-sensing cameras and handtracking devices to capture motion of hand, arm or the whole body of one user so that he becomes both visible and tangible to the other party. The proposed way of communication is validated by technical measurements and a user study. A test of remote connections over long distances was carried out to pave way for further studies.

The ubiquity of complex devices built on systems on chip (SoC) with multiple processor cores poses new challenges for developers of embedded systems. New development tools specifically designed for complex systems on chip can help solve them, but these tools are usually limited by the functionality of debugging support tools. High-quality debugging support with advanced features is necessary to take full advantage of complex SoC devices while reducing development time. The article discusses various mechanisms and ways to implement support for debugging systems on chip designed for complex real-time systems used, for example, in the Internet of Things (IoT) paradigm. This review includes an assessment of the available solutions and their suitability for use with the next generation of complex systems on chip with multiple processor cores. It is shown that many existing solutions do not allow developers to easily take advantage of complex functions integrated into the next-generation SoC. The basic debugging support functions for multicore SoCs are summarized and discussed. Recommendations are given for SoC develo­pers and for the future direction of research in this area in order to provide a more suitable basis for new development tools. Such tools are extremely necessary for all embedded hard real-time systems and are of high importance for minimizing the complexity of their development. Modern systems and devices implementing the Internet of Things paradigm are increasingly required to have sufficiently high real-time performance while maintaining low power consumption. These requirements lead to the cre­ation of multicore SoC solutions with support for a wide range of peripheral devices and communication protocols. The systems are limited by the requirements for working in harsh conditions, such as, for example, in the engine compart­ment of a car or on a radar tower. The development of embedded hard real-time systems, in which a task that fails to be completed on time can lead to physical damage of the device, is a complex process. Effective tools, such as interactive debuggers and profilers, are an integral part of solving these problems and are vital for developing reliable embedded systems. Modern technologies now allow the integration of the entire system on a single silicon chip, known as a system on a chip (SoC), which leads to the relocation of existing external interfaces, widely used for development purposes, to the chip. Traditionally, communication within an embedded system is carried out using an external processor system bus, which is implemented in the form of tracks on a printed circuit board. The printed circuit board must support the appropriate interfaces of development tools that require a physical connection, such as, for example, logic analyzers and oscilloscopes. Previously, placing exter­nal interfaces on a chip left fewer options for external analysis tools and, in fact, makes developers "blind" to the internal state of the SoC. Without a reliable and consistent representation of the state of the embedded system, the detection of defects or errors in the system may become difficult or even impossible. The main solution to the problem of the lack of external interfaces is to provide access to internal nodes from outside the system through existing interfaces. There are many different approaches to achieving the required visibility, and they are outlined in this review.

Computer‐aided software engineering (CASE) is both a field of study and a marketplace. As a field of study, it is the collection of research and development over many years in software development management, methods, environments, and software tools. In general terms, CASE is the industrialization of software engineering techniques and computer technology to improve and automate the practice of information systems development. It is an integration technology that incorporates software development techniques, tools, and approaches into common and consistent frameworks. CASE draws on technologies from computer‐aided design, software engineering, operating systems, database, networking, and many other computer disciplines. Thus CASE is not principally a field of new invention. Rather, it is a field of application, integration, and synthesis. As a marketplace, CASE represents a diverse set of products and services for software development and systems integration. The acronym CASE is used as an umbrella for a wide variety of claims regarding software tools and software development productivity. Definitions of CASE are given. CASE evironments, automation of analusis, computer‐supported collaboration, apportunities for quality engineering, maintenance and reengineering are discussed.

<div class="htmlview paragraph">In modern automotive systems, the complexity is growing by incorporating highly sophisticated microcontrollers running with more than 100MHz and consisting of more than 2500 registers. Software complexity is also growing in a similar, if not higher, rate.</div> <div class="htmlview paragraph">As semiconductor suppliers are also expected by their customers to include a hardware-dependent software layer in their products, testing must now include not only the hardware product but the delivery bundle of hardware and software modules.</div> <div class="htmlview paragraph">Testing this hardware-dependent software is complicated by the big amount of possible hardware-dependent configurations for this software layer which also extensively change the hardware test bench used in verification. The challenge of configuration complexity is solved by extensive use of test automation for both software generation, test bench configuration and test case runs. Additionally, in order to test the full delivery, all software modules have to be configured and tested together in a system-like test.</div> <div class="htmlview paragraph">This paper will discuss the Infineon approach in testing the microcontroller abstraction layer (MCAL) of the AUTOSAR implementation on 32-bit platforms.</div>

When we began, some years ago, building a programming environment for the logical programming language Prolog, the goals we had in mind were predominantly technical ones. Our basic aim was to combine the logical and object-oriented programming styles and to compile a set of tools for constructing Prolog software in a uniform environment. Once we felt we had found satisfactory solutions to the problems involved, we released the programming environment for use by other development groups. We were astounded to find that the external use of our environment led to a number of unexpected problems. We then began not only to eliminate technical errors and inconsistencies, but also to reflect on how it was possible for these problems to arise. The conclusion we reached was that we needed to find answers to a number of questions which went well beyond the original technical problems: What are the building blocks of a programming environment and how can they be “invented”? What is a good building block and how can it be smoothly integrated into an environment? How does an operational building block become an integral part of the developer’s daily work? What are we doing when we develop a programming environment and what are we doing when we work with it?

Software tools are an important part of the programming environment. Perhaps one of the most pervasive type of software tools is the “static analyzer”, as exemplified by cross reference listing tools, and call graph generators. In this paper, we describe an “extensible” static analysis tool (CESAT) which is based on the use of a data base management system and associated query language. The use of the dbms query language allows an virtually unlimited number of tools to be easily constructed, resulting in an “extensible” software tool.

PQE2000 is an Italian project on High Performance Computing (HPC), whose goal is the realization of innovative general purpose systems and programming tools, as well as the development of new strategic HPC applications for industry, commerce and public services. The research activities of PQE2000 include MPP architecture, software tools and programming environments, and applications in technical, transactional and new media areas. The results of these activities are transferred into industrial products. This paper describes the general guidelines, the current products and technologies of PQE2000, and the trends in the area of relationships between programming environments and architectural models for the efficient exploitation of large degree of variable grain parallelism in complex applications.

Imagine you need to build a house. You could choose to build it quickly with pre-made materials, or you could take more time to craft everything by hand for perfect precision. The tools and materials you choose change the speed of construction and the final quality of the home. Programming languages are like those tools for building software. Every programming language is designed with different goals. Some, like Python, are created to be simple and allow developers to write code quickly. Others, like C++, are built to give the programmer a lot of control to make software run as fast and efficiently as possible. This paper explores a simple but important question: How does the choice of a programming language affect the speed and efficiency of the software it creates? We will explore why a program written in one language might run instantly, while the same program written in another language might be slower. We will look at the key reasons for these differences, such as whether a language compiled (translated into machine code beforehand, like C++) or interpreted (translated on the fly while running, like Python). We will also discuss how languages manage memory and how that impacts performance. Ultimately, this research shows that there is no single "best" language. The choice is a classic trade-off: the need for raw speed and efficiency versus the need for fast development and ease of use. Understanding this balance is crucial for software developers and engineers to make the right choice for their specific project.

This paper presents the software tools developed for the research project Advanced Modelling for Power System Analysis and Simulation (AMPSAS) funded by Science Foundation Ireland from 2016 to 2021. The main objective of AMPSAS was the development of novel analytical and computational tools to understand, efficiently design, and optimise ever‐changing modern power systems and smart grids, through model‐based approaches. In particular, the paper discusses (i) stochastic differential equations for modelling power systems, which are subject to large stochastic perturbations (e.g. wind and solar generation); (ii) the effect of controller and modelling imperfections, for example, delays, discontinuities, and digital signals, on both local and area‐wide regulators in power systems; and (iii) the stability analysis and dynamic performance of power systems modelled through stochastic, delay and hybrid implicit differential‐algebraic equations. The software tool developed during the execution of AMPSAS integrates areas of applied mathematics, automatic control, and computer science. Several implementation features and open challenges of this software tool are also discussed in the paper. A variety of examples that illustrates the features of this software tool are based on a dynamic model of the all‐island Irish transmission system.

HPC system users depend on profiling and analysis tools to obtain insights into the performance of their applications and tweak them. The complexity of modern HPC systems have necessitated advances in the associated HPC tools making them equally complex with various advanced features and complex user interfaces. While these interfaces are extensive and detailed, they require a steep learning curve even for expert users making them harder to use for novice users. While users are intuitively able to express what they are looking for in words or text (e.g., show me the process transmitting maximum data), they find it hard to quickly adapt to, navigate, and use the interface of advanced HPC tools to obtain desired insights. In this paper, we explore the challenges associated with designing a conversational (speech/text) interface for HPC tools. We use state-of-the-art AI models for speech and text and adapt it for use in the HPC arena by retraining them on a new HPC dataset we create. We demonstrate that our proposed model, retrained with an HPC specific dataset, can deliver higher accuracy than the existing state-of-the-art pre-trained language models. We also create an interface to convert speech/text data to commands for HPC tools and show how users can utilize the proposed interface to gain insights quicker leading to better productivity.To the best of our knowledge, this is the first effort aimed at designing a conversational interface for HPC tools using state-of-the-art AI techniques to enhance the productivity of novice and advanced users alike.KeywordsConversational AIPerformance toolsSpeech recognitionNatural language processing

The application of quality management based on Islamic values has the potential to shape students’ holistic character by integrating cognitive, affective, and spiritual dimensions. However, the integration of modern management systems with spiritual values often remains conceptually fragmented and lacks a structured implementation framework. This study aims to explore the challenges of integrating spiritual values into modern educational management systems within Islamic educational institutions. Using a qualitative approach with a case study design, data were collected through participant observation, in-depth interviews with school leaders and teachers, and documentation analysis. The findings of the study reveal several key challenges in the integration process. First, there is a conceptual gap between managerial efficiency emphasized in modern systems and the moral-spiritual orientation upheld in Islamic values. Second, institutional resistance emerges due to the lack of understanding and capacity of school leaders in harmonizing both paradigms. Third, the absence of standardized indicators for measuring spiritual dimensions makes the integration process ambiguous and inconsistent. Fourth, external pressures such as accreditation demands and bureaucratic expectations often prioritize measurable outputs over spiritual growth. Lastly, there is limited professional development for educators in implementing spiritually grounded quality management. These challenges suggest the need for a comprehensive framework that aligns modern quality management principles with Islamic educational philosophy, supported by policy, training, and contextual adaptation within the institution.

The priority of modern business systems of municipal waste management is recycling of waste materials while the imperative of their mission is determined by the degree of digital transformation which enables their reproduction, distribution, usage, and storage of information in digital form, as well as new ways of digital communication with the general public. In this paper the focus is on examining the information practices and digital perspectives of municipal waste recycling service providers in Europe. The goal of this paper was to detect information concepts relevant for establishing the degree of their digital maturity. Five data classes were created for the purpose of content analysis method to conduct research on practices on digital communication channels in seven countries to evaluate their availability and accuracy. The designed information model defines a unique conceptual framework of the digital communication information set of the municipal waste recycling service providers.

A description is given of the hierarchical bus architecture (HBA), its programming environment, and algorithmic benchmarks. For local neighborhood operations the HBA implements the Apply programming model. Apply enables the vision programmer to write image-to-image transformations without regard to the details of parallelism, looping, of boundary conditions. The HBA supports all levels of vision operations with floating-point coprocessors, sufficient memory, rapid I/O, and software tools.< <ETX xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">&gt;</ETX>

A Functional Programming Based CACSD Environment

Educational data mining can miss or misidentify key findings about student learning without a transparent process of analyzing the data. This paper describes the first steps in the process of using low-level logging data to understand how middle school students used Alice, an initial programming environment. We describe the steps that were required and the decisions that were made in building a tool to translate the low-level logging data into a form that can be used to investigate educational questions about problem solving strategies for a range of different programming tasks. This work contributes to efforts to analyze educational data, and is important for researchers and tool builders involved with the design of logging systems for other programming environments and software tools.