Systems Software

Adopting the microservices architecture in software development supports modular design, helps programs scale better, and makes the release cycle much faster. This work reviews how Spring Boot supports creating microservices back-end systems in the cloud. It starts by comparing monolithic and distributed systems and highlights what microservices have overcome. Using Spring Boot, Spring Cloud and Spring Security from the Spring ecosystem, the study shares practical methods, successful patterns, and strategies for deploying with Docker and Kubernetes. It looks at implementing DevOps by paying special attention to continuous integration and delivery pipelines. Special attention is given to API design in modules, the ability to easily handle load changes and the separation of faults. Case studies and scholarly studies are presented in the paper to explain how Spring Boot makes development faster, maintenance easier and production scaling better. They show developers and architects how to design adaptable and stable systems with Spring Boot microservices.

A survey of 400 recent research articles suggests that computer scientists publish relatively few papers with experimentally validated results. The survey includes complete volumes of several refereed computer science journals, a conference, and 50 titles drawn at random from all articles published by ACM in 1993. The journals of Optical Engineering (OE) and Neural Computation (NC) were used for comparison. Of the papers in the random sample that would require experimental validation, 40% have none at all. In journals related to software engineering, this fraction is 50%. In comparison, the fraction of papers lacking quantitative evaluation in OE and NC is only 15% and 12%, respectively. Conversely, the fraction of papers that devote one fifth or more of their space to experimental validation is almost 70% for OE and NC, while it is a mere 30% for the computer science (CS) random sample and 20% for software engineering. The low ratio of validated results appears to be a serious weakness in computer science research. This weakness should be rectified for the long-term health of the field. 1. The fundamental principle of science, the definition almost, is this: the sole test of the validity of any idea is experiment.

This work addresses the leader election problem in partially synchronous distributed systems where processes can crash and recover. More precisely, it focuses on implementing the Omega failure detector class, which provides a leader election functionality, in the crash-recovery failure model. The concepts of communication efficiency and near-efficiency for an algorithm implementing Omega are defined. Depending on the use or not of stable storage, the property satisfied by unstable processes, i.e., those that crash and recover infinitely often, varies. Two algorithms implementing Omega are presented. In the first algorithm, which is communication-efficient and uses stable storage, eventually and permanently unstable processes agree on the leader with correct processes. In the second algorithm, which is nearcommunication-efficient and does not use stable storage, processes start their execution with no leader in order to avoid the disagreement among unstable processes, that will agree on the leader with correct processes after receiving a first message from the leader.

Software architecture design is challenging, especially for junior software designers. Lacking practice and experience, junior designers need process support in order to make rational architecture decisions. In this paper, we present the results of a comparative multiple-case study conducted to find out if decision viewpoints from van Heesch et al. (2012, in press) can provide such a support. The case study was conducted with four teams of software engineering students working in industrial software projects. Two of the four teams were instructed to document their decisions using decision viewpoints; the other two teams were not instructed to do so. We observed the students for a period of seven weeks by conducting weekly focus groups and by analyzing their work artifacts and minutes. Our findings suggest that junior designers who use decision viewpoints are more systematic in exploring and evaluating solution options. However, the decision viewpoints did not help them in managing requirements and complexity.

Design space exploration is the simultaneous analysis of problem and solution spaces for a specific domain or application scope. Performing this activity as part of the architectural design is beneficial, especially for software platforms, which are shared across organizations. Exploring the design space of software platforms in a multi-product and multi-domain context is not trivial, and only few methods exist to support this activity systematically. This paper reports on a longitudinal technical action research (TAR) study conducted to adapt and evaluate architecture decision viewpoints for supporting platform design space exploration. The study was conducted in the context of an ABB project, which was performed to explore the design space for a common software platform for mobile device support in several product-specific software platforms at ABB. The results indicate that the adapted decision viewpoints are well suitable for dealing with diverging stakeholder concerns, evaluating technological alternatives and uncovering relationships between decisions to be made.

In this paper, we introduce a documentation framework for architecture decisions. This framework consists of four viewpoint definitions using the conventions of ISO/IEC/IEEE 42010, the new international standard for the description of system and software architectures. The four viewpoints, a Decision Detail viewpoint, a Decision Relationship viewpoint, a Decision Chronology viewpoint, and a Decision Stakeholder Involvement viewpoint satisfy several stakeholder concerns related to architecture decision management. With the exception of the Decision Stakeholder Involvement viewpoint, the framework was evaluated in an industrial case study. The results are promising, as they show that decision views can be created with reasonable effort while satisfying many of the stakeholder concerns in decision documentation.

