Architectural prototyping: from CCS to .Net

Over the last decade, software architecture emerged as a critical issue in Software Engineering. This encompassed a shift from traditional programming towards software development based on the deployment and assembly of independent components. The specification of both the overall systems structure and the interaction patterns between their components became a major concern for the working developer. Although a number of formalisms to express behaviour and to supply the indispensable calculational power to reason about designs, are available, the task of deriving architectural designs on top of popular component platforms has remained largely informal. This paper introduces a systematic approach to derive, from CCS behavioural specifications the corresponding architectural skeletons in the Microsoft .Net framework, in the form of executable C and Cω code. The prototyping process is fully supported by a specific tool developed in Haskell

Slicing for architectural analysis

Current software development often relies on non-trivial coordination logic for combining autonomous services, eventually running on different platforms. As a rule, however, such a coordination layer is strongly woven within the application at source code level. Therefore, its precise identification becomes a major methodological (and technical) problem and a challenge to any program understanding or refactoring process. The approach introduced in this paper resorts to slicing techniques to extract coordination data from source code. Such data are captured in a specific dependency graph structure from which a coordination model can be recovered either in the form of an Orc specification or as a collection of code fragments corresponding to the identification of typical coordination patterns in the system. Tool support is also discussed

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

The role of coordination analysis in software integration projects

What sort of component coordination strategies emerge in a software integration process? How can such strategies be discovered and further analysed? How close are they to the coordination component of the envisaged architectural model which was supposed to guide the integration process? This paper introduces a framework in which such questions can be discussed and illustrates its use by describing part of a real case-study. The approach is based on a methodology which enables semi-automatic discovery of coordination patterns from source code, combining generalized slicing techniques and graph manipulation

Prototyping Concurrent Systems in Cw

Software architecture is currently recognized as one of the most critical design steps in Software Engineering. The specification of the overall system structure, on the one hand, and of the interactions patterns between its components, on the other, became a major concern for the working developer. Although a number of formalisms to express behaviour and supply the indispensable calculational power to reason about designs, are available, the task of deriving architectural designs on top of popular component platforms has remained largely informal. This paper introduces a systematic approach to derive, from behavioural specifications written in Cw, the corresponding architectural skeletons in the Microsoft .NET framework in the form of executable code

Prototyping Behavioural Specifications in the.NET framework

Over the last decade, software architecture emerged as a critical design step in Software Engineering. This encompassed a shift from traditional programming towards the deployment and assembly of independent components. The specification of the overall system structure, on the one hand, and of the interactions patterns between its components, on the other, became a major concern for the working developer. Although a number of formalisms to express behaviour and supply the indispensable calculational power to reason about designs, are available, the task of deriving architectural designs on top of popular component platforms has remained largely informal. This paper introduces a systematic approach to derive, from behavioural specifications written in Ccs, the corresponding architectural skeletons in the Microsoft .Net framework in the form of executable C] code. Such prototyping process is automated by means of a specific tool developed in Haskell

Tourists’ perceptions of world heritage destinations: the case of Guimarães

Guimarães is a world heritage site (UNESCO) since December 2001, and is hosting the European Capital of Culture (ECOC) in 2012. This paper examines the profile, destination image and motivations of tourists’ visiting Guimarães before the cultural event. Based on survey responses from 276 tourists, this study found that tourists arrived to Guimarães came from the two most important cities in the northern part of Portugal (Porto and Braga). They are relatively young and well educated compared with the average tourists that visited Portugal. The results suggest that many tourists are aware of the city status as a world heritage site encompassing a historic centre, monuments, and architectural buildings. Further, these perceptions shape the image of Guimarães, as the factor analysis indicates that “historical background and functionality” is the most reliable and valid factor behind the choice of visiting the city. Finally, the main tourists’ motivation to choose Guimarães as theirs destination is educational, rather than recreational as they want to live a learning experience.

Tourists’ perceptions of world heritage destinations: The case of Guimarães (Portugal)

Guimara˜es is a UNESCO world heritage site, deemed as such in 2001 and hosted the 2012 European Capital of Culture. This paper examines the profile, destination image, and motivations of tourists’ visiting behaviors in Guimara˜es before the cultural event. Based on survey responses from 276 tourists, we found that tourists arriving in Guimara˜es had previously visited the two most important cities in the northern part of Portugal. These respondents were relatively young and well educated compared to the average tourists that visited Portugal. The results suggest that many tourists were aware of the city status as a world heritage site that encompasses a historic center, monuments, and architectural buildings. Furthermore, these perceptions shape the image of Guimara˜es, as the factor analysis indicates that ‘‘historical background and functionality’’ was the most reliable and valid factor behind the choice of visiting the city.