Emotion mechanisms are often used to perform roles in artificial agents with the aim of improving task performance. A basis for making comparisons between these agents is proposed, in the form of a framework constructed from an analysis of architectural qualities (the agent architecture, the action selection mechanism, and the emotion mechanism along with the emotion model it was based on). Thi...

Complex software systems require expressive notations fo their software architectures. Two competing paths have emerged. O specialized notation for architecture – or architecture description lan The other is to adapt a general-purpose modeling notation, such as U has a number of benefits, including familiarity to developers, close m plementations, and commercial tool support. However, it remain...

Aim of the paper is the study of how architectural representation changed in the digital age, focusing the relationship between the two following opposing aspects: on one hand the idea of progressive loss of any referentiality with the real world—as suggested by the concept of “Hypereality” defined by Baudrillard at the end of the Seventies, i.e., a simulated reality more real of reality; on th...

The architectural aspects of software systems are not always explicitly exposed to customers when a product is presented to them by software vendors. Therefore, customers might be put at a major risk if new emerging business needs come to light that require modification of some of the core business processes within their organizations. So they might need to replace their existing systems or re-...

C&C and deployment are base views for describing software architectures. Both views typically exist of several models that highlight particular aspects of the software. From our experience, managing the dependencies between architectural models is a challenging, yet crucial task for maintaining consistency of an architectural description. In this paper, we focus on the composition of architectu...

Changes and evolution of software systems constantly generate new challenges for the recovery of software systems architectures. A system’s architecture, together with its elements and the way they interact, constitute valuable assets for understanding the system. We believe that offering multiple architectural views of a given system, using domain and pattern knowledge enhance understanding of...

Complex software systems require expressive notations for representing their software architectures. Two competing paths have emerged. One is to use a specialized notation for architecture, an architecture description language (ADL). The other is to adapt a general-purpose modeling notation, such as UML. The latter has a number of benefits, including familiarity to developers, close mapping to ...

Assurance Based Development (ABD) is an approach to the construction of critical computing systems in which the system and an argument that it meets its assurance goals are developed simultaneously. ABD touches all aspects of the system lifecycle, but in this paper we focus on how the evolving assurance argument can guide architectural choices to increase system dependability. The goals with th...

The architectural aspects of software systems are not typically explained to customers when a product is presented by respective vendors. One immediate downfall customers are likely to encounter emerges when new business needs necessitate modification of the core business processes within their organizations. In some cases, executives are forced to replace the entire systems or re-architect old...