Software architecture design is challenging, especially for junior software designers. Lacking practice and experience, junior designers need process support in order to make rational architecture decisions. In this paper, we present the results of a comparative multiple-case study conducted to find out if decision viewpoints from van Heesch et al. (2012, in press) can provide such a support. The case study was conducted with four teams of software engineering students working in industrial software projects. Two of the four teams were instructed to document their decisions using decision viewpoints; the other two teams were not instructed to do so. We observed the students for a period of seven weeks by conducting weekly focus groups and by analyzing their work artifacts and minutes. Our findings suggest that junior designers who use decision viewpoints are more systematic in exploring and evaluating solution options. However, the decision viewpoints did not help them in managing requirements and complexity.

Technical debt, a metaphor for the long-term consequences of weak software development, must be managed to keep it under control. The main goal of this article is to identify and analyze the elements required to manage technical debt. The research method used to identify the elements is a systematic mapping, including a synthesis step to synthesize the elements definitions. Our perspective differs from previous literature reviews because it focused on the elements required to manage technical debt and not on the phenomenon of technical debt or the activities used in performing technical debt management. Additionally, the rigor and relevance for industry of the current techniques used to manage technical debt are studied. The elements were classified into three groups (basic decision-making factors, cost estimation techniques, practices and techniques for decision-making) and mapped according three stakeholders' points of view (engineering, engineering management, and business-organizational management).

Software reliability is a cornerstone of software engineering as undetected bugs can have severe consequences. In this paper, We propose to use GA and SRGM to be our intelligent model which is to schedule the testing process to get maximum faults with minimal testing time. The proposed framework dynamically schedules testing efforts along with SRGM parameters, exploring GAs' optimization potential by extending basic models including the Jelinski-Moranda and the Goel-Okumoto models and further developments having covered to testing and adaptive test generation. The methodology is cost efficient and reliability oriented. Based on theoretical analysis and simulated case studies, we present that fault detection and resource allocation can be enhanced. This paper combines old and new results to answer open questions on complex software systems

Adopting the microservices architecture in software development supports modular design, helps programs scale better, and makes the release cycle much faster. This work reviews how Spring Boot supports creating microservices back-end systems in the cloud. It starts by comparing monolithic and distributed systems and highlights what microservices have overcome. Using Spring Boot, Spring Cloud and Spring Security from the Spring ecosystem, the study shares practical methods, successful patterns, and strategies for deploying with Docker and Kubernetes. It looks at implementing DevOps by paying special attention to continuous integration and delivery pipelines. Special attention is given to API design in modules, the ability to easily handle load changes and the separation of faults. Case studies and scholarly studies are presented in the paper to explain how Spring Boot makes development faster, maintenance easier and production scaling better. They show developers and architects how to design adaptable and stable systems with Spring Boot microservices.

Software reliability is a cornerstone of software engineering as undetected bugs can have severe consequences. In this paper, We propose to use GA and SRGM to be our intelligent model which is to schedule the testing process to get maximum faults with minimal testing time. The proposed framework dynamically schedules testing efforts along with SRGM parameters, exploring GAs' optimization potential by extending basic models including the Jelinski-Moranda and the Goel-Okumoto models and further developments having covered to testing and adaptive test generation. The methodology is cost efficient and reliability oriented. Based on theoretical analysis and simulated case studies, we present that fault detection and resource allocation can be enhanced. This paper combines old and new results to answer open questions on complex software systems

This study examines the effectiveness of a hybrid Convolutional Neural Network (CNN) and Long Short-Term Memory (LSTM) model for predicting software bugs, with the objective of improving code quality and dependability. The research leverages the JM1 dataset from the PROMISE Software Engineering Repository and utilizes sophisticated preprocessing approaches, including Borderline-SMOTE, SMOTETomek, RobustScaler, Yeo-Johnson transformation, and Recursive Feature Elimination, to mitigate class imbalance and feature redundancy. The CNN-LSTM model attained a validation accuracy of 98.10%, a precision of 91.42%, and a recall of 99.53%, exhibiting a minimal false negative rate and indicating great sensitivity in detecting defect-prone modules. The results underscore the model's capacity to identify spatial and sequential patterns in software metrics, providing a reliable instrument for early fault identification. This work enhances software engineering by confirming deep learning's efficacy in defect prediction, offering practical insights for developers, and delineating future research avenues for cross-project generalization and model optimization.

