As the demand for more capable and more feature-rich software increases, the complexity in design, implementation and maintenance also increases exponentially. This becomes a problem when the complexity prevents developers from writing, improving, fixing or otherwise maintaining software to meet specified demands whilst still reaching an acceptable level of robustness. When complexity becomes t...

Reactive applications is a wide class of software that responds to user input, network messages, and other events. Recent research on reactive languages successfully addresses the drawbacks of the Observer pattern – the traditional way reactive applications are implemented in the object-oriented setting – by introducing time-changing values and other ad-hoc programming abstractions. However, th...

Software analysis pattern is an approach of software reuse which provides a way to reuse expertise that can be used across domains at early level of development. Developing software for a mobile robot system involves multi-disciplines expert knowledge which includes embedded systems, real-time software issues, control theories and artificial intelligence aspects. This paper focuses on analysis ...

Many distributed software systems are communication-centric: they are composed of heterogeneous software artifacts that interact following precise communication structures (protocols). One much-studied approach to system analysis equips process calculi with behavioral types (such as session types) so to abstract protocols and verify interacting programs. Unfortunately, existing behaviorally typ...

Automatic generation of correct software from requirements has long been a “holy grail” for system and software development. According to this vision, instead of implementing a system and then working hard to apply testing and verification methods to prove system correctness, a system is rather built correctly by construction. This problem, referred to as synthesis, is undecidable in the genera...

We propose a reactive approach for handling a wide variety of software failures, ranging from remotely exploitable vulnerabilities to more mundane bugs that cause abnormal program termination (e.g., illegal memory dereference) or other recognizable bad behavior (e.g., computational denial of service). Our emphasis is in creating “self-healing” software that can protect itself against a recurrin...

We discuss our experience with linking (existing) reactive applications to X11 based graphical user interfaces. For implementing the user interface we choose to use the Tcl/Tk toolkit, whereas the application itself may be written in any language (even a declarative one) that provides means to perform primitive I/O. The application and the graphical user interface run as separate processes and ...