SERP4IoT'21 Workshop Report

We face a new software crisis. In 1968, computer scientists learned that developing robust software requires skills, methods, and tools. Today, software and hardware engineers realize that developing a robust Internet of Things (IoT) also pushes the states of their art and practice. Recent news illustrate the many problems faced by IoT: from lack of interoperability to broken updates to massive security attacks. In this context, the 3rd International Workshop on Software Engineering Research and Practices for the Internet of Things (SERP4IoT) aims to provide a highly interactive forum for researchers and practitioners to address the challenges of, nd solutions for, and share experiences with the development, release, and testing of robust software for IoT systems.

Modern Technologies of Designing Automation Systems

The paper presents the currently used techniques for the development of the automation control systems. It begins with the introduction of the concepts used in software engineering: software crisis, software disaster, and software life cycle. The subsequent chapters extend the latter by including the most popular software development models. Then, based on the V model, the role of verification and validation in the software and controller life cycle is presented, and the test techniques used in the controller validation are given. These test types include: software in the loop, processor in the loop, and controller in the loop. The last chapter describes the technique of designing automation systems based on the advanced mathematical models Model-Based Design.

Crisis Response and Management

Information technology is critically dependent on a number of technological and human factors. Software engineering processes are multi-sided; they include customer and developer parties. Conceptual misunderstanding by either party often results in the products which do not meet customer's expectations. This misconception of the software product scope usually leads to a crisis of software product delivery. To adequately manage and efficiently respond to this crisis, the authors recommend using software engineering models, methods, techniques, practices, and tools. Software engineering is a discipline which started in the 1960s as a response to the so-called “software crisis”; it combines technical and human-related skills. To manage the crisis, the authors suggest architecture patterns and instantiate them by implementation examples.

The 100 Year Web: In Praise of XML

It’s about sixty years since the start of public computing; fifty years since the term “software crisis” was coined; Europe is celebrating thirty years of the internet this year; and we’re celebrating twenty years of XML this year too. It is a milestone year for XML, and an important juncture as well. The last W3C XML WG has finished its work. What next? Where should we be heading, what do we want to achieve next, and how should we do it?

Ten Years of Experience with Agile and Model-Driven Software Development in a Legacy Platform

In this chapter, a report containing the author's many years of experience in software development together with a discussion of software engineering are presented. The report begins with the software crisis and includes different projects following the traditional waterfall model with heavy documents. In a re-engineering project of a legacy IT system by modernizing COBOL applications, we established an agile and model driven approach to software development. This approach which has been successfully applied in 13 projects since 2004 is presented. The key factors required for our success will also be discussed. Both the good and bad experiences of the last ten years will be summarized. The chapter will be finalized with a vision of a new architecture for agile software development.