Permasalahan kesehatan di masyarakat semakin kompleks. Permasalahan penyakit menular belum terselesaikan, sudah makin marak penyakit tidak menular. Permekes RI No. 36 tahun 2016 pasal 1 menyebutkan bahwa Penyelenggaraan Program Indonesia Sehat dengan Pendekatan Keluarga. Desa II Sukasari Desa Sukadadi Kecamatan Gedong Tataan Kabupaten Pesawaran Provinsi Lampung merupakan salah satu daerah dengan permasalahan komplek. Dengan permasalahan kesehatan yang ada dimasyarakat dibutuhkan kesadaran dan keterampilan masyarakat dalam melakukan upaya-upaya pencegahan dan pengendalian terhadap kejadian penyakit agar tidak semakin berat. Dalam mencapai tujuan tersebut, memerlukan peranan dari berbagai tenaga kesehatan secara terintegrasi dari berbagai disiplin ilmu berbeda yang memiliki kompetensi dan bekerja secara team work. Pelaksanaan pengabdian masyarakat Masyarakat di Desa Sukadadi Kecamatan Gedong Tataan Kabupaten Pesawaran diawali dengan penyamaan persepsi, pelatihan kader dan pendampingan...

Abstrak: Faktanya, masih ada beberapa guru SD yang menulis artikel di koran atau mempresentasikan artikel mereka di seminar regional / nasional. Akibatnya, mereka akan menghadapi kendala dalam meningkatkan nilai mereka. Berdasarkan survei, kami menemukan bahwa banyak guru SD di Desa Sagaranten Kecamatan Ciwaru Kab.Kuningan masih belum tahu bagaimana membuat artikel yang bagus. Juga, tidak ada Jurnal untuk guru SD sebagai media bagi mereka dalam mengirimkan artikel mereka untuk memiliki beberapa kredit. Berdasarkan kasus itu, tim layanan masyarakat mencoba memberi mereka beberapa pelatihan bagaimana merancang penelitian kelas, dan bagaimana membuat artikel yang bagus. Dengan memiliki ini, mereka diharapkan dapat menemukan topik mereka dan merancang penelitian kelas mereka, kemudian mereka akan membuat artikelnya yang dapat dikirim ke surat kabar atau jurnal. Secara otomatis, mereka akan memiliki beberapa kredit untuk menaikkan nilai mereka dan mereka akan sejahtera. Pelatihan diberik...

This paper gives a self contained description of classical IP internet protocol and ARP address resolution protocol o ver ATM asynchronous transfer mode and describes a model facilitating the implementation of the switched virtual circuit based local area network ATM subnet model. Its contents are distilled from the design and implementation of a prototype of a device driver for this particular subnet model. The work was conducted at the Computer Science Laboratory CSL at the Xerox Palo Alto Research Center PARC. We outline the main features of the two technologies, establish their importance as data communication paradigms, motivate their integration, and sketch several scenarios of their interaction. We concentrate on one speci c scenario: the utilization of ATM as a logical IP subnetwork. Building blocks of this approach are the ATM address resolution protocol as a unicast server based emulation of the classical broadcast address resolution protocol, and connection management functionality a s provided by the Q.2931 protocol. The manipulation of transmitted network protocol data units between their submission to the network layer and their transmission by ATM are detailed in an appendix. These explanations are structured analogous to the lower layers in the IEEE local area network model. The complexity and intricacy of the logical IP subnetwork LIS approach motivate the development of a model describing the interaction of all participants in an LIS. The devised model is based on a nite automaton. It instruments a structured implementation and it assists in convincing the implementor of the completeness and correctness of the implementation by facilitating its gradual testing and extension.

A communication protocol is a set of rules shared by two or more communicating parties on the sequence of operations and the format of messages to be exchanged. Standardization organizations define protocols in the form of recommendations (e.g., RFC) written in technical English, which requires a manual translation of the specification into the protocol implementation. This human translation is error-prone due in part to the ambiguities of natural language and in part due to the complexity of some protocols. To mitigate these problems, we divided the expression of a protocol specification into two parts. First, we designed an XML-based protocol specification language (XPSL) that allows for the high-level specification of a protocol-expressed as a Finite State Machine (FSM)using Component-Based Software Engineering (CBSE) principles. Then, the components required by the protocol are specified in any suitable technical language (formal or informal). In addition, we developed the multi-layer Meta-Protocol framework, which allows for on-the-fly protocol discovery and negotiation, distribution of protocol specifications and components, and automatic protocol implementation in any programming language.

Ketatnya persaingan sumber daya manusia (SDM) khususnya perawat dirasakan oleh puskesmas. Setiap pekerjaan menuntut sumber daya manusia (SDM) untuk meningkatkan kualitas pelayanan keperawatan. Pentingnya produktivitas kerja bagi perawat adalah bahan evaluasi untuk melakukan perbaikan secara terus menerus bagi komponen puskesmas dalam rangka peningkatan mutu hasil kerja yang ingin yang capai. Tujuan penelitian ini untuk mengetahui faktor – faktor yang berhubungan dengan produktivitas kerja perawat terhadap pelayanan keperawatan di Puskesmas Pidie Kabupaten Pidie . Penelitian ini bersifat Analitik dengan tehnik pengambilan sampel total sampling dan jumlah sampel 33 perawat. Data dikumpulkan langsung dari responden dengan mengedarkan kuisioner. Hasil penelitian diolah dengan menggunakan komputer dan disajikan dalam bentuk tabel distribusi frekwensi dan analisa silang. Penelitian dilakukan mulai tanggal 23 - 28 Maret 2019. Hasil penelitian P-value 0,004 < 0,05, ada hubungan motivasi ...

