A Comunicação Não-Verbal: especial relevância à função espaço-território da (comunicação) proxémica"

Aristotle said "Man is a social animal," that does not know how to live isolated and need interaction with their peers. Over several millenniums the man was found many ways to communicate – from smoke signals to sign language or even writing – and this need not slowed down over the years, instead of this, became increasingly glaring. Communication has become increasingly imperative in our lives. But the communication has long ceased to be seen merely as a transmission of words. Nowadays, in the today's society, the man relates to others through two levels: verbal and non-verbal. These two dimensions of communication arise often together, completing or in opposition to, even if the human being does not realize it. Proxemics, as one of the areas covered in Non-Verbal Communication is responsible for studying the distances and proximities that are between people and spaces and how each of us do to protect and defend their personal territory. Will be the Gender, Age, Profession or the Barriers to Communication able to significantly influence the proxemic? The present study will answer to these questions.

The GUISurfer tool: towards a language independent approach to reverse engineering GUI code

Graphical user interfaces (GUIs) are critical components of today's software. Developers are dedicating a larger portion of code to implementing them. Given their increased importance, correctness of GUIs code is becoming essential. This paper describes the latest results in the development of GUISurfer, a tool to reverse engineer the GUI layer of interactive computing systems. The ultimate goal of the tool is to enable analysis of interactive system from source code.

Domain-Specific Language for Coordination patterns

The integration and composition of software systems requires a good architectural design phase to speed up communications between (remote) components. However, during implementation phase, the code to coordinate such components often ends up mixed in the main business code. This leads to maintenance problems, raising the need for, on the one hand, separating the coordination code from the business code, and on the other hand, providing mechanisms for analysis and comprehension of the architectural decisions once made. In this context our aim is at developing a domain-specific language, CoordL, to describe typical coordination patterns. From our point of view, coordination patterns are abstractions, in a graph form, over the composition of coordination statements from the system code. These patterns would allow us to identify, by means of pattern-based graph search strategies, the code responsible for the coordination of the several components in a system. The recovering and separation of the architectural decisions for a better comprehension of the software is the main purpose of this pattern language