• Volume 17,Issue 6,2006 Table of Contents
    Select All
    Display Type: |
    • >Special Issue's Articles
    • Preface of Special Issue on Software Architecture

      2006, 17(6):1255-1256.

      Abstract (8579) HTML (0) PDF 120.25 K (8352) Comment (0) Favorites

      Abstract:

    • Progress of Research on Software Architecture

      2006, 17(6):1257-1275.

      Abstract (11580) HTML (0) PDF 926.08 K (16088) Comment (0) Favorites

      Abstract:As an important means to control the complexity of software systems, to improve software quality and to support software development and software reuse, software architecture has become a mainstream research field in the software engineering community. Now, software architecture research not only focuses on the design phase, but also covers every phase of software lifecycle. This paper surveys the update-to-date research and practice of software architecture from a software lifecycle’s perspective, and discusses the potential research directions of software architecture.

    • Study on Behavioral Compatibility of Components in Software Architecture Using Object-Oriented Paradigm

      2006, 17(6):1276-1286.

      Abstract (8051) HTML (0) PDF 812.15 K (10991) Comment (0) Favorites

      Abstract:Software architecture (SA) provides a high-level abstraction for component-based software development. It’s important to specify the interaction behavior of the components, verify the compatibility among the components, and ensure the deadlock-freedom of the composition configuration at the architectural level. Many component-based software architectures are using object-oriented paradigm, in which component composition is implemented by method invocations over component interfaces. Concentrating on the component composition in this kind of SA, this paper formally specifies the components and their interaction behaviors, distinguishes the caller’s behavior from the callee’s in interaction, and then presents a set of rules to verify the behavioral compatibility on the interfaces between the components composed together. Finally, an example of e-commerce application is presented to illustrate the feasibility and pertinence of the approach.

    • Formal Semantic of Architecture-Centric Component Model

      2006, 17(6):1287-1297.

      Abstract (8049) HTML (0) PDF 745.01 K (9524) Comment (0) Favorites

      Abstract:Existing software development approaches construct component model in an unstructured and informal way, and the dependencies among components are implicit and lack rigorous semantic. They don’t support top-down component reuse effectively. This paper tries to address these problems by using category theory to define the links between components, so that the links between components and the link compositions have rigorous meaning. The morphism composition is used to trace the relationships between components at different abstraction levels, and the architecture design pattern is used to define component composition and constrains precisely. Category theory supports the diagrammatic representation of component model that visualizes the relationships between components and the structural feature. The constructed component model is understandable, traceable, and hence reusable. Formal component modeling approach is suitable to the software development for reuse.

    • A Composite Reuse of Architectural Connectors Using Reflection

      2006, 17(6):1298-1306.

      Abstract (7688) HTML (0) PDF 544.26 K (8518) Comment (0) Favorites

      Abstract:A critical issue for complex software architecture design is the modeling and analysis of connectors. This paper argues for an approach to composite reuse of connectors based on reflection. To support this notion a set of mata-operations of connectors composition steming from the operations between processes in CSP have been identified, and the CSP semantics of composite connector are also provided. As it will be shown that it provides mechanisms for designing connectors in an incremental way, and can be analysed and checked automatically owing to the formal basis.

    • Feature Model and Component Semantics Based Conceptual Architecture Design

      2006, 17(6):1307-1317.

      Abstract (8821) HTML (0) PDF 651.67 K (9484) Comment (0) Favorites

      Abstract:DSSA (domain-specific software architecture) is essential for the development of applications in the same domain. Feature-based domain model makes the mapping from domain requirements to DSSA possible. In this paper, ontology is introduced as the representation basis for feature models, and feature ontology of a domain is also taken as the semantic description basis for business components in the domain. Then a feature model and component semantics based method for conceptual architecture design are proposed. Commonality, variability, binding time, structural relations, and dependencies are taken into account in the method. The component semantics act as the transition from feature to conceptual component design. The methods have been implemented in the ontology-based feature modeling tool and feature-based architecture development tool, and exhibit effective supports for domain development.

    • Modeling Patterns: A Method to Evaluate Non-Functional Attributes of Software Architectures

      2006, 17(6):1318-1327.

      Abstract (7683) HTML (0) PDF 529.06 K (9036) Comment (0) Favorites

      Abstract:The design of software architecture plays an important role in a software process. In the design phase, the non-functional feature evaluation of software architecture would contribute a lot in providing high quality software products. Modeling patterns, which is an extension of UML (unified modeling language), are brought forward for software non-functional feature evaluation in this paper. Furthermore, an example, in which modeling pattern “AvailabilityChain” is used to evaluate the availability of software architecture “1 Message Distributor—n Message Processors”, is given to illustrate the application of modeling patterns. Moreover, to support the application of modeling patterns, “Modeling Pattern Knowledge-Base”, in which modeling patterns and reference values of tags used by each modeling pattern are managed, is involved. UML-based Patterns and Modeling Pattern Knowledge base will simplify the evaluation of software architecture in the software process and contribute a lot in providing high quality software products.

    • Architectural Level Performance Modeling of Component System Based on Container Middleware

      2006, 17(6):1328-1337.

      Abstract (7758) HTML (0) PDF 672.64 K (8818) Comment (0) Favorites

      Abstract:This paper analyzes the effect of Container style middleware on the structure and performance of Component-based system based on architectural patterns, and proposes an approach integrating Container style middleware components and their interaction relation into the application UML (unified modeling language) models. The performance model derived from the integrated UML models can reflect the impact of middleware. So, analysts do not have to know the internal details of middleware at performance modeling. The architectural pattern-based method can be extended to deal with various style middlewares. In the paper, the proposed approach is illustrated by a case study.

    • Research on Generic Adaptive Software Architecture Style

      2006, 17(6):1338-1348.

      Abstract (8710) HTML (0) PDF 507.86 K (10958) Comment (0) Favorites

      Abstract:The generic adaptive software architecture style is studied. Through the analysis of the basic characteristics of adaptive software architecture, the generic framework for adaptive software architecture is extracted. The integrated reference model of adaptive software architecture (ASA-IRM) is proposed based on multiview modelling theory. The rules of model mapping and evolution in ASA-IRM are discussed. The algorithm of model mapping consistency is proposed based on metamodelling and graph transformation theories. Finally, an integrated support environment for ASA-IRM is developed. The adaptive software architecture can be used in the development of complex software system, especially in open