Nowadays, many companies design and develop their software systems as a set of loosely coupled microservices that communicate via their Application Programming Interfaces (APIs). While the loose coupling improves maintainability, scalability, and fault tolerance, it poses new challenges to the API evolution process. Related works identified communication and integration as major API evolution challenges but did not provide the underlying reasons and research directions to mitigate them. In this paper, we aim to identify microservice API evolution strategies and challenges in practice and gain a broader perspective of their relationships. We conducted 17 semi-structured interviews with developers, architects, and managers in 11 companies and analyzed the interviews with open coding used in grounded theory. In total, we identified six strategies and six challenges for REpresentational State Transfer (REST) and event-driven communication via message brokers. The strategies mainly focus on API backward compatibility, versioning, and close collaboration between teams. The challenges include change impact analysis efforts, ineffective communication of changes, and consumer reliance on outdated versions, leading to API design degradation. We defined two important problems in microservice API evolution resulting from the challenges and their coping strategies: tight organizational coupling and consumer lock-in. To mitigate these two problems, we propose automating the change impact analysis and investigating effective communication of changes as open research directions.

In FinTech organizations, there are trends toward employing agile methods, moving away from legacy monolithic technical architecture to microservices architecture, and focusing on collaboration and autonomy to boost innovation. When software teams have end-to-end responsibility and decision-making authority, they avoid handovers between teams and can develop software more quickly. Furthermore, effective coordination through meetings and digital collaboration tools is important for the success of the development of software applications. We conducted a case study in a large FinTech organization to understand behavioral aspects of software development and, specifically, their meeting practices. The results show that employees spend nearly half of their workday in meetings, posing challenges to productivity and availability. Strategies to reduce interruptions include blocking time in calendars, grouping meetings, and using digital tools such as Slack. Our findings indicate that achieving a balance between collaborative activities and uninterrupted work is not only challenging but essential in software development organizations. Consequently, it is important that team members discuss and actively experiment with various strategies to optimize this balance.

Software design patterns offer modular, maintainable, and scalable approaches for contemporary software engineering. This research offers a qualitative systematic review performed following PRISMA guidelines. Out of an initial search of 226 publications, 84 articles underwent full-text screening, leading to the inclusion of 42 peer-reviewed studies (published from 2013 to 2024) in the nal synthesis. The evaluation was directed by four research inquiries focusing on categorization, contextual application, compromises, and the development of design patterns. Results showed that architectural patterns (MVC, layered architecture, microservices) were the most frequently referenced, with 41 mentions, followed by cloud-native and microservice-related patterns (37 mentions), creational patterns (31 mentions), structural patterns (28 mentions), and event-driven/reactive patterns (25 mentions). Concurrency patterns were mentioned the least (14 occurrences), indicating their growing incorporation into frameworks. In various sectors, web, mobile, enterprise, and cloud applications displayed unique adoption patterns, with MVC leading in web environments, MVVM common in mobile platforms, and microservices and CQRS fundamental to cloud architectures. Analysis of trade-offs highlighted recurring con icts like simplicity versus testability (Singleton), exibility versus readability (Factory Method), and independence versus integration complexity (Microservices). Timeline mapping illustrated the transition from monolithic models to distributed, event-driven, and serverless architectures from 2010 to 2024, showing a distinct increase in cloud-native adoption after 2018. The study ends with suggestions for context-sensitive pattern choice and emphasizes the importance of further investigation into AIautomated patterns, edge-native orchestration, and quantum-ready software designs, framing design patterns as an ever-evolving structure for tackling software engineering challenges in the 21st century.

To what extent can the plyometric standing jump over training affect the jump height of the volleyball game jump service on the Men's Penjaskesrek Undana team? This study aims to see the results of the plyometric standing jump over training to increase the jump height of the service jump. This type of research is experimental research. The sample of this research is the men's team volleyball player Penjaskesrek Undana maybe 20 people. Data collection was carried out by means of observation, test and measurement techniques as well as documentation. Based on the results of the study, it can be seen that the significant value that is different between the two groups is 56.4 for the pre-test and 65.3 for the post-test in the experimental group while in the control group, namely 54.7 for the pre-test and 57.2 for the post -test -test. Because the second significant value is greater than 0.05 (significant> 0.05), the data is declared to be normally distributed (accepted). The d...

