Background: Several methodologies have been proposed since the first days of software development, from what is now named traditional/heavy methodologies, and later their counterpart, the agile methodologies. The whole idea behind agile methodologies is to produce software at a faster pace than what was considered with plan-based methodologies, which had a greater focus on documenting all tasks and activities before starting the proper software development. Problem: One issue here is that strict agilists are often against fully documenting the software architecture in the first phases of a software process development. However, architectural documentation cannot be neglected, given the well-known importance of software architecture to the success of a software project. Proposed Solution: In this article, we describe the past and current situation of agile methodologies and their relation to architecture description, as well as guidelines for future Agile Methodologies and Architecture Reconciliation. Method: We propose a literature review to understand how agile methodologies and architecture reconciliation can help in providing trends towards the success of a software project and supporting software development at a faster pace. This work was grounded in General Systems Theory as we describe the past, present, and future trends for rapid systems development through the integration of organizations, stakeholders, processes, and systems for software development. Summary of results: As extensively discussed in the literature, we found that there is a false dichotomy between agility and software architecture, and then we describe guidelines for future trends in agile methodologies and reconciliation of architecture to document agile architectures with both architectural decisions and agile processes for any system, as well as future trends to support organizations, stakeholders, processes, and systems.

The purpose of this paper is to model and analyze road intersection traffic signals by means of Petri nets and Linear Logic. The dynamic behavior of traffic signals is a discrete model. Several approaches have been applied to model and analyze traffic signals control, such as Petri nets. The Petri net formalism can be used to model an intersection that can be represented as a shared resource. Normally, the reachability tree is used to analyze the model in order to evaluate some good properties, such as absence of deadlocks and the return to the initial phase. The problem of this approach is the possibility of state-space explosion due to the high number of states that can be reached. The purpose of this paper is to model and formally analyze the good properties of traffic signals controlling a road intersection. A formal proof based on the sequent calculus of Linear Logic is done in order to analyze the properties of the model for a given scenario. The approach can prove that unsafe states, such as two greens in a shared road intersection, are not reached. This is done using the equivalence between Petri nets reachability and the proof of a set of sequents in Linear Logic.

This paper describes an approach to road network monitoring. The approach has the following main components: a multi-agent hierarchical monitoring system in which the agents are network elements such as crossings, road segments and routes, software engineering techniques to handle legacy sensors and to homogenise their heterogeneous data streams, distributed Kalman filtering to reduce sensor noise, and a traffic simulation model to help in predicting future traffic states and to replace missing physical sensors. The approach has resulted in a real-life test bed for network performance monitoring in which various configurations of agents and various ways of distributed Kalman filtering can be tested. The current, still rather simple monitoring configuration, is already in operational use for traffic management.