The component's interaction points with the external world play a fundamental role in the specification of an application's architecture. Current software architecture approaches consider an interaction point ...
详细信息
The component's interaction points with the external world play a fundamental role in the specification of an application's architecture. Current software architecture approaches consider an interaction point as an atomic element in the specification of interconnections, despite the complexity of its structure and the attached behavior. It is not possible in current component models to deal separately with an element of an interaction point when such an element is needed alone for specifying a specific logic. To support such logic and the specification of a wide range of early ideas in the process of elaborating a software system, the Integrated Approach to Software Architecture (IASA) uses an interaction point model which provides facilities to manipulate any structural or behavioral element defining an interaction point. In addition, such facilities represent the fundamental foundation of the native support by IASA of Aspect Oriented Software Architectures (AOSA) specifications. (C) 2010 Elsevier Inc. All rights reserved.
Without rigorous software development and maintenance, software tends to lose its original architectural structure and become difficult to understand and modify. archjava, a recently proposed programming language whic...
详细信息
Without rigorous software development and maintenance, software tends to lose its original architectural structure and become difficult to understand and modify. archjava, a recently proposed programming language which embeds a component-and-connector architectural specification within Java implementation code, offers the promise of preventing the loss of architectural structure. AliasJava, which can be used in conjunction with archjava, is an annotation system that extends Java to express how data is confined within, passed among, or shared between components and objects in a software system. We describe a case study in which we incrementally re-engineer an existing Java implementation to obtain an implementation which enforces the architectural control flow and data sharing. Building on results from similar case studies, we chose an application consisting of over 16,000 source lines of Java code and over 90 classes. We describe our process, the detailed steps involved (some of which can be automated), as well as some lessons learned and perceived limitations with the languages, techniques and tools we used. (C) 2006 Elsevier Inc. All rights reserved.
暂无评论