This paper presents an approach for analyzing complex processes, including those involving human agents, hardware devices, and software systems, and illustrates the utility of this approach by analyzing part of a process for holding an election. In the work described here, the Little-JIL process definition language is used to create a precise and detailed model of an election process. Given this process definition, two forms of automated analysis are used to explore the possibility that specified security policies could be undermined. Model checking is first used to identify process execution sequences that violate event-sequence security policies and other properties. After these are addressed, fault-tree analysis is applied to identify when the misperformance of steps might allow security breaches or other undesirable outcomes to occur. The results of these analyses can provide assurance about the process, suggest areas for improvement, and, when applied to a modified process defi...

Electronic voting machines are becoming an increasingly popular alternative to paper ballots. With this increase in use we must analyze how well these machines adhere to voting requirements, including those relating to security, privacy, and anonymity. This paper includes analysis of the security and auditing mechanisms of the open-source electronic voting system Scantegrity. We focus on Scantegrity, not to single it out as a vulnerable system, but because it is a popular system that has actually been used in practice. It may contain design flaws and vulnerabilities that might exist in other systems of similar designs, current or future. Therefore, it is our hope that the vulnerabilities that we bring to light will be considered by current and future designers of electronic voting systems, and that the solutions that we propose will also be considered as possible remediations.

The Information Technology Engineering and Measurement (ITEM) Model has been developed to describe the information processing activities of an enterprise, both the automated tasks performed by computer and the manual processes performed by the information technology staff of an organization. In this article, the ITEM model is applied to the description of software engineering environments as extensions to two previously developed reference models, the NIST/ ECMA framework (i.e., "toaster") model and the Project Support Environment reference model. The ability to measure the degree of automation within a process, the ability to define the complexity of a process, and the ability to measure technology transition via a concept called technological drift are ail metrics that can evolve from this model. 0 1997 by Elsevier Science Inc. The ability to accurately model information technology use within an organization is taking on increased importance as computers take on increasingly central roles in an organization. We describe one model that can be used to model this technology and which provides the basis for use in roles such as requirements analysis for software development, quantitative evaluation of computer technology use, and traceability of software requirements and designs. The concept of an environment within the software engineering field has grown to mean an infrastructure set of services (e.g., a file system) and a set of end user services (e.g., the set of tools to be used such as editors, compilers).

This study aimed to assess the effect of transformational leadership on the effectiveness of administrative decisions and to identify the level of practicing it in pharmaceutical companies in Yemen. It also aimed to identify any statistically significant differences among the participants› responses regarding the effectiveness of administrative decisions attributed to organizational variables, including company age, size and ownership. To achieve the study objectives, the descriptive analytical method was used and a questionnaire was administered to a sample of 330 participants selected by the complete census sampling method from nine pharmaceutical companies in Yemen. Only 273 questionnaires were valid for statistical analysis. Major findings revealed that the companies under study have shown paramount interest in the effectiveness of administrative decisions, including all dimensions, where the mean of the level of performance was high. However, the level of practicing transformational leadership did not reach the level of decision effectiveness, where the practice level was medium. Furthermore, there were differences at the level of the impact of the dimensions of transformational leadership on the effectiveness of administrative decisions; the highest effective difference was the individualized consideration, and the least one was the inspiration motivation. The study stressed the need to promote the practice of transformational leadership in companies so as to achieve effective administrative decisions.

There has been a massive explosion of data generated by customers and retained by companies in the last decade. However, there is a significant mismatch between the increasing volume of data and the lack of automation methods and tools. The lack of best practices in data science programming may lead to software quality degradation, release schedule slippage, and budget overruns. To mitigate these concerns, we would like to bring software engineering best practices into data science. Specifically, we focus on automated data validation in the data preparation phase of the software development life cycle. This paper studies a real-world industrial case and applies software engineering best practices to develop an automated test harness called RESTORE. We release RESTORE as an open-source R package. Our experience report, done on the geodemographic data, shows that RE-STORE enables efficient and effective detection of errors injected during the data preparation phase. RESTORE also significantly reduced the cost of testing. We hope that the community benefit from the open-source project and the practical advice based on our experience.

This position paper addresses the usefulness (or otherwise) of the Software Engineering Body of knowledge (SWEBOK) version 3 for software practitioners in industry, and the consequent need for the SWEBOK to evolve to better address current industry practice. The position taken in this paper is that agile and lean methods are now the predominant approach to software engineering, and that the limited and anachronistic coverage of agile methods in the SWEBOK, coupled with the absence of any acknowledgement of lean approaches, is undermining software engineering education, the career prospects of graduates, and the software industry as a whole. It is therefore proposed that the agile methods section of the SWEBOK is revised and expanded such that it provides a valid body of knowledge for contemporary software engineering

Offshore outsourcing across the world has triggered a new social structure in the way global businesses operate, resulting in emerging virtual social spaces between clients and vendors. These social structures involve understanding of cultural connections over space and time through telecommunication networks, as knowledge intensive tasks are being realized across national boundaries. Clients and vendors belonging to diverse cultures are required to take measures to build trust in relationships for sustained professional success. This paper looks at the trust building practice and experience of four small and medium sized software vendor organizations based in New Zealand and India. The case study data reveals how vendors are sensitized to client apprehensions in sharing knowledge across virtual social spaces. Some practices identified are face-to-face communication to bring visibility of social cue codes, documentation as a common thread of control, international accreditations to ...

Agile methods have been increasingly adopted as a way to increase the speed and flexibility of software development whilst maintaining or improving quality. However, organisations with a heavy investment in, and emphasis on, more traditional software engineering approaches may regard the wholesale adoption of agile methods as being potentially risky. As a result, a number of experiments in hybrid approaches have been made, suggesting that a combination of agile methods and traditional software engineering can be a route to quality software development. Further, that component based software engineering has an important role to play. In this paper we review the key issues in this debate and propose that test related practises are the most significant enabler in providing quality assurance in hybrid systems.

In this paper the problem of providing network response guarantees to multiple Virtual Machines (VMs) co-scheduled on the same set of CPUs is tackled, where the VMs may have to host both responsive real-time applications and batch compute-intensive workloads. When trying to use a real-time reservationbased CPU scheduler for providing stable performance guarantees to such a VM, the compute-intensive workload would be scheduled better with high time granularities, to increase performance and reduce system overheads, whilst the real-time workload would need lower time granularities in order to keep the response-time under acceptable levels. The mechanism that is proposed in this paper mixes both concepts, allowing the scheduler to dynamically switch between fine-grain and coarse-grain scheduling intervals depending on whether the VM is performing network operations or not. A prototype implementation of the proposed mechanism has been realized for the KVM hypervisor when running on Linux, modifying a deadline-based real-time scheduling strategy for the Linux kernel developed previously. The gathered experimental results show that the proposed technique is effective in controlling the response-times of the real-time workload inside a VM while at the same time it allows for an efficient execution of the batch compute-intensive workload.

This paper explores the migration from traditional on-premise systems to cloud-based solutions through a case study approach. It highlights the theoretical background, the process of migration, challenges encountered, and the results achieved. Findings reveal significant improvements in system performance, cost efficiency, and user satisfaction, alongside enhanced disaster recovery capabilities. The paper concludes with recommendations for organizations considering similar transitions.

In this paper, we discuss the two approaches to the type of formalism used to express specifications: logic-based approach and model-based approach. Temporal logic and state machine, representatives of formalisms used in each approach, are compared. As a result of this comparison, we know that although temporal logics have many advantages, especially abstraction and flexibility of the specification process, they fail to directly characterize situations easily modeled by model-based formalisms, such as "local" properties of execution sequences. To copy with these drawbacks, we present a new kind of formalism: fair transition system specification (FTSS). This approach combines the best features of temporal logic and state machine methods and it is easy to understand and use. A nontrivial example is used to illustrate our approach and it shows that our FTSS approach is promising.

Context: Software programs can be written in different but functionally equivalent ways. Even though previous research has compared specific formatting elements to find out which alternatives affect code legibility, seeing the bigger picture of what makes code more or less legible is challenging. Goal: We aim to find which formatting elements have been investigated in empirical studies and which alternatives were found to be more legible for human subjects. Method: We conducted a systematic literature review and identified 15 papers containing human-centric studies that directly compared alternative formatting elements. We analyzed and organized these formatting elements using a card-sorting method. Results: We identified 13 formatting elements (e.g., indentation) and 33 levels of formatting elements (e.g., two-space indentation), which are about formatting styles, spacing, block delimiters, long or complex code lines, and word boundary styles. While some levels were found to be statistically better than other equivalent ones in terms of code legibility, e.g., appropriate use of indentation with blocks, others were not, e.g., formatting layout. For identifier style, we found divergent results, where one study found a significant difference in favor of camel case, while another study found a positive result in favor of snake case. Conclusion: * Authors contributed equally.

DYANA 1 is an environment designed for development of distributed systems. We demonstrate that DYANA augmented with UPPAAL is well suited for simulation and model checking of real-time embedded system designs defined with UML statecharts. To this end, we present the case studies of onboard systems for cars and aircrafts as well as of a general-purpose fault-tolerant system for running parallel programs. For each case study we give its informal description, specify a formal model defined with UML diagrams and report on the simulation and model checking results.

In this paper we present DYANA, an HLA-based hardware-in-the-loop simulation tool. This tool is used for distributed Real-Time Embedded Systems (RTES) simulation. RTES models are described by Unified Modeling Language (UML) statechart diagrams. The statechart diagram is transformed into HLA-based Simulation Model (HSM). After translation into HSM we use CERTI as the simulation runtime. The statechart diagram is also transformed into a Network of Timed Automata (NTA). After translation into NTA we use UPPAAL for RTES model verification.

DYANA 1 is an environment designed for development of distributed systems. We demonstrate that DYANA augmented with UPPAAL is well suited for simulation and model checking of real-time embedded system designs defined with UML statecharts. To this end, we present the case studies of onboard systems for cars and aircrafts as well as of a general-purpose fault-tolerant system for running parallel programs. For each case study we give its informal description, specify a formal model defined with UML diagrams and report on the simulation and model checking results.

Computer-Supported Collaborative Language Learning (CSCLL) has been proved to offer many advantages to language learners. However, teachers argue that the use of complicated pedagogies such as imagination-based techniques in combination with innovative technologies lead to a "complex ecosystem" in which many issues of management appear. This paper examines how students' motivation and engagement are influenced when implementing imagination-based pedagogies in a web-based Computer-Supported Collaborative Language Learning writing activity with shared orchestration load.

This study was conducted to determine the effect of food safety knowledge level among high school students on their attitude to the subject. A total of 912 high school students between 15 and 17 years of age were included in the study and data was collected through questionnaires. The majority of those included in the study were male (70.4 %). The food safety knowledge level of females ( Χ =15.59±4.52) was found to be higher than that of males ( Χ =10.90±5.01). Similarly, the attitude scores of females were found to be higher in comparison with male participants ( Χ =46.67±5.98 and 43.53±7.03, respectively). A statistically significant difference between the genders in knowledge and attitude scores was found (p<0.001). There was also a positive relationship between food safety knowledge level and attitude (r=0.240, p<0.01).

Program conditioning consists of identifying and removing a set of statements which cannot be executed when a condition of interest holds at some point in a program. It has been applied to problems in maintenance, testing, re-use and re-engineering. Program conditioning relies upon both symbolic execution and reasoning about symbolic predicates. Automation of the process therefore requires some form of automated theorem proving. However, the use of a full-power 'heavyweight' theorem prover would impose unrealistic performance constraints. This paper reports on a lightweight approach to theorem proving using the FermaT simplify decision procedure. This is used as a component to ConSUS, a program conditioning system for the Wide Spectrum Language WSL. The paper describes the symbolic execution algorithm used by ConSUS, which prunes as it conditions. The paper also provides empirical evidence that conditioning produces a significant reduction in program size and, although exponential in the worst case, the conditioning system has low degree polynomial behaviour in many cases, thereby making it scalable to unit level applications of program conditioning.

We address the research question of transforming dependability requirements into corresponding software architecture constructs, by proposing first that dependability needs can be classified into three types of requirements and second, an architectural pattern that allows requirements engineers and architects to map dependability requirements into three corresponding types of architectural components. The proposed pattern is general enough to work with existing requirements techniques and existing software architectural styles, including enterprise and product-line architectures.

This study examines scientific publications during a pandemic through bibliometric network analysis. We explored three different journal databases to map COVID-19 research in humanities and social sciences, then zoom in to communication studies. Government policy, e-learning, anxiety, economic impact are popular keywords in international and Indonesian articles on Social and Humanities, while disinformation, health communication, behavior change, and literacy are more prominent in communication articles. The researcher chose the keyword occurrence analysis as the basis for mapping the research theme. The bibliographic network was deployed in three strategies to obtain keyword data co-occurrence from research abstracts, keywords from researchers, and coder&#39;s approval keywords. Lastly, Vos viewer is used to creating macro and detailed perspective networks for interpretation. The results show that journal policies and models affect the number of COVID-19 publications in the journal...

Object-oriented analysis and design has become a major approach in the design of software systems. Recent developments in CASE tools provide help in documenting the analysis and design stages and in detecting incompleteness and inconsistency in analysis. However, these tools do not contribute to the initial and difficult stage of the analysis process of identifying the objects/classes, attributes and relationships used to model the problem domain. This paper presents a tool, Class-Gen, which can partially automate the identification of objects/classes from natural language requirement specifications for object identification. Use case descriptions (UCDs) provide the input to Class-Gen which parses and analyzes the text written in English. A parsed use case description (PUCD) is generated which is then used as the basis for the construction of an initial UML class model representing object classes and relationships identified in the requirements. PUCDs enable the extraction of nouns, verbs, adjectives and adverbs from traditional UCDs for the identification process. Finally Class-Gen allows the initial class model to be refined manually. Class-Gen has been evaluated against a collection of unseen requirements. The results of the evaluation are encouraging as they demonstrate the potential for such tools to assist with the software development process.

A "Smart City" is intended as an urban environment which, supported by pervasive ICT systems, is able to offer advanced and innovative services to citizens in order to improve the overall quality of their life. In this context, the present contribution formulates a pioneering proposal, by drawing an advanced information centric platform for supporting the typical ICT services of a Smart City. It can easily embrace all available and upcoming wireless technologies, while enforcing, at the same time, ubiquitous and secure applications in many domains, such as,e-government and public administration, intelligent transportation systems, public safety, social, health-care, educational, building and urban planning, environmental, and energy and water management applications. All the details of the proposed approach have been carefully described by means of pragmatical use-cases, such as the management of administrative procedures, the starting of a new business in a given country, the navigation assistance, the signaling of an urban accident aimed at improving the public safety, the reservation of a medical examination, the remote assistance of patients, and the management of waste in a city. This description makes evident the real effectiveness of the present proposal in future urban environments.

The Amoeba distributed operating system has been in development and use for over eight years now, which is a long enough period to warrant taking a look back at its successes and failures. We will first describe the current version of the system in some detail, as it has evolved considerably since the first publication about it. We will emphasize those aspects of the system that we consider novel, interesting, and not present in many other systems of its type. Then we will look at the measured performance of Amoeba and compare it to the performance of other systems. Finally we will specifically discuss a number of the critical design choices we have made, and point out those we consider successful and those we consider unsuccessful.

Entity Matching (EM), ou seja, a tarefa de identificar entidades que se referem a um mesmo objeto do mundo real, é uma tarefa importante e difícil para a integração e limpeza de fontes de dados. Uma das maiores dificuldades para a realização desta tarefa, na era de Big Data, é o tempo de execução elevado gerado pela natureza quadrática da execução da tarefa. Para minimizar a carga de trabalho preservando a qualidade na detecção de entidades similares, tanto para uma ou mais fontes de dados, foram propostos os chamados métodos de indexação ou blocagem. Estes métodos particionam o conjunto de dados em subconjuntos (blocos) de entidades potencialmente similares, rotulando-as com chaves de bloco, e restringem a execução da tarefa de EM entre entidades pertencentes ao mesmo bloco. Apesar de promover uma diminuição considerável no número de comparações realizadas, os métodos de indexação ainda podem gerar grandes quantidades de comparações, dependendo do tamanho dos conjuntos de dados env...

Entity Matching (EM), i.e., the task of identifying records that refer to the same entity, is a fundamental problem in every information integration and data cleansing system, e.g., to find similar product descriptions in databases. The EM task is known to be challenging when the datasets involved in the matching process have a high volume due to its pair-wise nature. For this reason, studies about challenges and possible solutions of how EM can benefit from modern parallel computing programming models, such as Apache Spark (Spark), have become an important demand nowadays [1][2]. The effectiveness and scalability of Spark-based implementations for EM depend on how well the workload distribution is balanced among all workers. In this article, we investigate how Spark can be used to perform efficiently (load balanced) parallel EM using a variation of the Sorted Neighborhood Method (SNM) that uses a varying (adaptive) window size. We propose Spark Duplicate Count Strategy (S-DCS++), a Spark-based approach for adaptive SNM, aiming to increase even more the performance of this method. The evalu-

Model-driven engineering relies on effective collaboration between different teams which introduces complex model management challenges. DSE Merge aims to efficiently merge model versions created by various collaborators using searchbased exploration of solution candidates that represent conflictfree merged models guided by domain-specific knowledge. In this paper, we report how we systematically evaluated the efficiency of the DSE Merge technique from the user point of view using a reactive experimental Software engineering approach. The empirical tests included the involvement of the intended end users (i.e. engineers), namely undergraduate students, which were expected to confirm the impact of design decisions. In particular, we asked users to merge the different versions of the same model using DSE Merge when compared to using Diff Merge. The experiment showed that to use DSE Merge participant required lower cognitive effort, and expressed their preference and satisfaction with it.

Software reuse is a broadly accepted practice to improve software development quality and productivity. Although an object of study in software engineering since the late sixties, achieving effective reuse remains challenging for many software development organizations. This paper reports a systematic mapping study on how reusability relates to other non-functional requirements and how different contextual factors influence the success of a reuse initiative. The conclusion is that the relationships are discussed rather informally, and that human, organizational, and technological domain factors are extremely relevant to a particular reuse context. This mapping study highlights the need for further research to better understand how exactly the different non-functional requirements and context factors affect reusability.